Everyone agrees you should brief the team on what guests said. Almost nobody writes down what that sounds like when you say it.
So here is the actual speech. Six reviews, each briefed twice — once the way it usually comes out, once the way that gets a change. The difference between the two versions is not enthusiasm or leadership style. It's grammar.
The sentence underneath all of it
A briefing line that works has four parts, in this order:
- The guest's own words, quoted, short.
- One observable behaviour — something a person standing in the room could see happening or not happening.
- A named owner.
- When you'll look.
Miss part two and you've held an awareness session. Miss part three and everyone assumes it's about somebody else. Miss part four and the whole thing quietly expires by Wednesday.
The four parts fit in about fifteen seconds. Two of them is thirty. That's the entire brief, and the reason to keep it that short is that you're speaking to people who are tying aprons and thinking about their sections.
Six reviews, briefed twice
Review: "Waited 20 minutes for a drink."
Usually: "We've got to be quicker on drinks tonight, guys, there's a review about it."
Better: "Someone wrote 'waited twenty minutes for a drink.' Tonight, drinks order goes in before we talk about food, every table. Marta's watching the bar queue at eight. I'll check the tickets tomorrow."
The first version asks for effort. The second changes a sequence.
Review: "Nobody came back to check on us."
Usually: "Let's all remember to check back on our tables."
Better: "'Nobody came back to check on us.' One check-back after the first two bites — not at the end. Ben's got the far section, that's where it went wrong last week."
"Remember to check back" is already what everybody thinks they do. Naming the moment — two bites in — is a different instruction.
Review: "Chips were lukewarm."
Usually: "We've had another cold food complaint."
Better: "'Chips were lukewarm.' Nothing waits on the pass tonight, if a plate sits more than thirty seconds it gets called again. Chef's calling it, I'm running if we're short."
Note the last five words. A brief that adds a job for the team and none for you is heard as a complaint about them.
Review: "The server seemed annoyed we asked for changes."
Usually: "Bit of a tone thing in the reviews — everyone be friendly."
Better: "A guest said we seemed annoyed they asked for changes. Modification requests get 'yes, of course' first and the practicalities second. If the answer is genuinely no, come and get me and I'll say it."
This is the one most managers soften into meaninglessness, because saying it plainly feels like an accusation. The fix is to make the new behaviour specific and to take the hard version of it onto yourself.
Review: "Toilets were not great."
Usually: "Toilets need doing more often."
Better: "'Toilets were not great' — that's the second one this month. Half-hourly checks, initialled, from six. Sam at six, me at eight, Sam at nine."
Frequency without names is a wish. Three names and three times is a rota.
Review: "Lovely food but we felt rushed at the end."
Usually: nothing. Four stars, praise for the food, nobody briefs it.
Better: "Four-star review — food was lovely, but they felt rushed at the end. Bill goes down when they ask, not with the dessert plates. That's the second time someone's said rushed."
The four-star reviews are where the specific, fixable stuff lives, and they get skipped in briefings precisely because they aren't bad news. There's more on that pattern here.
Three things not to do out loud
Don't read the review in full. Guests write paragraphs. The paragraph contains a hotel-style opening, some scene-setting, and one operational sentence. Read the one sentence.
Don't name the member of staff the review describes. Even when you know exactly who it was. Brief the behaviour to the room, then have the individual conversation privately afterwards. Doing it in the huddle buys you one visibly humiliated person and a team that stops mentioning problems.
Don't stack five things. If you brief five signals, the team retains the last one and the loudest one. Two is the ceiling. Everything else waits for a fortnight's time.
When there's nothing to brief
Say so, in one sentence: "Nothing new in the reviews, we're still on drinks-before-food from Tuesday."
This matters more than it looks. If the brief only happens when something has gone wrong, then the brief itself becomes a signal that someone is in trouble, and people start to dread it in a way that makes them defensive before you've opened your mouth. A brief that occasionally says "all fine, carry on with the current thing" is a brief that stays usable.
It also reinforces the thing you asked for last week, which is the part that actually produces change — most briefs fail on repetition rather than on wording.
Where this doesn't work
If a review describes an allergy incident, illness, or an injury, none of the above applies. That's not a huddle item — it goes to a documented process the same day, and the first-hour sequence is here.
And if you find yourself briefing the same behaviour for the fourth week, the problem isn't how you're saying it. Something structural is making the behaviour impossible — usually a shift where one person is covering two roles at the hour the complaints cluster. Briefing harder won't move it.
If you want the printable version of the signals to keep at the pass, the card is here. OMMU sends the quoted sentence and the theme count so you're not doing the reading at 4:40pm, but the four-part sentence is yours either way.