“Showing” Alone Boosts Satisfaction by 22% — The Power of Operational Transparency 【Service Management ⑥】

“Showing” Alone Boosts Satisfaction by 22% — The Power of Operational Transparency 【Service Management ⑥】

This is the sixth installment in my Service Management learning series. Last time, I wrote about the psychology of queues. This time, I’ll cover another key to operations design — “Operational Transparency” — along with the Service Triangle, the structural foundation that supports service delivery.

Showing the Process Changes Satisfaction — A Harvard Experiment

There’s a fascinating experiment conducted at a Harvard University dining hall. Led by Harvard Business School Professor Ryan Buell and his colleagues, this study scientifically demonstrated the impact of operational transparency — a groundbreaking piece of research.

The experimental design was simple. Monitors were placed between the kitchen and the dining area so that diners could see the cooking in progress. The food was the same. The menu was the same. The only variable was whether the cooking process was visible.

The experiment ran under four conditions: ① Neither party could see the other (control), ② Diners could see the chefs, ③ Chefs could see the diners, ④ Both could see each other. The results were striking:

  • Customer satisfaction increased by 22% (when diners could see the chefs)
  • Cooking time decreased by 19% (when chefs could see the diners)
  • When both could see each other, food quality ratings were highest

The satisfaction increase is somewhat intuitive. But why did cooking time also decrease?

The awareness of “being watched” heightened the kitchen staff’s focus and motivation. When your work is directly visible to customers, you can’t cut corners — and you don’t want to. Even more interesting, just the chefs’ awareness that customers were watching changed how much care they put into the food. With the same menu, they plated more carefully and executed cooking steps more precisely.

This is the power of Operational Transparency.

Transparency Works in Both Directions

What makes transparency fascinating is that its effects aren’t one-directional.

Effect on customers: Seeing the work process creates a sense of reassurance — “they’re doing it properly.” Uncertainty about wait times also decreases. As a result, the same service receives higher ratings. In psychology, this is known as “labor visibility” — when people can see how much work goes into something behind the scenes, their evaluation of the output changes.

Effect on providers: Being visible to customers increases pride and sense of responsibility. Workers can feel “who they’re working for.” Performance improves as a result. This is different from mere surveillance effects (the Hawthorne effect). Surveillance creates pressure; transparency provides “the joy of being recognized.”

In other words, transparency is a mechanism that simultaneously enhances both customer satisfaction and employee satisfaction. From an SPC perspective, it’s an extremely efficient intervention.

Transparency Examples Across Industries

Operational transparency isn’t limited to the food industry. Several examples were discussed in class, and looking around, transparency examples are everywhere.

Travel search sites: During flight searches, displaying “Currently comparing over 200 sites” visualizes the process. Showing what’s happening behind the scenes improves the customer’s waiting experience far more than a simple loading screen.

Pizza delivery trackers: A major pizza chain introduced a real-time status tracker after ordering. “Stretching the dough,” “In the oven,” “Out for delivery” — by visualizing each step, customer satisfaction improved dramatically even though delivery times remained the same. The actual cooking and delivery process didn’t change. Only “how it was shown” changed.

Package tracking systems: Real-time parcel tracking has become standard. “Picked up,” “Arrived at distribution center,” “Out for delivery” — just having these status updates significantly reduces the anxiety of “when will it arrive?” This is a direct countermeasure to Principle ② from queue psychology (anxiety makes waits feel longer) that we learned last time.

CI/CD pipelines: In the software development world, CI/CD tools like GitHub Actions and Jenkins display build and test progress in real time. Which steps are complete and where things are stuck is immediately visible. For developers, this isn’t just a technical convenience — it’s “process transparency” itself.

Government services: One city made the status of citizen requests (pothole repairs, illegal dumping reports, etc.) publicly visible online. The sense that “my voice is being heard” and “action is being taken” increased trust in the government.

The common thread is this: “simply showing what’s happening behind the scenes” changes customer perception. Even without changing the service itself, changing how it’s presented transforms the experience.

The Satisfaction Mirror — The Law of Reflection

Related to operational transparency, we also learned about the concept of the Satisfaction Mirror.

Customer satisfaction boosts employee satisfaction, satisfied employees deliver even better service, which in turn increases customer satisfaction — a mirror-like mutual interaction.

“Thank you” and “That was delicious” — customer reactions fuel staff motivation. Motivated staff strive to deliver even better service to the next customer. This virtuous cycle keeps spinning.

The reverse is also true. Dissatisfied employees deliver lower-quality service, which increases customer complaints, and handling those complaints further exhausts the employees. The mirror effect works in both positive and negative spirals. That’s why leaders must consciously manage the direction this mirror spins.

Operational transparency is also a means of deliberately engineering this mirror effect. By showing the cooking process, customers’ “that looks delicious” reactions are transmitted directly to staff, strengthening the mirror effect. You could say transparency physically constructs an “emotional feedback loop” between customers and employees.

In IT, this mirror effect is observable daily. As a delivery manager, I notice that teams who receive words of gratitude from clients clearly perform better in the next sprint. Conversely, when “Is it done yet?” and “The quality is low” comments persist, team morale visibly declines. That’s why intentionally sharing positive client feedback with the team is so important.

The Service Triangle — Balancing Three Stakeholders

Another important framework from this session was the Service Triangle.

Service is built on relationships among three parties: “Company,” “Employees,” and “Customers.” When the balance of this triangle breaks down, service becomes unsustainable.

  • Company ⇔ Customer: Relationship Marketing (communicating the promise)
  • Company ⇔ Employee: Internal Marketing (enabling the promise to be kept)
  • Employee ⇔ Customer: Interactive Marketing (delivering the promise)

Even if a company promises customers “We’ll provide the best service,” it’s an empty promise if employees can’t deliver. Enabling employees to deliver is the company’s “Internal Marketing” — training, compensation, tools, and environment.

The practical implications of this framework are profound. For instance, if the marketing department raises customer expectations too high with flashy advertising, but the front line can’t meet those expectations, the gap breeds customer dissatisfaction. There must be no disconnect between the “promise” communicated to customers and the “capability” employees can deliver. All three sides of the triangle must be aligned.

In IT projects, I frequently see the pattern where sales over-promises to customers and the delivery team suffers. This is precisely a misalignment between the “Company ⇔ Customer” and “Company ⇔ Employee” sides of the Service Triangle. Are the people making promises and the people fulfilling them coordinated within the same triangle? Just asking this question reveals the root cause of many service quality problems.

The Danger of Depending on “Star Employees”

One of the most striking points from the lecture was that over-reliance on high performers is a barrier to sustainable growth.

“Everything runs because of that one person” may look great in the short term. But what happens when they leave? When they get sick? A state where the “Company ⇔ Employee” side of the Service Triangle depends on specific individuals is fragile.

Precisely BECAUSE people matter, you need to build systems that don’t depend on specific individuals. This is the essence of service management. Designing a system where ordinary people doing ordinary work can produce extraordinary results — that is the leader’s job.

The JD-R Model and Employee Engagement

To deepen the discussion on the Satisfaction Mirror and Service Triangle, the JD-R Model (Job Demands-Resources Model) provides useful additional context.

The JD-R Model posits that work has two dimensions: “Demands” and “Resources.” Demands include workload and pressure; Resources include autonomy, supervisor support, and growth opportunities. When demands significantly exceed resources, burnout occurs. When resources are abundant, engagement (deep involvement in work) increases.

Operational transparency can function as a “Resource” for employees. Seeing customers’ happy faces is a powerful resource that reinforces the meaning of one’s work. Conversely, an environment where only customer complaints are made visible increases “Demands.” When designing transparency, we should consider not only what to show, but which side of the equation it affects for employees.

A related concept is Job Crafting — the act of employees proactively adjusting how they define and approach their work to increase their own engagement. When transparency makes customer reactions directly visible, employees spontaneously begin innovating service quality. This is job crafting happening organically. Without managers giving instructions, employees start self-directing — that’s another effect of transparency.

Practicing Transparency in IT

The concept of operational transparency applies directly to IT projects.

Progress reporting IS transparency. What’s happening inside the project, what work is being done, what’s coming next — showing this to clients significantly reduces their anxiety, even with the same delivery timeline.

Conversely, a black-boxed project amplifies client anxiety. “I don’t know what they’re doing.” “Is it really progressing?” — this uncertainty is the breeding ground for dissatisfaction.

Dashboards for progress visualization, regular demos, shared work logs — none of these are technically difficult. But simply having the mindset of “showing” dramatically transforms the customer experience. The 22% satisfaction improvement proves it.

What I personally practice is including a “Behind the Scenes This Week” section in weekly status reports. Beyond surface-level progress, I share things like “We encountered this technical challenge and resolved it this way” or “We detected this risk early and mitigated it proactively.” This is essentially the IT version of the Harvard experiment’s “showing the cooking process.” Clients feel “this is worth what we’re paying,” and the team feels “our efforts are being recognized.” Bidirectional transparency effects in action.

Recommended Reading to Deepen This Session’s Learning

For a systematic understanding of operational transparency, the Service Triangle, and their relationship to employee engagement, the following book is invaluable. It comprehensively covers service management frameworks and provides a deeper foundation for the topics discussed in this session.

Next Time

We’ve been exploring operations design up to this point. Next time, we’ll dive into the “people” side of service. From the hiring and training systems of a luxury hotel chain, I’ll explore how to build an organization where “ordinary people can deliver extraordinary service.”