Blocking reason
Also known as Blocker category, Blocked-work reason
Definition
A blocking reason is the classified cause attached to work that cannot proceed. Common classes include dependency, decision, environment, capacity, defect, and approval, but the useful taxonomy depends on the workflow.
Why the label matters
Counting blocked items without a reason produces a queue alarm but little guidance. A reason turns a delay into a hypothesis about the constraint. The taxonomy should be short enough to use consistently and specific enough to support action.
A concrete example
Suppose eight items are blocked: three await a product decision, two depend on a platform change, one needs test data, and two are waiting for a reviewer. Those groups suggest different responses. Adding more implementation capacity would not directly solve all four causes.
Design a useful taxonomy
Use mutually understandable labels, define when a block starts, and allow a free-text note for unusual cases. Review the taxonomy periodically. If most items are placed in “other,” the categories are not helping diagnosis.
Limitations
Reasons can be subjective, and one item can have multiple blockers over time. A single current label may hide that history. Preserve event-level detail when the decision requires knowing which obstacle consumed the most time.
How this relates to Weave
Weave can provide delivery and review context that helps teams validate whether a reported blocker corresponds with a measurable delay. It does not infer an authoritative cause from timestamps alone, so teams should maintain the reason in their operational workflow.
Explore Engineering intelligence