In this guide
Describe the outcome from the user’s perspective
‘Completed onboarding’ describes a product step. ‘Received a useful answer to their problem’ describes an outcome to investigate. First value needs a definition for the segment and task being observed.
In a hypothetical reporting tool, users might connect a data source without ever using the first report to make a decision. Setup happened; usefulness remains uncertain. The signal you choose should be close to an outcome the user can recognise.
Reconstruct the journey before changing screens
Choose a segment and task. Compare the expected journey with observed sessions, available events and conversations about recent episodes. Data shows where to look; understanding the cause may need further observation.
- Where does the user come from and what do they expect?
- What information or permissions do they need?
- Where do they stop and what are they trying to do there?
- Do people who reach the outcome have different characteristics or conditions?
- Do recorded events represent the actions you intend to measure?
Separate possible explanations
Abandonment may reflect a difficult step, missing data, dependence on a colleague or a different expectation. These assumptions imply different interventions. Shortening the flow before separating them may leave the constraint in place.
Write down the observation, your interpretation and the check needed. An interview confirming a difficulty is evidence to compare with behaviour; it does not prove that this difficulty explains every abandoned account.
Choose a coherent check and measure
Define a change tied to the assumption: make data available, clarify an action or help the user complete the task. Specify who you will observe, the expected outcome and what could contradict the assumption.
The observation window depends on the usage cycle. A daily product and one used for a monthly decision need different interpretations. Also consider outcome quality, return usage and unintended effects; completing the flow alone may be insufficient.
The next step with your team
Bring one real journey, one open question and the smallest check that could change the decision to a review. Assign an owner and agree when to examine the evidence.
When signals are fragmented, a product diagnostic can connect flows, data and feedback. If the problem is already clear enough, the team can start with the agreed check.