Aglet

Triage a work dependency cycle before more delay

A dependency cycle is a coordination graph with no available next step. Triage should map the actual prerequisites, distinguish true dependencies from assumptions, and identify the smallest decision or scope change that can break the loop. The aim is one safe break point that changes the graph, not a new status for every waiting team.

Establish what is happening

  1. Draw the dependency chain

    List each work item, required output, responsible role, current state, and evidence that the dependency is real. Mark links based on sequencing, data, decision, access, or capacity, and remove merely related work from the cycle.

  2. Find the closed loop

    Trace prerequisites until the chain returns to an earlier item or reaches an authority with no next action. Verify both sides’ assumptions and identify any missing decision, interface, or temporary artifact that keeps the loop closed.

  3. Set a break point

    Choose a bounded scope split, ordering decision, temporary contract, or escalation to remove one edge. Assign the action and follow-up state, preserve the full cycle map, and state what remains blocked afterward.

What to carry forward

The output is a verified cycle map with a break point, responsible action, residual dependencies, and authority boundary. Stop triage when one safe edge can be removed; if no team can choose the break, escalate that decision instead of assigning parallel guesses.

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