Blocked columns seem harmless, just another column to keep track of stalled work. But they aren’t harmless. They’re workflow kryptonite.
Here’s the problem: A column should represent a state that work naturally flows through. But if your team is routinely moving work into “Blocked,” it means getting stuck has become part of the process. That’s a serious issue.
What happens next? The work sits. The team assumes someone else will handle it. WIP limits inflate. Context gets lost. Tasks lose priority. Before you know it, the board is cluttered with forgotten work, and real progress is suffocating under the weight of “maybe someday.”
A better approach? Keep blocked work in its current column. Tag it, highlight it, raise the alarm, but never let it disappear into a column that signals “not my problem.”
How does your team surface and handle blocked work?
Smart Classifications
Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.
What to read next
Why Using a Blocked Column in Azure DevOps Is a Mistake
Explains why a “Blocked” column in Azure DevOps hinders workflow, and suggests using tags and tracking to manage blocked work more …
Blocked Columns on Kanban Boards Obfuscate Workflow and Undermine Effectiveness
Using Blocked columns on Kanban boards hides workflow issues, causes task stagnation, and reduces transparency. Use tags to indicate …
Not all delays are the same
Explains the difference between waiting and blocked tasks, why clear distinction matters in workflows, and how to track and address sources …
3 best ways to wreck Kanban. Sweep problems under the rug
Ignoring problems in Kanban leads to workflow blockages, technical debt, and crises. Learn why prompt issue resolution and transparency are …
Mastering Your Kanban Board: A Practical Guide to Visualising Workflows for Maximum Efficiency
Learn how to design and customise Kanban boards to visualise workflows, identify bottlenecks, and boost team efficiency through clear, …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Estimating Better in an Overloaded System Is a Poor Man’s Strategy
High work in progress (WIP) causes delays and unpredictability; improving estimates won’t help. Limiting WIP and focusing on flow is key to …
The Open Guide to Kanban: Unlocking Collaborative Flow and Real-World Value for Every Team
Unlock better flow and real value with the Open Guide to Kanban, a practical, community-driven resource for teams in any industry. Join the …
Why Measuring Individual Cycle Time Fails to Help Teams
Measuring individual cycle time overlooks team performance and system bottlenecks. Focus on lead time, throughput, and process efficiency to …
Why Tracking Individual Cycle Time Distorts Team Behaviour
Tracking individual cycle time can harm team performance by encouraging task cherry-picking, reduced collaboration, and lower quality, …