Lead a Discovery Conversation About Scrap Costs Without Naming the Cause

A scrap review meeting on a manufacturing floor almost always starts with the same trap. The general manager already believes something is wrong, already has a number that hurts, and often already has a theory about the cause. Your job in that room is not to accept the theory. Your job is to slow the conversation down enough to separate the pattern that shows up in the data from the guess about what created it, then bring the people who hold the plant evidence into the room before anyone commits to a fix.

Why This Conversation Goes Wrong

Most account executives lose this conversation in the first two minutes. A general manager under margin pressure wants a decision, not a discovery process. If you let the urgency set the pace, you will end up agreeing to a project scoped around whatever the loudest theory in the plant happens to be. Maybe the quality manager suspects mold prep. Maybe operations blames a supplier alloy. Maybe finance just wants the scrap line to shrink and does not care why. None of those parties has bad intentions, but none of them has the full picture either, and a proposal built around one person's partial view rarely survives contact with the plant floor.

The deeper problem is that scrap data is messy by nature. A single rejected pour touches melt chemistry, mold condition, operator technique, and inspection criteria all at once. If you name a cause before the plant confirms one, you box yourself into a solution that might not fix anything, and you make it easy for the buyer to dismiss you later as someone who guessed instead of someone who checked. Discovery conversations reward the person who stays curious longest, not the person who sounds most confident first.

How to Prepare Before the Call

Walk into the meeting with a short list of questions rather than a short list of answers. Know the categories of evidence that matter in a scrap review. You want to understand which alloy family or part number shows up most often in the rejected tickets, which operation or work center the rejections cluster around, how the plant currently prices scrap, and what the quality team's disposition records actually say happened to each rejected unit. You do not need to know the answers before the call. You need to know which questions get you there.

It also helps to figure out, before you dial in, who actually owns each piece of evidence. The controller can speak to cost assumptions. The quality manager can speak to disposition records and inspection data. The melt supervisor or line supervisor can speak to what happens on the floor shift to shift. If your only contact so far is the general manager, treat this first call as the meeting where you find out who else needs to be in the next one, not as the meeting where you propose a solution.

If you want a broader sense of how this kind of evidence gathering plays out across other plant roles, the Manufacturing practice conversations hub covers several of these scenarios, including how a rep should question an assumed part before promising a fix in Identify a Seal Kit Before Promising a Repair Part.

What to Say in the Room

Picture a foundry general manager named Rosa opening the call with a demand instead of an invitation. Rosa says, "Finance already knows scrap costs us money. Just tell me what to buy to fix it." A rep who wants to close fast might name a project on the spot. A better response holds the line on the pattern first. Account executive Theo answers, "I want to help you land on the right project, and the fastest way there is to look at the pattern first. Which alloy family and which operation show up most in the rejected pours, and what do the disposition records say about them."

Rosa tells Theo that one alloy family accounts for most of the rejected tickets. Rosa mentions that the plant's quality manager has a theory that mold prep is the root cause, though nobody has run a study to confirm it. Theo does not treat that theory as settled and answers, "That is worth testing, and it might be exactly right. Before we talk about a fix, can we sit down with your quality manager and your melt supervisor and go through the scrap tickets, the melt records, and the disposition data together."

Notice what Theo does not do. Theo does not tell Rosa the quality manager is wrong. Theo does not tell Rosa the theory is correct either. Theo treats it as one input among several and asks for the records that would confirm or rule it out. That single move, asking for the next meeting instead of the next quote, is what separates a rep who sells based on evidence from one who sells based on whoever spoke first.

Mistakes That Undo a Good Start

The most common mistake is repeating the buyer's cause back to them as if it were confirmed. If Rosa says mold prep is probably the issue and Theo starts talking about mold maintenance packages, Theo has skipped discovery and started pitching. Even if mold prep turns out to be the actual cause, Theo has taught Rosa that the proposal will follow the buyer's opinion instead of the data.

A second mistake is asking for records without naming who owns them. If you leave the call with a vague agreement to look at the numbers, nothing happens, because no single person feels responsible for pulling the file. Always attach a name and a record type to each request. The controller pulls the cost breakdown. The quality manager pulls the disposition log. The melt supervisor pulls the shift records tied to the flagged alloy.

A third mistake is assigning blame to a person or a shift based on an incomplete account. Scrap conversations sit close to people's job performance, and a general manager who feels like your questions are building a case against an employee will shut the conversation down fast. Keep your questions aimed at the process and the data, not at who might be responsible.

How to Practice and Score This Conversation

This is a conversation worth rehearsing before you take it live, because the instinct to name a cause early is strong and it takes repetition to override it. Set up a mock scrap ticket with a manager or a peer playing the general manager role. Have the rep ask one question about the alloy or part family involved, one about the operation or work center, one about how the cost figure was calculated, and one about what the quality team's evidence actually shows. Four categories, four questions, no skipping ahead to a proposal.

Score the recap at the end of the mock call. A strong recap separates what the data confirms from what the plant team merely suspects, and it names which person owns which record before the next meeting happens. A weak recap blends the theory in with the facts, or it ends without anyone assigned to bring anything back. If you want another rehearsal case that pressure tests the same discipline of separating a symptom from a root cause, look at Discover Seasonal Overtime Cost Before Framing an Operations Project. Running these drills on DealSpeak before the live call gives you a chance to make the early mistakes somewhere that does not cost you the deal.

The plants that fix scrap problems for good are the ones where finance, quality, and operations compare notes before anyone signs off on a project. Your value in that process comes from insisting on that comparison instead of shortcutting it. Hold the line on evidence, name the records you need, and the right project will surface on its own.