Most service failures—and successes—begin in design, not at the front line.
Service design is never neutral. It reflects what the organization assumes about the public: how people will behave, what they will understand, what they will tolerate, and how they will access help. Those assumptions get embedded into policies, workflows, scripts, forms, websites, and routing rules.
Then the system treats customers according to those assumptions—whether they’re accurate or not.
And the front line delivers what the system has trained and reinforced: the service logic, the expectations, and the “normal” that leadership has built over time.
The hidden issue leaders underestimate
These assumptions are rarely explicit. They’re not written down. They’re not debated. They’re just baked in.
Which is exactly why they matter so much.
Inside the organization, a process can feel completely reasonable. It matches the workflow. It follows the rules. It fits the org chart. It aligns with how staff have learned to work.
But from the outside, that same process can feel confusing, fragmented, or impossible to navigate—especially when a customer’s need doesn’t fit the “standard” path.
What assumptions look like to the public
Customers don’t experience your internal logic. They experience whether they can get help.
They feel your assumptions in things like:
- What options are available—and what options are missing
- How customers are expected to navigate the system
- When a customer can reach a person (or can’t)
- The language the organization uses (and whether it matches what people know)
- What happens when the issue is unusual, urgent, or doesn’t fit the menu
A common design assumption is that customer needs will fit standard pathways. When they don’t, the burden shifts to the customer. People experience this when phone trees, websites, or intake menus don’t match their problem—and the alternative paths are hard to find.
Another common assumption is that legacy ways of working are “just how service works.” Customers experience this as a service posture that feels like: this is how we do things—and they have to escalate through layers to get a basic need met.
And one of the most damaging assumptions is treating the organization’s job as managing demand more than serving need. In those systems, customers are treated less like people to be helped and more like problems to be contained, redirected, or pushed aside so staff can get back to their “real work.”
Sometimes this isn’t indifference. Sometimes the service was never fully designed from the public’s point of view.
The contrast that signals strong service design
When an organization makes it easy to get accurate information, reach help, and resolve issues that fall outside the standard path, it usually reflects something different: It has listened closely to what the public actually experiences—and built the service accordingly.
That difference matters. Because poor service design remains one of the most consistent root causes of poor service delivery.
Why it’s hard to see from the inside
From years of analyzing customer feedback, conducting focus groups, and doing technology user acceptance testing, I’ve learned how difficult it is for people inside an organization to accurately predict the customer perspective—what is understood, what is needed, what works, and what doesn’t.
Organizations don’t deliver strong service just because they care. They fall short when assumptions baked into service design go unexamined—and internal processes get treated as ‘the way service works,’ even when they don’t work for customers.
A leader’s diagnostic that surfaces the real problem
The first step is to make those invisible assumptions visible.
Ask your team to answer these questions plainly:
- What does customer feedback tell us about where people get stuck or give up?
- What are we assuming about how customers will use this service?
- What happens when they don’t behave that way?
- What happens when the need falls outside the mainstream design?
- Where does our design make service harder than it needs to be?
If you want an immediate signal, pick one “non-standard” scenario—an exception, a language barrier, an urgent case, a multi-step request—and walk it end-to-end the way a member of the public would. The gaps you find are rarely “edge cases.” They’re often the real service.
Five leadership moves that improve service by design:
- Name the assumptions before you optimize the process
If the assumptions are wrong, efficiency just speeds up the wrong experience.
Leader move: “What are we assuming about the public—and which assumptions are we willing to test?”
- Design for exceptions, not just the happy path
Services fail where reality diverges from the menu.
Leader move: Collect and use customer feedback and recurring problems identified by staff to identify the top 10 exception types and decide: How will we help people when they don’t fit the standard path?
- Measure what customers experience, not just what units complete
Internal completion can look healthy while resolution stays low.
Leader move: Track one outcome metric that reflects resolution (not throughput) and review it alongside workload and rework.
- Make “finding help” a designed feature, not an accident
If alternative paths are hidden, customers pay the price.
Leader move: Require a visible escalation or “I don’t see my issue” option in every channel.
- Use real voice-of-customer evidence as a design input
Not anecdotes. Not assumptions. Evidence.
Leader move: Bring three artifacts to design reviews: call drivers, complaint themes, and a short set of customer quotes that reflect real friction.
Close: A Practical Call to Action
If you do nothing else this week, pick one high-volume service and ask: What does our design assume about the public—and where is that assumption failing?
Service improves when leaders question assumptions directly and design intentionally around real behavior.
