34 tagged decision notes. That's all it took to realize my Notion database was lying to me.
I run three revenue streams — ad ops automation, two niche content sites, and a CRM sync product still in beta. A year and a half ago I built a "second brain" across Notion and Obsidian with one rule: everything touching a client or a revenue line gets captured. Last month I ran my annual review. The numbers were interesting. The process was more interesting.
Here's the thing nobody says about Notion: the rows tell you what happened, not why you believed it was the right call. I had a row that said "paused client X" with a date stamp. That row is useless during a retrospective. It tells me nothing about whether I paused for good reasons or bad ones. Meanwhile, I had a note in Obsidian — written the night I took on a fourth ad ops client — with the actual reasoning: the revenue upside I was chasing, the risk I knew existed, and the part I consciously chose to underweight. That context is irreplaceable. The Notion row is noise.
I spent six months trying to fix this by building a Decision Log database in Notion — fields for context, alternatives, outcome, the works. I updated it eight times in six months. The problem isn't discipline. The interface is too formal for mid-thought capture. By the time I'd opened a new record and filled in the fields, the thinking had already collapsed into a conclusion. An Obsidian daily note with a #decision tag takes 90 seconds. The Notion database took 10 minutes per entry and the quality was worse. I killed it in month seven.
