Changeover time is one of those costs that hides in plain sight. Nobody argues it matters, but very few plants actually measure it consistently or treat reducing it as a standing priority rather than a project that happened once a few years ago.
Before touching any changeover process, I want real data on how long changeovers actually take today, broken out by the specific product to product transition, not an average across all changeovers. Averages hide the real problem, since a plant running mostly similar SKUs with the occasional wildly different one will have a misleading average that doesn't reflect where the actual time is going.
I'd log changeover start and end times for at least a month across all the meaningful SKU transitions a line runs, then rank them by frequency times duration to find where the cumulative time loss actually concentrates. It's common to find that a handful of specific transitions, maybe the ones requiring a full tooling change versus a simple parameter adjustment, account for the majority of total changeover time even though they're a minority of total changeover events.
This is the core idea behind SMED, single minute exchange of die, and it remains the single most effective lens for changeover reduction even outside of die changes specifically. Internal work is anything that can only happen while the line is stopped. External work is anything that can be done while the line is still running the previous SKU.
The mistake I see constantly is treating changeover as one undifferentiated block of downtime rather than breaking it into tasks and asking, for each one, does this genuinely require the line to be stopped, or has it just always been done that way? Staging the next job's tooling, materials, and fixtures at the line while the current job is still running is usually the single highest impact external conversion available, and it's often free, requiring only a process change rather than capital investment.
Once you've moved everything possible to external work, the remaining internal tasks are where you focus on genuine time reduction rather than just relocation. Common approaches that consistently deliver results:
Beyond making each individual changeover faster, there's a separate lever worth considering, reducing how often the most time consuming changeovers happen in the first place through smarter production sequencing. If certain SKU transitions are dramatically more time consuming than others, batching production runs to minimize how often you hit those specific high cost transitions, even if it means slightly less optimal batch sizes from a pure inventory standpoint, can produce a larger net time savings than further optimizing the changeover process itself.
A changeover reduction project that happens once and isn't maintained tends to drift back toward its old duration within a year or two, as new operators are trained on the old habits and small process deviations creep back in. I'd build a standard changeover procedure with the improved sequence documented and used for training, and I'd re-measure changeover times on a defined cadence, quarterly is reasonable, to catch drift before it becomes the new normal rather than discovering a year later that changeovers have quietly crept back up toward where they started.
A well run SMED style changeover reduction project on a line that hasn't been through this before typically achieves a substantial reduction from baseline, often cutting changeover time by roughly half through the internal to external conversion alone, before even addressing the harder internal task reduction work. That first pass is usually the highest return phase of the whole effort, which is exactly why it's worth doing properly rather than rushing to declare the project finished after the easy wins.