73% of my context switches last year traced back to a single root cause — not bad habits, not weak discipline, but a Notion dashboard that mixed ad ops client work with content publishing in the same view.
I run two genuinely different businesses. One is reactive: client Slack pings, campaign pacing, Meta and Google platform alerts. The other is slow and accumulative: SEO content, internal tooling, long-horizon experiments. For months I treated them as one organism inside one workspace. I even built a unified "Today" dashboard I was proud of — filtered views from both businesses, a single command center. What it actually did was guarantee the most urgent ad ops ticket was always sitting next to the most important content task. Urgency won every time. I tracked interruptions for six weeks to confirm I wasn't imagining it. I wasn't.
The fix that actually moved the needle wasn't a new tool — it was hard namespace separation. Two top-level Notion page trees with zero cross-links between them. No shared databases, no cross-references. Ad ops contractors can't see the content root; content collaborators can't see ad ops. Sounds obvious. I ignored it for four months because the shared setup felt "efficient." What it really did was create accidental visibility — a contractor would spot something from the content side, ask about it, and that was 20 minutes gone before I'd even started the task I opened Notion for.
The second shift was moving all drafting out of Notion entirely into Obsidian. Notion is good at structured status tracking. It is genuinely bad for thinking — the database UI creates a false sense of progress. A row exists, therefore work is happening. Moving first drafts to Obsidian and only syncing final status back to Notion cut my half-finished project count from 22 down to 8 in two months. That number surprised me more than anything else in 18 months of running this.
I wrote up the full breakdown — including the specific Notion properties I use in each business, how I handle the two categories that legitimately touch both sides (invoicing and contractor comms), and the CRM decision that goes against the standard "one master CRM" advice — over on dailyfocusmag.com.
Top comments (0)