The lure of the “perfect system” is a powerful drug. There is a specific dopamine hit that comes with discovering a new tool—a Notion template with just the right database views, a minimalist markdown editor that promises “distraction-free” writing, or a complex Kanban board that makes a simple to-do list feel like a NASA mission control center. For a few hours, I’m not actually working; I’m preparing to work. And in my head, that preparation feels like the most important part of the process.

I’ve fallen into this loop more times than I care to admit. I start with a simple goal: “Write a few notes on a new project.” But then I realize my current notes are fragmented. I need a system. I spend the afternoon researching “Personal Knowledge Management” (PKM). I discover Zettelkasten. I spend an entire weekend learning how to link notes bidirectionally and setting up aliases. By Sunday evening, I’ve built a magnificent, interconnected web of knowledge, but I haven’t actually written a single sentence about the project.

It is a form of procrastination masquerading as efficiency. We call it optimizing the workflow, but usually, we are just avoiding the friction of the actual task. The real work—the deep thinking, the coding, the wrestling with a stubborn bug—is messy. It is slow. It doesn’t always fit into a neat Trello card or a color-coded tag.

Recently, I’ve been trying a different approach: the “dumb” method. If I have a thought, I write it in a plain .txt file. No tags, no fancy databases, no relational links—just a cursor and a blank screen. There is a strange, grounding comfort in the lack of options. When the tool doesn’t offer a way to “organize” the thought, the only way to make the thought useful is to actually finish it.

I suspect the most productive people aren’t the ones with the most sophisticated setups. They are the ones who have a high tolerance for a little bit of digital chaos in exchange for a lot of actual output. The tool should be a transparent window to the work, not the work itself.