Decide where the work belongs
Measure the blocked outcome
Describe which customer, release, operational, or decision outcome cannot progress and how reversible the delay is. Record affected scope and evidence freshness without treating elapsed time alone as severity. Tie urgency to the outcome waiting on the handoff, not to the existence of a waiting message.
Evaluate unblock leverage
Estimate whether one decision, artifact, access grant, or dependency response would release multiple paths. Compare that action with a workaround or scope split, and state what remains blocked after each option.
Set the unblock queue
Choose a priority, responsible role, expected response point, and escalation trigger. Keep the receiving team’s next action visible so a completed unblock does not become another silent handoff. Record what becomes unblocked when the selected action succeeds.
What to carry forward
The output is a queue decision tied to blocked impact, unblock leverage, workaround, and time sensitivity. Stop when the next action and escalation trigger are owned; if leverage is uncertain, prioritize a bounded dependency check rather than broad coordination work.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow