What does it mean that the two-minute rule for capture?

If processing an item takes less than two minutes, do it immediately — deferring it costs more than completing it.

Example: A developer captures a note during a meeting: 'Refactor auth middleware to use the new token format.' She looks at it during inbox processing. The actual change is three files and will take an hour. That gets deferred to her task list. The next item is a note that says 'Reply to Sasha — confirm Thursday demo time.' She could add it to her task list, tag it, set a due date, create a context label. Or she could pull up Slack, type 'Thursday works, 2pm?', and send it. Twelve seconds. The task is gone — not deferred, not tracked, not consuming a slot in working memory. She moves to the next item. By the end of her processing session, she has completed nine two-minute actions and deferred four substantial ones. Her task list is lean instead of bloated with trivia, and her mind is clear instead of tracking thirteen open loops.

Try this: Process your current inbox — email, notes app, physical papers, whatever contains unprocessed items. For each item, ask one question: 'Can I complete this in under two minutes?' If yes, do it immediately and move to the next item. If no, defer it (add it to your task list, calendar, or reference system). Track two numbers: (1) how many items you completed immediately, and (2) how many you deferred. Most people discover that 40-60% of their inbox items are two-minute actions they have been hoarding for days or weeks. Notice how your cognitive load shifts as you clear them.