Capture actions as specific next physical steps (not "handle client project" but "email Sarah the revised timeline") — eliminate re-processing at execution time

Why This Is a Rule

A vague task on your list ("Handle client project") requires a second round of decision-making before you can act on it: "What does 'handle' mean? What's the first step? Who do I contact? What tool do I use?" This re-processing at execution time costs 2-5 minutes of deliberation per task and, more importantly, creates starting friction that makes the task feel harder than it is. The vagueness is a decision-barrier that your brain must overcome before any action occurs.

A specific next physical action ("Email Sarah the revised timeline by 3pm") requires no re-processing. You know exactly what to do: open email, type to Sarah, attach timeline, send. The action is immediately executable — you can begin without thinking about what "begin" means. David Allen's insight in GTD is that the cognitive work of clarifying "what does this mean and what's the first step?" should happen once during processing, not every time you look at your task list.

The "physical" qualifier is essential. "Decide about the proposal" isn't a physical action — it's a mental outcome that requires identifying the physical steps that lead to the decision. "Read the proposal PDF and write three bullet points of concerns" is physical — you can observe yourself doing it. Physical specificity eliminates the ambiguity that creates starting friction.

When This Fires

• When capturing any action item during inbox processing (Process inboxes sequentially top-to-bottom, never cherry-picking — skipping difficult items creates a permanent maybe pile, Route actionable items to your task system and reference items to your reference system — never store both in the same location)
• When reviewing your task list and finding items you keep skipping because they feel overwhelming
• When procrastination is present — often the cause is vague tasks that feel undoable
• Complements Competent stranger test for workflow steps — could someone complete this step with zero clarifying questions? If not, it is not yet atomic (competent stranger test) applied to self-assigned tasks

Common Failure Mode

Project-level task entries: "Website redesign," "Tax preparation," "Quarterly review." These aren't tasks — they're projects containing many tasks. Putting them on a task list guarantees they'll sit there unacted-upon because no single physical action can "do" them. Each needs to be decomposed into its current next physical action.

The Protocol

(1) For every action item, ask: "What is the very next physical thing I would do to move this forward?" (2) The answer should describe a visible, physical action: open, write, call, email, read, walk to, type, print. Not: think about, decide, handle, plan, consider. (3) Include specificity: who (email Sarah), what (the revised timeline), where (in the shared drive), when (by 3pm). The more specific, the less re-processing needed. (4) If you can't identify a clear next physical action, the item needs clarification first: "Spend 10 minutes brainstorming what 'handle client project' actually means" becomes the next action. (5) When a next action is completed, immediately define the new next action for the project. The project always has a current next physical action until it's complete.