Organize actions by execution context…

When This Fires

• When organizing your task management system and choosing the primary grouping
• When you have free time in a specific context and don't know what to work on
• When project-based lists feel overwhelming because they mix executable and non-executable items
• Complements Capture actions as specific next physical steps… (next physical action) with the organizational system that makes those actions findable by context

Common Failure Mode

Over-contexting: creating 15 context lists for every possible location and tool combination. This defeats the purpose by making the system too complex to maintain. Most people need 4-6 contexts at most. The contexts should match your actual recurring execution environments, not every theoretically possible one.

The Protocol

(1) Define your 4-6 primary execution contexts based on where and how you actually work: @computer, @phone, @errands, @home, @office, @agenda (for discussions with specific people). (2) When capturing an action (Capture actions as specific next physical steps…), assign it to the context where it can be executed. "Email Sarah the timeline" → @computer. "Buy printer paper" → @errands. "Discuss budget with Mike" → @agenda-Mike. (3) When you have time to work, check the list for your current context. All items on that list are executable right now. (4) Maintain project lists separately for planning purposes, but use context lists for execution. The project list answers "What does this project need?" The context list answers "What can I do right now?" (5) Review and adjust contexts quarterly. If a context list is always empty or never checked, eliminate it.