Aglet

Turn Solution Comparisons Into Better Product Choices

Alternative comparison teaches the team where solution enthusiasm can narrow discovery. Save the paths, outcome comparison, user and operational evidence, and reason a non-build option was deferred or retained. Use the case to make future choices deliberate without requiring a large strategy exercise.

Keep the lesson for the next incident

  1. Capture the choice story

    Keep the problem frame, alternatives, changed journeys, evidence, counterexample, and final decision together. Include a path that looked cheaper but shifted burden to users or staff. The record should show the tradeoff, not only the chosen design.

  2. Improve option review

    Add a shared outcome, non-build option, reversibility, and affected-party check to solution briefs. Require a small comparison before a major commitment. Explain how the change addresses the premature narrowing in the comparison.

  3. Watch for feature lock-in

    Set a signal such as one named feature in every proposal, missing current-state evidence, or options compared only by interface preference. Assign an owner to review proposals and revisit the practice when the signal returns.

What to carry forward

The learning record should connect the selected path to evidence, tradeoffs, changed review practice, and recurrence signal. State what the team will compare next time. Keep the decision revisable when user outcomes or constraints change.

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