Method ·
Capture First, Organize Later: The Inbox Method
The fastest way to lose an idea is to make it fill out a form before it is allowed to exist.
Ideas do not arrive on schedule. They arrive in the shower, mid-meeting, on the walk back from lunch, three minutes before sleep. And they leave just as abruptly. Working memory holds a thought for seconds; whatever capture system you use has roughly that long before the thought degrades or disappears.
Now count the questions a typical notes app asks before a thought is allowed to exist: Which notebook? Which folder? What title? Which tags? Each question is small. Together they form a toll booth, and the toll is paid in the currency you can least afford — the idea itself, half-evaporated while you were filing it.
Two Jobs That Should Never Share a Moment
The root mistake is treating capturing and organizing as one activity. They are opposites.
Capturing wants speed, zero ceremony, and tolerance for mess. Organizing wants judgment, context, and calm. Doing both at once means doing both badly: you either capture slowly because you are organizing, or you organize badly because you are rushing.
David Allen made this separation famous in Getting Things Done: everything goes into an inbox first, and a separate processing pass decides what each item means. The insight is not about productivity systems. It is about cognitive load — decisions deferred are attention preserved.
The Workflow, Concretely
Here is the loop as it works in an outliner like AnyMind. Give the inbox its own branch at the very top of the tree, apart from your projects — that separation is the whole trick:
- Capture (seconds). Zoom into the Inbox branch, press Enter, type the raw thought, stop. No title, no folder, no tags. Misspelled is fine. Fragmentary is fine. The only job is to get it out of your head before it dissolves.
- Triage (minutes, once or twice a day). Walk the inbox top to bottom. For each item, make one decision: act on it, move it into the tree where it belongs, expand it into a real note, or delete it. Moving a node is a drag or a couple of keystrokes — this is where outliners quietly beat every folder-based system, because "organizing" is just reshaping a tree, not filing documents.
- Execute (ongoing). Items that turned out to be actions get a
/todomarker and move into the project they serve, ready to be checked off in place. Items that turned out to be knowledge get nested under the topic they belong to. Items worth remembering forever get a review schedule.
The crucial property: the inbox is allowed to be ugly. It is a staging area, not a library. Mess there is not failure; it is the system working as designed.
Why the Inbox Must Be Separate
A common variant fails: people capture directly into their project notes "to save the triage step." Within a month, every project outline has a sediment layer of half-thoughts at the bottom, and opening any project means wading through its debris. The mess has colonized the library.
Keeping the Inbox branch physically separate from your projects protects both: capture stays guilt-free because it cannot pollute anything, and the tree stays trustworthy because everything in it was placed there by a deliberate decision.
The Compounding Effect
After a few weeks the loop changes your relationship with your own attention. You stop carrying open loops in your head, because the reflex "write it down, deal with it at triage" is faster and more reliable than remembering. Meetings get sharper. Deep work sessions stop being interrupted by your own brain offering errands.
And because triage happens inside the same tree where work lives, the captured material actually becomes structure — project plans, arguments, decisions — instead of rotting in a "quick notes" graveyard.
If you want to see the full daily rhythm built on this loop, the daily planning guide shows how capture, triage, and execution fit into a morning routine.