Exceptional Service, Exceptional Profit: engagement by design

Who should read it

Read it if you already believe great service matters and you want the actual machinery: a hiring filter, an onboarding sequence, a four-step complaint protocol, a simple way to remember what your regulars like. Owners who train new staff themselves, or who want to hand training to a floor manager without losing consistency, get the most out of it. Skip it if you're after stories and inspiration rather than a checklist; this reads like an operating manual, not a memoir.

Engagement is a system, not a personality

The book opens with a maintenance engineer up a ladder who notices a mother struggling with bags and wet towels near the lobby door, climbs down, and opens it for her. Most managers hearing the story love it. Inghilleri and Solomon don't — the woman had to fumble with the door and look exasperated before anyone reacted. That's reactive service, and it's a weak way to build loyalty. The version they want is the same employee opening the door before she has to ask, because he understands his job isn't changing light bulbs, it's creating a good experience for guests — function versus purpose, one sentence apart in timing and everything apart in effect.

For an independent restaurant this distinction matters more than the hotel-scale examples suggest. You don't need sensors or a concierge app to anticipate needs — you need a team that has been told, explicitly, that noticing a regular's coat on the back of a cold chair or a toddler about to knock over a glass is part of the job, not an interruption to it. The book's real claim is that this kind of attentiveness isn't a lucky personality some servers happen to have; it's a standard you set, train for, and notice out loud when you see it.

That reframing is the spine of the whole book: every following chapter — hiring, onboarding, language, recovery, tracking, empowerment — is really just an answer to the same question, asked from a different angle: how do you make anticipatory care happen reliably, on a Tuesday lunch shift with two people on the floor, rather than only when you personally happen to be in the room?

Hire for the five traits you can't teach

The authors' hiring argument is blunt: personality is largely fixed by adulthood, while almost any technical skill can be taught in weeks. So hire for warmth, empathic skill, an optimistic outlook, a team orientation, and conscientiousness — five traits they've found predict service quality across industries — and worry about coffee technique or POS systems afterwards. A candidate with a perfect CV and a flat, guarded manner in the interview is, on their evidence, a worse bet than someone whose experience is thin but who visibly enjoys other people.

The chapter is equally blunt about the cost of getting this wrong: one weak hire doesn't just cost you their own shifts, it drags down your best people, who quietly cover for them and eventually leave. In a kitchen or dining room of three or four, that effect is faster and more visible than in a hotel of three hundred — there's nowhere for a mismatched hire to hide, and nobody else to absorb the gap.

None of this requires psychometric software. It requires deciding, before your next interview, which two or three of those five traits matter most in your room, and asking questions that actually surface them instead of restating the CV back to the candidate.

Day one decides the next two years

Orientation, the book argues, doesn't start on someone's first shift — it starts the moment they're offered the job, and every contact before day one (a rushed phone call, a form nobody bothered to proofread) is already teaching them what kind of place this is. The cautionary example is a new hire handed off to a disgruntled colleague who mutters, essentially, let me tell you how it really works around here — and that unplanned five minutes can undo weeks of good intentions.

Their fix is to spend day one on purpose before function: why the place exists, who it's for, what it's trying to make people feel — not the fridge-cleaning rota. They go as far as recommending the most senior person available deliver at least part of it personally, the way Horst Schulze did every Ritz-Carlton opening himself for years. An independent owner can do the equivalent in five minutes with a coffee, and it costs nothing but attention.

The other rule worth keeping is patience: don't let a new hire face guests unsupervised before they've absorbed that purpose, even if you're short-staffed that week. A guest served badly by someone who was thrown in too early costs you more than the shift you saved.

Build a lexicon, not a script

Chapter Three treats the exact words your team uses as something worth designing on purpose, not leaving to whoever happens to be on shift. The recommendation isn't a script to recite — the authors are clear that overused scripted phrases (their example: a hotel chain's my pleasure repeated until it started sounding hollow even when meant sincerely) get spotted by guests and start to work against you. Instead, build a short lexicon: a handful of phrases that fit how your own team actually talks, plus a short list of phrases to retire because they put customers on the back foot.

Their example of a phrase to retire is the classic defensive reflex — it's our policy — and any close relative of you're wrong, both of which turn a guest's minor frustration into a small confrontation. A better version of the same information, in their language, gets the same point across without making anyone lose face: our records seem to show instead of a flat contradiction.

This is one of the cheapest ideas in the whole book to copy, because it costs a notebook and one team meeting, not a training department. What it produces — staff who sound genuinely like themselves under pressure instead of reaching for a stock phrase — is exactly the thing guests notice when it's missing.

Four steps, every time, no improvising

The book's recovery method has a memorable name: the Italian Mama Method, against what it calls the Courtroom Method — the instinct to establish facts and assign blame before offering comfort. Their four steps run in a fixed order: apologise sincerely and ask forgiveness before doing anything else; let the guest explain the problem in their own words; fix it and follow up fast — the book's own benchmark is roughly twenty minutes, either to resolve or to check back in and explain progress; and finally, write down what happened.

The order is the whole discipline. Jumping straight to a fix, however generous, before the guest feels heard reads as management processing a complaint rather than a person responding to another person — and an apology delivered while already building your defence ("if what you say is correct, I certainly apologise") reads as an accusation, not a repair. Practising the sequence with your own team, out loud, before a real complaint happens is what makes staff able to do it under pressure instead of freezing or arguing.

The fourth step, writing it down, isn't about blame — it's how one badly cooked steak stays a one-off mistake while ten in a week becomes a training problem, and only a written record tells you which one you're looking at.

Give everyone a number they're allowed to spend

The book's best-known detail is The Ritz-Carlton's discretionary budget: for decades, every employee — housekeeping included — could spend up to $2,000 per guest to resolve a complaint however they judged best, without asking a manager first. The point, the authors stress, was almost never the money itself; staff rarely needed anywhere near that amount. The point was that nobody ever had to say I'll need to ask a manager, the single phrase that turns a fixable problem into a guest who feels unimportant.

Scaled to an independent restaurant, this becomes a fixed, modest number — a free dessert, a bottle, a round on the house — that every staff member, including the newest hire, is explicitly authorised to offer without finding you first. The number matters less than the clarity: staff need to know exactly what they're allowed to do, not guess and risk being overruled in front of a guest.

The related point is who gets to start a recovery at all. The book's answer is everyone, not a designated complaints tier — a runner or a dishwasher should be able to say I'm so sorry, let me get that fixed instead of you'll need to ask the manager, which is itself a small service failure on top of the original one.

Note five, satisfy three

Long before hotel guest-preference software existed, the earliest version of this system at The Ritz-Carlton was staff carrying notepads, and a deliberately modest goal: note five preferences about a guest and aim to satisfy three of them next time. The book calls this the Keep Your Systems Simple principle — tracking too much data buries the few preferences your team can actually act on, and an over-engineered system quietly stops getting used.

For an independent place, the whole apparatus fits in a shared notebook or a phone note by the till: not a CRM, just one line per regular — a preferred table, a standing order, an allergy, a reason they come in on Thursdays. The value isn't the record itself, it's a new hire being able to offer the right table on their first week without anyone having to explain who's who.

One caution from the book is worth keeping: preferences change. Someone's Thursday-night regular order this year might not be next year's, and a system that's never revisited turns a thoughtful gesture into an awkward, outdated one.

Recharge the team before the doors open

The book makes an observation that's easy to miss: on a factory line, output starts at its theoretical maximum and only degrades once something goes wrong during the shift. In a service team, capacity is already degraded before the first guest arrives — someone had a small car accident on the way in, someone else just found out a forgotten bill went to collections. Leadership's job, the authors argue, is reconnecting people to why the work matters, every single day, because the day starts already dented.

Their five traits of a good service leader are worth keeping in mind even if you never write them on a wall: a clear picture of where you're going, one simple idea the whole team can hold onto, real standards you actually hold people to, the practical support to do the job, and genuine recognition when someone does it well. A short daily huddle that touches purpose, not just the specials list, is their recommended way to do this in minutes rather than hours.

The underlying principle is what they call moral leadership: staff are not, in their phrase, 'eight hours of labour' — they're people whose pride, involvement, and sense of purpose you're either building or eroding, in small ways, every single shift.