Sample frameDay 203·Operations · Service

Morning. Everything that decides whether your service works sits below a line the customer never sees.

Operations.

The Service Blueprint

5 min read·Apply by lunch

The question

Think of the last complaint that reached you personally — the thing that arrived late, or wrong, or twice. Was the failure inside a step somebody owns, or in the handover between two people who'd each done their own part correctly? If it's the handover, it belongs to nobody. Nothing in your business is currently pointed at it, and it will happen again this month.

The idea

In 1984 the Harvard Business Review published Designing Services That Deliver by G. Lynn Shostack, then senior vice president in charge of the Private Clients Group at Bankers Trust. Her complaint was that manufacturers designed products from drawings, while service businesses designed by anecdote, goodwill and the hope that decent people would work it out on the day. Her answer was the blueprint. She took the simplest service she could find — a corner shoeshine — and drew it: brush, apply polish, buff, pay. Above a line of visibility goes everything the customer experiences. Below it goes everything that has to be true for those steps to happen at all: the supplies, the systems, the person who restocked the polish. Then she marked the fail points, and put a clock on the whole thing — a standard execution time of two minutes, decided rather than observed. The trap is treating a service as a sequence of steps performed by good people. It isn't. It's a set of crossings between what the customer sees and what they don't, and almost every failure you investigate this year will live at one of them.

The framework

01
Draw the line first, then fill in both halves.
Take one service you actually deliver — an order, an onboarding, a repair — and draw a horizontal line across a page. Above it, write only what the customer experiences, in their sequence and their words. Below it, write everything that has to happen for those steps to occur: the systems, the approvals, the supplier, the colleague who prepares something the night before. Most operations documentation only ever describes the bottom half, which is exactly why it reads as accurate and still doesn't explain what the customer felt.
02
The crossings, not the steps.
A step has an owner. A crossing usually doesn't. When a promise made at the front depends on a supplier confirming stock, or a salesperson's commitment depends on a delivery team who weren't on the call, the handover between them is where the service actually breaks — and it belongs to no one. Walk your blueprint and mark every arrow that crosses the line of visibility in either direction, then put a single name beside each one. You'll find most of them have never been anybody's job, and that is the finding.
03
Where will this break, and what happens next?
Shostack's blueprints marked fail points: the specific places where the service is most likely to go wrong, identified in advance rather than after a customer tells you. The discipline is asking, at every step, what the most probable failure is and what follows it — does the customer notice, does anybody below the line notice, and is there a recovery already designed? A service without designed recovery doesn't fail gracefully. It fails in front of the person paying, at the judgement of whoever happens to be standing there.
04
Every step above the line already has a clock. You just haven't set it.
Shostack's shoeshine carried a standard execution time — two minutes, set deliberately, so anybody doing the work knew what on time meant. Most services never make that decision. The reply to an enquiry, the quote, the fix, the invoice: each takes as long as it takes, an average nobody has measured and nobody owns. Put a designed number against every step above your line, then time what those steps actually take this week. The gap between the two is a promise you've been making to customers without ever having agreed to make it.

Members only · 4 principles + template + AI mentor

364 more frameworks are waiting.

The Service Blueprint is Day 1 of 365. One framework every morning for a year — across strategy, sales, negotiation, leadership, and more.

$1 /day

Billed $365/yr · cancel any time

365 frameworks

12 topics · templates · AI mentor

Reserve your place — $365/yr →

One payment a year · the whole library · no auto-renewal.

More Operations frameworks

All 24 operations frameworks →