Building Systems Where “Ordinary People Deliver Extraordinary Service” 【Service Management ⑦】

This is the seventh installment in my Service Management learning series. Previous sessions focused on operations design. This time, we dive into the “people” side of service.

The case study featured a luxury hotel chain with a global presence. What makes this hotel — known for “the finest service” — remarkable is NOT that exceptional people deliver exceptional service. It’s the reproducibility: ordinary people join the company and grow into professionals through the system.

Breaking down this system reveals three precisely coordinated phases: “Hiring,” “Training,” and “Daily Culture Reinforcement.” And running through all of it is a powerful corporate culture.

Hiring: Attitude and Values Over Skills

This hotel chain’s hiring criteria are clear: prioritize attitude and values over skills.

Hospitality techniques can be taught. But empathy, a spirit of service, and the sensitivity to anticipate others’ feelings — these are difficult to develop through training. So they’re assessed at the hiring stage.

Interviews emphasize dialogue that draws out a candidate’s ability to ask questions and show empathy. Rather than seeking “correct answers,” they’re observing “how this person responds to others’ feelings.” For example, behavioral questions like “Tell me about a time you noticed a colleague struggling — what did you do?” dig into past actions to reveal core values.

Skills can be added later, but a values mismatch cannot be corrected after the fact — this decisive clarity is the starting point of their people development.

This offers important implications for IT hiring as well. Technical skills can grow after joining, but “the willingness to contribute to the team” and “the sensitivity to treat a client’s challenges as one’s own” are largely determined at the point of hire. On my own team, when we’ve been torn between a candidate with high technical test scores but questionable collaboration skills and one with room for technical growth but strong alignment with team values, choosing the latter has proven right more often than not.

Training: The First Two Days Teach No Skills

The most striking aspect of this hotel’s training design was that no skills whatsoever are taught during the first two days after joining.

So what do they teach? “Why this work matters” — values.

They share the company’s credo, thoroughly instilling “who we are” and “why we can take pride in this work.” Skill training begins on Day 3. This sequence matters.

Using concepts from the lecture, the period immediately after joining is when “psychological malleability” is at its peak. During this time of mixed anxiety and excitement about a new environment, injecting values ensures deep internalization. Teaching skills first would form an identity as a “task worker,” making cultural absorption shallow.

This aligns with the theory of Organizational Socialization — the process through which new members learn an organization’s norms, values, and behavioral patterns to become functioning members. Research shows that the first 90 days (especially the first few days) are the most critical period for organizational socialization. This hotel maximizes that “golden window.”

Organizational socialization involves three zones: Comfort Zone — feeling safe in familiar surroundings with no growth. Stretch Zone — moderate tension that maximizes learning. Panic Zone — excessive stress that shuts down thinking. This hotel’s training is designed to intentionally place new hires in the Stretch Zone. Values-sharing provides psychological safety (“you’re one of us”), while presenting the appropriate challenge of “how should you act as a member of this organization?”

Daily Reinforcement: The 15-Minute Morning “Ritual”

There’s also a mechanism to sustain the values instilled during training.

Every morning during the “Lineup” (morning briefing), one item from the credo is discussed by the entire team. Additional reflection opportunities are built in at Day 21 and Day 365 after joining.

This is “ritualization.” Rather than teaching values once and moving on, embedding them into daily routines transforms culture from individual consciousness into organizational infrastructure.

Notably, this ritual takes the form of “discussion,” not “recitation.” Simply chanting the credo would lead to hollow formality. “Share a recent real situation related to today’s theme” — this kind of interactive dialogue reinterprets the credo in fresh contexts each time. This keeps the credo alive as a “working decision-making guide” rather than “words in a frame on the wall.”

The “daily standup” common in IT teams originally serves this ritualization function. In practice, however, it often devolves into nothing more than task progress updates. Adding just 1-2 minutes to share the team’s values or quality standards could dramatically change the meaning of the standup.

The Big Picture Through McKinsey’s 7S Framework

The McKinsey 7S Framework is useful for getting a panoramic view of this hotel chain’s people development. The 7S captures an organization through seven elements: Hard 3S (Strategy, Structure, Systems) and Soft 4S (Shared Values, Skills, Staff, Style).

At this hotel chain, all 7S elements align toward a single point: “service excellence.” Hiring criteria (Staff) are values-focused. The training system (Systems) begins with values instillation. Daily discussions (Style) maintain the culture. Delegation of authority (Structure) empowers frontline decision-making. And tying it all together, the shared values (Shared Values) are codified in the credo.

The 7S teaches us that changing just one element won’t transform an organization. Changing hiring criteria without changing training yields limited results. Changing systems while keeping the old management style prevents adoption. Only when all seven elements point in the same direction does the organization function as a unified culture.

Two Quality Management Approaches — Working in Tandem

This hotel chain’s service quality management employs two coexisting approaches.

① TQM (Total Quality Management) — Process Standardization

Service quality is measured quantitatively and managed through statistical methods. Errors are treated not as individual failures but as “system defects,” and processes are improved accordingly. The TQM principles developed in manufacturing are applied to intangible services.

② Concertive Control — “Horizontal” Rather Than “Vertical” Control

The second is “Concertive Control” — maintaining quality through mutual checking and support among members who share common values, rather than through top-down directives.

These two approaches don’t contradict each other. Manuals build the foundation while frontline discretion and creativity bring it to life. The standardization “management” foundation gives the front line confidence to make decisions. And because discretion exists, standardization doesn’t devolve into mechanical work — it enables moments of genuine customer delight.

In IT terms, TQM corresponds to CI/CD pipelines and coding standards — building the quality foundation through automation and standardization. Concertive control corresponds to code review culture and pair programming — peers elevating quality together. Only when both are in place can high-quality software be shipped sustainably.

What the “What the “$2,000 Discretionary Authority” Really Means,000 Discretionary Authority” Really Means

A signature example is the “up to $2,000 per day” discretionary authority granted to every employee. They can spend up to this amount to satisfy a guest without needing supervisor approval.

More important than the dollar amount is the message this policy sends: “We trust your judgment.” “We won’t punish you for taking initiative.” This is psychological safety codified as institutional policy.

Visions and values remain abstract unless translated into systems. This discretionary authority is a mechanism that connects the organization’s ideals directly to frontline split-second decisions.

However, this authority only works because the three-stage foundation of hiring, training, and daily reinforcement is functioning properly. Granting $2,000 of discretion to someone whose values haven’t been internalized could simply lead to waste. Put differently, values internalization is the prerequisite for this policy, and a coherent flow of “culture → systems → behavior” has been designed.

Corporate Culture Replaces Management Costs

As we touched on in a previous case study, a strong corporate culture lowers management costs.

Employees who have internalized the values can make appropriate decisions without detailed rules. Even in situations not covered by the manual, they can think “What would our company do?” and act accordingly. As a result, the personnel and processes needed for oversight and supervision are reduced.

What struck me most while writing the report on this hotel was that corporate culture is not “motivational talk” — it’s “an alternative to formal control.” Culture internalizes decision-making criteria in employees, creating a mechanism where quality is maintained even without a manager present.

In economic terms, this is an application of Transaction Cost Theory. The costs of monitoring and coordination within an organization (agency costs) are replaced by culture as a “soft mechanism.” In the long run, having everyone deeply internalize a 10-line credo is far more cost-effective than writing a 100-page manual.

Furthermore, a strong culture accelerates decision-making speed. When facing uncertainty, instead of consulting the manual, employees can immediately decide by asking “How does this align with our values?” On the service front line, this speed — being able to respond without making customers wait — significantly impacts experience quality.

Implications for IT Team People Development

In IT projects too, new member onboarding directly impacts quality.

We tend to immediately teach new hires tool usage and development procedures, but this hotel’s case demonstrates the importance of the sequence: “values first.” “What does our team value?” “Why is this project important to the client?” — only with this foundation in place do skills get directed the right way.

And if we were to design an IT team equivalent of the “$2,000 discretionary authority,” it would be “explicitly defining the scope of decisions the front line can make on their own.” Clearly defining escalation criteria is, in reverse, giving people the reassurance that “you’re empowered to make decisions within this scope.”

On my own team, I dedicate an hour on the first day of onboarding to sharing “team commitments.” Not a technical stack overview, but a values conversation: “How do we approach our clients?” “What are our quality standards?” “How do we ask for help when we’re stuck?” Since implementing this practice, the time it takes for new members to become autonomous has noticeably shortened. The same principle behind this hotel’s “first two days” works in the IT world too — I’ve seen it firsthand.

Recommended Reading to Deepen This Session’s Learning

For understanding the philosophy of people development in service from a practitioner’s perspective, these two books are particularly recommended.

The first is a book on service philosophy by a former general manager of the hotel’s Japan operations. It offers a ground-level view of how hospitality excellence is practiced.

The second is a book where the founder himself describes the full picture of building the organization. From hiring to culture creation, it shows how a service organization was designed from a CEO’s perspective.

Next Time

This time we explored the systems behind people development. Next, I’ll examine whether these systems can “replicate” service quality across the globe — the story of the 7-day intensive program for opening new hotels, and the management decisions behind it.