Skip to content
BENIBIX Learn

Service Design and Blueprints

Level 1 · What UX is

How to plan a whole service, both the screens people see and the work behind them. Service blueprints and customer journey maps.

Course contentsLesson 4 of 21

After this lesson you can

  • Say what service design covers
  • Read the rows of a service blueprint
  • Map how a journey feels step by step

11 mincovers 3 glossary entries

Worth reading first: User Flows and Edge Cases

How to plan the work behind the screen

Service design is planning a whole service, not just one screen. It covers what customers see and the work done behind it. A hotel check-in is a service. The booking site, the front desk, the cleaning team and the room system all have to work together, or the guest waits.

A service blueprint maps a service in rows. The top row is what the customer does: book, arrive, check in, get a key. Below that is the front stage, the staff the customer sees. Then the back stage, the work they do not see. The bottom row is the systems.

A line of visibility runs between front stage and back stage. The customer sees all that is above it. What is below it they only feel, as a wait or a mistake. The blueprint was first described in a business journal in 1984, and it is still drawn the same way.

The power of a blueprint is that it finds hidden causes. A guest waits at the desk. The blueprint shows why: the desk cannot hand over a key until the cleaning report says the room is ready, and that report is typed up late. No screen design fixes that.

A customer journey map tells the same story from the customer's side. It lists each stage, such as discover, sign up, first use, get help and come back. Under the stages, a line rises and falls to show how the person feels at each one. The lowest point is where to start.

The two maps work as a pair. The journey map shows where people feel bad. The blueprint shows what inside the company causes it. Teams that only draw the journey map know where it hurts and not why.

The common mistake is to treat a service problem as a screen problem. A slow refund feels like a bad app, so the team redesigns the app. The refund is still slow, because the hold-up was a person checking each one by hand.

The wait at the desk starts three rows down. The guest never sees the cleaning report, only the delay it causes.

Worked example

A clinic finds the slow step

A clinic drew a journey map. Patients felt worst while they waited to be called. The wait was about 25 minutes.

The blueprint showed why. Each file was printed and carried to the doctor by hand. Sending files to a screen cut the wait to 10 minutes.

The words for this lesson3

Check yourself

What does a service blueprint show that a journey map does not?

Finished this lesson?

Marking it complete also marks its 3 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.