KEISSMEDIAGet in touch
← All resources

Keiss Media · Practical resources

User journey and prototype

Describe what participants do, how screens respond and what the prototype needs to test.

Fill in the template ↓Download a blank template (.md)
When to use it
Before design and development, when the concept needs a concrete user journey.
What you will have
A user flow, screen states and open questions to review in a prototype.
What to check
This worksheet needs to be used alongside a prototype. A completed form alone does not validate the experience.
View the worked example

The example is fictional. It shows how to record questions and untested work.

User journey and prototype: the example drink learning example

All information is fictional. This is not a commission, an acceptance record, a verified result or a required service package.

Status

An illustrative scenario. The images are not a working game.

User and goal

An adult visitor wants to understand the flavour options quickly and try the mechanic. This is an example hypothesis, not a research finding.

Screens

S01: product and three flavours → S02: rules → S03: game board → S04: result and flavour card. From S04, the visitor can replay or return to the flavours.

Move

Swap two adjacent pieces. A match of three identical citrus pieces disappears and the charge meter increases. Rules for unsuccessful swaps and move counting need separate agreement.

Story and criterion

The visitor wants to understand the result of a move. Check that a valid match produces a visibly changed board, score and remaining-move count. Shape and numbers accompany colour.

Failure states

No valid move: show a hint or reshuffle under an agreed rule. Reload: decide in advance whether the round persists. Service unavailable: show a clear message and retain the flavour choice if the requirements provide for it.

Prototype

No working prototype link is available. The next step is to build and review it, not to mark the stage complete.

Full workflow: https://keissmedia.com/resources/project-workflow/#scenario

Download example (.md)

Fill in the template

If an answer is unknown, say so. You can leave fields open and record what needs clarification.

Project, version, status, author, date and reviewer.

Who participates, what they need and why.

Screen identifier, action and next screen; errors and return paths recorded separately.

For each story: user, need, purpose and a testable result.

Controls, valid moves, scoring, limits, completion and replay.

Loading, offline, empty data and errors; keyboard operation, labels and distinctions that do not rely on colour alone.

Link, version, review date and findings; unknowns and the person responsible for clarification.

Fields work in your browser. Your text is not sent to us or saved after the page closes. Download the document to continue later.

Sources and adaptation

Keiss Media working guidance and learning examples. This route reuses the library’s existing brief, concept, requirements, scope-change, handover and hosting resources. Their sources and reuse terms are given on the respective pages. The new journey, planning and test-record templates connect those resources; they are not an official standard or a contract. User stories and acceptance criteria were checked against the GOV.UK Service Manual; the distinction between objectives and hypotheses follows 18F Methods. The examples were written for the fictional the example drink project.

Version 1.0 · 5 November 2026