A usability plan, one booking journey
Silent video. Hypothetical example, not study findings.

[0–5]
Tecno Stack • UX RESEARCH • Plan one usability test • A method, not a result • Task • Observe • Evidence • Retest • Keep interpretation separate
The Tecno Stack cover introduces UX RESEARCH and Plan one usability test, with the qualifier A method, not a result. The diagram connects Task to Observe, then Evidence and Retest, with a dashed return to Task. Keep interpretation separate is a separate note, not a fifth step. This introduces the hypothetical booking example, not findings or a successful outcome.

[5–12]
Hypothetical example • Give the goal. • Book a website consultation for next week. • No route instructions. • Services • Website consultation
A simplified hypothetical service-selection prototype shows a website-consultation tile. A cursor approaches it after the neutral task appears. The task describes the goal without naming an interface control.

[12–18]
Hypothetical example • Record what happens. • Returns to the service list. • Services • Website consultation • Service details • Observation
The same prototype starts on Service details. The cursor moves back to Services and the service list reappears. A note records this invented behaviour without claiming why it happened.

[18–24]
Hypothetical example • Keep interpretation separate. • Returned to the list. • Missing information? • Ask what they expected. • Services • Website consultation • Observation • Interpretation
The observation and interpretation occupy separate surfaces beside the same prototype. Returned to the list is the observation; Missing information is a question to investigate. The suggested follow-up asks what information the person expected.

[24–30]
Hypothetical example • Choose a change. Retest. • Clarify the service description. • Same task. Revised flow. • Services • Website consultation • Discuss a new company website.
The same service-selection prototype gains the proposed description Discuss a new company website. The cursor makes a second attempt on that service after the description appears. The revised flow is ready to test; no improvement, completion rate or successful result is asserted.