Aglet

Verify a Product Problem Frame Before Building

A problem frame is ready for the next phase when it describes a real outcome and the evidence needed to reason about it. Verification tests the frame against current journeys, edge contexts, and known constraints. It also checks that the wording does not quietly smuggle in the requested implementation.

Check whether the outcome improved

  1. Set frame acceptance checks

    Require a named user situation, trigger, desired outcome, observed barrier, evidence links, and explicit exclusions. Add a check that the statement remains meaningful if the proposed feature is removed. Identify the context in which the frame is valid.

  2. Review across real cases

    Apply the frame to successful, failed, assisted, and workaround paths. Compare different user groups and service channels. Mark where the wording fits, where it needs qualification, and where a separate problem has been incorrectly folded into the same statement.

  3. Record what remains open

    State whether the frame is ready for solution exploration, needs another research round, or should be narrowed. Note policy, feasibility, or measurement questions separately. Keep the frame tied to evidence rather than treating stakeholder agreement as validation.

What to carry forward

The verification record should include acceptance checks, cases reviewed, exclusions, and open constraints. Approve the frame only for the contexts it describes. A verified problem frame supports exploration; it does not select a feature or establish that building is the only response.

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