User Journey Mapping examines what someone experiences while pursuing a particular goal within a product or service. It brings their circumstances, actions, questions, expectations, and difficulties into one view so we can understand what the design needs to support.
Finding a document, changing an appointment, setting up a product, or asking for help can appear simple from inside the system. For the person doing it, the experience may involve uncertainty, missing information, interrupted attention, or a decision that matters more than the interface suggests.
At Abstraction Creative, we want to understand that experience before deciding how it should work differently.
Start with what the person needs to accomplish
“Use the portal” describes activity in a product. “Find out whether my request has been accepted” describes something a person needs to know.
That difference changes where we look. The relevant journey might begin in an email, continue in the portal, and end with a conversation. A map that starts at the login screen may miss the information that brought the person there. A map that stops after submission may miss whether they understood what happened.
We define the goal, the person or relevant user group, and the circumstances surrounding the task. A first-time user may need explanations that an experienced colleague no longer notices. Someone using an internal tool may be accountable for the outcome without having chosen the software. A person acting on someone else's behalf may need information or permissions that the standard path does not anticipate.
We do not need a separate map for every possible individual. We do need to notice differences that could change the design.
Understanding the task means understanding what it asks of the person.
The path and the experience are related, not identical
A User Flow describes actions, decisions, conditions, and routes. A User Journey Map gives us more room to examine what those moments mean to the person moving through them.
Two people might take the same path through an appointment system. One understands the process and completes it confidently. The other reaches the same final screen without knowing whether a previous booking has been canceled. Counting the same sequence of clicks would not reveal that difference on its own.
The terms user journey and customer journey are sometimes used interchangeably. Within Abstraction's Index, Customer Journey Mapping addresses the wider relationship with an organization across relevant channels and time. User Journey Mapping takes a closer view of a particular goal within a product or service.
This is a useful distinction in scope, not a claim that a user journey must stay on a screen. A phone call, a physical visit, or help from another person may be part of completing the goal.
What a useful map makes visible
We choose the detail around the question we are investigating. A map should help the team understand the experience, not reward us for filling every possible row.
The situation before the first action
What prompts the need? What does the person already know? What information, access, or assistance do they need to begin?
Someone may arrive through a reminder, a search result, or a request from a colleague. They may be returning to something they started earlier. Those conditions influence the explanations and choices that will make sense.
The moments that move the goal forward
We identify meaningful stages and actions without turning every click into a separate chapter. What is the person trying to understand or decide at each point? What does the product or service ask of them? What tells them they can continue?
Content and behavior matter together. A control may work exactly as designed while the language around it leaves its consequence uncertain.
The effort and uncertainty along the way
We examine questions, expectations, interruptions, and relevant emotional responses. We distinguish what someone has told us or what we have observed from what the team is inferring.
A pause might reflect confusion, careful consideration, distraction, or a need to consult someone else. The map should help us investigate, not turn one visible behavior into an invented explanation.
Alternatives, help, and the meaning of completion
What if the person cannot provide the requested information? What if the available options do not suit them? Can they return later, change their mind, or ask for help without losing their place?
We also ask what completion means to them. A system may have saved a request while the person is still waiting to know whether anything will happen. That gap deserves design attention even if the interface reports success.
Understand what happens now before drawing what should happen
An existing journey can be explored through relevant research, appropriate observation, stakeholder knowledge, support records, analytics, and examination of the product or service. We keep the source and limitations of the material visible.
Abstraction can plan and facilitate the mapping work, synthesize available evidence, and identify where further investigation is needed. Our regular discovery practice draws strongly on stakeholder conversations and existing organizational knowledge. Direct user interviewing and specialist participant testing can be coordinated with research partners when the question calls for them.
An assumption-led map can be useful early on. We identify it as a hypothesis rather than presenting internal agreement as proof of how people behave or feel.
You do not need complete analytics or a finished research programme to begin. We can bring the knowledge you have into view and identify the gaps that matter to the next decision. We do not fill those gaps with an invented account of the person; we agree how to investigate them.
We also keep the current journey separate from a proposed future one. A proposed route may express a thoughtful idea, but it still needs evaluation and implementation. A polished map does not make those steps complete.
Shape an appointment change around the person making it
When we map an appointment-change experience with your team, we begin with what the person needs to achieve: a suitable new time and confidence about what happens to the booking they already have.
We examine the moments around that goal together. How do they find the original confirmation? Where do they discover the change option? What do they need to know before looking at alternatives? The journey may move between a message, a website and a conversation with someone on your team.
Your knowledge helps us understand the service conditions. Does the existing appointment remain in place while someone considers a new time? Will the same specialist be available? Which information can carry forward, and what needs checking again?
We place those conditions beside the person's questions. That makes the consequences easier to discuss. A technically successful change may still leave someone wondering whether they have canceled the original visit, lost their preparation notes or created a second booking.
Together, we explore where an explanation, a different interaction or a staff-assisted route would help. We keep proposed responses distinct from what the evidence establishes, then decide which questions a prototype or appropriate research should examine.
Content Design develops the explanations. User Flows specify the supported paths and conditions. Service Blueprinting examines how the change reaches the staff and systems responsible for the visit.
The map keeps the person's goal visible while those disciplines develop their parts. Your team can see why a recommendation matters, what it depends on and what needs to be learned next.
Turn the map into decisions people can understand
The map, findings, and opportunities can be the central deliverables of a focused engagement. They can also inform broader UX Strategy, Content Design, Interaction Design, or service work.
We look at which difficulties matter, what the evidence supports, and what could make the experience more useful or considerate. A recommendation should explain why it follows from the learning and what remains uncertain.
Sometimes the response is a clearer explanation. Sometimes it is a different interaction, an alternative route, or a change outside the interface. Removing a step may help; retaining a deliberate review step may help someone avoid a consequential mistake. Fewer actions are not always the right objective.
A journey is not complete simply because the interface says it is.
Co-Creation helps bring these tradeoffs into the open. The client can contribute operational context, the implementation team can identify dependencies, and relevant research can challenge what everyone assumed. We want the resulting decisions to be understandable, not simply announced.
Try it: look beyond “done”
Choose a task your product or service describes as complete. Write down what the system has finished, what the person still needs to know, and what another person or system may still need to do.
If those accounts differ, mark the uncertainty. What would help the person understand the actual state of the task and what comes next?
This small exercise does not establish a research finding. It gives you a question worth investigating—and a reason to look past the final button.
Revisit the journey as the experience changes
The work follows our continuing process: Discover → Define → Explore → Design / Develop / Market → Learn → Advance → Discover.
Mapping contributes to Discover and Define when we investigate an existing experience, and to Explore when we consider a new one. It can return whenever making or using the product exposes something we did not anticipate.
Usability Testing and other appropriate evaluation can examine parts of the proposed journey. Learning from the live experience can reveal whether people take different routes, seek assistance, or encounter circumstances the original map did not include. Those signals need interpretation, not automatic assumptions about cause.
We preserve meaningful decisions and findings with the client so that Learn and Advance lead into a better-informed Discover. The map remains useful when it can change with what we know.
What is someone trying to do—and what are we asking of them?
We can investigate and map a focused journey independently or include it within a larger design effort. The starting point may be a task that seems harder than it should be, a new product idea, or an experience your team understands differently from the people using it.
Bring the goal and the uncertainty. We can work with you to see the experience more clearly and decide what deserves attention next.