Your Techs Aren't the Bottleneck. Your Front Counter Is.
I can't tell you how many times I'm on a call with a shop owner and they say: "I'm drowning. I think I need to hire another tech." And 10 minutes later we realize: Another tech won't fix it. It'll magnify it. Here's what usually happens on those calls. Owner says: "We're booked out two weeks. Cars stacked up. I need another tech." I ask: "How often do your techs wait on approvals? Parts? Dispatch?" Long pause. "Honestly… a lot." "Cool. Then the problem isn't production. It's feeding production." Here's the hard truth nobody wants to hear: When cars are backed up, it's usually NOT because you need more production. It's because: → Work isn't approved fast enough → Parts aren't sourced fast enough → Jobs aren't dispatched fast enough → Tech questions don't get answered fast enough → Cars and keys aren't moved fast enough The real constraint is front-of-house throughput. Hiring a tech first often makes the problem worse—because you're adding horsepower to a system that can't feed it. Let me twist the knife a little more: Every minute a tech waits is a minute you paid for nothing. When techs stand around, owners blame techs… but the shop is usually choking them. Hiring another tech doesn't fix starvation. It just adds another mouth to feed. Your techs aren't the bottleneck. Your front counter is. THE 30-MINUTE BOTTLENECK AUDIT Stop guessing. Measure it for one day. Here's how: Step 1: For one full day, track every time a tech is stopped for a non-wrench reason: Waiting on parts Waiting on approvals Waiting on dispatch/next car Waiting on answers Keys/vehicle movement Step 2: Put a clipboard at the counter. Every time it happens: hash mark. Step 3: At close, answer: What stopped tech momentum most often? What one role or process change removes that stoppage? Step 4: Implement ONE change for 7 days, then re-tally. This isn't theory. This is data. Data kills drama. COPY THIS SCORECARD TECH STOPPAGE SCORECARD (1 day) Waiting on parts: ___