The practical answer
Follow one type of customer through discovery, evaluation, enquiry, decision and onboarding. Record their question, the information they need, the action they take and who in your business handles the next step. Use evidence to identify gaps.
A customer does not experience your website, Instagram page, WhatsApp inbox and quotation process as separate departments. They experience one business.
That experience can break even when each individual part looks reasonable. The website may explain the service, but the enquiry form asks unrelated questions. A helpful conversation may end with a proposal that introduces unexpected conditions. A paid client may not know what happens next.
Mapping the customer journey from website visitor to client makes those connections visible. It is useful work within digital strategy and positioning, especially when a business is active online but cannot explain where suitable prospects stop progressing.
Choose one customer and one service
Start with a defined journey. A school administrator seeking an admissions portal has different questions from a shop owner seeking a product catalogue. Combining both into one vague “customer” can hide important differences.
Describe the person’s situation, the decision they need to make and the limits they face. Focus on relevant behaviour rather than inventing a detailed personality. You need to understand the job they are trying to accomplish.
Make clear whether the map describes observed behaviour or a proposed future process. A planning workshop can generate useful hypotheses, but it does not turn assumptions into customer research.
Gather evidence from more than analytics
Review enquiries, sales conversations, common objections and support questions. Speak with the people who handle those interactions. Where appropriate, ask customers how they found the business and what they needed before deciding.
Website reports can show activity, but they may not explain uncertainty or an offline handover. A customer might read several pages and then call a colleague for a recommendation. Your map should allow for that reality.
Use aggregated patterns and protect private information. A team discussion rarely needs screenshots exposing someone’s personal phone number or confidential project details.
Build a simple journey table
The following example follows an institution considering a portal. It is a planning illustration, not a report about a particular client.
| Stage | Customer’s question | Useful support | Business responsibility |
|---|---|---|---|
| Discovery | Can this person help an institution like ours? | Clear service description and relevant experience | Make the offer understandable |
| Evaluation | What would the project involve? | Scope explanation, examples and sensible answers | Explain process and limitations |
| Enquiry | What information should we send? | A clear contact route and brief questions | Receive and acknowledge the request |
| Decision | What exactly are we approving? | A specific proposal and agreed responsibilities | Resolve scope and ownership questions |
| Onboarding | What must we provide now? | Named contact, next steps and dependencies | Coordinate the start of the work |
You can add more detail later. Begin with a map the operating team can understand and correct.
Record the question behind each step
A page should help somebody answer a question or complete a task. The service page may establish relevance. A case study may show the kind of work completed. A contact form may collect the information needed for an informed reply.
If several pages repeat the same introduction but none explains the project process, the journey has a content gap. If the first form asks for a detailed technical specification, it may demand a decision the prospect is not ready to make.
The school website versus management system article is an example of content that helps a prospect distinguish needs before requesting a project. Supporting articles should serve a decision like that.
Pay attention to handovers
Mark every point where responsibility moves: website to inbox, receptionist to consultant, consultation to proposal, approval to delivery.
For each handover, ask what information is passed, who owns the next action and how the customer knows what to expect. A good page cannot compensate indefinitely for an inbox nobody checks.
Agree a realistic response arrangement. Do not publish an instant-response promise simply because it sounds persuasive. The expectation should match the team’s capacity and the type of enquiry.
Include reassurance where it is needed
Trust questions change through the journey. Early on, a visitor may want to know whether you understand their industry. Later, they may need clarity about fees, ownership, project responsibilities or maintenance.
Place proof and explanations near the relevant decision. A genuine case study is useful when it shows comparable work and accurately describes the contribution. A long list of unrelated achievements may not answer the immediate concern.
Avoid claiming that a testimonial proves every future result. Use evidence to establish experience and fit, while keeping the proposed scope specific to the new customer.
Measure the stages without merging them
Track meaningful steps where you can: relevant visits, actual enquiries, qualified conversations, proposals, accepted work and completed onboarding. Define each stage so staff use the same meaning.
Counts may not match perfectly across systems. A person can enquire through more than one channel, and some decisions happen offline. Record what is known rather than forcing an apparently perfect funnel.
Look at both volume and quality. Fewer but better-informed enquiries can be useful if the business can respond and deliver well. More activity is not automatically progress.
Turn the map into a short improvement list
Prioritise gaps that prevent an important task, create repeated confusion or leave a responsibility unowned. Assign an owner and describe the evidence that would show improvement.
Test the revised journey with representative people. Ask them to find information or complete an enquiry without coaching them through the answer. Update the map when their behaviour challenges the team’s assumptions.
Nielsen Norman Group describes journey mapping as a way of understanding a person’s process over time. Your business map should remain a working aid informed by real interactions, not a decorative poster that is never revisited.
Frequently asked questions
Do we need specialist mapping software?
No. A shared document or table can be enough. The value comes from accurate evidence, clear questions and agreed responsibilities.
Should every customer follow the same route?
No. Map important patterns and allow for different entry points. Customers may arrive through a referral, a search, a social post or a direct conversation.
Where should the journey end?
Include at least the handover into delivery. A sale followed by confusing onboarding can damage trust and create avoidable work for both sides.
Further reading
Reference addresses are provided as plain text for copying.
https://www.nngroup.com/articles/journey-mapping-101/
Discuss your next step
Want to understand where website enquiries stall? Share the service involved and how a prospect moves from first contact to delivery. I can help map the journey and prioritise the handovers that need improvement.





