This is the second installment in my Service Management series. Last time, I wrote about the four characteristics of services. This time, the topic is Customer Satisfaction (CS) Management.
“Customer satisfaction matters” — everyone knows that. But the moment you try to put it into practice, you hit walls. How much is enough? How do you measure it? Does it actually impact the bottom line?
What I learned in the lecture was an approach that treats CS management not as “intuition” but as “science.”
- 1 The Cliff Between “4” and “5”
- 2 The Five Stages of Customers — From “Terrorists” to “Apostles”
- 3 The “Expectation Disconfirmation Model” — Satisfaction Is the Gap Between Expectation and Reality
- 4 “Dissatisfaction” and “Un-satisfaction” Are Different Concepts
- 5 The “Three Barriers” of CS Management
- 6 How One Company Broke Through All Three Barriers
- 7 CS Measurement Tools — NPS and CES
- 8 Reflections as an IT Manager
- 9 Recommended Reading for This Session
- 10 Coming Up Next
The Cliff Between “4” and “5”
In a customer satisfaction survey, the difference between a “4 (satisfied)” and a “5 (very satisfied)” on a 5-point scale looks like just one point.
But the impact of that single point on repeat rates and referral behavior is far greater than you’d imagine.
According to data presented in the lecture, there’s an overwhelming difference in repurchase rates between customers who rate “4” versus “5.” “Reasonably satisfied” doesn’t translate into loyalty. Only when you create an experience at the “delight” level do customers become repeat buyers and active advocates.
This was eye-opening. Many companies set “customer satisfaction score of 4.0 or higher” as a target, but that may actually be insufficient. A 4.0 sits in “good enough, nothing special” territory — customers at this level can easily switch to a competitor. What truly moves the needle is 5.0 — making customers feel that their expectations were exceeded. There’s an invisible cliff between “pretty good” and “I want to come back.”
The Five Stages of Customers — From “Terrorists” to “Apostles”
The lecture introduced a model that classifies customers into five stages based on satisfaction level.
- Outraged: They become “terrorists” — igniting social media firestorms and spreading negative word-of-mouth
- Dissatisfied: They leave quietly — saying nothing, never returning
- Neutral: Indifferent — no loyalty is generated
- Satisfied: Not bad, but they’re perfectly willing to switch to a competitor
- Delighted: They become “apostles” — voluntarily spreading word-of-mouth, returning repeatedly, and purchasing additional services
The key insight is that from “neutral” through “satisfied” is essentially an indifference zone. The business impact concentrates at both extremes — it boils down to two priorities: “reducing the outraged (terrorists)” and “increasing the delighted (apostles).”
Rather than spreading resources across the middle tier, concentrate investment on “defense — bringing dissatisfied customers close to zero” and “offense — growing the number of delighted customers.” This thinking aligns with the marketing fundamental of “focus and concentration.”
The “Expectation Disconfirmation Model” — Satisfaction Is the Gap Between Expectation and Reality
The theoretical model that explains customer satisfaction is Oliver’s “Expectation Disconfirmation Model.”
Put simply, it works like this:
Customer Satisfaction = Actual Experience – Prior Expectation
Exceed expectations and satisfaction results; fall short and dissatisfaction follows. It sounds obvious, but the implications run deep.
Managing expectations is critical. Set expectations too high, and even excellent service produces dissatisfaction. Set appropriate expectations and then exceed them, and you create delight.
The pattern I often see in the IT industry — “overpromise in the proposal, inflate expectations, then disappoint at delivery” — is a textbook negative example of the expectation disconfirmation model.
Let me give a concrete example. On one project, the sales team pitched the proposal as “a groundbreaking system leveraging cutting-edge AI capabilities,” but the reality was closer to a combination of existing technologies. The system itself was perfectly functional, but because the client’s expectations had been inflated to “groundbreaking,” the reaction at delivery was “not as impressive as we expected.” Objectively the quality was high, yet satisfaction was low. That’s the danger of the expectation disconfirmation model.
There’s an opposite example too. On another project, we were upfront: “We’ll start with the minimum viable feature set and expand in phases.” When Phase 1 was delivered, the client’s reaction was “this is more robust than we imagined.” By managing expectations appropriately, the exact same level of quality produced an entirely different satisfaction outcome.
“Dissatisfaction” and “Un-satisfaction” Are Different Concepts
Another concept from the lecture that left a strong impression was: Dissatisfaction and Un-satisfaction (unfulfilled needs) are distinct concepts.
Dissatisfaction is the negative emotion that arises when something you expected doesn’t materialize. “It was supposed to be this way, but it wasn’t.” Un-satisfaction, on the other hand, refers to a state where needs the customer wasn’t even aware of remain unfulfilled.
Why does this distinction matter? Because dissatisfaction can be addressed through reactive measures (complaint handling, quality improvement), but un-satisfaction requires the company to proactively discover and propose solutions, since customers themselves aren’t aware of the gap.
For example, during maintenance and operations for an IT system, a client had no particular complaints about the monthly reports (zero dissatisfaction). But when we analyzed the reports and proposed “this failure pattern can be proactively prevented,” the client was genuinely delighted: “We had no idea that was possible.” This was the discovery and fulfillment of un-satisfaction. Anticipating needs the customer didn’t know they had — that’s where the possibility of moving beyond “satisfaction” to “delight” lies.
This also reveals a limitation of CS surveys. Surveys fundamentally measure only the evaluation of needs customers are already aware of. Needs they’re not conscious of (un-satisfaction) simply don’t appear in the questionnaire. So a high survey score isn’t reason for complacency. There may always be hidden, unrecognized needs lurking beneath the surface.
The “Three Barriers” of CS Management
Even when companies understand that customer satisfaction matters, many fail to implement CS management effectively. The lecture framed the causes as three barriers.
Barrier 1: The Impact on Business Performance Isn’t Felt
“If customer satisfaction goes up, will revenue actually increase?” Unless leadership is convinced of this causal relationship, investment in CS improvement gets deprioritized. “Customer satisfaction is important, but this quarter’s numbers come first” — many companies fall into this pattern. CS investments have a time lag before showing results, making them a poor fit for quarterly performance management.
Barrier 2: Nobody Knows What to Do or How Far to Go
Companies want to improve customer satisfaction, but which attributes should they focus on for maximum impact? Trying to improve everything leads to exhaustion with nothing to show for it. “Let’s listen to all customer feedback and address everything” looks virtuous on the surface but is actually the worst approach — it scatters resources and burns out the front line. What matters is identifying which attributes have the greatest impact on customer satisfaction and concentrating investment there.
Barrier 3: Organizational Obstacles Stand in the Way
Organizational silos, inter-departmental conflicts, contradictions with existing KPIs — even when people want to improve CS, structural barriers within the company block progress. For instance, even if the customer support department pursues “thoughtful, thorough responses,” if the cost management department has set “reduce handling time” as a KPI, frontline staff are caught in a bind. CS management cannot be achieved through one department’s efforts alone — it requires positioning as a company-wide strategy.
How One Company Broke Through All Three Barriers
The lecture featured a case study of a North American roadside assistance company. This company operated on a B2B2C model, providing roadside services as a behind-the-scenes partner for automakers and insurance companies.
What made it fascinating was how this company tackled each of the three barriers head-on.
Addressing Barrier 1: Proving causation with data. By analyzing millions of annual service interactions, they quantitatively demonstrated the correlation between customer satisfaction and vehicle repurchase intent. They confronted leadership with the numbers: “CS drives business results.” This wasn’t mere correlation — it was evidence approaching causation, showing that “customers with high roadside service satisfaction were significantly more likely to repurchase the same brand of vehicle.” Leveraging the strengths of their B2B2C model, they provided data that was valuable to the automakers as well.
Addressing Barrier 2: Identifying the high-impact points. Analysis revealed that the factors most influencing satisfaction weren’t call center interactions, but rather the reliability of on-site arrival times and the attitude of service technicians. The priority of “what to focus on and how far to go” became crystal clear. Customers judged satisfaction not by the politeness of the call center, but by “how quickly will someone arrive?” and “what’s their attitude when they get here?” This insight was somewhat counterintuitive, but the data showed the way.
Addressing Barrier 3: Restructuring the organization. To break down departmental silos, they integrated the contact center and field management operations. They also tied all employees’ compensation to CS scores. Changing the compensation structure had a major impact on employees — CS improvement shifted from “extra work” to “core business that directly affects my paycheck.”
This process was a prime example of transforming CS from “feel-good rhetoric” into “a business mechanism.” Not relying on gut feeling, but proving causation with data, identifying high-impact points, and restructuring the organization. Only when you go that far does CS management truly start working.
CS Measurement Tools — NPS and CES
Measurement is essential to operationalizing CS management. The lecture introduced two representative metrics.
NPS (Net Promoter Score) asks “How likely are you to recommend this service to a friend?” on a 0-10 scale, then subtracts the percentage of detractors (0-6) from promoters (9-10). It’s simple but shows high correlation with loyalty. The strength of NPS lies in the question itself — “would you recommend it?” is more directly tied to behavior than “are you satisfied?” Someone might answer “yes” to satisfaction but “no” to recommendation — and that gap is where true loyalty reveals itself.
CES (Customer Effort Score) measures the degree of “effort” or “hassle” customers feel when using a service. Recent research suggests that “not making the customer work hard” may actually be more effective at driving loyalty than “exceeding expectations with delight.” For example, calling a support center only to be transferred multiple times — that “effort” isn’t erased no matter how politely you’re treated afterward. CES shines a light on the importance of reducing negative experiences.
It’s not about which metric is superior — the point is to choose the metric that fits your service characteristics and track it consistently. CES tends to work well for frequently used services, while NPS pairs better with services where emotional value is important.
Reflections as an IT Manager
In the IT industry, plenty of companies run “customer satisfaction surveys” as a formality. But how many actually connect the results to organizational transformation?
The roadside assistance company we studied didn’t just collect CS scores — they identified causal relationships from the data and went as far as changing compensation structures and organizational design. That’s when it hit me: this is what CS “management” really means.
Looking back on my own experience, post-project CS surveys had become largely ceremonial. Low response rates, overly abstract questions, and collected data that never led to concrete action. This is precisely Barrier 2 (nobody knows what to do or how far to go). If you’re going to measure, you need to dig deep enough to identify “which attributes most influence customer decision-making” — otherwise it’s pointless.
Another point that stayed with me was: “It’s critical to have the conviction to narrow down whose satisfaction you want to achieve, and through which attributes.” Try to satisfy everyone, and you’ll delight no one. Pick your target and concentrate resources there. This “courage to narrow the focus” mirrors the thinking behind scope definition in IT projects. Systems that try to be everything to everyone tend to end up mediocre for all.
And the discovery of un-satisfaction may be the single greatest differentiator in IT services. Proactively proposing solutions to latent needs that customers can’t even articulate — this transcends mere “order-taking” and represents true professional service value. Because we’re technology specialists, we can see possibilities that customers can’t. Translating and delivering those possibilities to the client — that, I believe, is the essence of service management for an IT manager.
Recommended Reading for This Session
To further explore the theory and practice of CS management, I’d recommend the following two books.
“The Ultimate Question 2.0” (ネット・プロモーター経営) by Fred Reichheld, Bain & Company — This is the foundational work by the creator of NPS. It explains how to measure customer loyalty and integrate it into business management, backed by abundant case studies and data. Essential reading for understanding why NPS is more powerful than traditional satisfaction surveys. It reveals the management philosophy behind the deceptively simple principle of “grow promoters, shrink detractors.”
“Introduction to Customer Loyalty Strategy That Drives Revenue” (売上につながる「顧客ロイヤルティ戦略」入門) by Naoki Endo, Nihon Jitsugyo Publishing — A practical guide to implementing NPS in the context of Japanese companies. Beyond theory, it addresses the organizational challenges specific to Japanese firms — breaking down departmental walls, gaining leadership buy-in — with concrete advice. Full of actionable hints for breaking through the barriers of CS management.
Coming Up Next
So far, we’ve established that customer satisfaction matters. But how do you turn customer satisfaction into sustainable revenue? Next time, I’ll write about the core framework of service management: the Service Profit Chain (SPC). A counterintuitive conclusion awaits — “employees first, customers second.”