Write blockers as 'I cannot [action] because [obstacle]'…
Write blockers in the form 'I cannot [specific action] because [specific obstacle]' immediately upon noticing friction to convert ill-structured problems into solvable ones.
When This Fires
- When you notice yourself stuck, spinning, or avoiding a task
- When progress on a task stalls and you can't identify why
- During any work session where friction appears and you're tempted to switch tasks
- As part of a daily or weekly review to clear accumulated blockers
Common Failure Mode
Writing vague blockers: "I cannot move forward because this is hard." Neither the action nor the obstacle is specific enough to act on. The action must be something you could do in the next 30 minutes if the obstacle were removed. The obstacle must be something you could address, ask about, or work around.
The Protocol
When you notice friction or stuckness: (1) Write: "I cannot [specific action I'm trying to take] because [specific obstacle preventing it]." (2) Read it back. Is the action specific enough to attempt right now? Is the obstacle specific enough to address? If either is vague → narrow further. (3) The obstacle is now your next action: resolve it (learn, ask, find), work around it, or escalate it. The format converted "I'm stuck" into "here's what I need to do next."