I remember logging into a team’s board one morning, hoping to see some progress. But instead of a smooth flow of tasks, I was greeted by a “Blocked” column—stacked high with cards. It was a sign that something had gone very wrong.

The “Blocked” column might seem helpful at first glance. It highlights issues, sure, but it also creates a false sense of productivity. The work just sits there, piling up, while everyone moves on, as if identifying the problem is enough.

Why do teams create a “Blocked” column?

Because it’s easier than fixing the problem. It’s a way to avoid discomfort and shift responsibility. But here’s the truth: “Blocked” isn’t a workflow; it’s a red flag. It signals that something needs immediate attention, not a place to park problems.

The real danger of a “Blocked” column is that it hides the real issues. It becomes a crutch—a way to pretend progress is being made when it isn’t.

Instead of a “Blocked” column, teams should rally around blocked items. Address them in real-time, during daily stand-ups. Use simple visual cues like a red dot on the card to indicate a problem, but don’t let it linger. Move quickly to remove blockers and keep the work flowing.

Building a truly agile team means focusing on finding and solving problems, not shelving them. If something is blocked, it should be everyone’s priority to unblock it as soon as possible.

The “Blocked” column isn’t part of the solution; it’s part of the problem. Let’s stop using it as a hiding place and start dealing with the real work at hand.