The "Blocked" column - control or avoidance?
Many teams create a Blocked column with good intentions.
- It looks structured.
- It looks transparent.
- It feels responsible.
But do you know if in practice?
It often becomes a waiting room for accountability.
When something is hard, unclear, politically sensitive, or cross-team-dependent, we move it to Blocked.
And suddenly…
- It's no longer urgent.
- It's no longer owned.
- It's no longer pushed.
- It's "visible".
On paper, visibility improves - In reality, momentum dies.
Let's be honest.
Most blocked work isn't blocked by infrastructure.
It's blocked by:
- unclear ownership
- avoided escalation
- uncomfortable conversations
- dependency management no one truly owns
A column does not resolve friction.
It labels it.
The dangerous part?
"Blocked" can normalize waiting.
Teams start managing the board instead of resolving the constraint.
Work doesn't move because it was categorized.
Work moves because someone takes responsibility.
In mature delivery systems, blocked items are not parked.
They are actively managed.
The real question isn't:
"Do we need a blocked column?"
It's:
"Who wakes up every day thinking about unblocking?"
Visibility without ownership is decoration.
Control requires action.