Customers rarely blame the system. They blame the person in front of them — the support rep who couldn’t resolve the issue, the delivery that came late, the order that arrived wrong. But in a lot of cases, that person or that moment is just the visible tip of a failure that started somewhere else entirely: a scheduling tool nobody updated, a handoff between two departments that has no clear owner, an inventory count that’s been wrong for three weeks because nobody’s job is to fix it. The customer experiences a single bad moment. The actual defect usually lives several steps upstream, inside a system nobody outside the company ever sees.
Jan Carlzon, who ran Scandinavian Airlines through its 1980s turnaround, built his entire management philosophy around this gap between the visible moment and what produces it. He defined a “moment of truth” as any episode where a customer comes into contact with the organisation and forms an impression — positive or negative — often in a matter of seconds. SAS’s reputation, in his framing, wasn’t decided by advertising or strategy documents. It was decided in thousands of small daily interactions: a boarding gate, a delayed flight, a lost bag. His response was to “turn the pyramid upside down” — push decision-making authority down to frontline staff, give them the information and standing to resolve a problem on the spot rather than escalate it, and treat those small moments as the actual site of competitive advantage.
[ Read More: Process and System Design Services ]
It’s a genuinely useful reframe. But it’s also where a lot of businesses stop halfway, because they take the empowerment part and skip the infrastructure part. You can tell a frontline employee they’re now authorised to resolve a customer’s problem — but if they don’t have visibility into the order status, if there’s no system that tells them what actually happened, if resolving the issue requires three other departments to respond and none of them are set up to do that quickly, empowerment just means the employee now absorbs the blame for a system failure that was never theirs to fix. Carlzon’s frontline staff could act because SAS built the operational backbone underneath them first. Skip that part and “empowerment” becomes a nicer word for exposure.
Why the failure shows up so far from its cause
There’s a reason this kind of breakdown is hard to catch early, and it’s structural rather than a matter of not paying attention. The Service-Profit Chain — a model developed by Harvard Business School researchers James Heskett, Earl Sasser, and Leonard Schlesinger, first laid out in a 1994 Harvard Business Review article — maps exactly how many steps separate an internal system problem from the customer-facing symptom of it. The chain runs: internal service quality (the tools, training, technology, structure, and support given to employees) shapes employee satisfaction, which shapes employee retention and productivity, which shapes the quality of what employees deliver externally, which shapes customer satisfaction, which shapes customer loyalty, which eventually shows up as revenue. As HBS’s Ryan Buell puts it, the point of the first link is to “create systems around our employees to ensure that they can thrive in the delivery of outstanding service” — the customer’s experience is the fourth or fifth domino in a chain that starts with something almost entirely invisible to the customer: whether the person serving them was actually set up to succeed.
That distance is exactly why a broken internal system kills customer experience quietly. A leadership team looking at a spike in complaints is looking at link five or six. Their instinct, reasonably, is to fix what’s visible — retrain staff, tighten a script, offer a discount, hire a few more support agents. Those interventions can genuinely help for a few weeks. But if the actual defect is back at link one — an unclear handoff process, a tool that doesn’t give employees the information they need, a workload that makes consistent service structurally impossible — the same failure resurfaces a month later wearing a different complaint. Nobody connects it back to its source, because the source is several links removed and nobody was looking there.
Where the business model comes in
This is also where a business’s stated model and its actual operating capability tend to quietly drift apart. Alexander Osterwalder’s Business Model Canvas splits a business into building blocks — value proposition and customer relationships and channels on one side, key activities and key resources and key partnerships on the other. The first set is essentially the promise: what you’re offering customers and how you engage them. The second set is the engine meant to deliver that promise. A canvas can look internally consistent — the value proposition is clear, the customer segments are defined, the revenue streams check out — and still hide a serious mismatch, because nothing about filling in the canvas forces anyone to stress-test whether the key activities and resources can actually produce the value proposition at the volume and consistency the customer relationships promise.
A services firm’s sales team might sell a fast turnaround because it’s part of the value proposition, while the delivery team operates on a process that was never redesigned to support that speed. A growing D2C brand might promise personalised support as a core part of its customer relationship strategy, while its actual support system is a shared inbox with no routing logic and no visibility into order history. On paper, in the business model, everything lines up. In practice, the gap between what the model promises and what the internal system can execute becomes the customer’s problem — one bad interaction at a time, without ever showing up as a line item anyone reviews.
What actually catches this
The useful move, when you’re chasing a recurring customer complaint, is to work backward rather than forward. Start at the moment of truth — the actual interaction the customer had — and trace it back through what the employee in that moment had access to: what information, what authority, what tools, what support from other parts of the business. Most of the time, the defect isn’t the employee’s judgement. It’s somewhere in that chain of internal service quality Heskett and his co-authors described three decades ago — a system that was never built to let a capable person do their job well, consistently, at scale.
[ Read More: Brand Management Services: Build a Strong, Clear, and Consistent Brand ]
That backward trace is, in practice, a lot of what process and system design work actually involves for a growing business — not another round of frontline training or a new script, but going back to where the value proposition was defined and checking whether the operational engine behind it was ever actually built to deliver it. Get that alignment right, and the moments of truth mostly take care of themselves, because the person standing in front of the customer finally has what they need to succeed in that moment.
