User journey map: connect paths to opportunities

A journey map helps the team visualize an experience that is often divided across screens, areas, and responsibilities. It becomes useful when it shows what a person is trying to achieve, what obstacles they encounter, and where there is an opportunity for sustained improvement supported by evidence.

Choose a person and a situation

Imagine a company that offers professional courses. The journey to investigate is that of someone who needs to prove a qualification to participate in a selection process.

The goal is not “to use the student area.” It is to obtain the correct document within a deadline. This difference opens space to observe activities outside the interface, such as checking the selection requirement or asking for help from customer service.

Avoid gathering audiences with incompatible needs in a single map. Recently graduated students and professionals returning years later may depend on different paths and information.

Assemble stages from collected material

Use interviews, responses, observations, and navigation logs to identify relevant moments. An initial structure for the example could include perceiving the need, locating the document, checking its validity, and sharing it.

At each stage, record:

• The person's action or need.
• What was observed or reported.
• The source of the evidence.
• The doubt that remains.
• The opportunity that deserves investigation.

Do not fill in emotions by intuition. If the material does not allow stating that someone was frustrated, describe the behavior and leave the interpretation as a hypothesis.

Use paths between screens as a layer

In UXTap, the Compatible Study Journey view organizes navigation evidence between screens. It helps investigate passages, returns, and points of difficulty, in conjunction with results and sessions.

This visual path is a layer of the analysis. To understand the broader objective, combine it with questions about the context and accounts of real experiences.

In the certificate example, a person might repeatedly open the same page because they are comparing data with an external requirement. Without this information, the return could be interpreted as disorientation.

Turn a breakdown into a useful hypothesis

Suppose participants find the certificate but look for an explanation of its validity. The problem might not be locating the file; it could be deciding if it serves the intended purpose.

An opportunity would be to present essential information alongside the document. Before implementing, test whether the text answers real questions and remains understandable to the involved audiences.

Also record who can act. A language problem might require content; a delay in issuing the document might depend on operations. The map should help assign responsibility without reducing every difficulty to a screen adjustment.

Keep the journey linked to date and scope

Products and processes change. Include research period, audience, observed channels, and limitations. Mark already investigated opportunities and preserve the evidence that led to the decision.

Do not turn the map into a permanent drawing that comes to represent all customers. Revise sections when there are significant changes or when new research contradicts an interpretation.

Build a small journey to obtain a certificate

In the fictional example of professional courses, the starting point could be receiving a requirement for proof of qualification for a selection process. The desired outcome is to deliver an accepted document, not just to open the certificate page. This difference changes the stages that need to appear on the map.

Organize an initial sequence: understand the requirement, locate the qualification, obtain the certificate, check the data, and send it through the requested channel. For each stage, record what was observed, what the person reported, and what is still a hypothesis. An external requirement might be outside the product but influence the entire user experience.

Do not automatically fill an emotion line with happy or sad faces. If there is a report of concern about the document's validity, record its context. If no one mentioned it and the behavior does not allow a conclusion, leave the information as unknown. A visually complete map can hide research gaps.

Relate screens to needs, without reducing the journey to the flow

Navigation between pages shows part of the activity. A person might leave the portal to consult a public notice, ask a recruiter, or check a course name in another document. If you only observe the application, these external actions might appear as unexplained pauses or returns.

Use a follow-up question to understand the episode: “What did you need to check before sending the certificate?”. Combine the answer with the recorded path. If the person returned to the page to compare the workload, the opportunity might be to facilitate document verification, rather than simply reducing round trips between screens.

Separate paths that represent different situations. Someone who completed the course yesterday might have recent access at hand; someone returning after a long time might need to recover their account. Trying to put both on a single ideal path can hide significant difficulties in resuming.

Make the map produce a delimited decision

Choose a breakdown with sufficient evidence. Imagine that participants find the certificate but don't know if it contains the required information. The revision hypothesis could be to present a preview of the fields and explain where they appear in the document. This is more specific than “improving the certification experience.”

Associate the opportunity with a responsible party and a next research activity. A task could ask the person to verify if the certificate meets a fictitious requirement. Content testing helps examine the interpretation of this information; navigation testing can verify if it is found.

Record the date and conditions of the map. If the portal changes or external requirements are different, parts of the journey will need to be reviewed. Preserve the evidence history so that the team does not reuse an old drawing as a current portrait of all participants. The map is a situated synthesis, not a definitive description of human behavior.

Choose an opportunity to test

At the end of an analysis session, select a point in the journey that has sufficient evidence and a possible action. Define how the team will recognize an improvement.

To start, choose an existing task in UXTap and relate the path between screens to a context question. Assemble a small map with identified evidence. Then, choose an opportunity, a responsible party, and a next round of validation.

To support a stage of the map, consult the replay analysis guide and explore UXTap results along with individual evidence.

Frequently asked questions about journey maps

Is a screen flow already a complete journey?

Not necessarily. It describes the navigation available or recorded in the product. A journey can include previous actions, other channels, decisions, and expectations that do not appear on the screens. Use the flow as a layer of evidence and delimit which parts of the experience were outside the observation.

Can I create a map before collecting data?

You can elaborate a journey hypothesis to organize questions and plan the research, provided you identify its provisional nature. Separate what the team assumes from what was observed. The collection should allow correcting the design, including unexpected stages and situations that do not fit the imagined path.

How to choose which opportunity to prioritize?

Consider the effect on the person's need, the observed recurrence, the scope of the problem, and the possibilities for intervention. Do not prioritize only the point with the most annotations. Relate the opportunity to the evidence and the risk of the decision, preserving what still needs to be investigated.

Create your UXTap account to prepare your first study.