Separate Planning From Execution
Directive 16: Separate Planning From Execution
Planning and execution require different cognitive modes. When they are mixed, neither works properly. Planning becomes endless analysis, and execution degrades into hesitation.
This directive enforces a hard boundary between deciding what to do and doing it.
The Core Principle
Planning ends before execution begins.
Once execution starts, no new decisions are allowed. All choices must be resolved in advance. This prevents mid‑task debate, scope creep, and loss of momentum.
A disciplined system treats execution as mechanical.
Why This Fails for Most People
Most people plan while executing. They revise goals, change methods, and reconsider priorities mid‑action.
Common failures include:
- Re‑planning during work
- Adjusting scope mid‑task
- Researching alternatives instead of executing
- Stopping to “think it through” again
This converts action time into disguised procrastination.
The Gyōji Directive
Do not plan while executing.
If new decisions are required, execution must stop and return to planning mode.
Implementation Protocol
- Schedule dedicated planning sessions.
- Resolve all decisions during planning.
- Document the execution plan.
- Execute without modification.
- Capture improvements only after execution ends.
Planning produces instructions. Execution follows them.
Common Errors
- Treating execution as flexible
- Allowing ideation during action
- Changing tools mid‑task
- Restarting planning to avoid difficulty
Enforcement Rule
If execution pauses to decide, the boundary has failed.
Final Order
Decide first. Execute without thought.