Choose the first useful step
Silent video.

[0–6]
Name the difficulty • Use a task and a source of evidence. • “Make the page modern” • Send enquiry after correcting email • Observation · language · device • Hypothetical task · record evidence and date
A vague preference to modernise a page is connected to a specific hypothetical task: send an enquiry after correcting an email. The route then attaches an observation, language and device context; evidence and its date must be recorded.

[6–12]
Check the signal • A missing event can resemble lost enquiries. • Enquiry attempt • Request saved • Tracking event absent • Check records and tracking separately
One hypothetical enquiry attempt branches independently to a saved operational request and an absent tracking event. The saved request and missing event remain separate. Missing analytics alone cannot prove the request was lost or establish revenue impact.

[12–18]
Match evidence to work • Fix, audit or prototype the changed flow. • Isolated, reproducible defect • Known defect → fix • Difficulty, cause unclear • Unclear cause → audit • Roles or flow changed • Changed flow → prototype
Three independent conditions connect to the reviewed illustrated branches. An isolated reproducible defect with agreed intended behavior can justify a focused fix. An observed difficulty whose cause is unclear supports an audit. Changed roles or workflow support prototyping the changed flow. No route is ranked as universally best; related work may be combined.

[18–24]
Separate observation and interpretation • Mark the suspected cause as unverified. • Observed • Hypothesis • Correct email; submit stays disabled • Possible state-update fault · unverified • Invented example · reproduce before diagnosis
The solid Observed frame shows a form whose submit control remains disabled after a valid email correction. A separate dashed Hypothesis frame suggests a possible state-update fault. That suspected cause is unverified and requires developer investigation. The example is invented; no observed frequency or business loss is claimed.

[24–30]
Agree how to verify • Name the owner, dependency and acceptance. • Reproduce the disabled-submit case • Owner + developer investigation • Retest enquiry + received request • Verification pending · no outcome claimed
The disabled-submit case is linked to an owner and developer investigation, then to retesting the complete enquiry and checking the received operational request. The gate stays pending: no fix or acceptance result is claimed.