You Cannot SOP Someone Into Caring

A service business can write down almost everything.

How a guest is greeted.

How a workstation is prepared.

How a service is delivered.

How an appointment is closed.

What happens when something goes wrong.

What it cannot write into an SOP is the thing customers notice most.

Whether somebody actually cares.

That was one of the more useful lessons to emerge while working inside a premium men’s grooming business in Goa.

Hospitality could be designed.

It could be reinforced.

It could be measured.

But it could not simply be scripted.

The starting point was not “better service”

The business already operated in a category where technical execution mattered.

A haircut had to be good.

A beard service had to be good.

The environment had to feel considered.

But technical competence is only the minimum condition for a premium service business.

The more interesting question became:

What should a guest feel while the service is happening?

That changes the operating conversation.

The business is no longer delivering only a technical output.

It is designing a sequence of moments.

Arrival.

Recognition.

Comfort.

Consultation.

Service.

Recovery if required.

Departure.

Memory.

Each moment may look small.

Together they become the experience.

Hospitality is easy to admire and difficult to operationalise

Will Guidara’s Unreasonable Hospitality gave useful language to an idea that felt immediately relevant:

exceptional hospitality often comes from treating the human experience as seriously as the product being delivered.

The danger is turning that philosophy into theatre.

A team reads a book.

Management announces that everyone should “go above and beyond.”

A few elaborate gestures happen.

Nobody knows what good hospitality means on an ordinary Tuesday.

That is not an operating system.

The useful work begins when philosophy becomes behaviour.

Start with the minimum standard

Before asking a team to create exceptional moments, the ordinary experience has to be reliable.

The basics cannot depend on inspiration.

For a premium service environment, that means clarity around:

• How the guest is received.

• How the consultation happens.

• What standards apply during the service.

• How the environment is maintained.

• How dissatisfaction is identified.

• Who owns fixing a problem.

• How the guest leaves the business.

Those standards create the floor.

They do not create the ceiling.

That distinction matters.

Recovery says more about the culture than perfection does

No service business gets everything right.

The important operating question is what happens next.

One practical discipline was to check satisfaction at the point of checkout rather than discover dissatisfaction later.

If a guest was unhappy with the work, the system needed to make recovery possible immediately.

Where appropriate, that could mean correcting the service, removing the charge, or making sure the guest knew the business would take ownership of putting it right.

The principle underneath this was simple:

the team should not have to protect the transaction at the expense of the relationship.

That is partly a service standard.

It is also an authority question.

People can only recover a situation quickly when they know what they are allowed to do.

Caring requires discretion

This is where SOPs reach their limit.

A process can tell somebody to offer water.

It cannot tell them when a guest needs quiet.

A checklist can require a consultation.

It cannot manufacture curiosity.

A script can prescribe a greeting.

It cannot create recognition.

The most valuable service moments often require somebody to notice something the system could not have predicted.

That means the operating model needs two things simultaneously:

standards strong enough to make the baseline reliable;

and

discretion wide enough for people to remain human.

Remove the standards and service becomes inconsistent.

Remove the discretion and hospitality becomes robotic.

The experience is built in small things

Premium service is frequently misunderstood as expensive extras.

Often it is much quieter.

A calm environment.

A coffee arriving without friction.

Remembering a preference.

Not rushing a consultation.

Recognising when somebody wants conversation and when they do not.

Taking ownership when something feels wrong.

Making the guest feel that the business noticed them rather than merely processed them.

None of those actions is transformational by itself.

Their cumulative effect can be.

That is why experience work can be frustrating for operators.

There is rarely one heroic intervention.

There are dozens of small behaviours that need to survive repetition.

The commercial outcomes moved too

During the broader operating period in which hospitality became a more deliberate part of the guest experience, the business moved from roughly 4.4 stars across about 340 Google reviews to 4.8 across more than 600 reviews.

At the same time, the commercial picture strengthened materially.

Across one six-month stretch, monthly revenue more than tripled, while new-customer acquisition nearly doubled.

Those outcomes matter.

But attribution matters too.

It would be irresponsible to suggest that hospitality alone created them.

Many things changed across the business during that period — operating discipline, customer acquisition, pricing, management, service consistency and the underlying commercial system.

Hospitality was one input into a broader operating reset.

That is the more useful lesson.

Customer experience becomes powerful when it is not treated as a campaign sitting beside operations, but as something the operating system itself is designed to support.

Reviews are an operating signal, not the objective

There is another trap.

Once a business sees ratings improve, the rating itself can become the target.

That produces bad behaviour.

Aggressive review requests.

Cherry-picking happy customers.

Treating complaints as threats to the metric.

The more useful interpretation is that review behaviour gives the organisation a noisy but valuable signal about how the experience is landing.

A rating is the exhaust.

The operating system is the engine.

Optimising the exhaust is backwards.

The leader’s behaviour becomes part of the standard

Service culture is especially sensitive to contradiction.

If leadership talks about care but only discusses revenue, the team notices.

If management asks employees to take ownership but punishes every discretionary decision, the team notices.

If service recovery is encouraged until it costs money, the team notices.

People learn what an organisation values from what survives pressure.

That means hospitality cannot sit only inside training material.

It has to appear in management behaviour.

What gets praised.

What gets corrected.

What gets protected.

What gets forgiven.

What gets repeated.

That is how culture becomes operational.

You cannot SOP someone into caring

This is the part worth preserving.

Processes matter.

Standards matter.

Training matters.

Measurement matters.

But there is a point beyond which additional documentation stops improving the experience.

Because hospitality contains judgement.

Attention.

Empathy.

Pride.

A willingness to take ownership.

The operating system cannot manufacture those qualities.

What it can do is create an environment where they are easier to express.

Clear standards reduce confusion.

Authority makes recovery possible.

Good management reinforces the right behaviour.

Strong systems prevent ordinary failures from consuming all of the team’s attention.

Then people have room to care.

The machinery should disappear

The best service often feels effortless to the customer.

That does not mean it was effortless to produce.

Quite the opposite.

The experience can feel spontaneous because much of the machinery behind it has already been considered.

That is the paradox.

Exceptional service feels human because the system handles enough of the routine work for the humans inside it to remain human.

You cannot SOP someone into caring.

But you can build an operating system that makes caring easier to notice, easier to act on and more likely to survive a busy day.

That may be the more useful definition of hospitality at scale.