Aglet

Turn Assumption Tests Into Discovery Practice

Learning from assumption testing is more useful than preserving a yes or no label. Record how the original belief was formed, what the test exposed, and which part of the team's reasoning changed. Then turn that lesson into a question, artifact, or review habit that fits future discovery work.

Keep the lesson for the next incident

  1. Preserve the reasoning trail

    Write the original belief, decision at risk, test design, and strongest counterexample beside the result. Keep participant context and raw observation links available. A short conclusion without the reasoning cannot teach a later team what to repeat.

  2. Change the working method

    Update the assumption template, research question bank, or review agenda with the lesson. For example, require a disconfirming observation or a context comparison before a belief receives high confidence. Explain why the change addresses the earlier blind spot.

  3. Set a recurrence signal

    Choose a future trigger such as a new solution request, a changed audience, or repeated reliance on the same workaround. Assign an owner and review point. Reopen the lesson when the trigger appears rather than treating the original test as permanent truth.

What to carry forward

The learning record should connect the original assumption to the observed counterevidence, changed practice, and recurrence trigger. State whether the team kept, revised, or retired the belief. Keep the lesson revisable when user context, product scope, or evidence quality changes.

Technical background: GOV.UK user 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