$5,000 in Pizza Saved Them 10 Years of Turnover

Chris Lawson

9d • 🏅Retention Strategies🏅

Can $5K in pizza outwork $60K in turnover?

A $5K weekly lunch habit beats a $60K bad hire — if you ask the right question and shut up after.

In this post:

The question that turns "fine" into a fix.
Why monthly meetings fail where weekly ones win.
The ten-second discipline that makes or breaks the meeting (and it's not the lunch).
The math: $29,500 per bay × 50% gross profit, and why $5K starts looking cheap.
The six-step Monday version — including the week most owners quit before it works.

4 min read. Short on time? Watch or listen to the video walkthrough below while you're on the go.

___

Five thousand dollars a year.

That's what a shop in the Midwest spends on Thursday lunch for the team.

They've been doing it for ten years. They've fired exactly two people in that time. Most of the team has been there since the day they were hired.

It's not the lunch.

Same day, every week. That's the cadence.

One question with a specific shape: "If we tweaked one process around here, what would you tweak?"

Then the owners shut up.

Three things, working together. None of them work alone.

WHY WEEKLY

Most shops run feedback as an event. Annual reviews. Quarterly check-ins. Maybe a monthly meeting if the owner is ambitious.

Each one fails for a different reason.

Annual reviews show up too late. By the time you hear about the broken process, the tech has either worked around it or left.

Quarterly check-ins turn into HR theater. Everyone shows up with rehearsed answers because they've had three months to forget what was actually irritating them in March.

Monthly meetings get closer. But the average tech has already swallowed three or four small complaints by the time the meeting comes around. Most won't bother resurfacing them.

Weekly is different.

The irritation is fresh. The tech remembers the exact thing that broke yesterday. The fix is still cheap.

Frequency is what converts feedback into a culture. Without it, feedback decays into compliance — and compliance is what techs do right before they update their resume.

THE QUESTION

"How's it going?" gets you "fine."

"Any problems?" gets you "nope, all good."

"What's one process we should tweak around here?" gets you a fix.

Look at why each word in that question is doing work:

Tweak — small, low-stakes word. Tells the tech you're not asking him to indict the whole shop.

Process — depersonalizes the issue. He's not complaining about a person. He's commenting on a system.

What — open-ended. "Is there anything?" can be closed with "no." "What" forces a name.

Around here — invites him to comment on the whole shop, not just his bay.

The question you ask determines what you get back. Question design is a leadership skill that almost nobody talks about — and it's the cheapest upgrade you can make to any meeting you already run.

THE SILENCE

Here's where this kind of meeting usually dies.

Tech says: "The parts shelf is a mess."

Owner says: "Well, that's because we've been short-handed and Mike was supposed to reorganize it but I had him on a different priority and honestly the supplier's been late and—"

Tech stops talking for the next eleven Thursdays.

It's an easy trap to fall into. Most of us think we're listening when what we're actually doing is defending. The two feel almost identical from the inside. From the tech's side of the table, they don't.

The discipline that makes this meeting work isn't the lunch. It's what happens in the ten seconds after the question.

Ask the question.
Wait. Let the silence get uncomfortable.
When someone speaks, write it down. Don't respond. Don't explain. Don't justify.
Ask one follow-up: "Say more about that." Then write that down too.
Decide later, alone, what to do with the information.

The owner I'm describing said it better than I can: "We've learned to shut up. Ask what they think we should do, and then just shut up and let them tell us."

That's the whole game.

THE MATH

$5,000 a year in lunches sounds like a lot. It's not.

Run the math yourself. The average independent shop does about $29,500 a month in sales per bay. At 50% gross profit, that's $15,000 walking out the door every month a bay sits empty.

One bad hire — wrong fit, washes out at month four — runs $60,000 to $100,000. That's the empty-bay months, the recruiting spend, and the comebacks his replacement has to clean up.

If one Thursday lunch a year surfaces one tech-irritation early enough to fix, you just made the math twelve times over.

It's worth filing under "labor cost," not "culture." The owners who treat retention as a soft cost tend to be the same owners whose hiring problem never goes away.

RUN THIS MONDAY

If you've never done this before, here's the smallest version that still works:

Pick a day. Same day every week. Don't move it. The day matters less than the consistency.
Buy lunch. Pizza or sandwiches is fine. The food is the trojan horse, not the point.
Ask one question: "What's one process we should tweak around here?"
Shut up. Write down the answer. Ask "say more about that" once. Write that down too.
Don't respond in the meeting. Decide later, alone, what to do with the information.
Show up next week and do it again. The first three weeks will be quiet. Week four is when it starts working.

If you've tried something like this before and it fizzled, the failure point was almost always #5. Owners who skip the silence kill the meeting before it has a chance.

If you ran this Thursday and asked your team "what's one process we should tweak," what do you think the first answer would be?

Drop it in the comments. The predictions tell you almost as much as the actual answers do.

Weekly lunches are bench insurance. They keep the techs you've already got, and surface the cracks before those cracks become resignations.

7:23

2 comments