Execution
Table of Contents
A decision earns nothing until finished work lands, not when the slide deck or the intention is done.
Key Concept
- Execution turns a decision into finished work - not slides, intentions, or we will get to it later.
- Execution is the gap between deciding and delivered - plans earn nothing until work lands.
Level 1 - Recognize
Execution is turning a decision into finished work - not slides, intentions, or we will get to it later.
Level 2 - Explain
Close the tab marked decided - like naming the next physical action and doing it before you open another thread.
Level 3 - Use
Name the next physical action that finishes the decision and do it before you open another thread - discussed is not done.
Level 4 - Connect
Execution turns a decision into finished work - the standard is done, not discussed; pairs with Getting Things Done next-action clarity when the gap is task capture, not intent.
Level 5 - Create
Build an execution handoff that names the owner, next physical action, deadline, and proof of done so the decision can land without another meeting.
Examples
- Glad one neighbor showed up with gloves and a start time - our block cleanup had a group chat full of enthusiasm and no bags until then.
- The coach drew a beautiful play on the whiteboard - execution started when players were on the field and someone named who cuts where on the first whistle.
Note Relationships
| Relationship | Wikilink | Reason |
|---|---|---|
| contradicts | Slow Productivity | when rushing to “done” on six fronts beats finishing three properly |
| extends | Complete the Cycle | Execution includes follow-through, not only the first push |
| extends | Finish Strong | Done means the last step, not the kickoff |
| extends | Outcomes Over Pitch Decks | Fruit beats deck polish |
