University of Melbourne · FACULTY OF MARKETING

MKTG90041 Chap.6 Journey Maps and Service Blueprints

- one subject, every graph, every model, every mark
6 Chapters3-page Bible
Our own words - no uploaded lecturer files
Updated for this semester
Chapter 6 of 8 · MKTG90041

Journey Maps and Service Blueprints

A journey map follows customer progress across stages, actions, touchpoints, thoughts, feelings, pain points and opportunities. It makes the whole experience visible, especially the gaps created when different channels or teams each optimise their own interaction.

A service blueprint turns the map toward delivery by connecting customer action to visible employee behaviour, backstage work, support processes, systems and evidence. This chapter explains how to define a useful boundary, distinguish current and future states, locate moments of truth and trace a customer failure to the organisational mechanism that produces it.

In this chapter

What this chapter covers

  • 01

    Journey purpose, actor, start, end and level of detail

  • 02

    Stages, actions, touchpoints, thoughts, emotions and pain points

  • 03

    Moments of truth and handoffs that shape the whole experience

  • 04

    Current-state evidence versus future-state design hypotheses

  • 05

    Frontstage, backstage, support process, system and evidence layers

  • 06

    Failure tracing from customer symptom to operational cause and owner

Worked example · free

AskSia practice weighting: blueprint a repair booking

Q [6 marks]. A customer books an appliance repair online, receives confirmation, then calls twice because the appointment window is not visible and the agent cannot see the web update. Diagnose the journey and blueprint failure. The marks used here are not an official University marking scheme.
  • 1Set the journey boundary from recognising the fault to receiving a confirmed repair outcome.
  • 1Place booking, confirmation, waiting, status checking and service in customer sequence.
  • 1Mark uncertainty before the appointment as a moment of truth rather than treating each call separately.
  • 1Connect the visible web confirmation and agent response to backstage scheduling and case data.
  • 1Identify the support failure: channel systems do not share appointment-window status.
  • 1Propose one owner and measure repeated contact, visible-status comprehension and kept appointments.
The customer experiences one repair journey, even though the organisation sees a web booking and two calls. The critical failure is invisible and inconsistent appointment status. In the blueprint, customer status checking links to frontstage web and agent responses, backstage scheduling, the case record and integration rules. A future state should provide one governed status across channels, an escalation path and measures at journey scale.
Sia tip — Start with the customer action row. Add organisational layers only when they explain how that action is enabled, constrained or repaired.
Glossary

Key terms

Journey boundary
The explicit actor, purpose, start and end that determine what the map includes.
Journey stage
A meaningful phase of customer progress that contains one or more actions and touchpoints.
Moment of truth
A point with disproportionate influence on trust, progress, choice or the overall experience.
Handoff
A transfer of customer need, information or responsibility between channels, roles or teams.
Current-state map
An evidence-based representation of how the journey operates now, including workarounds and failures.
Future-state map
A proposed experience that makes design hypotheses and intended changes explicit.
Frontstage
People, actions and artefacts visible to the customer during service delivery.
Backstage
Work hidden from the customer that enables or constrains the visible service.
Support process
A policy, capability, workflow or function that supports frontstage and backstage delivery.
Line of visibility
The boundary separating what customers can observe from internal service activity.
FAQ

Journey Maps and Service Blueprints FAQ

What makes a journey boundary useful?

It should follow a customer purpose rather than one department. Name the actor, the progress being pursued, a meaningful start and a meaningful end. A boundary is too narrow when it hides the handoff causing the problem and too broad when stages cannot be researched or acted on.

Is a touchpoint list a journey map?

No. A touchpoint list records interactions but may miss sequence, customer purpose, time, emotion, handoffs and the relationship between interactions. A journey map shows how the connected experience helps or obstructs progress.

How should emotion be represented?

Emotion should be grounded in research rather than drawn as a decorative curve. Link each emotional state to an event, observation or quote, preserve uncertainty where evidence is weak and avoid averaging away differences that matter.

Why separate current and future states?

The current state reports evidence about existing behaviour and delivery. The future state is a design proposition. Combining them can make an aspiration look observed and can hide which new process, role, system or assumption still requires testing.

What does a service blueprint add?

It explains how the experience is produced. By aligning customer action with frontstage, backstage, support and system layers, it reveals operational causes, dependencies and ownership that a customer-facing map alone may not show.

How detailed should the blueprint be?

Include enough detail to explain the priority journey moments and enable a delivery decision. A blueprint is not a complete process manual. Select the actions, roles, rules and systems relevant to the customer problem and proposed future state.

What should be measured after redesign?

Combine customer and operational evidence. For a status problem, measures might include comprehension of the next action, repeated contact, transfer rate, elapsed time, failure recovery and completion. The measure should correspond to the job and journey outcome.

Study strategy

Exam move

Build maps from a short scenario without drawing first. Write the actor, purpose, start, end and evidence boundary. List customer actions in time order, then add touchpoints, thoughts, emotions and pain points only where supported. Circle moments of truth and mark every transfer of information or responsibility. For a future state, label each changed element as a hypothesis.

Next, choose one priority moment and construct a narrow blueprint: customer action, visible response, backstage work, support process, system dependency and evidence. Trace a failure downward until a plausible mechanism and owner are visible, then trace the proposed improvement upward to a customer outcome.

Compare local touchpoint measures with journey measures so that a successful channel does not conceal repeated effort elsewhere. Review the map from right to left as well as left to right. Reverse reading exposes prerequisites and information that must already exist before a promise can be kept. Mark any stage where the customer currently supplies missing integration work.

Working through Journey Maps and Service Blueprints in MKTG90041? Sia is AskSia’s AI Marketing tutor — ask any MKTG90041 Journey Maps and Service Blueprints question and get a clear, step-by-step explanation grounded in how MKTG90041 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.

A+Everything unlocked
Unlocks this Bible + all 177 of your University of Melbourne subjects - and 1,000+ Bibles across every Australian university.
Sia - your MKTG90041 tutor, unlimited, worked the way the exam marks it
The full 3-page Bible + practice bank with worked solutions
Chrome extension - sync your LMS so Sia knows your deadlines
Bilingual EN / Chinese on every Bible and every Sia answer
$0.99 Trial
30-day money-back · cancel in one tap · how it works