Digital products ·
A customer journey map reveals the work between screens
A customer journey map describes a person’s movement towards an outcome rather than a sequence of pages. It connects the website, conversations, staff work and waiting time into one observable journey.
The journey starts before the interface
People rarely begin on a homepage. They notice a problem, look for an explanation, compare approaches and ask for advice before opening a particular website. The journey also continues after a form is submitted through confirmation, waiting, payment, delivery and support.
A customer journey map is therefore broader than a screen map. It records stages, goals, actions, channels and obstacles. The interface occupies only part of that system, while the quality of the product also depends on what happens between screens.
A map needs one journey
“Our customer’s journey” is too broad to design. A new visitor choosing a service behaves differently from a returning customer placing another order. An employee approving a document follows a different path from a manager reviewing the outcome.
Begin with one participant, one task and one observable finish. For example, a founder decides whether a working format fits, submits a useful enquiry and receives a clear next step. This boundary keeps the map from becoming a collection of assumptions about the entire business.
Stages follow changes in the decision
A stage is not necessarily a page or channel. It changes when the person’s question changes: recognising the task, choosing an approach, establishing trust, accepting the terms and completing an action. One stage may involve search, an article, a conversation and a client portal.
For each stage, record the goal, action, available information, uncertainty and evidence of completion. This shows where the product supports a decision and where it merely presents another screen without answering the central question.
Connect an obstacle to its cause
A low form conversion rate does not explain the problem. A person may not understand the outcome, may be reluctant to share data, may be unable to find a price or may not know when a reply will arrive. The same visible behaviour can require very different product changes.
Separate observation from interpretation. Mark what analytics, interviews or support enquiries confirm and what remains a hypothesis. This prevents a team from launching a confident redesign based on one opinion.
Backstage work is half the journey
Internal work supports every visible customer action. An enquiry needs to reach the right system, a member of staff needs the context, the status needs to change and the notification needs to arrive. If one connection fails, the interface promises something the organisation cannot deliver.
Place team actions, data and systems beside the customer journey. This turns the map from a presentation diagram into a foundation for a website, client portal, workflow automation or API integration.
An opportunity must change a specific moment
A journey map can produce a long list of ideas. A better next step is to choose a moment with a costly failure: an unclear beginning, repeated data entry, waiting without status or a manual hand-off between staff. The solution should address the cause rather than merely add a feature.
Ask how often the obstacle occurs, how severely it prevents completion and whether a digital product can influence it. These questions turn the map into a sequence of testable changes rather than a discussion of taste.
The map becomes a prototype brief
A useful journey map ends with a question for the next product version. How will a person understand the difference between the available formats? What follows data submission? Where will they see progress? These questions become prototype journeys and usability test criteria.
Within the Method, I connect the customer journey to the operational process, data and team responsibilities. This makes it possible to choose the form of the digital product before development and build a prototype around a completed action rather than a collection of screens.
From an idea to a digital product
If the task calls for a service or internal tool, we can define the first complete journey and a path to a working release.