User Experience: Research the Whole Journey
User experience includes the whole interaction with a product or service, not only the appearance of a screen.
- Author
- absequ
- Published
- Updated
- Category
- UI and UX
- user experience
- ui and ux
- practical guide
User experience includes the whole interaction with a product or service, not only the appearance of a screen. Someone may discover a service through search, compare it with alternatives, submit an enquiry and wait for a reply. A polished form cannot compensate for misleading information or a workflow that never delivers the expected outcome.
On this page
The mental model
Separate user needs from proposed features. A request for a dashboard might represent a need to understand whether a process is progressing. A useful design could be a dashboard, a notification or a simpler process with fewer uncertain steps. Research should investigate the goal and context before committing to the first suggested interface.
A journey includes handoffs between pages, people and external services. Map the moments where users lack information, repeat data entry or lose confidence. Distinguish what you directly observed from a hypothesis. A small number of task observations can reveal a concrete usability problem, but should not be presented as a statistically representative market study.
A practical workflow
Define a task and recruit suitable participants with informed consent. Ask them to attempt the task using a realistic scenario rather than directing every click. Observe where they hesitate or recover. Keep questions neutral and avoid turning the session into a sales demonstration that rewards agreement.
Convert observations into a prioritized change with a measurable outcome. For example, making a form requirement visible before submission may reduce avoidable retries. Establish a baseline and review whether the change helps without harming accessibility or privacy. Completion rate, errors and qualitative explanations are more informative together than a single vanity metric.
Worked example
Research note
Task: find whether technical hiring support fits an upcoming role
Observation: participant searched for service details before opening the form
Hypothesis: a concise service summary near the enquiry action may help
Proposed change: clarify scope using existing verified service information
Check: repeat the task; record errors, unanswered questions and completion
Do not claim an improvement until the revised workflow is observed.A research note should make its evidence traceable without retaining unnecessary personal data. Describe the behavior, the context and the uncertainty separately. A user's suggestion can inspire a solution, but it is not automatically proof that the solution will work for others. Prototype the smallest change that can test the hypothesis.
Consider service delivery beyond the browser. If a page promises a response within a period, the organization needs a process capable of meeting that promise. Design should make real capabilities clearer, not invent clients, achievements or operational guarantees to make a page look more persuasive.
Failure modes and security
Dark patterns can optimize a short-term metric while harming the user. Hidden costs, confusing opt-outs and coercive consent undermine trust. Include unsuccessful attempts and opt-out flows in the journey rather than evaluating only conversion. A person choosing not to proceed can still have a clear and respectful experience.
Research records can contain personal information. Obtain appropriate consent, limit collection and redact examples before sharing them broadly. Accessibility is part of the experience from the beginning, not a final visual checklist. Include users and contexts that differ from the design team's own devices and assumptions.
Practice and verification
Map the journey from arriving on a service page to receiving the expected result. Mark what the interface promises and what the organization actually does at each step. Identify one uncertain handoff, propose a small truthful improvement and define how it will be evaluated. Keep a record of alternatives considered. If the necessary business information is unavailable, show that uncertainty internally instead of publishing invented proof or unsupported assurances.
References
Definition of UX — Nielsen Norman Group
Usability heuristics — Nielsen Norman Group