Aglet

Prioritize Which Product Experiment to Run

When several experiments are possible, the fastest one is not always the most useful. Prioritize the experiment that resolves a risky product assumption with a meaningful observation and manageable exposure. Compare learning value with instrumentation, support, interpretation, and reversibility costs.

Decide where the work belongs

  1. Rank the unanswered bets

    List the product decisions each experiment could inform and the assumptions underneath them. Give weight to uncertainty that could reverse the roadmap, not only to outcomes that are easy to count. Note affected users and operational dependencies.

  2. Compare experiment quality

    Review treatment clarity, comparison integrity, sample access, observation time, and guardrail coverage. A polished metric with weak assignment or a short window should rank below a simpler design that answers the real question.

  3. Select a controlled next step

    Choose one experiment, define the preparation needed, and set a stop or review date. Defer ideas whose result would not change a decision. Document what evidence would move a deferred experiment ahead of the selected one.

What to carry forward

The priority output is an experiment queue with decision value, uncertainty, exposure, comparison quality, and preparation cost. Select the design that can change a meaningful decision within a bounded risk. Keep deferred experiments visible with explicit triggers rather than treating them as rejected ideas.

Technical background: IDEO design thinking 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