What does it mean that first capture, then organize?

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.

Example: You're in a 1:1 with your CTO and she mentions a pattern — microservices that share a database are creating coupling your team hasn't 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've 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.

Try this: For the next 48 hours, run a split experiment. Keep two columns on a sheet of paper: LEFT column is 'Capture' (write thoughts the instant they arrive, no formatting, no categorization). RIGHT column is 'Organize' (once per day, spend 10 minutes reviewing left-column items and deciding where each one belongs). At the end of 48 hours, count: How many items did you capture? How many survived into your system? Compare this to your normal process. The difference is your current information loss rate.