Service Blueprint Lite

Draw a service as the person receiving it meets it, then draw the work they never see underneath, and find which hidden step produces which visible pain.

Service blueprinting is a practitioner design method from service scholars, widely used and without outcome studies showing that blueprinted services perform better (Shostack, 1982; Bitner, Ostrom & Morgan, 2008). The AI note is consulting practice (Bain/NPS Prism, 2026). Time ratios and ratings are rules of thumb.

Use it when:

• A service is slow, inconsistent or complained about and the team argues about the symptoms.
• You are redesigning a process that a customer, employee or partner goes through and several departments are involved.
• You want to add automation or AI to a service and need to see what the person actually meets.

Skip it when:

• You only need to see the person's experience, not the machinery: use 6.3 Customer Journeys Map or 6.13 Stakeholder Journey Map.
• You want to map the internal process in detail, step by step: use 8.1 Process Map (Current State).

Service blueprinting claims that a service succeeds or fails as a system: what the person meets in front is produced by work they never see, so fixing only the visible layer treats symptoms. The method's contribution is the line of visibility, which makes you document both sides and the links between them. It was proposed as a way to design services with the rigor products get (Shostack, 1982) and later set out as a practical innovation technique (Bitner, Ostrom & Morgan, 2008). The evidence is honest but thin: this is a design method, and no study cited here shows better results from using it. Its worth is diagnostic, because much visible friction has an invisible cause.

The lite format keeps the mechanism and drops the ceremony: four steps, each with a visible side, a hidden side and the time taken. It then asks who absorbs the complexity, the person receiving the service or you. An automated step is still a visible step produced by hidden choices.

Pick a service small enough to draw in one sitting, from the receiver's first action to the last.

Strong answer: "Applying for a parental-leave top-up, as an employee, from the first form to the payment." Not "HR".

Service: Receiver: Why it matters now:

Illustrative example: the organization and all times are made up.

A municipal housing office in Norway blueprints "apply for a housing allowance". Applicants complain about weeks of silence.

Step 1: service: housing allowance application. Receiver: a resident.

Step 2: step 1, the resident fills a form online (smooth). Step 2, receives "we have your application" (okay). Step 3, waits (frustrating). Behind step 3: a caseworker checks income against a second system and asks a manager to sign off; up to ten working days (illustrative).

Step 3: visible pain "no news for weeks", hidden cause "every case needs a manager's signature". Fix difficulty: easy.

Step 4: resident spends 20 minutes but waits 14 days; the office spends 90 minutes. The resident absorbs the approval chain.

Step 5: manager signs off only cases above a set amount, and the system sends a status message when the check starts. Owner: head of the office.

The page changes one thing at once: the signature rule, not the website.