Short spoken advice on raising technician productivity by nudging the bottom-performing technicians (bottom 20–33%) upward. Recommends setting modest minimum requirements just above the current bottom tier rather than extreme targets, measuring small per-tech time gains (e.g., half-hour improvements) and modeling their financial impact; emphasizes many workers do only the bare minimum.
Just take like the bottom 20% or maybe the bottom third and, and set your minimum requirements just right above that. They don't have to be anything crazy. Somebody. Some people get carried away with it sometimes or, or even when they're setting forecasts and things. They'll set a forecast for a technician that, oh, you know, he has to be at nine hours or eight hours or 10 hours. And I'm like, okay, what is he at right now? They're like four. I'm like, okay, so we're probably not going to take, you know, so it's. Yeah, when you're setting minimum requirements, just come right in above the top of. Of where that bottom third is. Bottom 20%. They don't have to be crazy, but you can do those little exercises that are like, you know, what does it do to my financials if I get, you know, a half hour per tech or per stall or whatever? There's a bunch of different ways to do it, and it's crazy. So. Especially when you bring up that bottom third just a little bit. But there's a big percentage of the workforce today that'll get by on the bare minimum.
