What is Service Design?

Understanding how services are delivered across multiple touchpoints and backstage operations

The framework

Overview

Service Design maps how a service is actually delivered: the actors involved, the touchpoints customers meet, and the behind-the-scenes processes that make it work. Unlike product design, which focuses on a single artifact, it treats the whole network as the thing being designed. It is the second of the two perspectives RoleDream unifies — see How RoleDream Connects Them.

"Services are experiences, not objects. Service design maps the flow of people, touchpoints, and processes that shape the customer experience."

Building blocks

Core Concepts

Frontstage

Everything the customer sees and interacts with directly. This includes customer-facing staff, interfaces, physical spaces, and touchpoints.

Backstage

Operations and processes that happen behind the scenes to support the frontstage experience. Customers don't see this, but it's essential for service delivery.

Touchpoints

Specific moments of interaction between the customer and the service. Each touchpoint is an opportunity to create (or destroy) value.

Service Actors

Everyone involved in delivering the service: customers, employees, partners, systems. Each has different goals and perspectives.

Support Processes

Infrastructure, systems, and organizational functions that enable the service. Includes technology platforms, policies, and logistics.

Physical Evidence

What customers physically encounter during the service — the details that prove quality and shape lasting impressions.

The tool

The Service Blueprint

Service Design's primary tool is the service blueprint—a visual map showing how a service works across multiple layers:

PHYSICAL EVIDENCE

Tangible items customers see/use (receipts, packaging, app UI)

CUSTOMER ACTIONS (Frontstage)

What the customer does (browse menu, place order, receive delivery)

FRONTSTAGE EMPLOYEE ACTIONS

Visible employee interactions (driver delivers food, support chat)

Line of Visibility

Everything below this line is invisible to customers

BACKSTAGE EMPLOYEE ACTIONS

Internal operations (restaurant prepares food, logistics routing)

SUPPORT PROCESSES

Infrastructure (payment processing, inventory systems, customer database)

Why This Matters

By mapping all layers, you can identify where things break down, optimize handoffs between actors, and design cohesive experiences that work for both customers and employees.

In RoleDream

How RoleDream Maps to Service Design

RoleDream's unified data model makes it ideal for service design. Here's how RoleDream entities correspond to service design concepts:

RoleDream for Service Blueprints

Segments — the top Blueprint band: who delivers the service and who it serves
Jobs — the needs the service is organized around
Solutions — the service journeys that fulfil a job
Solution Steps — the ordered activities within a journey
Staged Resources — each step's tools and systems sit in the Frontstage or Backstage lane, drawing the line of visibility

Service Design Workflow in RoleDream

Create Segments for who the service is for (e.g., "Home diners")
Create Segments for who delivers it (e.g., "Delivery Drivers", "Chefs"), typed as teams or roles
Add Jobs for what each segment needs done or performs, linked segment ↔ job
Add a Solution per journey and break it into Solution Steps
Stage each step's resources in the Frontstage or Backstage lane — the line of visibility
Select a segment on the Blueprint to read its complete service blueprint end to end

Service Design Terminology Mapping

Here's how traditional service design terms map to RoleDream:

Service Blueprint Term	RoleDream Equivalent
Actors	Segments — customers, teams, groups, and individual positions alike
Customer Actions	Solution Steps of the customer segment's job
Frontstage	Resources staged in the Frontstage lane (customer-visible)
Backstage	Resources staged in the Backstage lane (internal)
Line of Visibility	The boundary between the two staging lanes under each step
Support Processes	Resource hierarchies behind the staged resources
Physical Evidence	Resources (type: artifact or document)

Example

See It Applied

The food delivery walkthrough maps a complete service — the actors, one job with competing solutions, the step tree, and the resources staged behind each step.

Food Delivery Example How RoleDream Connects Them