Managing Blocked Items

Overview

Blocked items represent work that cannot progress.

They require explicit unblock ownership and sequencing decisions.

Key Concepts

• Blocked status: explicit signal that work cannot proceed
• Unblock condition: what must happen to resume work
• Owner: Teammate accountable for progressing the item

How It’s Used

Use blocked-item reviews during governance meetings.

Use them during daily execution triage.

Benefits

• Faster escalation of risk
• Cleaner communication across teams
• Less hidden idle time in delivery plans

Setup Steps

1

Identify blocked work

1. Open Requirements or Tasks.
2. Filter for Status = Blocked (or equivalent field).
3. Save the view as a Save View for repeatable reviews.

2

Record unblock conditions

1. Open each blocked item.
2. Add a comment stating the unblock condition.
3. Add the accountable owner in the comment.

3

Clear blocked signals

1. Update dependencies when prerequisites are completed.
2. Update status from Blocked to the next valid status.
3. Record the reason for the change in a comment.

Best Practices

• Keep Blocked as a high-signal status.
• Require an unblock condition on every blocked item.
• Review blocked work at least weekly.

Summary

Blocked items should be visible and managed actively.

Save Views keep the blocked review repeatable.