Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How One Factory Cut Changeover Time 45 Percent With One Color Code
Transcript
- Lucas: So we're at a midsize auto parts plant outside Detroit, and the plant manager, Dana Reyes, has a problem. Changeovers on their stamping presses were eating twenty percent of the shift, and scrap was piling up in the first hour after every die change. Luna: That first hour after changeover is brutal. Everything's out of spec, operators are rushing, and you burn parts just to get the press dialed in. Lucas: Exactly. And Dana told me she watched the same thing happen every single time. The operators knew the steps, they'd been trained, they had a checklist laminated on the side of the press. But in the heat of a changeover, two steps kept getting skipped, and those two steps were exactly the ones that caused misalignment. Luna: So what did she do? More training? Bigger checklist? Lucas: No. She did something almost embarrassingly simple. She color-coded the sequence. She mapped the entire seven-step die change process and assigned each step a color — red for the setup, yellow for the alignment, blue for the test run, that kind of thing. Then she painted a stripe on the floor, color-coded the tooling cart, and put matching colored tape on the press controls. Luna: So the operator physically moves from the red zone to the yellow zone to the blue zone. It's like a path. Lucas: Right. And the skipped steps were both in the yellow zone. The alignment checks. So she made the yellow zone visually dominant — she painted the alignment fixtures bright yellow, and the press controls for those adjustments got yellow handles. You couldn't miss it even if you were running on three hours of sleep. Luna: And what happened? Give me the numbers. Lucas: Within a month, average changeover time dropped from forty-seven minutes to twenty-six. That's a forty-five percent reduction. And scrap rate in that first hour after changeover fell by a third. Dana says the operators stopped skipping steps because the visual cues made the correct sequence the path of least resistance. Luna: I love that phrase — 'the path of least resistance.' But let me push back a little. Isn't this just a band-aid? If the process is that fragile, shouldn't you redesign the equipment or retrain people more deeply? Lucas: That's a fair challenge, and Dana heard it from her own engineers. But here's the thing — the equipment was fine. The training was fine. The problem was that in a high-pressure, time-constrained situation, the human brain defaults to what's most salient. The old checklist was text on paper. The color coding made the right action the most visually prominent thing in the room. Luna: So it's not about intelligence or skill. It's about designing for how people actually operate under stress. Lucas: Exactly. And that's the broader lesson. Dana didn't add more procedures, she added more signal. She told me, 'The operators weren't dumb. They were just human. I had to make the right thing easy to see.' Luna: Have you seen this work in other industries? Because I feel like I've heard of color coding in hospitals for like, IV lines or something. Lucas: Absolutely. Hospitals use color-coded wristbands and IV tubing to prevent misconnections. Airlines color-code their fuel panels and hydraulic systems. And in logistics, one major parcel carrier color-codes the loading zones by destination — drivers know exactly where to drop each pallet without reading a single label. Luna: So it's a universal principle, but the application has to be specific to the workflow. Lucas: Right. And that's what made Dana's version work. She didn't just slap colors on everything. She studied the process first, identified the two steps that were being skipped, and then made those steps impossible to ignore. Luna: And the operators — did they resist at first? I imagine a veteran machinist might see color coding as a bit, I don't know, childish. Lucas: That's a great question. Dana said the initial reaction was exactly that. A few of the older operators rolled their eyes. But the first time they ran a changeover in twenty-six minutes, they were sold. One guy told her, 'I didn't realize how much I was guessing.' Luna: That's the thing — when you remove ambiguity, you also remove a lot of stress. Nobody likes to feel like they're guessing. Lucas: Exactly. And that's why this is such a great tactical win. It's cheap, it's fast, and it leverages the way our brains are wired. But it also requires the discipline to actually map your process and find the weak points. Luna: So, practical question for someone listening who runs a warehouse or a clinic or a restaurant — how do they start? Do they just buy a roll of tape? Lucas: Start with a process map. Write down the steps in order, then watch it happen live, three or four times. Mark where people hesitate, where they check their phone, where they skip ahead. Those are your weak points. Then assign a color to each phase of the flow, and make the physical environment match that color at every decision point. Luna: And one more thing — you mentioned the scrap rate. That's a huge cost saver. Did Dana quantify the total annual savings? Lucas: She did. Between the faster changeovers and the reduced scrap, she estimated the plant saved about four hundred thousand dollars a year. And that's before you count the ripple effect — fewer delays downstream, less overtime, and a lot less frustration on the floor. Luna: Four hundred thousand from a few rolls of tape and some paint. That's the kind of win that makes an operator's manual worth reading. Lucas: And that's exactly why we keep doing these episodes. Every day we pick one tactical move, one decision, and we break down how it actually works in the real world. If these conversations have moved your work forward in some small way, you know what, we'd love it if you considered supporting the show. We deliberately don't run ads on these, and that's a choice. If you want to support that choice, the link is buy me a coffee dot com slash fexingo. Luna: Yeah, it's a small way to keep the thing going. No pressure, just if it's worth a coffee to you. Lucas: Anyway, back to Dana. She's already planning phase two. She's looking at the maintenance schedule now, because she noticed that the same kind of skipped-step pattern happens when the press techs do their weekly lubrication checks. Luna: So the color coding is spreading. I bet she'll find the same kind of gain. Lucas: Probably. And that's the thing about this approach — once you see the power of making the right action visible, you start seeing opportunities everywhere. It's not a one-off fix, it's a lens. Luna: I think that's the real takeaway. It's not about the tape, it's about the thinking. Lucas: Exactly. So next time you're watching a process and you see someone skip a step, don't ask 'why didn't they follow the checklist?' Ask 'what would make it easier for them to do it right?' Luna: That's a good question to end on. But before we go — do you have a quick example of a color coding failure? Because it can't be all success. Lucas: Oh, sure. There was a hospital that color-coded all their IV lines by drug type, but they used the same color for two drugs that were often given together. So the nurses saw two blue lines and assumed they were the same drug. They had to redesign the whole system — they switched to shapes as well as colors, because color-blind staff were missing the distinction. So the lesson is: color coding has to be tested with your actual users, including people with color vision deficiencies. Luna: Good point. One system, one meaning. Don't overload it. Lucas: Right. Anyway, that's our tactical win for today. Color coding, done right, can cut changeover time by nearly half — but only if you start with a real process map and identify the specific failure points. Luna: So, what's the next episode about? I'm curious what other little change is gonna have a big payoff. Lucas: Next time, we're looking at a restaurant chain that cut food waste by thirty percent with one change to their inventory ordering — they switched from ordering by case to ordering by weight. It sounds trivial, but the data is wild. Luna: I can't wait. See you tomorrow.