Service Blueprint for Beginners: 4 Layers to Find Where the Experience Breaks Down

Business & Strategy

Service Blueprint for Beginners: 4 Layers to Find Where the Experience Breaks Down

A beginner template for a first service blueprint, lining up customer actions, frontstage, backstage, and support in four layers to find where the experience breaks down. The whiteboard has four pages - page 1 sets the scene and lists customer actions in five steps, page 2 fills the four layers and notes waits, confusion, and gaps, page 3 picks the breakdown by impact/frequency and writes the As-Is/To-Be gap, and page 4 assigns an owner and deadline, tests the fix, and sets the next redraw date. The task board has five columns from 'Get ready to draw' to 'Done', with four parent tasks and three subtasks each. Swap the salon example for your own service and fill it in top to bottom, one page at a time. Frontstage is what the customer sees, backstage is unseen staff work, and support is the tools, systems, and rules behind it. It suits teams improving a store, counter, or online service, or mapping the internal side after a journey map.

0 Likes 0 Copies Author: WeProcess
service blueprint customer experience process improvement As-Is/To-Be for beginners
Other language versions
Sign up free and use this template

Once you have a free account, you can copy this template from the marketplace

Whiteboard preview

Preview mode Service Blueprint for Beginners: 4 Layers to Find Where the Experience Breaks Down
Sign up free and use this template

Whiteboard preview

① The Scene and Goal to Map (start here) ② Customer Actions ③ Frontstage (visible to the customer) ④ Backstage (not visible to the custo... ⑤ Support Processes ⑥ Flow of Customer Actions (5 steps l... ⑦ The Three Lines (drawn between laye... ⑧ The Four-Layer Blueprint (turn the ... ⑨ Where the Customer Waits ⑩ Where Staff Get Confused ⑪ Where Support Is Missing ⑫ Pick the Breakdown (place the notes... Big impact × occasional Big impact × frequent Small impact × occasional Small impact × frequent ⑭ Where the Cause Is (the 3 items pic... ⑮ What to Fix (choose from the cause ... ⑯ Flow for Testing and Checking ⑰ Next Redraw Date and Carry-Overs Service Blueprint... How to use (4 pag... Goal & desire... Rules, lines &amp... Breakdowns & ... Insights & ca... 1/4 Pick your scene Ctrl+F / ⌘F : 2/4... → 2/4 2/4 Map the four layers ↙ 3/4 Scene to mape.g. A salon booking, from reservation to checkout(a first-time customer) Goale.g. Reduce complaints about wait times after arrival Scope and participantse.g. Start = books an appointment, end = pays and leavesParticipants: receptionist, stylist, manager Write the actions the customer takes on their own e.g. Books, waits, pays Always keep the customer as the subject The staff and screens the customer sees moving e.g. Receptionist's greeting, booking confirmation email Where the customer interacts directly Staff work the customer doesn't see e.g. Copying the booking into the ledger, prepping tools Work people do to support the frontstage Tools, systems, and rules people use e.g. Booking app, paper ledger, cash register Write things and rules, not people 1 Booke.g. At home, via the phone booking appPlace the starting action here 2 Check ine.g. At the entrance desk 3 Waite.g. On the sofa next to the desk 4 Get the servicee.g. In the styling chair 5 Pay and leavee.g. At the register by the entrancePlace the ending action here Line of interaction (between ② and ③)Where the customer touches staff or a screen.e.g. Giving your name at the deskIn this case: ____ Line of visibility (between ③ and ④)Below this line, the customer can't see.e.g. Flipping through the ledger behind the deskIn this case: ____ Line of internal interaction (between ④ and ⑤)Where staff use tools or systems.e.g. Copying from the ledger into the booking appIn this case: ____ 1 Book 2 Check in 3 Wait 4 Get the service 5 Pay and leave Customer action e.g. Chooses date, time, and menu e.g. Gives their name e.g. Waits to be called e.g. Checks the result e.g. Pays in cash Frontstage e.g. Booking confirmation email e.g. Receptionist looks up the booking e.g. No update given e.g. Stylist checks the finish e.g. Offers the next booking at the register Backstage e.g. Copies the booking into the ledger e.g. Flips through the paper ledger e.g. Previous customer's service runs long e.g. Preps the products e.g. Tallies sales by hand Support e.g. Booking app e.g. Paper booking ledger e.g. None (no way to share wait times) e.g. Paper client card e.g. Register (no card payments) e.g. Waits 20 minutes on the sofa after checking in e.g. Not called even past the booked time Note which column of ⑧ it relates to Also write roughly how long they waited (minutes) e.g. Receptionist searches the ledger for the booking e.g. No one decides who greets the customer Look in the Backstage row of ⑧ Also write how often it happens (per day) e.g. Booking app and ledger aren't connected e.g. No way to tell customers about the wait Look in the Support row of ⑧ Cells marked "None" are candidates too 3/4 Pick the root cause → 4/4 4/4 Fix and check 縦軸: Impact on the... e.g. A booking isn't moved to the ledger and two people get the same slot. Just decide how to handle it if it happens. The first candidate to fix. Pick 3 from here, write the first on ⑬, and all 3 on ⑭. e.g. Waiting 20 minutes after check-in Just log it and skip it for now. Look again at the next redraw. If it's a quick fix, fix it on the spot. e.g. An old sign in the store ⑬ Gap Analysis (A... As-IsCurrent state Write the current state in facts and numberse.g. Average wait after check-in is 20 minutes, with no explanation given Gap & Issue The gap between current and desired statee.g. The wait is 15 minutes too long, and customers don't know why or for how long To-BeDesired state The state you wante.g. Wait under 5 minutes, with the reason and estimate given Layer where sympt... Layer with the cause What the cause is Breakdown 1 e.g. Customer action (waiting) e.g. Support e.g. No way to tell the desk or customer when the service runs long Breakdown 2 e.g. Frontstage (check-in) e.g. Backstage e.g. No fixed way to look up bookings in the ledger Breakdown 3 e.g. Frontstage (payment) e.g. Support e.g. Register doesn't take card payments Fix Layer to fix Owner & deadline How to check Item 1 e.g. Add a tool to tell the desk when a service is running long e.g. Support e.g. Manager, in 1 month e.g. Record wait times daily Item 2 e.g. Set a fixed way to look up bookings e.g. Backstage e.g. Receptionist, in 2 weeks e.g. Measure lookup time (minutes) Item 3 e.g. Tell customers the reason and estimate for the wait e.g. Frontstage e.g. Receptionist, in 1 week e.g. Hear from 3 customers a day Item 4 e.g. Enable card payments e.g. Support e.g. Manager, in 2 months e.g. Share of non-cash payments 1 Try it smallTest with one day of the week or one person for 2 weeks 2 Measure itRecord wait times and the like the same way you measured the As-Is on ⑬ 3 Compare to To-BeSee if you reached the To-Be on ⑬. Keep customer comments too 4 Decide to expandIf you reached it, roll it out fully. If not, go back to ⑭ and rethink the cause Next redraw datee.g. Redraw the table in ⑧ 1 month after starting the fixDate: ____ Numbers to check thene.g. Wait time after check-in (minutes), time to look up a booking (minutes) Breakdown carried forwarde.g. The occasional double booking not picked this time in ⑫ → 2/4 Map the four layers ↙ 3/4 Pick the root cause → 4/4 Fix and check
100%

Drag to move, scroll to zoom

Task board contents

Get ready to draw 16 items

Pick your scene
Map the four layers
Pick the root cause
Fix and check
Set scene and goal
Learn layers & lines
List customer steps
Fill the layer grid
Mark wait points
Mark missing tools
Pick by impact/rate
Write As-Is/To-Be
Table the causes
Assign fix & owner
Test and measure
Set the redraw date

Drafting layers 0 items

Finding the cause 0 items

Testing the fix 0 items

Done 0 items

Related templates

← Back to templates