Day 203 of the Daily · Operations

The Service Blueprint

5 min read · 4 principles · apply it by lunch

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

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.

In the Daily · 4 principles and a template

The Service Blueprint is Day 203 of 365.

In the Daily, each of its four principles is explained in full, with a one-page template to apply it the same day. A new framework arrives every morning at 7am for a year, across all fifteen courses of the FutureMBA curriculum.

$29 a month · cancel any time · 7-day money-back guarantee

More from Operations

The next four in the course.

All 24 Operations frameworks
Day 212 · Operations

The Seven Wastes

Take the busiest hour of your week — the floor, the inbox, the board, wherever the work actually happens. Of everything going on in it, how much would survive if the customer had to approve each item separately, knowing they were paying for it? You already know it isn’t most of it. The useful question is which of seven kinds the rest turns out to be.

See the framework →
Day 220 · Operations

Utilisation and Variability

Take your most loaded person or team — the one absorbing something like ninety per cent of everything they can handle. There’s a queue sitting in front of them right now. If you handed back a fifth of their capacity, how much of that queue would clear? Far more than a fifth. The relationship isn’t linear, and no amount of effort from them is going to make it so.

See the framework →
Day 229 · Operations

The Product-Process Matrix

How many jobs did your operation deliver last quarter, and how many of those needed a step your standard path doesn’t have — and was the way your work is organised designed for that pair of numbers, or for the pair you had the day you set it up? Whenever the honest answer is the second one, the gap between those two pairs is coming out of your margin every week, in a line nobody can quite locate.

See the framework →
Day 239 · Operations

Takt Time

Ask whoever runs your busiest repeated process how often a finished one has to come off the end for the business to keep the promises it’s already made — could they give you a number, or would they tell you they’re going as fast as they can? One of those is a rate you can staff to. The other is an apology.

See the framework →