Before You Expand the Facility, Improve the Operating System
Capacity should be understood before capital is committed.
From CI Activity to Execution Reliability
These articles extend the themes from the KPI Fireside podcast conversation. The point is not that continuous improvement fails because the tools are wrong. The deeper issue is that tools, training, events, dashboards, and certifications only create value when leaders connect them to a clear business condition, disciplined problem solving, capability building, operating cadence, and follow-through.
In that sense, the question for executives is not simply whether the organization is doing continuous improvement. The better question is whether the operating system is performing differently because of the improvement effort.
The Instinct to Add Capacity
When an organization feels capacity constrained, the first instinct is often to add something. Add people. Add equipment. Add space. Add a shift. In more significant cases, the answer may appear to be a new facility or facility expansion.
In the KPI Fireside conversation, I mentioned two examples. One involved a nonprofit that was trying to increase capacity and was considering a new building. Another involved a local company that manufactures crash test dummies and related products. They were also looking at ways to increase capacity, including the possibility of another building or additional equipment.
Both situations illustrate the same executive question: before we commit capital, do we understand the actual operating constraint?
Capacity Is Not Only an Asset Question
Capacity is often treated as an asset question. How much space do we have? How many machines do we have? How many people are available? Those questions matter, but they are incomplete.
Capacity is also created or lost through flow. If work waits between steps, if material is moved too often, if scheduling is disconnected from actual constraints, if approvals are delayed, or if rework consumes available time, the organization may appear to be out of capacity when it is actually losing capacity inside the current system.
In those cases, expansion may still eventually be needed, but the timing, size, and design of the expansion should be informed by the real workflow. Otherwise, the organization may simply reproduce the same operating problems in a larger space.
The Right First Step
The right first step is to look at the entire workflow and identify the capacity levers. Where is demand entering the system? Which step determines the pace? Where is work waiting? Which resources are overloaded? Which activities consume space without creating value? Where do decisions or information slow the flow?
For this kind of situation, value stream mapping can be a useful tool, but again, the tool is not the point. The point is to understand the operating system well enough to make a better executive decision. If the goal is to increase output by 50 percent, leaders need to know what specifically prevents the current system from reaching that level.
Measure Twice, Cut Once
Keith used a phrase in the conversation that fits this issue well: measure twice, cut once. A facility decision is often expensive, disruptive, and difficult to reverse. It affects capital allocation, management attention, staffing, layout, customer commitments, and future flexibility.
That does not mean leaders should move slowly for the sake of moving slowly. It means they should be disciplined. When significant capital is involved, the organization should understand whether the constraint is truly space, equipment, labor, layout, scheduling, process stability, or leadership cadence.
The Execution Reliability Lesson
The execution reliability lesson is that capacity problems should be diagnosed before solutions are selected. A new building may be the correct answer. New equipment may be the correct answer. But those answers should come after the organization understands the current condition, the target condition, the constraint, and the value of closing the gap.
Executives do not need more improvement activity around capacity. They need a reliable way to determine whether the current operating system can be improved before capital is committed.
More Stories Behind the Conversation
- Lead Time Reduction and Execution Reliability
- Green Belt Certification and Business Results
- Why We Built CI Navigator
- KPI Fireside Podcast: From CI Activity to Executive Execution
No sales pitch. We’ll determine quickly whether there is meaningful value to create.