First capture, then organize

The idea

Capture and organization are separate cognitive operations. Merging them creates friction that kills both: you lose the thought while searching for where to put it.

You are standing at a whiteboard after a product review and three things collide in your head at once: a user complaint from last week, a technical constraint your team keeps hitting, and a design principle you read about months ago. For half a second, you see how they connect. It is the kind of insight that reframes a problem.

Then you reach for your notes app, and the question hits: _Where does this go?_

An example

You are in a 1:1 with your CTO and she mentions a pattern — microservices that share a database are creating coupling your team has not accounted for. You immediately think: 'That connects to the reliability issue from last sprint.' But instead of writing it down, you try to figure out where it belongs — is it an architecture note? A sprint retro item? A Slack message to the team? By the time you have mentally auditioned three destinations, the specific connection — the one that linked coupling to last sprint's outage — is gone. You remember the topic. You lost the insight.

Where it goes wrong

The failure is invisible and feels like good practice. You open your note app, have an idea, and pause to pick the right folder or tag. The pause feels responsible — organized, even. But during that pause, the thought simplifies. The original insight had three connected pieces; the version that survives your filing decision has one. You do not notice the loss because the simplified version still feels like the same thought. It is not.

Make it stick

Designate one single capture destination — a daily note, a physical inbox, a pinned note on your phone — and commit to putting everything there first. No tags, no folders, no decisions. Once per day, process the inbox: move items to their proper locations, add context, discard what is dead.