Trace one evidenced problem | Kickoff from Problem to Backlog

Label persona statements observed, assumed or excluded. Choose one priority user problem and map the path required to complete it. Put alternative branches outside the first slice.

Failure mode: a richly described persona is treated as research. Record the evidence source or call it a user hypothesis.

Reading

core

Evidence before character detail

For every persona statement, record its source or label it assumed. Choose one evidenced problem and map an end-to-end path to the user’s goal. Alternative paths remain visible but outside the first slice.

Personas communicate research; they do not create it.

Worked example and transfer practice

All examples below are fictional teaching material. Use synthetic notes; no workplace or personal data is required or uploaded.

Separate observation from invention. In the fictional repair service, three callers report that they cannot confirm a visit while at work. That is a reported need from a small sample, not proof that all callers want an app. A stakeholder invents ‘Sam, aged 35, who loves mobile alerts’. Mark those details assumed. Trace one reported problem through request, confirmation and arrival; include a phone route for people without online access.

Try before reading the guide: Label these statements: two borrowers could not find the collection date; most borrowers prefer texts; volunteers believe clearer dates would help. Choose one research action to test the least supported material claim.

Practice review guide

The first is bounded observation, the second is unsupported unless its source is supplied, and the third is a stakeholder hypothesis. A persona’s vividness cannot upgrade its evidence.

References

Learning about users and their needsprimary
How the discovery phase worksprimary

Knowledge check

core

Practice · formative check

Check the persona evidence

Identify the honest evidence label.

Concepts: user need, assumption

1. A stakeholder invents a plausible user's age and habits without research. How should the team record it?

As an observed persona because the detail feels realisticAs a validated user need in the backlogAs a provisional user hypothesis with a research action

There is no attempt limit or pass/fail state. Completing the check only enables the lesson's separate explicit completion control; it never records completion or certificate eligibility itself.

Use the equivalent lesson path

Activity ready. Attempts are unlimited. Completing this practice activity enables the lesson's separate, explicit completion control.

Equivalent non-interactive path

Answer and feedback guide

A stakeholder invents a plausible user's age and habits without research. How should the team record it?

As an observed persona because the detail feels realistic: Realistic detail does not make a claim observed.
As a validated user need in the backlog: Validation requires evidence from actual or likely users.
As a provisional user hypothesis with a research action (best answer): Correct. Plausibility is not user evidence.

References

Learning about users and their needsprimary