Customers do not know where marketing ends, sales begins and support takes over. They see one company. That is why a good impression breaks when they read one promise on a website, hear another in a sales conversation, and have to explain their needs again after signing.
A customer journey helps identify those breaks. It is not a tool for drawing a neat sequence of stages. It is a way to examine the full customer experience, especially the handoffs that no one inside the company considers their responsibility.
A company can easily draw a journey around its own process: ad, enquiry, quote, contract, onboarding. Customers usually do not think in that order.
They may first notice that production deadlines are slipping. Finance may be spending too much time on manual checks. A sales manager may lack a complete history of customer interactions. Before contacting a supplier, people often try to solve the problem with existing tools, ask colleagues, compare risks and look for information.
That is why a customer journey map should start with two simple questions:
This starting point changes the conversation. Instead of asking how to generate more leads, a team can ask whether a potential customer has enough clear information to assess whether a solution fits their process. Instead of asking whether onboarding has been sent, it can ask whether the customer knows what to prepare and who is responsible for what.
B2B CX is not the experience of just one person. Different people in the same decision assess different consequences.
One customer journey map does not need to capture every detail for every role. It should, however, show where their needs overlap and where they differ. If a sales conversation only answers the director's questions, future users and IT may still lack what they need to proceed.
It helps to choose one specific scenario, such as the handoff from an approved proposal to the start of an ERP implementation. The team can then follow what actually happens, who passes on information and where new questions arise.
The experience often does not stall within a single task. It stalls when responsibility moves from one team to another. Customers do not see that handoff. They only need the conversation to continue without having to start their story from the beginning.
In practice, situations like these are common:
These are not only communication failures. They often reveal that data, systems and responsibilities are not connected. One additional CRM field can help, but only if the team knows why it is entered, who uses it and at what point.
For a more connected transfer of context from the first contact into sales work, it is useful to consider how Orkasta CRM for connected sales work is organised. A tool alone does not resolve unclear ownership, but it can support an agreed way of working.
There is no need to start with a large workshop or an attempt to cover the whole company. Choose one important journey, one customer group and one handoff between departments. Then record six elements for every stage.
Write down what the person is trying to achieve in their own terms. This is different from the team's internal activity. A customer does not simply want to "receive a proposal". They may want to understand scope, compare risk or gain a basis for a discussion with colleagues.
What does the person need to know to continue? It may be a timeline, responsibility, a process example, an explanation of an integration or confirmation of what happens after signing.
There is no need to guess emotions. Record moments of uncertainty, relief or frustration only where there is a signal: a question from a conversation, a support message, a task recording, feedback after a meeting or a pattern in the data.
If there is no such signal, label the item as an assumption. That distinction prevents a team from presenting its own opinion as a fact about the customer.
For every important claim, note what supports it. Evidence can be a conversation record, a repeated question, a number of incomplete handoffs, a reason a process was interrupted or an observation from people who work with customers regularly. Not all evidence has equal weight, but the basis for a conclusion should be visible.
Describe what slows the person down or undermines trust. Be specific: the customer waits without information about the next step, receives two different instructions or has to explain the same request for a third time.
Name the person or team that can change the situation. The owner is not necessarily the person who caused the problem. It is the person who can bring together the required people, make a decision or carry out the change.
A physical process wall often helps because the team can see the complete sequence at once. Cards for marketing, sales, delivery and support can show where information disappears, work is duplicated and customers wait. A digital view can be useful later, but the conversation is more valuable when the real workflow is aligned first.
Mapping usually produces a long list of problems. Trying to fix everything at once is not useful. Prioritise friction that happens often, has a strong effect on trust or blocks an important next step.
For each possible change, check:
The answer is not always a new interface, automation or a large project. It may be a better email after a meeting, a required note when an opportunity is handed over, a clearer handoff owner or a conversation with the customer before implementation starts.
For example, if the implementation team repeatedly has to collect basic information that sales has already heard, the first step may be to agree on a short handoff form. The form should include only information the next team actually uses: the customer's goal, key processes, open questions, agreed scope and people involved in the decision. If nobody reviews the form before work begins, it will quickly become another document with no effect.
A customer journey map is not a replacement for customer conversations, orderly data or decisions about priorities. It also cannot remove every wait and every complexity.
Some checks in an ERP project are necessary. An integration may require additional questions. A change to a customer's process may need time for alignment. The aim is not to promise simplicity where it does not exist, but to explain clearly why a step is necessary, what follows and who leads the process.
There is also a risk that the map becomes an attractive document without a change in daily work. This happens when a team collects observations but does not set an owner, a review date and a signal of progress. After a workshop, there should therefore be a small, workable list of changes, not only a visual display of problems.
It is useful to review three questions from time to time:
If the answer is often no, the issue is probably not one individual email. Look at the handoff between teams, the data that travels with the customer and the decisions that nobody has taken ownership of.
Start with one handoff where a customer repeats information or waits without a clear reason. Mark the real flow, collect available signals, name an owner and agree on one measurable sign of change. For a broader view of connecting processes, data and teams, see Connected operations . This is how a customer journey map stops being an illustration and becomes a working tool for more consistent B2B CX.