Skip to content
RANGE

Jon PeckPeople & LeadershipSeptember 30, 20268 min read

The general manager gave notice two days after telling the director of operations that the restaurant was fine. It was the fourth week running they had said it, and the director had no reason to doubt it. The numbers held, the reviews held, and this was the manager who had never missed a Friday. Everyone in the group says they did not see it coming, and everyone is telling the truth. Nothing in the way that group ran was built to show it.

Most groups treat how to get restaurant managers to take ownership as a hiring question, and go looking for a better manager. Go back six months in this one instead. Every habit that ended in that notice belonged to a leader, each one looked reasonable at the time, and each one taught the manager the next.

The ask that never said what done looks like

Six months earlier the founder walked through that restaurant on a Thursday and told the general manager the place needed to tighten up. To the founder that was a clear instruction. The finished restaurant was already in their head, along with everything in the one they were standing in that was off. To the general manager it was a mood. Tighten up what? Service, the dining room, appearance, pre-shift? They did not ask, because asking sounded like not having paid attention.

So the general manager watched. The founder had looked at the bathrooms and straightened a chair at the host stand, so for three weeks the bathrooms and the chairs were perfect. The founder came back, saw the same problems in the dining room, and said in front of the manager that the team was not listening. The team had listened harder than anyone in the building. They were listening for the wrong thing, because nobody had said what to listen for.

The founder’s next move was a second walk-through, said louder, and it taught the same lesson faster. What the general manager took from the month was not that the dining room needed work. It was that an ask is a mood, that the job is to read the founder, and that a question costs more than a wrong guess. The version that would have worked is one sentence: what done looks like in something you can count or see, and a date. By the end of the month every check is delivered inside four minutes of the guest asking for it, and I will time three of them on a Friday. Then ask for it back in the manager’s own words. If it comes back different, you found out in a minute and not in a month.

Tell us what’s breaking.

The fastest way to find out whether RANGE can help.

Book a call with Jon (opens in a new tab)

The decision nobody made

In the second month the same general manager and the one at the next restaurant over both needed the group’s strongest sous chef. The director of operations had run a restaurant and remembered what it was like to have a boss pick a side, so the answer was, work it out between yourselves.

They could not, because it was never theirs to decide. One asked the chef directly. The other went to a peer. By the third week the two restaurants were keeping count of who had the chef last, and the other general managers had started choosing sides. The director saw it, decided it had gone on too long, and settled it with the whole group listening: the chef goes to the first restaurant, and that is the end of it. It landed harder than it needed to, because it arrived after three weeks of nothing and carried all of them.

Nobody did anything wrong. The director did not want to be the kind of boss who plays favorites, and the managers did what people do when nobody has decided. But the general manager now knew two more things: decisions go to whoever pushes hardest, and pushing gets you the chef and a public correction in the same week. A leader who will not own their authority does not remove it. They leave a vacuum, and somebody on the team fills it. Owning it means deciding the day it comes up, saying why in one sentence, and saying when you will look at it again.

A team can work under a hard decision. It cannot work under a pending one.

The conversation you cannot afford to have

By the third month the general manager had a version of the same problem one level down. The bar manager was the one guests asked for by name and the reason the bar did the volume it did. Then something slipped. Pre-shift started ten minutes late, and the side work got signed off without being walked. The general manager had just watched what a correction looks like when it comes three weeks late and in public, and knew what Friday at that restaurant looked like if the bar manager walked. So nothing got said.

The team saw it in the first week. They were watching to find out whether the standard applied to everyone or to everyone except that person, and by the second month a new hire was starting pre-shift late too. The manager who would have corrected it let it go, because everyone knew how the last correction had gone.

The general manager was doing sensible math. The cost of the conversation was visible and would land that week; the cost of skipping it showed up slowly, on somebody else’s shift. What makes that conversation possible is settling the fear before it, not during it. Write down who runs that person’s Friday if they walk out. Then say the one thing that happened, on the shift it happened, about the shift and not the person. The person being protected usually knows. They are waiting to see whether anyone will say so, and when nobody does they read it one of two ways: either the standard has an exception with their name on it, or the group has decided they are too valuable to be told.

The gift card that stands in for an answer

What the general manager gave instead was recognition, because a gift card is easier to give than a conversation and this group handed out a lot of them. After a strong Saturday the team got a shout-out, and the server whose name had come up in three reviews got a gift card. Everyone meant it. Nobody had told that server what they were measured on, whether they were ahead of where the group expected them to be, or what the next job was and what it took to get there. The server had wondered about all three and had not asked, because asking sounded like admitting they should already know. That is the same lesson the general manager learned from the founder in month one, now taught one level down.

Telling someone where they stand is hard. They might hear it as a no, and the schedule was already thin. So the friendly thing got done, and it felt like an answer. It put the question off. The good ones notice first, because they can tell recognition from direction, and the ones who need direction never get it. The version that works takes ten minutes at the end of a shift: what the person is measured on, where they stand against it, and what they need from you to get to the next job. Then do the first thing they say.

Fine is the safe answer

Which brings the story back to the weekly meeting. In six months the general manager had learned that a question reads as inattention, that pushing gets you corrected in front of the group, that the strongest person on the team is exempt, and that the friendly thing passes for an answer. Fine is what all of that adds up to. The schedule was thin, the sous chef was at the other restaurant, the reservation book was full through Saturday, and the answer was still that things were fine. The manager was protecting a reputation the group had given them, and the director was taking a good answer at face value, because a good answer is what the job usually produces.

What changes it is small and has to be repeated. Ask what is going worst instead of how it is going, in the same words every week, so it stops sounding like a performance review. Then watch what you do with the first answer, because every other manager is watching too. “Why didn’t you tell me sooner?” turns the answer into a fault. Fixing it on the spot, in front of everyone, takes the problem out of their hands. Saying thanks and doing nothing is the worst of the three. Thank them in one sentence, then take one thing off their plate before the conversation ends.

Managers take ownership of what the leader has said out loud

Ownership is not a trait some managers have and some lack. A leader makes it possible or makes it impossible, mostly without meaning to, and the five habits above are how it usually goes. Each one has a test you can run this week and a fix that fits in one sentence.

A vague ask
What the manager learns: The ask is a mood, so the job is to read the leader
The test for this week: Ask three managers what done looks like on the last thing you asked for, and count the different answers
The fix: Something you can count or see, and a date, said back in their words
A decision left open
What the manager learns: Decisions go to whoever pushes hardest
The test for this week: List what your managers are working out between themselves that was never theirs to decide
The fix: Decide the day it comes up, say why in one sentence, say when you will look at it again
The conversation you skip
What the manager learns: The standard has an exception, and it is the strongest person
The test for this week: Name the person you cannot afford to lose and the last thing you did not say to them
The fix: Write down who runs their Friday if they walk, then say the one thing that happened
Recognition where a conversation belongs
What the manager learns: Being thanked and knowing where you stand are different, and only one is offered
The test for this week: Ask your best server what they are measured on and what the next job is
The fix: Ten minutes at the end of a shift: measured on, where they stand, what they need from you
A straight answer that costs the person who gave it
What the manager learns: Fine is the safe answer
The test for this week: Count the managers who told you something was going wrong in the last month
The fix: Ask what is going worst, and take one thing off their plate the same day

Managers are only as open as the last answer they watched someone get. A manager owns what the leader has said out loud, decided, and made safe to report on. Start with the row you recognize.

Written by Jon Peck, founder of RANGE: two decades inside multi-unit restaurant operations, P&L responsibility through Chief Operating Officer.