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:
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?
If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.
We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.
Schlumberger
CR2
Lockheed Martin
Jack Links
Kongsberg Maritime
Slaughter and May
Akaditi
SuperControl
New Signature
Healthgrades
Cognizant Microsoft Business Group (MBG)
Boxit Document Solutions
NIT A/S
Epic Games
Brandes Investment Partners L.P.
YearUp.org
Lean SA
Flowmaster (a Mentor Graphics Company)
Ghana Police Service
New Hampshire Supreme Court
Washington Department of Enterprise Services
Royal Air Force
Nottingham County Council
Department of Work and Pensions (UK)
NIT A/S
Brandes Investment Partners L.P.
Illumina
Schlumberger
Bistech
Ericson