Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How a Single Policy Cut Overtime Costs 15 Percent
Transcript
- Lucas: So there's a 500-person plant outside Toledo that makes injection-molded dashboard components for three different automakers. Standard shift work, two shifts, some weekend coverage. At the start of last year, their overtime line was running about 18 percent of total labor cost. That's high — not catastrophic, but high. Luna: Right, and overtime tends to be one of those line items that just creeps. A few hours here, a double shift there, and suddenly it's baked into the budget. Lucas: Exactly. And most plants respond with a clamp-down: tighten approval, cap hours, maybe bring in a software tool. This plant did something much simpler. They changed the tracking period from weekly to biweekly. Luna: Meaning instead of measuring overtime within each monday to friday week, they measured over a two-week pay period? Lucas: Yes. And here's the key — they didn't change the overtime premium. If you work more than 40 hours in a week, you still get time and a half. But the thing is, under the old weekly system, a lot of overtime was essentially automatic. You'd have a Tuesday where a machine goes down, you need people to stay late to catch up. That pushes Wednesday and Thursday into overtime by default, because you're already past 40 by Thursday morning. Luna: And once you're in overtime, there's no marginal cost difference between doing a little more and a lot more. So the incentive is to stretch the week. Lucas: Exactly. The plant manager told me, and I'm paraphrasing, 'Once you hit 40 hours on Thursday, Friday is essentially free to the floor because the incremental cost of more output is the same as Thursday.' So people would drag work into Friday, even if it could have been done Monday. Luna: Oof, that's a perverse incentive. So how does biweekly fix it? Lucas: Under the biweekly system, overtime is triggered at 80 hours in the two-week period. But here's the subtle part — in week one, you can work 45 hours and not trigger overtime yet, because you're only at 45 of 80. So the plant has a full week to absorb that extra time. And in week two, they can schedule lighter. The result is that the total hours across two weeks might still be 90, but the overtime bucket is smaller because the threshold is higher. Luna: Wait, so are they gaming the system? I mean, legally, overtime is still owed weekly under the Fair Labor Standards Act, right? Lucas: Right, that's the crucial point — they did not change the FLSA compliance. They still pay time and a half for any hours over 40 in a week. But they changed their internal scheduling policy. The biweekly tracking is a planning tool, not a payroll tool. So the scheduler now looks at the two-week total and tries to balance hours so that no single week goes over 40 if possible. And when a week does go over, they actively pull back the next week to keep the two-week total under 80. Luna: So it's a scheduling heuristic that makes overtime more visible and forces rebalancing. Lucas: Yes. And the result: within six months, overtime as a percentage of labor cost dropped from 18 percent to just over 15 percent. That's a 15 percent reduction in overtime spending — roughly $420,000 a year for that plant. Luna: And that's without any new technology or hiring consultants. Just a rule change and a spreadsheet tracker. Lucas: No software. The plant manager literally used a whiteboard for the first two months. He'd write the running two-week total for each shift. People could see, 'Okay, we're at 72 hours with three days left in the period, so we can afford a bit of overtime if needed, but we also know we have to balance.' It became a visual anchor. Luna: I can imagine some pushback from employees who liked the Friday overtime checks. How did they handle that? Lucas: They did get some grumbling initially. But the plant manager framed it as: 'We are not cutting your total earnings. We are smoothing them. You will still have opportunities for overtime, but it will be more predictable and less likely to burn you out.' And because the total overtime hours plant-wide didn't actually drop that much — it just got redistributed — most employees ended up with similar paychecks, just less erratic. Luna: And less burnout probably means lower turnover, which is another cost savings. Lucas: Exactly. They didn't measure turnover specifically, but the manager said absenteeism dropped about 5 percent in the same period. He attributes some of that to the schedule smoothing. Luna: That's a nice secondary effect. So this is a great example of an operational tweak that pays for itself in months. But I do wonder about contexts where overtime is more irregular — like a hospital where patient volume is unpredictable. Lucas: That's a good point. There's actually a parallel case from a regional hospital system in North Carolina that tried a similar approach with nursing shifts. Their problem was that overtime was concentrated on weekends — nurses would work extra shifts to cover gaps, and by Sunday they'd be in overtime for the whole next week. The hospital switched to a two-week scheduling horizon for shift bidding, not for pay, but for scheduling. Nurses could pick up extra shifts early in the two-week period, knowing they had a full week to balance out. It didn't cut overtime as dramatically — only about 8 percent — but it did reduce weekend premium pay because more shifts got covered during the week. Luna: So the core insight is that the measurement period itself changes behavior. Weekly tracking creates a cycle of feast or famine. Biweekly gives you a buffer to optimize. Lucas: Right. And the beauty is, it's completely free to try. You can pilot it with one department for a month. If it doesn't work, you just go back. There's no sunk cost. Luna: I think this is a really useful episode for anyone who manages a team where overtime is a persistent line item. And it's exactly the kind of thing we try to do on this show — find one concrete shift that delivers real savings. Lucas: If that's useful to you, the way these episodes stay ad-free and listener-supported is through people who find value in them. If you'd like to help keep it going, you can buy me a coffee dot com slash fexingo. No pressure, but it does make a difference for a small show like ours. Luna: Yeah, and we really appreciate those who do. It lets us keep digging into these stories without any sponsor influence. Lucas: Alright, back to the plant. One more detail I liked: the plant manager said the biweekly system also made it easier to plan maintenance. Under the old weekly, maintenance was always pushed to Friday afternoon because that was 'overtime time' anyway. Under the new system, maintenance got done Monday through Wednesday, which meant fewer breakdowns later in the week. Luna: So the policy change had a cascading effect on reliability. Lucas: Yes. And that's the kind of second-order benefit you don't see on the initial spreadsheet. So if you're thinking about trying this, start with your highest-overtime department, track two metrics — overtime percentage and unscheduled downtime — and see if you get a similar bump. Luna: And if it works, you've saved a couple hundred thousand dollars with a whiteboard and a meeting. Lucas: Exactly. That's the operator's manual playbook right there.