Not all delays are the same.
A task waiting on legal approval isn’t blocked—it’s in a waiting state. A task that needs a missing dependency to proceed is actually blocked. These distinctions matter.
Why? Because treating “waiting” as “blocked” distorts your workflow. It hides the real problem areas and makes it harder to optimise the system. It also encourages teams to wash their hands of responsibility—“It’s in blocked, so it’s not on me.”
A better approach? Make the source of delay explicit. Use tags, highlight blockers visually, and—most importantly—track how long work sits idle. The goal isn’t just to know something is blocked; it’s to fix the systemic issue behind it.
How does your team make these distinctions visible?
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.
Qualco
Milliman
Healthgrades
ProgramUtvikling
Hubtel Ghana
Schlumberger
Trayport
Xceptor - Process and Data Automation
Alignment Healthcare
Flowmaster (a Mentor Graphics Company)
Emerson Process Management
Boeing
Sage
Microsoft
Akaditi
Kongsberg Maritime
YearUp.org
Jack Links
Nottingham County Council
Royal Air Force
Department of Work and Pensions (UK)
Washington Department of Enterprise Services
Washington Department of Transport
New Hampshire Supreme Court
Jack Links
Boxit Document Solutions
Schlumberger
New Signature
Healthgrades
Deliotte