Tasks
Review Blocked Work Before It Becomes a Crisis
Use a short review rhythm to identify blocked tasks, name the missing input, and decide the next escalation.
Blocked work needs a next move. Otherwise it becomes a quiet pile of unfinished promises.
Name the blocker precisely
Do not stop at “blocked.” Write what is missing: approval, data, access, reviewer time, a decision, a dependency, or a working file.
A precise blocker points to the person or action that can move the task forward.
Separate waiting from blocked
Waiting means the next step is known and someone else is expected to respond. Blocked means the owner cannot continue without intervention.
This distinction helps teams avoid escalating ordinary waiting while still acting quickly on real stuck work.
Escalate with context
When escalation is needed, include the task, the blocker, the impact, and the decision or help requested.
A good escalation makes it easy for a manager or stakeholder to act without asking for the entire project history.
Quick checklist
- Identify every blocked task.
- Name the missing input.
- Assign the person who can help.
- Record the impact.
- Choose the next escalation.
Guide FAQ
How should I adapt this guide for a small team?
Start with the checklist, assign one owner, and run the workflow for one week before adding extra fields or process steps.
Should this replace our project-management software?
No. These guides are designed to clarify lightweight workflows. They can support a larger tool, but they do not need to replace one.
What is the best first step?
Write the outcome you want, choose the smallest related template or checklist, and test it on one real workflow before scaling it.