6. Customer Journey Mapping and Service Design

Introduction and context

Quality is experienced by customers as a journey rather than as an isolated transaction. A customer may first encounter an organization through a search engine, recommendation, advertisement, or physical location; compare alternatives on a digital platform; seek advice through a contact centre; purchase through an application; receive delivery through a logistics partner; and request assistance through social media. The customer evaluates the combined experience across these interactions, even when each interaction is managed by a different department or channel.

This creates an important quality-management challenge. Organizations often optimize individual touchpoints—such as reducing call-handling time or improving website speed—without examining how those touchpoints connect. A process that appears efficient within one department may create additional work, confusion, or dissatisfaction elsewhere. Customer journey mapping and service design address this problem by making the complete experience visible and by connecting the customer’s perspective with the operational processes that support it.

Journey mapping is primarily an analytical and sense-making activity. It represents the sequence of customer actions, questions, emotions, expectations, channels, and interactions across a defined experience. Service design extends this analysis into the systematic design or redesign of the service, including frontstage interactions, backstage processes, technology, people, policies, and physical or digital evidence. Together, these approaches support customer-centred quality improvement, innovation, and organizational alignment.

The subject is particularly relevant to Total Quality Management (TQM). TQM emphasizes customer focus, process orientation, prevention of defects, employee involvement, evidence-based decisions, and continual improvement. A journey map provides a customer-centred view of the process, while a service blueprint connects that view to the organizational system capable of delivering quality.

Learning objectives

By the end of this chapter, students should be able to:

1. Explain the meaning, purpose, and scope of customer journey mapping and service design.

2. Distinguish between journey maps, service blueprints, process maps, experience maps, and ecosystem maps.

3. Identify stages, touchpoints, channels, moments of truth, pain points, backstage activities, and service evidence.

4. Apply design-thinking, co-creation, prototyping, and inclusive-design methods to service improvement.

5. Analyse omnichannel journeys using qualitative and quantitative evidence.

6. Evaluate risks, ethical issues, technological implications, and implementation challenges.

7. Develop practical recommendations for improving an end-to-end customer experience.

The customer journey as a quality system

A customer journey is the sequence of activities and perceptions through which a person attempts to achieve a goal. The goal may be opening a bank account, obtaining medical treatment, returning a product, enrolling at a university, or resolving a service failure. The journey includes both interactions controlled by the organization and experiences that occur outside its direct control.

A journey normally contains five related dimensions. First is the customer’s goal: what the person is trying to accomplish. Second is the sequence of stages, such as awareness, consideration, purchase, use, support, and renewal. Third are touchpoints, including websites, staff, forms, applications, kiosks, messages, invoices, and physical spaces. Fourth are customer perceptions, including expectations, effort, confidence, anxiety, satisfaction, and trust. Fifth is the wider context, such as family influence, regulatory requirements, competing providers, accessibility needs, and the customer’s previous history with the organization.

The journey is not necessarily linear. Customers may move between channels, repeat a step, abandon the process, or begin with a complaint. A useful map therefore represents actual behaviour rather than an idealized organizational procedure. It distinguishes the organization’s intended journey from the lived journey.

A touchpoint is any moment at which the customer encounters the organization, its partners, its communications, or its service environment. Touchpoints may be human, digital, physical, or mediated by another organization. A channel is the medium through which the interaction occurs, such as a branch, telephone, website, mobile application, email, chatbot, marketplace, or social-media platform. The distinction matters because the same touchpoint may operate differently across channels. For example, changing an address may be simple in a mobile application but difficult through a call centre.

A moment of truth is an interaction that strongly influences the customer’s judgement of the service. It may be a first response to a complaint, the explanation of a medical procedure, the confirmation of a payment, or the arrival of a time-sensitive delivery. Not every touchpoint has equal strategic importance. Journey analysis helps managers identify where trust is gained or lost.

Customer effort is the physical, cognitive, emotional, financial, and time-related burden required to complete a task. Reducing effort does not mean removing all customer choice or human contact. It means eliminating unnecessary repetition, ambiguity, waiting, transfers, and documentation. In quality terms, many pain points are forms of process failure visible from the customer’s perspective.

Mapping different layers of experience

Several forms of mapping are useful, but they answer different questions.

An experience map describes the broader activities, needs, and emotions of a person, sometimes without reference to a particular organization. It is useful when exploring a problem space. A customer journey map focuses on a specific customer segment and a defined relationship with an organization. It shows stages, actions, questions, channels, expectations, and perceptions. A service blueprint adds the organization’s delivery system: frontstage employee actions, backstage activities, support processes, technology, policies, and evidence. A process map documents operational steps, decisions, inputs, outputs, and handoffs, usually from an internal perspective. An ecosystem map shows relationships among customers, employees, suppliers, regulators, partners, platforms, and other actors.

These maps should not be treated as competing alternatives. They operate at different levels. An ecosystem map may reveal that a delivery service depends on a logistics partner and a payment platform. A journey map may show that customers receive contradictory notifications. A service blueprint may identify that the contradiction originates in two unconnected databases. A process map may then be used to redesign the data-transfer procedure.

A high-quality journey map commonly includes:

• customer persona or segment and the journey goal;
• stages and customer actions;
• questions, expectations, needs, and emotions;
• touchpoints and channels;
• pain points, failure points, and opportunities;
• customer effort, waiting, repetition, and handoffs;
• organizational responses and relevant performance evidence.

Maps should state their scope clearly. “The banking experience” is too broad for effective analysis. “First-time digital account opening for salaried customers using a smartphone” is sufficiently specific to guide research and action.

From customer evidence to an actionable map

Mapping should begin with evidence rather than assumptions. Relevant sources include interviews, observation, contextual inquiry, diary studies, complaint records, call transcripts, web analytics, search queries, transaction data, customer surveys, social-media comments, accessibility testing, and employee knowledge. Quantitative data reveals frequency, duration, abandonment, transfer rates, and variation. Qualitative evidence explains why those patterns occur.

The first task is to define the customer and the job to be done. A persona should be evidence-based and should represent meaningful behavioural or contextual differences, not merely demographic stereotypes. The team then establishes the journey boundary: where the experience begins, where it ends, and which adjacent activities influence it.

Next, the team reconstructs the current-state journey. Participants should describe what they actually did, not what the organization expects them to do. Researchers can ask: What triggered the need? What did you try first? What information was missing? Where did you wait or repeat yourself? What did you expect at that point? What happened when something went wrong?

The draft map is then validated with customers and employees. Validation is essential because a visually attractive map may still be inaccurate. Different segments may have different journeys, and a single average journey can hide important experiences of older customers, people with disabilities, people with limited language proficiency, or customers with low digital confidence.

Pain points should be prioritized rather than listed indiscriminately. A practical prioritization considers severity, frequency, customer effort, business impact, equity impact, and feasibility of intervention. Root-cause analysis tools such as the five whys, cause-and-effect diagrams, failure-mode analysis, and Pareto analysis can be applied to high-priority points. The aim is to distinguish symptoms from causes. For example, repeated calls may be a symptom; the underlying cause may be unclear status information, incompatible systems, or a policy that prevents frontline employees from resolving the issue.

Service blueprints: connecting experience to operations

A service blueprint is a structured representation of how a service is delivered. It places the customer journey at the centre and adds the organizational activities required to support it. A conventional blueprint includes the following layers.

The customer actions layer records what the customer does. The frontstage layer records visible employee actions and interactions, such as greeting, advising, approving, communicating, or resolving. The backstage layer records activities that support the frontstage but are not normally visible, such as verification, scheduling, case review, or system updates. Support processes include activities performed by other departments, suppliers, technology platforms, and external partners. Physical or digital evidence includes documents, screens, messages, receipts, signage, packaging, and other artefacts that the customer encounters.

Three lines are especially useful. The line of interaction separates customer actions from organizational contact. The line of visibility separates visible frontstage actions from invisible backstage work. The line of internal interaction separates frontline delivery from support activities. These lines reveal where failures, delays, and ownership gaps may occur.

For quality management, a blueprint has three major uses. It exposes handoffs that can generate defects; it clarifies ownership and service standards; and it connects customer outcomes to process measures. For example, a customer’s inability to track a complaint may be linked to a missing case identifier, a manual handoff between departments, and a policy that prohibits frontline access to the relevant system. The blueprint makes the chain visible.

Blueprinting should include failure points and recovery mechanisms. A service is not designed only for normal conditions. It must also address lost payments, unavailable systems, incorrect deliveries, language needs, privacy incidents, and exceptional customer circumstances. Effective recovery includes detection, ownership, communication, authorization, correction, and learning. A recovery process that compensates the customer but does not remove the root cause is incomplete from a TQM perspective.

Design thinking, co-creation, and prototyping

Service design commonly uses design thinking as an iterative approach to uncertain problems. Its activities are often described as empathize, define, ideate, prototype, and test. These activities should not be understood as a rigid linear sequence. Research may change the problem definition; testing may reveal a new need; and implementation may require another cycle of investigation.

Empathy involves understanding the customer’s context, motivations, constraints, and emotional experience. It is not simply being polite or asking whether a customer is satisfied. Definition converts a broad concern into a focused design challenge, such as: “How might we help a first-time applicant understand the next step without contacting support?” Ideation produces multiple possible responses before the team selects an option. Prototyping makes an idea tangible. Testing gathers evidence about desirability, usability, accessibility, feasibility, and operational consequences.

Co-creation involves customers, employees, partners, and other stakeholders in the design process. Customers provide lived-experience knowledge; frontline employees understand workarounds and exceptions; technology and compliance specialists assess feasibility; and managers address resource and governance constraints. Co-creation is not equivalent to asking customers to design the entire service. The organization remains responsible for ethical decisions, feasibility, and quality assurance.

Prototypes can be inexpensive. They may be paper forms, storyboards, role-play scripts, clickable screens, revised messages, mock service counters, or manual versions of an automated process. A prototype should answer a specific question. A storyboard can test whether the sequence is understandable; role-play can test the emotional and operational experience; a clickable prototype can test navigation; and a pilot can test actual performance in a controlled setting.

Testing must measure more than preference. Useful indicators include task completion, time, error rate, abandonment, comprehension, accessibility, perceived effort, first-contact resolution, and employee workload. A solution that customers like in a demonstration but cannot be delivered reliably is not a quality solution.

Designing for omnichannel and inclusive experiences

Omnichannel service is not simply the presence of many channels. It is the coordination of channels so that customers can move between them with continuity. Continuity requires consistent information, recognizable identity, appropriate transfer of context, and clear responsibility. A customer who begins in a chatbot should not have to repeat the entire issue when transferred to an employee.

Channel integration involves technology, process, and policy. A unified customer record may be necessary, but it is not sufficient. Employees also need access rights, training, service standards, and authority to act. Organizations should decide which channel is appropriate for which task, while preserving customer choice for critical or complex interactions. Digital self-service should simplify routine work, not become a barrier that forces vulnerable customers to use technology they cannot access.

Inclusive design considers the widest range of users from the beginning. Accessibility includes visual, auditory, motor, cognitive, linguistic, financial, and situational dimensions. Examples include readable contrast, keyboard navigation, captions, plain language, multilingual support, predictable forms, alternatives to voice-only verification, and physical access. Inclusive design also considers temporary and contextual limitations, such as a broken arm, noisy environment, limited connectivity, or stress.

Personalization can improve relevance, but it creates risks. Incorrect assumptions, discriminatory segmentation, intrusive data use, and inconsistent treatment can undermine trust. Organizations should provide transparency, meaningful choices, human escalation, and equitable service standards. A premium digital experience should not imply that customers unable to use digital channels deserve inferior treatment.

Measuring journey quality

Journey measures should combine outcome, experience, process, and equity indicators. Common customer measures include satisfaction, recommendation intention, perceived effort, confidence, trust, and complaint resolution. Process measures may include waiting time, abandonment, repeat contact, transfer frequency, first-contact resolution, rework, error rate, and completion time. Business measures can include retention, cost to serve, conversion, renewal, and employee workload.

A single aggregate score can conceal variation. Managers should examine performance by stage, channel, segment, location, issue type, and outcome. For example, an acceptable average waiting time may hide extremely long waits for customers requiring language support. Journey analytics can connect behavioural data across channels, but only when identity matching and consent are appropriately managed.

Measurement must support decisions. If a map identifies uncertainty after an application is submitted, the relevant measures may be status-page visits, repeat contacts, abandonment, and confidence—not merely overall satisfaction. Leading indicators, such as unresolved handoffs or increasing form errors, can help prevent later dissatisfaction.

Digital technology, analytics, and artificial intelligence

Digital tools can support journey discovery and service improvement. Process-mining software can reconstruct actual process paths from event logs and identify loops, delays, and deviations. Text analytics can classify complaint themes and detect changes in customer language. Speech analytics may reveal repeated explanations, transfer patterns, or emotional escalation in contact centres. Experimentation platforms can compare alternative messages or interfaces.

Artificial intelligence may assist with personalization, recommendation, conversational support, summarization, routing, and anomaly detection. However, AI must be governed as part of the service system. Risks include inaccurate answers, opaque decisions, automation bias, privacy breaches, exclusion of minority language users, and difficulty escalating complex cases. Human review is particularly important where decisions affect eligibility, finance, health, safety, or legal rights.

Technology should follow a validated customer and operational need. Automating a poorly designed process can increase the speed and scale of failure. Data quality, model monitoring, access control, cybersecurity, explainability, retention, and accountability should therefore be included in the service blueprint and not treated as separate technical matters.

An illustrative case: redesigning a university admissions journey

Background

The fictional Northbridge University receives applications through a web portal, email, telephone, and in-person admissions offices. The university has invested in a modern application system, yet applicants frequently contact staff to ask whether documents have been received and what will happen next.

Situation and problem

Applicants report that the process is confusing. The portal uses formal language, email messages come from different addresses, and applicants must repeat their application number when moving from email to telephone. International applicants are uncertain about document certification, while applicants with disabilities report difficulty navigating some portal functions. Admissions staff spend considerable time answering status questions rather than assessing applications.

Analysis

A research team conducted interviews with applicants, observed admissions staff, reviewed contact-centre records, and analysed portal events. The current-state journey showed five major stages: discovering requirements, preparing documents, submitting the application, waiting for a decision, and accepting an offer. The most important pain point occurred after submission. The portal confirmed receipt of the application but did not clearly distinguish between “application received,” “documents under review,” and “additional information required.”

The service blueprint showed that the portal, document-management system, and admissions case system were not fully synchronized. Staff updated one system while applicants viewed another. The organization had a process for correcting missing documents, but ownership was unclear. The blueprint also identified a policy requiring applicants to contact a central office before staff could update certain records, creating avoidable transfers.

Approach and solution

The university formed a co-creation group containing applicants, admissions advisers, accessibility specialists, IT staff, and compliance representatives. The group developed a future-state journey with a single status vocabulary, a secure message centre, and a visible next-action field. Applicants would receive a persistent case reference across portal, email, and telephone channels. Staff would see the same status information as applicants and would be authorized to correct defined document-record errors.

Before full implementation, the team tested paper prototypes of status messages and a clickable portal design. Testing revealed that applicants interpreted “processing” as a final decision. The wording was changed to “your documents are being checked; no action is required at present.” An accessible version was tested with screen-reader users and with applicants using mobile devices. A limited pilot was then conducted for one postgraduate programme.

Outcome

The pilot produced a measurable reduction in repeat status contacts and improved applicants’ understanding of the next step. Staff reported fewer transfers and clearer ownership of exceptions. The pilot also identified a new issue: some automated messages were sent before manual document checks were complete. The university therefore added a release rule requiring system status changes to pass a validation check.

Learning points

The case demonstrates that a visible customer problem may originate in backstage integration and policy rather than employee attitude. It also shows why omnichannel improvement requires consistent data, shared terminology, employee authority, accessibility testing, and controlled prototyping. Most importantly, the university treated applicants and employees as sources of knowledge and used measures linked to the identified pain point.

Challenges, limitations, and professional governance

Journey maps can become politically attractive but operationally weak. Common mistakes include mapping the ideal process instead of the lived experience, using unsupported personas, treating workshops as research, confusing touchpoint volume with importance, and stopping at visualization without assigning ownership. Another danger is “map theatre”: producing a polished artefact that is not connected to budgets, targets, process redesign, or governance.

Maps also simplify reality. Different customers may experience different journeys, and emotions are difficult to measure consistently. A map can become outdated when systems, policies, partners, or customer expectations change. It should therefore have an owner, evidence record, review date, and change-control process.

Ethically, research participants must understand how their information will be used. Sensitive data should be collected only when necessary, protected appropriately, and retained for a justified period. Organizations should avoid designing only for profitable or digitally confident customers. Accessibility and non-discrimination should be treated as quality requirements, not optional enhancements.

Governance should clarify who owns each stage, who approves changes, how exceptions are handled, and how performance is reviewed. Regulatory obligations may apply to privacy, accessibility, consumer protection, financial services, healthcare, education, or records management. Service design cannot override legal rights or professional duties.

Current developments and best practices

Several developments are shaping contemporary service design. Organizations increasingly use real-time journey signals to identify failed payments, abandoned applications, or repeated contacts before a complaint is made. Digital twins and process-mining techniques allow teams to model operational consequences of proposed changes. Generative AI is being explored for research synthesis, content drafting, conversational interfaces, and design ideation, but its outputs require human validation and careful control of confidential information.

The most reliable practice is to combine human research with operational evidence. A strong organization maps journeys at the level where decisions can be made, validates maps with affected users, links pain points to root causes, prioritizes by value and equity, prototypes before large investment, and monitors outcomes after implementation. It also treats employees as participants in service quality rather than as obstacles to automation.

Service design should ultimately become part of the improvement system. Journey maps inform problem selection; blueprints guide process redesign; prototypes reduce implementation risk; measures verify outcomes; and learning from failures feeds the next cycle of improvement. In this way, customer experience is connected to the disciplines of quality planning, assurance, control, and continual improvement.

Chapter Summary

Customer journey mapping represents the lived sequence of customer actions, interactions, perceptions, and problems. Service design extends this view by showing the frontstage, backstage, support, technological, and policy components required to deliver the service. Journey maps, service blueprints, process maps, experience maps, and ecosystem maps serve different but complementary purposes.

Effective mapping begins with a defined customer, goal, and journey boundary. It uses qualitative and quantitative evidence, validates the current state, identifies moments of truth and pain points, and applies root-cause analysis. Design thinking supports empathic research, problem definition, ideation, prototyping, and testing. Co-creation incorporates the knowledge of customers, employees, partners, and specialists. Omnichannel design requires continuity across channels, while inclusive design ensures that service quality is available to diverse users.

For TQM, the value of journey mapping lies in connecting customer outcomes to organizational processes and measurable improvement. Technology, analytics, and AI can strengthen discovery and delivery, but they require governance, privacy protection, accessibility, human oversight, and attention to unintended consequences. A map becomes valuable only when it leads to accountable action, measurable outcomes, and continual learning.

Key Terms

Journey map: A visual or structured representation of a customer’s experience across stages, actions, touchpoints, and perceptions.

Service design: The systematic design of customer-facing and operational elements required to deliver a service.

Service blueprint: A map linking customer actions with frontstage, backstage, support, and evidence layers.

Touchpoint: Any moment at which a customer encounters an organization, its service, communication, or partner.

Channel: The medium through which a service interaction occurs, such as a branch, website, telephone, or application.

Moment of truth: An interaction that significantly shapes the customer’s judgement of the service.

Pain point: A difficulty, failure, delay, or source of dissatisfaction in a customer journey.

Customer effort: The time, cognitive, emotional, physical, or financial burden required to complete a task.

Frontstage: Service activities visible to or directly experienced by the customer.

Backstage: Internal activities that support service delivery but are normally invisible to the customer.

Service evidence: Physical or digital artefacts through which customers experience or interpret a service.

Omnichannel experience: A coordinated experience in which customers can move across channels with continuity.

Co-creation: Collaborative development of a service with customers, employees, partners, or other stakeholders.

Prototype: A preliminary representation or pilot used to test a service concept or feature.

Inclusive design: Designing services to be usable and equitable for people with diverse abilities, needs, and contexts.

Process mining: The analysis of event-log data to reconstruct and evaluate actual process paths.

Customer effort score: A measure of how easy or difficult customers perceive a task or interaction to be.

Service recovery: Actions taken to correct a service failure, restore trust, and learn from the cause.

Ecosystem map: A representation of the actors and relationships influencing service delivery and experience.

Review Questions

Short Answer Questions

1. What is the difference between a touchpoint and a channel?

2. Why should a journey map be based on actual customer behaviour rather than the ideal process?

3. What is the purpose of the line of visibility in a service blueprint?

4. Define customer effort and identify two forms it may take.

5. Why is validation important after preparing a journey map?

Long Answer Questions

1. Explain how customer journey mapping contributes to Total Quality Management.

2. Compare a customer journey map, service blueprint, process map, and ecosystem map.

3. Describe the use of design thinking, co-creation, and prototyping in service improvement.

4. Explain the requirements for designing a coherent omnichannel experience.

5. Discuss the ethical and governance issues involved in using AI and customer data in service design.

Analytical / Application Questions

1. A hospital receives complaints that patients repeatedly provide the same information at registration, consultation, and billing. Construct a short analysis of the likely journey and blueprint failures, and recommend measures to investigate the root cause.

2. A retailer has excellent digital sales but poor accessibility for customers who rely on screen readers or telephone support. Design an inclusive research and prototyping approach for improving the journey.

3. Using the Northbridge University case, identify two leading indicators and two outcome indicators that should be monitored after full implementation. Explain why each is appropriate.

22. Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes a service blueprint from a customer journey map?

A. A blueprint focuses only on customer emotions, while a journey map focuses only on costs.

B. A blueprint connects customer actions with frontstage, backstage, support, and evidence layers.

C. A blueprint is used only for digital services, while a journey map is used only for physical services.

D. A blueprint excludes operational processes so that it remains customer-centred.

Correct Answer: B. A blueprint connects customer actions with frontstage, backstage, support, and evidence layers.

Question 2

A customer must repeat information every time a chatbot transfers the interaction to a call-centre employee. Which issue is most directly indicated?

A. Excessive personalization

B. Insufficient channel continuity and context transfer

C. Overuse of physical evidence

D. Failure to create a customer persona

Correct Answer: B. Insufficient channel continuity and context transfer

Question 3

Which research approach would best reveal why applicants abandon an online application after uploading documents?

A. Reviewing only the organization’s process manual

B. Measuring annual revenue without examining user behaviour

C. Combining portal analytics with interviews or contextual inquiry

D. Asking managers to estimate the cause

Correct Answer: C. Combining portal analytics with interviews or contextual inquiry

Question 4

In a service blueprint, the activity of checking a document in an internal system is most likely classified as:

A. Customer action

B. Backstage activity

C. Physical evidence

D. External advertising

Correct Answer: B. Backstage activity

Question 5

Why is a prototype useful in service design?

A. It guarantees that a service will succeed after launch.

B. It allows a specific concept or assumption to be tested before major investment.

C. It eliminates the need for customer research.

D. It replaces operational performance measurement.

Correct Answer: B. It allows a specific concept or assumption to be tested before major investment.

Question 6

Which measure is most directly related to the pain point of customers being uncertain about application status?

A. Number of office locations

B. Repeat status contacts and customer understanding of the next step

C. Total number of employees in the organization

D. Annual advertising expenditure

Correct Answer: B. Repeat status contacts and customer understanding of the next step

Question 7

An organization automates an inaccurate process and thereby sends incorrect notifications to more customers. What lesson does this illustrate?

A. Automation always reduces customer effort.

B. Technology should be applied before the process is understood.

C. Automation can increase the scale of an underlying process failure.

D. Customer journeys are unrelated to backstage processes.

Correct Answer: C. Automation can increase the scale of an underlying process failure.

Question 8

Which practice best reflects inclusive design?

A. Designing exclusively for the average digitally confident customer

B. Providing a premium experience only through mobile applications

C. Testing the service with users having varied abilities and contexts

D. Removing human escalation to improve efficiency

Correct Answer: C. Testing the service with users having varied abilities and contexts

Question 9

A journey map shows many complaints at one touchpoint, but root-cause analysis reveals that the problem originates in an incompatible database. What does this demonstrate?

A. Customer-facing problems may originate in backstage systems.

B. Touchpoints are always the root cause of service failures.

C. Complaint data cannot support service design.

D. Blueprints should exclude technology.

Correct Answer: A. Customer-facing problems may originate in backstage systems.

Question 10

Which is the strongest governance practice for a journey map?

A. Treating it as a permanent representation that never requires revision

B. Assigning ownership, recording evidence, setting a review date, and linking it to improvement actions

C. Allowing only senior managers to interpret it

D. Using it as a substitute for legal and accessibility review

Correct Answer: B. Assigning ownership, recording evidence, setting a review date, and linking it to improvement actions