The pre-shift review brief has a very consistent life cycle. Monday it happens properly. Tuesday it happens. Wednesday it's a sentence on the way past the pass. Thursday somebody else is duty manager and it doesn't happen at all, and by the following week nobody remembers there was a system.
This is so reliable that it's worth treating as the default rather than as a failure of discipline. If the brief needs an unusually organised manager on an unusually calm evening, it isn't a process — it's a mood. What follows is what actually breaks, roughly in the order it breaks.
1. Nobody ever checks whether the change happened
This is the big one and everything else is downstream of it.
A composite, but a familiar one: an operator we worked with briefed reviews before service on eleven shifts across a fortnight. They could evidence that the briefed change had actually occurred on three of them. Not that it failed on the other eight — that nobody knew either way, because the brief named a behaviour and then nothing looked at it again.
The team works this out faster than the manager does. Once a briefed change has been quietly dropped twice with no consequence, the brief becomes an announcement rather than an instruction, and people listen to it the way you listen to a safety video.
Cost to fix: one line in the shift log, and ninety seconds the next day. Genuinely that small, and it's still the step that gets skipped, because it's the step with no audience.
2. It's timed for the manager's convenience, not the team's attention
4:40pm sounds like the natural moment. It's twenty minutes before doors, everyone's in, nobody's serving.
Everybody is also mid-task — cutting garnish, counting a till, hunting for a clean apron. You are speaking to a room whose attention is committed elsewhere, and the retention is about what you'd expect.
Cost to fix: move it to the moment the team is already standing still and facing you, whatever that moment is in your building. Often that's straight after the food tasting, or the first sixty seconds of the shift-start line-up. If there's no such moment, make one and always use the same one.
3. It asks for effort instead of naming a change
"Let's be sharper on drinks tonight" cannot be complied with, because everyone already believes they are being as sharp as circumstances allow. "Drinks order goes in before we discuss food" can.
Effort requests feel like leadership and function as noise. The difference is mostly grammatical, and it's worth practising the sentence.
Cost to fix: free, and it's the single highest-return change on this list.
4. It only happens after something bad
If the brief appears exclusively in the wake of a one-star review, then the brief itself becomes the announcement that someone is in trouble. People arrive at it defensive. Worse, they start to associate guest feedback with being blamed, which is expensive in a way that shows up much later, when a server stops telling you about a table that went wrong because they've learnt it becomes a huddle item with their section in it.
Cost to fix: run it on the good weeks too, at thirty seconds. "Nothing new, still on the drinks thing from Tuesday."
5. Five signals instead of two
A brief covering five themes leaves the team holding the last one you said and the one you sounded most annoyed about. The other three are gone before service starts.
Two is the ceiling, and two for a fortnight rather than two a night. Changing the focus every shift is how you ensure nothing is in place long enough to become normal. The card is designed around two for that reason.
Cost to fix: free, but it requires deciding that three real problems will go unaddressed this fortnight, which is harder than it sounds.
6. The people who were briefed aren't the people working
In a team with part-time staff and a rolling rota, briefing Monday's team and Tuesday's team is briefing two different rooms. A change agreed with one group is invisible to the other, and the theme keeps appearing in the reviews at exactly the hours the second group works.
Cost to fix: the current focus goes somewhere physical and permanent for the fortnight — the card at the pass, the same two lines on the shift sheet — so the brief is a reminder of something visible rather than the only place it exists. Compressing it to ninety seconds and repeating it every single shift is the version that survives a rota.
7. The fix costs money and the brief can't say so
Some review themes are genuinely not behavioural. If the complaints cluster at 8pm on a Friday because one person is covering the pass and the floor at the hour with the most covers, then briefing is asking people to compensate for an under-resourced hour with attentiveness.
They will manage it for about a week. Then the theme comes back, and the third week of briefing it does real damage — the team now knows you know, and that the response was another huddle. The version of this we see most often is a rota gap rather than a skills gap.
Cost to fix: actual money, or an accepted trade-off, honestly named. "We're not adding hours this quarter, so Fridays after eight are going to be slower and we'll manage expectations at the door" is a legitimate position. Pretending it's a training issue is not.
The uncomfortable summary
Six of the seven failures cost nothing to fix and one costs money — and the one that costs money is the one most often mistaken for the other six.
If you only change one thing, make it the check the next day. A brief with verification survives a bad wording, a bad timing and a mediocre manager. A brief without it dies by Wednesday no matter how well you deliver it.
Automating the part that flags when a theme you marked as handled comes back is roughly why OMMU exists, but the shift log and a note in your phone do the same job if you'll keep it up.