Service · Systems

Service Journey Blueprinting

Mapping service dependencies and operational touchpoints to enable cross-functional alignment

Service design

Systems Thinking

Cross-functional

Enterprise

Service blueprint showing links between customer touchpoints, teams, systems and operational processes.

Overview

Role

Service Designer

Brand

Vodafone

Focus

Service Design & Systems Mapping

Methods

Service Blueprinting, Workshops, Journey Mapping, Stakeholder Facilitation

Outcome

Shared service visibility across product, engineering, and operations

Timeline

Q2-Q3, 2024

The Challenge

SIM-only and wearable service journeys involved many digital touchpoints, internal systems, teams, and operational processes.

Without a clear picture of how customer-facing experiences connected to backend systems and operational workflows, teams were making improvements in isolation — sometimes creating downstream problems they couldn't see.

The objective was to create a clear service blueprint that visualised both the customer-facing journeys and the internal systems and processes supporting them.

SIM-only and wearable service journeys involved many digital touchpoints, internal systems, teams, and operational processes.

The objective was to create a clear service blueprint that visualised both the customer-facing journeys and the internal systems and processes supporting them.

Business Requirements

Create shared visibility of end-to-end service journeys across teams

Identify operational and delivery gaps impacting service quality

Enable coordinated improvements across product, engineering, and operations

Establish a reusable service design framework for future journeys

Challenges

Limited visibility of how systems and teams supported the journeys

Fragmented ownership across product, engineering, and operations

Operational and delivery gaps were difficult to identify without a systems view

Coordinating improvements across the full service experience was challenging without shared documentation

Risks & Constraints

Tribal knowledge dependency — much of the operational and systems knowledge existed only in the heads of individuals across teams. Surfacing and documenting it required significant facilitation effort rather than desktop research.

Fragmented ownership — no single team had full visibility of the end-to-end journey. Ownership was split across product, engineering, and operations, making alignment workshops complex to facilitate and time-consuming to run.

Multiple systems involved — the journeys spanned multiple platforms and system dependencies, each owned by different teams with different priorities and release cycles.

No existing framework — there was no established service design methodology or blueprint template within the organisation. The framework had to be developed and validated as part of the project itself.

MY ROLE

What I owned

Service design methodology, blueprint structure, and facilitation across all mapping and alignment workshops. I defined the blueprint framework, led the mapping of customer touchpoints, display logic, ownership, and system dependencies across the SIM-only and wearables journeys, and facilitated the collaborative sessions where teams reviewed and identified gaps.

What others owned

Product, engineering, and operations contributed domain knowledge and validated the accuracy of the blueprint content. Technology leads confirmed system dependencies and integration points. Operations confirmed the accuracy of back-of-house processes mapped within each journey stage.

My Approach

Understand

Researched the SIM-only and wearables journeys to establish a picture of the customer-facing experience before mapping the supporting systems and processes beneath it.

Align

Facilitated workshops with product and technology leads to map the full service ecosystem — identifying key frontstage touchpoints, backstage operational processes, system dependencies, and ownership across teams.

Design

Developed service journey blueprints for SIM-only plans and wearables service journeys — visualising how customer interactions connected with operational workflows and system dependencies across the Narrow, Decide, Buy, and Use journey stages.

Validate

Facilitated collaborative workshops where teams reviewed the blueprint and identified operational gaps and improvement opportunities. The blueprint became a shared reference for product, engineering, and operations.

Key Decisions

Before

Teams working on individual parts of the journey with limited visibility of upstream and downstream dependencies. Fragmented ownership across product, engineering, and operations. Operational and delivery gaps were difficult to identify.

Fragmented & Unmapped

After

A shared service blueprint giving all teams visibility of the end-to-end journey — customer touchpoints, display logic, ownership, and system dependencies mapped across every stage.

Aligned & Mapped

Map Before Designing

Established a complete systems picture before any solution work began, preventing false starts and misaligned priorities.

Four-Layer Structure

Mapped Journey Stages, Display Logic, Ownership, and Systems as distinct layers within the blueprint, making dependencies and gaps immediately visible.

Facilitated Ownership

Used the blueprint as a facilitation tool in workshops, not just a documentation artefact, so teams could actively identify and discuss gaps rather than passively receive information.

Design for Reuse

Developed the blueprint structure to be repeatable across future service journeys, not just a one-off exercise.

Outcome & Impact

The blueprint made system and process ownership visible and surfaced gaps where responsibilities or interactions were unclear. I facilitated cross-functional alignment sessions with the relevant teams to work through those gaps, clarify ownership and build a shared view of how the service should operate.

Cross-functional Alignment

Teams developed a shared understanding of the end-to-end service, using facilitated alignment sessions to work through gaps in ownership and process.

Service & Operational Visibility

System dependencies, operational processes and their relationship to customer-facing journey stages became visible and documentable.

Living Service Reference

The blueprint became a shared reference across Product, Engineering and Operations as the service continued to evolve.

AI in my practice

AI tools supported my work in synthesising workshop outputs, structuring blueprint documentation, and preparing facilitation materials — allowing more time to focus on the quality of cross-functional conversations and the accuracy of what was mapped.

Tools used

Figma AI

Miro AI

Microsoft Copilot

ChatGPT

Miro AI

Used to rapidly synthesise notes from multi-team mapping workshops into themes and structured draft documentation, reducing turnaround time between sessions.

Microsoft Copilot

Used to help prepare workshop facilitation guides and discussion prompts for cross-functional alignment sessions.

ChatGPT

Used to help prepare workshop facilitation guides and discussion prompts for cross-functional alignment sessions.

Tools used

Miro AI

Microsoft Copilot

ChatGPT

AI in my practice

Tools used

Figma AI

Microsoft Copilot

ChatGPT

Miro AI

Used to rapidly synthesise notes from multi-team mapping workshops into themes and structured draft documentation, reducing turnaround time between sessions.

Microsoft Copilot

Used to help prepare workshop facilitation guides and discussion prompts for cross-functional alignment sessions.

ChatGPT

Used to help prepare workshop facilitation guides and discussion prompts for cross-functional alignment sessions.

Tools used

Miro AI

Microsoft Copilot

ChatGPT

Reflection

This project reinforced that effective service blueprinting is as much about facilitating shared understanding as documenting processes. The framework only became valuable because it gave product, engineering, and operations a common language for discussing complexity and making decisions together.