Learning objective
Map one service scenario across customer, evidence, frontstage, backstage and support layers, then diagnose a visible failure through its hidden delivery mechanism.
Why it matters
Customers experience one service; organisations manage several systems. A fast interface can conceal long queues, lost evidence or a control failure. The line of visibility makes that disconnect inspectable.
Core concept: the promise and its production system
Customer actions and evidence sit above visible interactions. Backstage work and support systems sit below the line of visibility. Every important frontstage promise needs a credible backstage mechanism.
Scenario
A bank’s assistant says identity verification is complete, but a manual queue later rejects the application because one document was not transferred.
Worked decision
Map the confirmation as digital evidence, the assistant as frontstage, document transfer and validation as backstage, and identity/integration services as support. Redesign the confirmation so it follows successful validation and add a recovery path that preserves evidence.
Decision rule
If a customer promise cannot be traced to backstage action, support dependency, evidence and exception ownership, it is not ready for delivery.
AI lens
AI may draft links from approved logs; human participants validate actual work and customer meaning. Generated completeness is not observed truth.
Quick check
Where does a hidden eligibility decision belong?
A. Customer action.
B. Physical evidence.
C. Backstage action linked to its policy or system.
D. Nowhere because the customer cannot see it.
Answer: C. Hidden work still produces the service and its risks.
Next step
Use the Service Blueprint workspace and complete the clinic booking case.