← back to notes

Service design, explained by one three-week refund

Nobody in the story was careless. Both delays happened in a gap between two departments, and no department was measured on the gap.

  • for clients
  • service design
  • blueprints
  • journey maps
  • 2026

Three weeks, as it happened

  1. Day 0, Saturday. A jacket bought online goes back to a store, because the site said any store would take it. The till refuses it. The counter staff writes a paper slip instead, and says ten days.
  2. Day 12. No money. The person on the phone can see the return was accepted and can see no refund was issued, and cannot say why: refunds are a team he can email but not call.
  3. Day 21. The money appears, with no message attached.

Ask anyone inside that company and it went fine. The site worked, the store took the return, the refund was issued. The only person who experienced it as one event was the customer.

Every part hit its target

The till refused because the jacket shipped from a warehouse belonging to the online business, and the till belongs to the store. That is a fact about the company, and the customer has no way to know it and no reason to care.

Who was measured on what, and what that made correct behaviour
whomeasured onso the correct move was
the store tillqueue speedTake the jacket, write a slip, keep Saturday moving.
the refunds teambatch throughputLeave a slip that arrived out of channel for the next batch.
the phone linecalls closedEmail the team that owns it, and close the call.
nobodythe whole tripThree weeks appear in no one's numbers.
Nobody was wrong Both teams hit their targets that month. The gap between them had no owner, no budget, and no measure.

The counter staff knew all of this before any designer did. Her knowledge does not travel: there is no route from her till to the person who could change the rule, and nothing in her week rewards her for finding one.

The refund drawn as a service blueprint Two lanes. The upper lane is one unbroken bar spanning twenty-one days, marked at day zero when the jacket is handed back, day twelve when the customer phones, and day twenty-one when the money appears. The lower lane is four separate boxes, with visible gaps between them: the online warehouse, the store till, the refunds team, the bank. Dashed lines rise from each of the three gaps toward the unbroken bar above. what you lived · one continuous event day 0 · you hand it back day 12 · you phone day 21 · money appears the warehouse the store till the refunds team the bank what the company ran · four owners, and the three joins between them
The same three weeks, drawn twice Every box in the lower lane did the job it was measured on. Both delays happened in a gap: the slip waiting for the next batch, and the nine days after the phone call. The dot is the trip advancing; nothing underneath it moves.

What the work actually is

Less drawing than the name suggests. It starts inside the client's building, talking to the people who each know one stretch of the trip and have never seen the stretch on either side of it. Then one surface holds the whole thing, usually as two related pictures.

  • journey mapThe customer's trip, step by step, in the order they lived it. Waiting and phone calls included.
  • service blueprintThe same trip with the organization's side stacked underneath: staff, systems, rules, and which team owns which.
  • touchpointAnywhere the person and the service meet. Here: the site, the counter, the phone call, the bank notification.
  • front of house / back of houseWhat the customer can see, against what they never see and wait on anyway. The counter is front; the refunds batch is back.

The picture earns its keep in one moment: a room of people who each own one stretch look at the whole trip at once, most of them for the first time. The target is the seam nobody owns. Naming it out loud is most of the work.

Not the same as making the app nicer

Redesign the returns page properly: clearer wording, fewer steps, a form that remembers the order. All genuine improvements, and the refund still takes three weeks, because the delay was never on the page.

The distinction is commercial before it is philosophical. Interface work ships from the team that owns the interface. Fixing the seam means changing what a store manager is measured on, or who owns the refunds queue, or a rule finance wrote for reasons nobody in the room remembers. A rough test:

  • interface workOne team could ship it without asking permission.
  • a seamThe room goes quiet when someone asks who would approve it.

Where I have done a piece of this

A seven-person art studio had never mapped how it works as a whole. I talked to each department, drew what I saw, and found five processes that barely connected, with gaps between them where a name, a payment, or a handoff could fall through. Reading them as one student lifecycle over a single shared record means a student is entered once instead of re-typed at every stage. That was the same move as the three weeks, on a studio whose internal shape had been showing through as somebody else's problem. Five tangled boards, read as one lifecycle.

Still figuring out

  • The claim underneath this is that drawing the thing changes it. That holds only if the drawing reaches someone who can move a boundary between two departments, and nothing says the person who commissioned the work is that person. A blueprint can be admired, filed and quoted approvingly for a year while the three weeks carry on.
  • The diagnosis may be wrong. From the pavement every organization's trouble looks like a bad join, because the constraints are invisible from outside. Those three weeks might be a contract with a payment processor, or a fraud rule, and the woman at the counter probably knows which. I notice that my explanation flatters the person who draws pictures for a living.
  • My test is too neat. Plenty of real seams have an owner who knows exactly what is wrong and cannot act, and a test tuned for ownerless seams walks past those.

One engagement behind me and a lot of reading: enough to describe the work honestly, not enough to know which parts generalize.