Understanding Blocked Columns and Stalled Work in Project Boards

TL;DR; Using a separate “Blocked” column on project boards makes stalled work seem normal, leading to forgotten tasks, inflated work-in-progress, and lost context. Instead, keep blocked items visible in their current workflow state and highlight or tag them so the team addresses issues quickly. Review your process to ensure blocked work is surfaced and resolved without becoming invisible.

Published on 4 March 2025

Written by Martin Hinshelwood

1 minute read

https://nkdagility.com/resources/6K6oGV9pRbC

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?

Also published on: LinkedIn

Connect with Martin Hinshelwood

If you've made it this far, it's worth a conversation. Tell us where you are and what you're trying to change. Martin reads every inquiry and replies personally.

Start the conversation

Our Happy Clients

We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.