Service blueprints: connect your website to what happens next

Key takeaways

A service blueprint maps what the customer does and sees alongside what your team and systems do behind the scenes to deliver it. For website planning, it shows whether the promises on your pages, such as 'reply within two hours', are backed by a real process. Draw one for your main enquiry-to-delivery journey before you publish promises the business cannot keep.

• A blueprint shows customer actions, frontstage, backstage and processes.
• The line of visibility separates what customers see from what they do not.
• Every website promise should trace to a backstage process with an owner.
• One blueprint for the main enquiry-to-delivery journey is enough to start.

What is a service blueprint?

A service blueprint is a diagram that shows the relationships between the parts of a service: what customers do, what staff do in front of them, what happens behind the scenes and the systems that support it. Nielsen Norman Group defines it as a diagram that visualises the relationships between different service components. The idea dates back to Lynn Shostack's 1984 Harvard Business Review article on designing services.

• How to design a website around your customer journey
• Customer touchpoints: where your website fits in the journey

What are the parts of a service blueprint?

A service blueprint has five layers. Customer actions are what the buyer does. Frontstage actions are what they see your people or technology do. Backstage actions support those out of sight. Processes are the internal steps and systems that make it all work. The line of visibility separates what customers see from what they do not.

• Customer actions: submits form, receives call, books visit, pays.
• Frontstage: confirmation page, reply email, phone call, visit.
• Backstage: enquiry assigned, diary checked, quote drafted.
• Processes: CRM, calendar, quoting tool, payment system.
• Line of visibility: what the customer sees above, what they do not below.

• Customer journey mapping for small businesses in one day

How is a service blueprint different from a journey map?

A journey map shows the customer's experience: what they do, ask and feel. A service blueprint shows how the business delivers that experience. You usually draw the journey map first, then a blueprint for the parts of the journey that depend on your internal process, such as the steps after an enquiry. The blueprint explains why a journey step works or breaks.

• A customer journey map template for website planning

Why does a service blueprint matter for your website?

A service blueprint matters because the website makes promises the business must keep. 'We reply within two hours', 'book online in a minute' and 'free survey within 48 hours' are frontstage promises. If nobody owns the backstage step, the promise breaks and the buyer remembers the website as misleading. The blueprint checks every promise against a process.

• After the enquiry: designing the journey to the first call
• When your website and sales process do not match

How do you draw a simple blueprint?

Draw a simple blueprint by taking one journey, usually enquiry to first appointment, and writing the customer's steps across the top. Under each, add what they see from you, then what your team does behind the scenes, then which system is involved. Mark any step with no owner, no system or a long wait.

• Choose one journey: enquiry to first appointment is a good start.
• Write customer steps across the top.
• Add frontstage, backstage and process rows under each.
• Draw the line of visibility.
• Mark gaps: no owner, no system, long waits.
• List website promises that depend on each gap.

• Running a customer journey workshop with your team

When is a service blueprint unnecessary?

A blueprint is unnecessary for very simple services where one person handles everything and the steps are obvious. It earns its place when several people, systems or suppliers touch the journey, or when the website is about to promise something new, such as online booking or same-day replies.

What does this look like in practice?

A pattern we see when blueprinting enquiries: the form sends an email to a shared inbox that three people check 'when they can'. The website promises a reply the same day. On busy days, enquiries wait until the next afternoon, and the buyers most likely to convert, the urgent ones, go elsewhere.

Assigning an owner and a check time, or routing enquiries to a dedicated team, makes the promise true. Across our client work we have seen a 2.4x enquiry rate from conversion changes of this kind. Global Bridge Labs (GBL) blueprints the steps behind the form when we build it.

• See client work
• Website Design & Development for UK businesses
• outsourced customer support for UK SMEs

Service blueprint checklist

• Pick one journey that depends on internal process.
• Map customer actions, frontstage, backstage and processes.
• Mark the line of visibility.
• Give every backstage step an owner.
• Check every website promise against a step.
• Fix or remove promises with no process behind them.

• Finding customer journey pain points, on and off your website

Next step

If your website promises fast replies or easy booking, it is worth checking the process behind it. We will blueprint the steps after your form and show any gaps.