Build a Changeover Baseline Before an Industrial Evaluation

A long changeover deserves a review that starts with facts, not a pitch. When a plant tells you a changeover ran late, your first move should be to help them establish what actually happened during recent changeovers, before either of you proposes a fix. That means asking for records, naming an owner for those records, and agreeing on a window to review them, all without asking operations to shut down a line so you can run a demonstration.

Why This Conversation Goes Wrong

Most reps hear "the changeover ran long" and reach for a solution. They start talking about a faster tool change, a new sequencing method, or a system that promises shorter transitions. The plant leader hears a sales pitch attached to a problem they have not yet defined for themselves, and they push back, often by refusing to give up production time for a demo.

The real issue is that nobody has looked at what happened yet. Two flavor changes running long last month could mean the standard instruction is wrong, a new operator needed more time, a changeover crew was short staffed, or the schedule left too little buffer between runs. Each of those has a different owner and a different fix. If you propose a solution before anyone has pulled the changeover sheets, you are guessing, and plant leaders can tell when a rep is guessing. That guess, even a well intentioned one, is what turns a five minute conversation into a stalled deal.

Build a One Page Changeover Map

Before your next call, put together a single page that lays out what you know and what you still need to find out. Include the line affected, the dates of the recent changeovers that ran long, the name of the person who owns the completed changeover sheets, and the person who controls the production schedule. Add the standard instruction time for that changeover next to the actual time it took, if you can get it in advance. If you cannot, leave that space open and treat it as your first question on the call.

This map does two things. It shows the plant leader you are not walking in cold, and it keeps you from drifting into recommendations before the group has the facts in front of them. Resist the urge to fill in blanks with assumptions. If you do not know who owns the changeover sheets, write "unknown, ask on call" rather than guessing at a title. A map with honest gaps is more useful than one that looks complete but is wrong.

What to Say

Dana, an operations director at a bottling plant, opens with a common objection. She says, "Two flavor changes ran late last month, but I cannot stop the line so you can run a demo."

Malik, the account executive, does not defend the demo or drop it either. He says, "Let's start with the records from those two changes. Which steps ran longer than the standard instruction called for, and who holds the completed changeover sheets for that line?"

Dana explains that the packaging manager keeps those records, and the continuous improvement lead tracks the production schedule and the summer launch calendar. Malik follows with, "Once that calendar is published, would a short review make sense, one where we compare the documented steps against the windows you actually have open?" Dana agrees and says she will bring both people to that meeting.

Notice what Malik does not do. He does not claim a shorter changeover is guaranteed, and he does not name a product before anyone has looked at the records. He asks for evidence, identifies who holds it, and proposes a meeting timed to something the plant already controls, its own launch calendar. That last part matters. A meeting date tied to operations availability is far more likely to survive than one tied to your sales calendar.

Mistakes to Avoid

A few habits sink this kind of conversation before it gets anywhere.

1. Proposing a demo or a specific fix before anyone has reviewed the changeover records. This signals that you are selling a product, not solving a documented problem.

2. Treating one late changeover as proof the whole line has a systemic issue. Two flavor changes running long could be an anomaly. Let the records show a pattern before you call it one.

3. Letting the continuous improvement lead speak for the packaging manager, or the reverse. Each owns a different piece of the picture, and skipping one means your next meeting will stall on a question nobody in the room can answer.

4. Closing the call without a specific next meeting tied to a real date. "We will follow up soon" is not a commitment. A date tied to the summer launch calendar is.

5. Recapping more than the plant has actually confirmed. If Dana has not verified the standard instruction times, do not summarize the call as though she has.

Practice It and Score It

This conversation is easy to describe and harder to run well, especially the instinct to fill silence with a pitch once the plant leader mentions a real problem. Rehearsing it with a manager, or with a partner playing the operations director, exposes that instinct before it costs you a deal.

Ask whoever plays your manager or coach to listen for three specific things during the practice run. First, did you ask for evidence, meaning the actual changeover records, before suggesting anything. Second, did you get a named owner for that evidence, not just a department. Third, did you leave the call with a next meeting on a date that matches operations availability rather than your own calendar. Score the call low if you recapped anything the plant has not actually confirmed.

DealSpeak is built for exactly this kind of rehearsal, letting you run the conversation against an AI counterpart that reacts the way a skeptical operations director actually would, then scores how you handled the pushback. If you want more scenarios built around plant realities like this one, the Manufacturing practice conversations library covers this and other situations specific to industrial accounts. For a related example of grounding a technical conversation in verified site facts before proposing anything, see how a rep approaches a Coordinate a Chemical Cabinet Delivery Check With Site Facts conversation, and for a case built around change control constraints in a controlled area, look at how to Frame an Air Handling Assessment Within Change Control for a Controlled Area.

The goal in every one of these calls is the same. Get the facts a plant already has on paper, name who owns them, and agree on a next step that respects the production schedule instead of fighting it. A rep who does that consistently earns the kind of trust that gets the next call returned.

You can rehearse this exact conversation in the Manufacturing practice conversations library before it happens for real. When you have this one down, read Coordinate a Chemical Cabinet Delivery Check With Site Facts next.