When manufacturing costs are too high, the conventional response is to increase output. Spread fixed costs over more units. Improve OEE. Push harder on throughput. This logic is sound when the constraint is capacity. It is counterproductive when the constraint is execution. And in most plants where costs are chronically above target, the constraint is execution. Increasing output through a broken execution system amplifies the cost of every execution failure. More throughput means more expediting. More units in process means more quality escapes. More schedule changes means more coordination overhead. The fixed costs get spread, but the variable execution costs grow proportionally — and they are much harder to see on a standard P&L. The manufacturers who reduce costs most durably fix execution first, then scale. --- Why Execution Costs Are Invisible on Standard P&L Execution costs hide in variance lines and in the cumulative effect of small decisions made without full information. They are not captured in the standard cost model because the standard cost model assumes execution runs as planned. When execution does not run as planned, the deviations appear as variances: yield variance, efficiency variance, overhead absorption variance. These are measured and reported but treated as outcomes rather than as symptoms of specific execution failures. The explanation of last month's yield variance consumes management time. The conversation about what will be done differently to prevent next month's variance rarely happens with the specificity needed to produce a different result. --- The Highest-Leverage Execution Cost Drivers Unplanned downtime from coordination failures. Equipment downtime is visible and measured. Coordination-related downtime — waiting for material, waiting for a quality decision, waiting for a setup instruction — frequently appears as reduced throughput with no obvious cause. In plants where execution coordination is weak, coordination-related losses often account for 30–50% of total OEE loss. Quality escapes from late detection. The cost of a quality failure scales dramatically with how late it is detected. A deviation caught at the in-process check costs the time to correct the process. The same deviation caught at final inspection costs the full batch plus rework or disposal. Execution failures that delay quality detection turn cheap corrections into expensive ones. Schedule instability and changeover waste. Every unplanned schedule change drives a sequence of costs: a changeover that was not in the plan, materials that need to be restaged, a production run that ends earlier than the setup cost justified. The root cause of schedule instability is usually execution decisions that create surprises — a batch that fails quality and needs rescheduling, a material that arrives late because the procurement trigger was delayed by a posting lag. Expediting and premium freight. Expediting cost is perhaps the most visible execution cost because it appears as a discrete spend item. What is less visible is that expediting is almost always the final cost of an earlier execution failure — a quality problem that delayed a shipment, a schedule change that compressed lead time, a material shortage that could have been identified and addressed a week earlier. --- How to Fix Execution Before Scaling Output Stage 1: Make execution costs visible. For each cost driver above, establish a current-state measurement. Coordination-related downtime requires capturing waiting events explicitly. Late-detection quality costs require tracking where in the process defects are found. Schedule instability requires counting unplanned schedule changes and their downstream costs. Stage 2: Design decision workflows that address root causes. The cost visibility exercise identifies specific decision failures producing costs. For each, design the minimum workflow that prevents the failure: an in-process checkpoint that surfaces quality deviations earlier, an exception routing that gets material shortages to procurement before they create line stops, a schedule change communication that reaches the floor before setup begins. Stage 3: Measure cost outcomes, not system activity. The temptation is to measure how much the system is being used. The outputs that matter are coordination-related downtime rate, quality detection timing, schedule stability, and expediting spend. Track these weekly and connect improvements explicitly to the workflow changes made. --- The Sequence That Makes Scaling Work Once execution costs are visible, controlled, and falling, scaling output becomes straightforwardly value-creating. The same unit of additional throughput that would have amplified execution costs in a broken system now flows through a controlled process. Schedule adherence is high enough that capacity planning is reliable. Quality detection is early enough that production runs complete rather than fail at final inspection. Coordination overhead is low enough that adding volume adds throughput rather than proportionally more management complexity. Fix execution first. Then scale.