Aglet

Prioritize repeatedly reopened work by outcome risk

Repeated reopening consumes attention and can signal real harm, but recurrence alone does not define urgency. Prioritization should weigh the remaining outcome risk and the evidence that prior closure was incomplete, then choose a repair, investigation, or closure-contract improvement. A recurring cycle deserves attention when it shows unresolved outcome risk, not only repeated status movement.

Decide where the work belongs

  1. Measure the unresolved risk

    Compare recurrence frequency, affected scope, consequence, workaround, and time since last closure. State which cycles are comparable and which represent new scope. Keep unknown exposure visible rather than multiplying reopen count into severity.

  2. Assess closure confidence

    Review the evidence used at each close and identify the weakest condition. Consider whether another implementation cycle, focused investigation, or acceptance clarification would reduce risk more than repeating the prior path.

  3. Set a priority and trigger

    Choose a queue position, owner, and revisit or verification trigger. State what would justify closure, escalation, splitting, or continued monitoring so another cycle does not start from an empty rationale.

What to carry forward

The output is a priority decision tied to remaining harm, recurrence comparability, closure confidence, and the next risk-reducing action. Stop when a meaningful closure condition exists; if scope is changing, prioritize a split rather than an endless reopen loop.

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