Planet RoadmapA blocker is anything that prevents a team member from making progress on their work. Left unresolved, a single blocker can cascade through a project, delaying dependent tasks and blowing timelines. The key is to surface blockers early, resolve them quickly, and build systems that prevent the same blockers from recurring.
Common Types of Blockers
Not all blockers are created equal. Understanding the type helps you choose the right resolution strategy.
- Technical blockers: a bug, architectural limitation, or missing API that prevents progress
- Dependency blockers: waiting on another team, vendor, or approval
- Decision blockers: work stalled because nobody has made a required decision
- Resource blockers: not enough people, environments, or licenses to proceed
- Information blockers: unclear requirements or missing context
Surface Blockers Early
The worst blockers are the ones nobody talks about. Create a team culture where flagging a blocker is expected, not embarrassing. Daily standups should focus on blockers more than status updates. If someone says "I am blocked," the next question should be "who can help unblock this today?"
Your project board should have a clear way to mark items as blocked. A blocked label or status column makes these items visible to the whole team and to managers who can escalate.
Resolution Strategies
For dependency blockers, communicate urgency to the blocking team and agree on a date. For decision blockers, set a deadline for the decision and identify a fallback if the deadline passes. For technical blockers, timebox the investigation—if you cannot solve it in a day, escalate or find a workaround.
The most effective strategy is prevention. During sprint planning, explicitly ask: "What could block this task?" For each answer, define a mitigation plan before work starts.
Tracking Blockers Over Time
If the same type of blocker keeps appearing, you have a systemic problem. Track blockers in your project management tool and review them in retrospectives. Planet Roadmap lets you flag and track blocked items across your projects, making patterns visible so you can address root causes instead of firefighting the same issues every sprint.