It’s 7:15 AM and the day is already off script. A machine went down overnight. A key operator called in sick. A customer wants their order moved up a week. By 9 AM, you’ve made six decisions that weren’t on your calendar, and the actual plan for the day hasn’t been touched. If that sounds familiar, you already know the difference between firefighting and system building, even if you’ve never put a name to it.
Firefighting feels productive. You’re solving real problems, moving fast, and the plant keeps running because you’re the one holding it together. System building feels slower and less urgent, right up until the day you’re not in the building and everything still needs to run without you. Most plant leaders know intellectually that system building matters more in the long run. Few have an honest read on how much of their actual week goes toward it.
This self-assessment is built to give you that read, and a practical way to start shifting the balance.
Why Does Firefighting Feel Like the Job?
Firefighting isn’t a character flaw. It’s what happens when a plant’s problems consistently arrive faster than its systems can absorb them. A leader who’s good in a crisis gets rewarded for being good in a crisis, which reinforces the exact behavior that keeps crises coming.
The trap is that firefighting produces visible wins. You solved today’s problem. The line is running again. The customer got their order. Those wins feel like leadership, and in the moment, they are. What they aren’t is progress on the underlying reason the fire started in the first place.
System building is different. It’s the maintenance schedule that prevents the breakdown, the cross-training plan that means one sick call doesn’t derail the shift, the standard work that makes the answer to “how do we handle this” something other than “ask the plant manager.” None of it feels urgent on any given Tuesday. All of it determines whether next Tuesday looks the same as this one.
The Self-Assessment: Five Questions for Plant Leaders
Answer these honestly, based on the last two weeks, not your intentions for the next two.
One: When something goes wrong on the floor, does the fix stop at “problem solved,” or does someone ask why it happened and change something so it’s less likely to happen again? If the answer is almost always the former, you’re in firefighting mode by default.
Two: If you were out of the building for a full week with no phone access, would production, quality, and shipping run at their normal pace? If the honest answer is no, the plant is running on your presence rather than on documented systems, and that’s a system building gap, not a staffing problem.
Three: How many decisions came to you last week that a properly trained supervisor should have been able to make without you? If you’re losing count, decision-making authority hasn’t been pushed down far enough, and every one of those decisions is time stolen from actual system building.
Four: When you look at your calendar from the last month, how much of it was reactive versus planned? Plant leaders stuck in firefighting mode often find that 70 percent or more of their week gets consumed by things that weren’t on the calendar Monday morning.
Five: Do you have a written standard for your top three recurring problems, the ones that show up every month like clockwork? If those problems still get solved fresh every time, with no documented process feeding back into prevention, that’s the clearest sign that system building hasn’t caught up to the plant’s actual needs.
What Your Answers Are Telling You:
If most of your answers point toward reactive, individual-dependent decision-making, you’re not failing as a leader. You’re operating in a pattern that most growing manufacturing businesses fall into, because system building takes time upfront that firefighting never seems to allow for.
The plants that break out of this pattern don’t do it by working harder or being available more hours. They do it by deliberately shrinking the firefighting workload, one recurring problem at a time, and reinvesting that recovered time into the systems that prevent the next fire. This is the same shift founders go through when they finally stop being the single point of failure for every decision in the business, and start building a team that can make calls without them.
Moving From Firefighting to System Building
Start small and specific. Pick the single most frequent fire, the problem that eats the most time across a typical month, and build one system around it. A checklist, a standard, a clear escalation path, something concrete that exists whether or not you’re in the room.
Push decision-making down deliberately. If your supervisors are checking with you on calls they’re capable of making, that’s not caution, it’s a system gap. Give them clear boundaries for what they can decide on their own, and hold them accountable to those boundaries rather than pulling every decision back to yourself.
Protect time for system building the same way you’d protect a production deadline. If it’s not scheduled, firefighting will always win, because firefighting is urgent and system building is only important. A recurring block of time each week, even ninety minutes, dedicated specifically to closing one system gap, adds up faster than most leaders expect.
Track the shift. Revisit this self-assessment every quarter. The plants that actually change aren’t the ones with the best intentions, they’re the ones that measure whether the ratio of reactive to planned time is actually moving.
System building doesn’t eliminate every fire. Manufacturing will always have surprises. But a plant with strong systems has fewer fires, smaller ones, and a leadership team that isn’t the only thing standing between order and chaos. That’s the real payoff, and it’s available to any plant leader willing to trade a few hours of firefighting each week for the harder, quieter work of building something that doesn’t need them in the room to function.