← Back to blog

Keeping the Team During a Restructure

215 people. Eleven months. A hard rescue with real cuts. What held the team together was not the stay bonus. It was the calendar, and what we said out loud in the room.

Kiyong (Eric) Lee·Operations Executive·August 2026·9 min read

The short version

Rumor is faster than any email. Replace it with a weekly cadence that runs whether the news is big or small.
Meet your top ten to fifteen operators one on one within 72 hours of the first announcement. Never let them hear it first in a room of 200.
Communicate cuts on Monday morning, in person, before service. Never Friday. Never by email.
Stay bonuses are a scalpel, not a spray. Six to ten people at most. Everyone else is held by the truth and the calendar.
Trust is rebuilt in month nine, not month two. Keep the cadence running past the fire.

The first week of a restructure is the week you lose the team, or you do not. Everything after that is easier or harder depending on what you did in those first ten days. Not because the first week is where the cuts happen. Cuts usually come later. The first week is where the story of the restructure gets written in every person's head, and once it is written it is very hard to rewrite.

I ran the workforce side of a Fractional Head of Operations & Turnaround Lead engagement at a $30M Michelin-recognized Bay Area group. Three underperforming locations, an eleven month rescue, roughly $4.9M in operating profit to recover, and a workforce of 215 people who had heard a version of "we are looking at options" for the better part of a year before I got there. By the end of the eleven months the operation was healthy, the three underperforming locations were carrying contribution, and the workforce was still 215 people. Not the same 215. But 215.

The retention story is not the interesting part. The interesting part is what actually held them, because it was not what I expected when I walked in.

What you inherit on day one

You do not walk into a restructure. You walk into the fifth month of one, whether it has been called that or not. By the time an outside operator is brought in, the workforce has already lived through:

A quarter or two of missed numbers that nobody named out loud.
A leadership team that started meeting behind closed doors more often.
Vendor calls the front office started taking on speaker in the manager's office and closing the door.
A hiring freeze that nobody announced but everyone noticed when the last three requisitions did not get approved.
One or two quiet departures at the assistant general manager level that read, correctly, as leading indicators.

The team you inherit already knows something is wrong. What they do not know is what, how big, how fast, and whether they are on the list. Your first job is not to reassure them. Your first job is to tell them what you actually know, name what you do not, and give them the calendar on which they will hear the rest.

The workforce is not fragile. It is patient with hard truth and impatient with soft evasion. You lose people to the second one, not the first.

The first all-hands: what to say and what not to say

Hold one all-hands with the whole workforce in the first ten days. Not a memo. Not a video. A room. If the operation is spread across locations, do it in each location, back to back, same script, same day. The medium is the message here. Speaking it out loud tells people it is real. Sending it as a PDF tells people it is not.

Three rules for what you say:

Name the situation in a sentence a line cook would use

Not "we are engaged in a strategic review of the operating footprint." Say: "Three of our locations are losing money. We have about a year to fix it or we will have to close units. I am here to help fix it and I am going to tell you what is happening every week for as long as it takes." That is the entire opening. If a line cook cannot repeat your sentence back to a coworker at family meal, you wrote it for the board and not for the room.

Name the timeline, even a rough one

Give the workforce a horizon. "We are going to know a lot more in 60 days. In the meantime the operation runs as it does today." The timeline is not a promise about outcomes. It is a promise about when the next update lands. Silence is what turns anxiety into attrition, and a timeline is the only thing that gives people a reason to wait for information instead of leaving to go find it somewhere else.

Name what is not yet decided

This is the part most operators skip and it is the part that costs them the most. If cuts are possible, say cuts are possible. If you do not yet know which roles, say you do not yet know which roles. Do not promise "no layoffs" unless you can actually promise it, because that promise is the one people will remember when it breaks, and every promise you make after it will carry the same discount.

The 72-hour rule for key operators

The big room is for the workforce. It is not for your key people. Your top ten to fifteen operators, the people whose exit would break the operation, cannot hear the story only in the all-hands. They have to hear it from you, one on one, within 72 hours of the first announcement.

What goes in those meetings is different from what goes in the room. In the one on ones you tell each of them, by name:

Exactly what you need from them over the next 60 days.
What you can promise about their role and what you cannot.
What the operation looks like from their seat if the plan works.
How they will hear news going forward, and how quickly.
Whether there is a retention structure in place for them, and what triggers it.

The people you meet with in the first 72 hours will not leave. The people you do not meet with will start updating their resumes that weekend. This is not a mystery. It is a math problem. Attention is the currency of retention during a restructure, and attention has to be spent on the people whose loss would break the operation, in the order that loss would break it.

The weekly Friday note that runs no matter what

The single highest-return tool in a restructure is a boring one. Every Friday at the same time, in the same channel, a short update goes out. Two to five sentences. What we learned this week. What we decided. What we did not decide. When the next update lands.

The magic of the weekly note is not the content of any single week. It is the fact that the note runs whether the news is big or small. When there is no news, the note says so. "This week: no updates on the restructure. Numbers were on plan. Next update Friday." That single sentence, repeated for eight weeks, does more work for retention than any all-hands you will ever run.

Fig. 1 · The four-part cadence that replaces rumor with rhythm.

How to communicate a cut

You will have to let people go. In most real restructures there is no version where nobody is cut. The question is how it happens.

The rules are simple and they are not up for debate:

Monday morning, before service. Never Friday. A person let go on a Friday spirals alone for two days. A person let go on a Monday can get to a phone call, a resource, a next conversation. Give them the week, not the weekend.
In person. No email. No video call unless the person is remote and there is no other way. The medium tells the person how you saw them. A memo tells them they were an entry in a spreadsheet.
Severance paperwork in the room. The last check, the details of benefits continuation, the reference letter, the contact for outplacement if you are offering it. Do not send them home to wait. Give them everything they need to leave with dignity in the same conversation.
Answer the question the rest of the team will ask by lunch. "Is that it, or is there more coming?" You have to know the answer before you walk into the day, and you have to say it out loud to the room within four hours of the last cut. Vague answers here cost you the next month of trust.

How you fire is how the people who stay understand how you would fire them. It is the loudest cultural statement a leader makes during a restructure, and most operators mumble it.

Stay bonuses versus transparency

Stay bonuses are a real tool and they are misused more often than they are used well. Here is the framework I run:

Stay bonuses are for the six to ten operators whose loss would break the operation between now and the far side of the restructure. Usually that is the general managers of your best-performing units, one or two chefs, the head of catering, and the finance lead. Structure the payment on real milestones tied to the plan, not on a calendar date, so the money says "we need you inside the work" and not "we need you in a chair."

Everything else, do not touch. Do not sprinkle retention pay across the org chart. Two things go wrong when you do. First, the workforce reads it as guilt money and it undermines the credibility of everything else you are saying. Second, you are teaching the wrong lesson: that money is what holds people through hard change. It is not. What holds people through hard change is knowing what is happening, when, and from whom.

Most of your workforce, if given honesty and a real cadence, will stay through the restructure without any retention pay at all. That is not a theory. That was 205 of the 215.

What actually held the team over eleven months

Looking back at the Zareen's engagement, if I have to rank what kept the workforce intact through eleven months of rescue work, the order surprised me at the time and it does not surprise me now:

The weekly Friday note. Every Friday, without exception, for the full eleven months and past it. The single highest-return communication tool I have ever run.
The one on ones with the top operators. Not the money. The attention. The people who felt inside the decision stayed inside the operation.
The way we did the two rounds of cuts. Monday morning, in person, with the answer to "is more coming" ready by lunch. The workforce watched us do it and read it correctly as respect.
The stay bonuses, narrowly used. Six people. Milestone-triggered. All six stayed the eleven months. Two of them stayed the four years after.
Not lying about the timeline. We overshot the original 90-day plan. We said so, on a Friday, in a two-sentence note, with the revised timeline. Nobody left over the delay. People leave over surprise, not over difficulty.

What I got wrong the first time

Two mistakes I am honest about, because both cost me operators I liked.

The first: I underestimated how much the frontline workforce wanted the truth, and I softened the first all-hands more than I should have. I hedged on the word "close" when three units might actually have closed. The workforce read the hedge accurately and the rumor filled the gap I left. I lost two shift leads that month who would have stayed if I had said the harder version of the same sentence.

The second: I stopped the weekly Friday note two months after the last cut, because the restructure "felt over." It was not over. The workforce still needed the cadence, and the two months of silence undid maybe 40 percent of the trust the previous nine months had built. When I restarted it in month twelve, I said out loud that I had made the wrong call in stopping it, and the note ran without a break for the following two years.

The point

You do not keep a workforce through a restructure with speeches, and you do not keep them with money. You keep them with a calendar you actually run, one on ones with the people whose loss would break you, cuts you communicate like an adult, and a weekly note that shows up on Friday whether the news is dramatic or boring.

The workforce is not asking you for certainty. They know you cannot give it. They are asking you to tell them the truth on a schedule they can plan around, and to treat the people you have to let go the way they would want to be treated if it were them. Do those two things and the operators you want to keep will stay through eleven months of hard work.

Cadence beats charisma in the P&L. It also beats it in the workforce. Every time.

Restructure ahead of you and 200 people who need to hear from you?

I take on a small number of turnaround and restructure engagements each year, mostly restaurant and hospitality groups in the $10M to $60M revenue range. If you are staring at hard cuts and a workforce that is starting to leak, I am happy to trade notes.

Get in touch

Questions people ask

How do you keep the team during a restaurant restructure?

You keep the team by replacing rumor with rhythm. Hold one all-hands in the first ten days that names the situation in plain language. Meet every key operator one on one within 72 hours. Install a weekly Friday update that runs whether the news is big or small. Communicate cuts on Monday morning in person, never on Friday and never by email. Reserve stay bonuses for the six to ten people whose exit would break the operation. The calendar is the retention tool, not the money.

What should you say in the first all-hands of a restructure?

Name what is happening, name the timeline you are working to, and name what is not yet decided. Do not promise no cuts if cuts are possible. Do not hedge on a decision that is already made. Tell people how they will hear news going forward, when the next update will land, and where they can bring questions in the meantime. Take questions until there are no more questions. Leaving the room with something unsaid is how trust breaks the next week.

Should you use stay bonuses during a restructure?

Yes, but narrowly. Stay bonuses are for the six to ten operators whose loss would break the operation, structured with clear milestones and paid on those milestones. Spreading retention pay across the org chart reads as guilt money and it undermines the people you actually need to hold. Most of your workforce is not held by money in a restructure. They are held by knowing what is happening, when, and from whom.

When should you communicate layoffs during a restructure?

Monday morning, in person, before service. Never Friday, because the person you let go has the weekend to spiral alone. Never during service, because their coworkers do not have room to absorb it. Have the severance paperwork ready in the room. Be prepared to answer the question the rest of the team will ask by lunch: is this the last round, or is more coming. A vague answer here costs you the next month of trust.

How do you rebuild trust with the team after a hard cut?

You rebuild trust with cadence, not with speeches. The weekly Friday update has to keep running for at least six months after the last cut. The standing one on ones with your operators have to happen when they are boring, not only when there is news. Trust after a restructure is a compound curve. It rebuilds in month nine, not month two, and only if the calendar held between.

What mistakes are common in communicating a restructure?

The three common mistakes are: sending news by email or memo instead of speaking it in a room, going silent between announcements so the workforce fills the gap with rumor, and treating the emergency communication cadence as temporary. The all-hands, the weekly Friday note, and the standing one on ones with operators are not a phase. They are the new normal. Stop them too early and every gain from the restructure decays.

How do you keep your key operators from leaving during a turnaround?

Your key operators leave when they feel invisible and blindsided. Meet them one on one within 72 hours of the first announcement. Tell them by name what you need from them, what you can and cannot promise, and what the next 60 days look like from their seat. Give them a real seat at the operating table during the restructure, not after. When people are inside the decision, they stay. When they are receiving the decision, they polish their resumes.