Aglet

Investigate evidence behind a feedback priority dispute

Investigation should answer the factual questions beneath the disagreement and isolate the remaining judgment call. Reconstruct the evidence each position relies on, run bounded comparisons, and report where the queue still depends on values or incomplete information. Investigation should reduce factual disagreement before the team debates legitimate value choices.

Build a useful investigation brief

  1. Trace each position

    For every proposed rank, list the observations, assumptions, exclusions, and comparison item that support it. Check whether the parties used different time windows, duplicate handling, customer segments, or definitions of severity.

  2. Run the highest-value check

    Test the claim that most affects the ranking, such as a workflow failure rate, affected-role boundary, workaround cost, or recurrence. Record negative results and method limits; do not choose a test merely because it favors one position.

  3. Separate fact from judgment

    Write a brief with resolved facts, remaining uncertainty, and explicit product or risk judgment. Recommend a queue position or a follow-up decision meeting only after the evidence boundary is clear.

What to carry forward

A useful investigation narrows the dispute to verified facts and clearly labeled judgment. Stop when the disputed claim is answered enough for a queue decision; if evidence remains inconclusive, make uncertainty and the chosen risk tolerance visible.

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