Ask a leadership team how many hours went into last quarter’s operating review. Then ask how many of those hours went into a problem the team had already solved once before. Watch how the room reacts to the second question.

That reaction is the tell. Most organizations don’t have language for it, much less a number, because they’ve never separated a new problem from an old one wearing a different name. A fire that’s fought instead of extinguished at the source doesn’t stay out. It comes back, and the second and third responses cost more than the first: more meeting time, more credibility lost with the board, more of the leadership team’s attention pulled away from the work that actually moves the business forward.

Part of why this stays invisible is where it lives. Recurring fires rarely start at the top. They start with a frontline or middle manager who’s handed a problem or a deadline, but none of the training to close it out for good. So they patch it and move on, because patching is what gets rewarded in the moment. SHRM’s 2026 CHRO Priorities and Perspectives report found that leadership and manager development has ranked as chief human resources officers’ (CHRO) single top priority for two years running, cited by nearly half of them.

That’s not HR chasing a trend. It’s the function closest to the problem naming it directly: The managers tasked with closing issues for good are, by their own leadership’s admission, still the biggest unsolved capability gap in the building. Multiply that gap in every plant, region, or business unit, and firefighting stops being an occasional event. It becomes the operating model.

In one capital-intensive manufacturing engagement, recurring throughput shortfalls were handled as isolated production events. Teams added labor, reshuffled schedules, and escalated maintenance until output recovered, at which point the issue was considered closed. But the constraints returned because production and maintenance lacked a shared understanding of the required actions, and no cross-functional owner was accountable for making the fix hold. The pattern reduced throughput, left production assets underused, and limited the return on a major investment. Once leadership recognized the recurrence as a systemic execution failure rather than a series of emergencies, it aligned ownership, actions, and performance management around eliminating the cause instead of celebrating the recovery.

This isn’t a training gap or a communication gap on its own. It’s a measurement gap. Asana’s Anatomy of Work Global Index found that the average knowledge worker loses roughly 209 hours a year—more than five work weeks—to duplicative work. These are tasks that have, in some form, already been done. Recurring fires aren’t a rounding error inside that number. They’re most of it.

Ask most CEOs to name their top strategic risk, and they’ll give you a confident answer: tariffs, talent, technology, geopolitics. Ask how much leadership bandwidth went last year into re-solving problems that were supposedly closed out, and the confidence disappears. That’s not because the number is small. It’s because no one has ever tried to count it.

That’s starting to change at the board level, even if the language hasn’t caught up yet. The Conference Board’s most recent CEO research identifies the single biggest priority for boards and CEOs in 2026 as closing the gap between the strategy set at the top and what actually happens on the ground, under real operating conditions. Boards are being told, in effect, that the risk sitting closest to home isn’t the next external shock. It’s whether the organization can execute reliably once the shock hits. For years, that kind of execution risk sat quietly underneath strategy on the board’s list of concerns. Naming it directly is a meaningful shift, and it means the organizations that can actually measure and reduce recurrence now have a real head start over the ones still treating it as background noise.

Recurring operational failure is exactly that risk, just measured at the wrong altitude. It shows up in the board deck as “execution risk.” In the abstract and on the floor, it’s the same defect, the same missed handoff, the same customer complaint, quarter after quarter.

That gap matters more than it looks like it should. The American Society for Quality estimates that the cost of poor quality (the rework, scrap, warranty claims, and customer attrition that come from doing the same job twice) runs at 10% to 20% of revenue in a typical organization, manufacturing or otherwise. In defense and manufacturing environments specifically, that math gets even less forgiving: The same failure that shows up as a line item elsewhere can trigger a customer audit, a contract penalty, or a safety review long before it ever reaches a P&L. That’s not a rounding error. It’s often the gap between a good year and a great one, quietly handed back to problems nobody actually rediagnosed the first time.

And it’s a drag that compounds quietly. Strategic ambiguity gets debated in the boardroom. Recurring operational failure doesn’t. It gets absorbed, one fire drill at a time, until it’s simply how the place runs. The Project Management Institute’s most recent published measure puts a number on one slice of it: Organizations waste roughly a dime of every dollar invested in projects to poor performance. A meaningful share of that is the same execution failures resurfacing project after project, team after team. Multiply that pattern across every function, not just formal projects, and recurrence stops looking like a rounding error and starts looking like a line item nobody’s tracking.

That’s the part worth fixing first. Before an organization can reduce operational drag, it needs a way to see it—to tell a genuinely new problem apart from a familiar one in different clothes, and to know how its own constraints stack up against organizations solving the same problem better. Most companies can tell you their revenue, their margin, their head count. Very few can tell you how many of last year’s fires were repeats, or how that number compares to a peer running a similar operation. That’s the gap Brooks International is now studying directly in research that will let CEOs compare their own operational constraints against their peers’ for the first time.

None of that requires a finished benchmark to start. Three moves work now: Tag every fix as “new” or “repeat” before the ticket closes; assign one owner to anything that happens twice; and put the repeat count, not just the incident count, on the dashboard leadership already reviews. None of it is sophisticated. It’s just the first time anyone’s kept score.

So ask the question plainly: How many hours did your leadership team spend last quarter solving a problem it had already solved once? Would anyone in the room be able to answer that with a number, rather than a guess? And if the honest answer is no, that’s not a gap in your memory. It’s a gap in your operating model.