Essay
The quiet cost of unmapped handoffs
A chatbot that answers “where is my request?” is often cheaper to buy than an afternoon spent naming who owns the file at 4:55 p.m. It is also usually the wrong purchase. In Service Blueprint Studio we treat the gap between teams as the product. The customer only hears the gap as delay, contradiction, or a second phone call.
Handoffs hide in polite language. “We’ve sent it to the back office” rarely includes a clock. Overnight batches, contractor portals, and the person who is “copied for visibility” all count as actors. If they do not appear on the wall, the map is a story about how leaders wish work travelled.
Cost-to-serve shows up when the same customer is identified twice. Finance already knows this in blended handling time. Experience teams often discover it late, after a campaign about warmth. Mapping the wait in hours — and putting a name next to the wait — is unglamorous. It is also how a New South Wales utility we worked with found a 41-hour hole between field completion and SMS confirmation.
You do not need a new platform to start. You need a sample of tickets, one sceptical operations lead, and permission to say that a team’s “closed” status is not the customer’s closed status. The studio syllabus spends a full week on time as the product for this reason.