Aglet

Resolve a feedback priority disagreement with evidence

Priority disagreement often reflects different weights rather than different facts. Prioritization should expose the weights, test the strongest assumptions, and record why one queue position wins while preserving a credible alternative and revisit trigger. A queue decision is stronger when reviewers can see which weight or fact changed the rank.

Decide where the work belongs

  1. Build a shared comparison

    Place the request beside nearby queue items and compare reach, severity, urgency, confidence, effort, reversibility, and strategic fit. Use the same evidence basis for each dimension and note where estimates are unavailable.

  2. Test the deciding assumption

    Identify the assumption that most changes the ranking, then seek the smallest evidence that can confirm or narrow it. If the disagreement is a value choice, label it as a policy or product judgment rather than a factual gap.

  3. Record the queue rationale

    Select a position, decision owner, and review trigger. State the tradeoff in plain language, including what the chosen position delays. Keep the alternate rationale linked so a future change can be understood without restarting the debate.

What to carry forward

The output is a ranked decision that explains evidence, weights, uncertainty, and opportunity cost. Stop when the decision rule is explicit and the owner accepts the revisit trigger; if evidence and values cannot be separated, record both instead of pretending a score settled them.

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