PLANNING

Service design canvas

This service design canvas connects a student-facing room booking experience to the work that supports it. Students need to reserve a room and trust that it will be available when they arrive. The frontstage section lists the interactions they see, from search to confirmation and check-in. The backstage section makes the less visible calendar, access control and staff response work explicit. The measures include both completion and no-show rates, plus student confidence in availability. A team can use the canvas to identify where a service promise fails: an interface may be clear while the calendar is inaccurate, or a room may be booked but inaccessible. The canvas supports a practical conversation across service owners.

UPDATED 2026-09-24
TYPEMatrix
EXAMPLEService design canvas
Make this diagram your own.

Open it in the AI editor with a prompt pre-filled — keep what works, change what doesn't.

CASE ANALYSIS

Scenario

A university library is improving how students book and access group study rooms.

Key decisions

  • Start with a goal: Describe the outcome students need, not only the booking interface.
  • Reveal delivery: Include staff and systems that make the promise possible.
  • Choose measures: Track both operational results and customer confidence.

When to reuse this

Use for services where visible interactions depend on internal people, systems and policies.

FAQ

Frequently asked questions

What does frontstage mean?01
Frontstage is the part of a service customers directly see or interact with.
What does backstage mean?02
Backstage is the staff work, systems and policies that enable the customer-facing service.
Why include customer confidence?03
A service can be operationally fast while still feeling unreliable to the people using it.
Open this example in the editor →

Tweak it with chat, export PNG/SVG, or fork it for your own use case.