The first turnaround I ever worked on, I did the communication badly. I gathered the back of house at one location on a Tuesday morning, before the lunch rush, and I told them the truth. I said the operation was going through a turnaround, that we were fixing the systems, and that everyone's job was safe. I meant every word. Two weeks later three of the strongest line cooks had given notice. One of them told me on his last day that as soon as he heard the word "turnaround" he started applying, because in his experience that word always meant layoffs were coming and management was lying about it.
The word had done all the damage. Not the plan, not the change, not the systems work. The single word. That morning cost me most of a quarter of retention I did not have to lose. I have run several turnarounds since. I have never used the word turnaround with a line cook again.
Communication during a turnaround is not about telling the truth. Everyone deserves the truth. Communication during a turnaround is about telling the truth in the language, order, and shape that lets the person on the other side actually hear it and stay. Line staff are not the boardroom. They should not get boardroom language. They should get the version of the truth that answers the questions they actually have.
Language before message
Every word an operator uses when talking to line staff during a turnaround has a translation in the line cook's ear that the operator does not always feel. Here is a rough dictionary I keep in my head.
- Turnaround means layoffs coming.
- Restructure means layoffs coming, but faster.
- Right-size means layoffs of the people saying it.
- Optimize means the schedule is getting cut.
- Streamline means my prep list is about to double.
- Realign means my general manager is leaving.
- New leadership means the general manager I trust is being replaced.
- Renewed focus means somebody upstairs is angry about something.
Every one of those words is neutral in a boardroom. Every one of them is a signal in a kitchen. If you use them, you have already lost the audience before the actual message lands, because they are running the translation while you are still talking.
The alternative is operator language. Simple words that describe what is changing for the person in front of you, not what is changing for the organization above them. Fix. Change. Add. Improve. Set up. Tighten up. New training. Better tool. Cleaner schedule. Every one of those describes an outcome the line cook can picture. None of them signals danger.
The boardroom hears "operational restructuring." The prep cook hears "they are going to cut my Saturday." Same event, two languages, one of them costs you the shift.
The cascade that keeps the message clean
The order in which people hear the news matters as much as the words. If a line cook hears about a change from their shift lead, that is normal information flow and they process it as normal. If a line cook hears about the same change from the operator's all-staff email before their shift lead knows, they process it as a threat, because now they are ahead of their direct manager and that is destabilizing.
The cascade has to be top down, in order, in one week. No shortcuts, no group emails, no exceptions.
Fig. 1 · The cascade compresses gossip into one week and puts every conversation in the right voice.
Sunday: the operator gets the message
The turnaround is decided at the board or owner level. On the Sunday before the communication week, the operator sits with whoever made the call and confirms the message. Not the plan. The message. Two paragraphs of language that will be reused down the cascade, so the words that reach the line cook on Friday are the same words the operator heard on Sunday. Anything else generates telephone-game distortion, and the distortion is always in the direction of worse.
Monday: the operator briefs the general managers
In person, at each unit, one at a time. Not a group Zoom. Not a company-wide email with a call-in number. The general managers get their turnaround conversation face to face because they are the ones who will have to answer questions from their people for the next 90 days, and they need to see the operator's eyes when they hear the plan. This is also where the operator gives each general manager permission to translate the language for their specific team.
Tuesday and Wednesday: general managers brief shift leads
Each general manager sits down with each shift lead and lead cook one on one. Not in a group. Not at a meeting. In the office, on their break, with 15 minutes and no phones. Same message, in the same words. This is where the message starts translating from English into the languages the shift lead will use with the line, and where the general manager tells the shift lead what questions to expect and how to answer them.
Thursday and Friday: shift leads talk to the line at lineup
Not a special meeting. The regular pre-shift lineup, with a couple of extra minutes added. The shift lead delivers the message in the language the line thinks in, using operator language, answering the three questions before they get asked. Line cooks watch the shift lead the whole time. They will decide whether to believe the message based on whether the shift lead looks like they believe it, and the shift lead will only look like they believe it if the general manager sat down with them properly on Tuesday.
The trilingual reality of a real back of house
In every restaurant I have run, the back of house speaks at least two languages and often three. English, Spanish, and depending on the market, Korean, Mandarin, Tagalog, or something else. The prep cook whose native language is Spanish and whose English is functional but not fluent will hear a message in English and respond correctly in English. That does not mean they heard the message. It means they heard the words they were expected to hear.
I speak English, Korean, and Spanish. That helps but it is not the whole answer. Even if the operator speaks the language, delivering a hard message in your third language leaves gaps the listener will fill in with their own worry. The reliable move is to prepare the message in each language, with the same nuance, and let a native speaker at the shift-lead level deliver it. If the operator can drop in and reinforce it in Spanish or Korean during a walk-through later that week, that carries real weight, but the primary delivery needs to be by someone who thinks in that language.
The three concrete things I do here:
- Write the message in every language it will be delivered in. Not a translation of the English version. A version written for the ear of the language, by a native speaker who knows the team. Different construction. Different emphasis. Same information.
- Brief the delivering shift lead in their language. If the shift lead thinks in Spanish, they need to hear the message in Spanish first, in a conversation, with a chance to ask questions. If they only ever hear it in English, they will translate it word by word to the line and the message will land wrong.
- Show up in person and use the language. Later that week, on a walkthrough, I will greet the line in Spanish, ask about the shift in Spanish, and thank them in Spanish. Not for the message. For the relationship. The relationship is what holds them when the message causes doubt.
The three questions line staff actually ask
Line staff do not ask about EBITDA. They do not ask about brand positioning. They do not ask about strategic priorities. In every turnaround I have run, the questions from the line have been the same three, in the same order, sometimes out loud and sometimes only in their heads. The message has to answer all three, specifically.
Is my schedule going to change
The single most important question. A line cook has a life outside the restaurant. Their Tuesday off is not a scheduling detail to them. It is when they see their kid. If the turnaround is going to change the schedule, say so, and say how. "We are tightening the schedule to follow demand. Some Tuesday shifts are going to move to Thursday. Your Tuesday off is safe. If your shift changes, you will hear from your shift lead this week, in person, with two weeks of notice."
Vague reassurance triggers flight. "Nothing is changing" is a lie the line cook will catch inside a month, and after they catch you in it they will not trust anything else you say. Concrete answers, even hard ones, hold the team together.
Is my general manager staying
The loyalty in a restaurant is to the person, not the brand. If the general manager the line cook came in for is staying, the line cook will absorb almost any operational change. If the general manager is leaving, no amount of communication will hold them. This means two things.
First, decide the general manager question before the cascade runs. If the general manager is going to be replaced, they know it before the shift leads know anything, and the shift leads know about the replacement before the line does. Nothing is worse than a line cook finding out on Friday that the general manager they trust is gone on Monday. That story travels through the neighborhood faster than any operator can chase it.
Second, name the people who are staying. Not in a memo. In person, at lineup, by name. "Chef Alma is staying. Miguel is staying. Sarah is staying." That sentence carries more than an hour of strategy talk. It is what the line will remember.
Is my pay changing
Wages, tips, overtime access, shift differentials, meal comps. Any of these being touched by the turnaround needs a direct answer. If pay is not changing, say so, in dollars per hour, so it is unambiguous. If pay is changing, say how and when and what the pathway back to prior earnings looks like.
Pay is where trust is either kept or broken. A line cook who feels the pay conversation was straight will stay through most of the rest of the change. A line cook who feels the pay conversation was evasive will start applying that night.
The line does not need the whole plan. They need the answer to their three questions, in words that describe their week, from a person they see every day.
The mistake I still see operators make
The most common mistake I see in turnaround communication is that the operator confuses the boardroom message with the line message and delivers the boardroom message to both audiences. The board needs to hear a coherent multi-year plan with EBITDA targets and a capital story. The line cook needs to hear that their Tuesday off is safe. Both are true. Both need to be said. Neither should be said to the other audience.
The second mistake is speed. Operators tell the board on Monday and email the whole staff Tuesday morning because they are worried about the story leaking. This blows past the cascade and lands the message with the line cook in the wrong voice from the wrong sender. The story does not leak inside one week if the cascade runs cleanly. Leakage is what happens over months, not days.
The third mistake is treating communication as a single event. It is not. It is a rolling drumbeat for the entire turnaround. Every weekly lineup, every monthly all-hands, every walkthrough by the operator is another impression on the line's understanding of what is happening and whether they should stay. Communication is a cadence. Like the operating rhythm itself, it beats or it does not, and if it does not, everything downstream drifts.
The point
Turnaround communication is the work of translating a boardroom decision into a shift-lineup conversation, without losing the truth and without losing the team. It is done through language chosen for the ear that will hear it, cascaded top down in a single week, delivered in every language the team actually thinks in, and answering the three questions the line will always ask.
Do it well and the operation absorbs the change without losing the people who make it work. Do it badly and the P&L improvements you spend six months building get eaten by the retention losses you triggered in your first all-staff email.
The word "turnaround" belongs in the boardroom. Not in the kitchen.