Aglet

Prioritize Which Product Alternative to Explore

A familiar feature can crowd out a simpler process change or a deliberate deferment. Prioritize alternatives by the outcome they can improve and the uncertainty they can resolve. Make tradeoffs visible so the queue reflects user value rather than internal ownership alone.

Decide where the work belongs

  1. Compare user value

    Describe how each option changes the blocked outcome, effort, access, trust, or handoff. Identify which users gain and which may inherit work. Give weight to an option that addresses the barrier directly, even when it is less visually impressive.

  2. Assess feasibility and reversibility

    Review constraints, dependencies, maintenance, adoption, and ability to test or undo the path. Separate known limits from team preference. Record where a small exploration could answer a major uncertainty before a larger commitment.

  3. Choose an exploration queue

    Select an option, decision owner, evidence request, and review date. Defer paths whose assumptions are untested with a trigger. If the best choice depends on one question, prioritize that question before the solution.

What to carry forward

The priority output is an option queue with user outcome, affected parties, feasibility, reversibility, evidence gap, and review trigger. Explore the path whose learning can change the choice soonest. Keep a non-build option visible when it remains credible.

Technical background: IDEO research guidance.

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