Learning AI · Practical guide

Test a product decision with one small journey.

Hands typing on a laptop keyboard.
Image: Glenn Carstens-Peters · CC0 1.0

Build a navigable mockup of supply requests to observe whether someone understands how to create and inspect a request, before implementing storage, permissions and integrations.

What you will find

  • Choose a question the prototype can answer
  • Represent states that affect the decision
  • Give a task without explaining the route
  • Turn findings into requirements

01Choose a question the prototype can answer

Example question: can someone find a request’s status without help? Prepare a list and a detail screen with three fictional records. You do not need to represent every future feature to observe this journey.

State what the exercise will not check: access security, real persistence or behaviour with thousands of records. Successful navigation does not establish those properties.

“Focus on testing your riskiest assumptions”

[1] GOV.UK Service Manual

02Represent states that affect the decision

Include a pending request, an approved one and a rejected one with a reason. Add an empty list to see whether starting is clear. Keep wording and states consistent between screens.

Label demonstration data and simulated actions. If save only changes the mockup, do not present it as a completed operation in a real system.

03Give a task without explaining the route

Ask: “Find out whether the notebook request was approved and what you can do next.” Observe clicks, interpretations and questions without pointing to the answer.

Record the precise confusion. “They do not understand” is less useful than “They look at the date for a decision because they do not recognise the status label.” Change one thing and repeat the journey.

04Turn findings into requirements

Record the question, example and useful change. Then list capabilities missing from a real application: saving requests, enforcing permissions and handling failures, according to its scope.

Finish the prototype when it supports the specific decision behind the exercise. Keep fictional data as examples for implementation tests.

Frequently asked questions

Can a prototype replace a real application?

Only when the need is to show or explore a journey. Actions in this exercise are simulated; storing data, controlling access and operating the process need further implementation.

Sources (1)

  1. How the alpha phase works · GOV.UK Service Manual — Prototypes for testing specific assumptions.

Editorial approach and corrections