Why Using a Blocked Column in Azure DevOps Is a Mistake

TL;DR; Using a blocked column in Azure DevOps causes work to stall and be forgotten, rather than resolved. Instead, use a visible blocked tag and keep items in their active state to maintain focus and encourage action. Track blockages to address root causes and keep work moving.

Published on 20 February 2025

Written by Martin Hinshelwood

1 minute read

https://nkdagility.com/resources/H8CRQrD64JY

If your team is using a “Blocked” column in Azure DevOps, you’re probably doing it wrong.

Why? Because work doesn’t flow through blocked, it stops there. And once it’s there, it tends to stay there.

Instead of a blocked column, try this:

Use a Blocked tag on work items.
Colour-code the tag for visibility.
Keep blocked work in its active state on the board.
Track the frequency and causes of blockages.

This keeps the problem in sight while preventing blocked work from becoming a dumping ground. More importantly, it helps teams take action instead of waiting for work to magically resolve itself.

How does your team flag ‘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.