Dead Program Walking

Sooner or later, every organization under resource pressure asks the same question about its continuous improvement and innovation program: is this worth keeping? The question usually arrives dressed as prudence. Budgets tighten, a reorganization gets underway, and someone observes that improvement is everybody's job anyway (good people fix things without a program telling them to). On the spreadsheet, the program looks discretionary: a staff line, a software line, a training line. With no product or platform attached. Because of this, it is often the first line offered up.

The question has a second form and arrives with new leadership. An incoming executive inherits dozens of functions and questions almost none of them. Nobody surveys the org chart, notes that the previous administration ran a finance department, and concludes that finance was the last regime's pet enthusiasm. But an improvement program (innovation, continuous improvement, Total Quality Management, Six Sigma, Lean) reads differently, especially one the predecessor visibly championed. It reads as a personal project. If its results were never made legible (and in loosely run programs they rarely are), the conclusion writes itself. That was the last leader's thing and it never seemed to do much. So, the program is dissolved, not because evidence condemned it, but because nobody ever positioned it as what it is: a standing capability of the enterprise. No more optional than the ledger and no more attached to any one leader's tenure.

Both versions deserve a serious answer, based on evidence, not sentiment. What follows is that case. What happens to organizations that run continuous improvement and innovation as a structured, staffed, and funded capability? What happens to those that run it ad hoc? And why the difference compounds.

Does any of this show up in the financials? The strongest data comes from an eight-year natural experiment. A study published in Production and Operations Management followed more than a thousand publicly traded firms that won innovation awards (the awards serving as a proxy for programs that actually execute) and compared each against matched control firms from before the award through the years after. The winners' mean change in return on assets ran roughly 33 percent higher than the controls'. Their change in sales ran 39 percent higher. Their cost per dollar of sales improved while the controls' deteriorated. And the market priced it in. The change in their Tobin's Q (market value measured against the replacement cost of assets) ran nearly 24 percent higher. Effective programs do not merely produce ideas. They produce financial performance. And they keep producing it for years.

That is what effectiveness pays. So, how many organizations can collect? In BCG's 2024 study, 83 percent of more than a thousand senior innovation executives ranked innovation among their organization's top three priorities. Yet only three percent qualified as ready to deliver on it (down from 20 percent two years earlier). McKinsey's research shows the same shape. More than 80 percent of executives call innovation a top-three priority. Yet fewer than 10 percent are satisfied with their innovation performance. Belief is nearly universal; capability is rare. The distance between the two is where programs (or their absence) do their work.

What lives in the gap between believing and being able? Not a shortage of talent, or desire, or even funding. BCG has a name for it: zombie organizations. These are enterprises that go through the motions of innovation, running activity without strategy, readiness, or connection to the business. The pattern is recognizable at any scale. Innovation as event rather than discipline (the offsite, the hackathon, the idea challenge that ends the day the winners are announced). The part-time champion assigned to transformation on top of a day job. The pilot that succeeds and then dies because no mechanism exists to carry it anywhere. Fifty-two percent of innovation executives name an unclear or overly broad strategy among their top three challenges. This is another way of saying the activity was never designed to produce anything in particular.

Ad hoc efforts do not fail for lack of enthusiasm. They fail because nothing holds them up when the enthusiasm moves on: no dedicated owner, no budget that survives the quarter, no standard for deciding which ideas matter, no cadence that carries a validated idea into operation. Informal improvement produces anecdotes. A program produces a pipeline.

What does having neither cost? Nothing, at first; neglect sends no invoice. No organization announces a decision to decay. It simply stops deciding otherwise. Processes drift from the way work is actually done. Workarounds harden into procedure. And rework accumulates the way deferred maintenance accumulates. Invisibly. Then expensively. By the time decline shows up in a metric that leadership watches, it has been underway for years. Too late to be proactive. Maybe too late to be reactive.

The people closest to the work notice first, and they respond rationally. Gallup and Workhuman found that employees whose contributions are recognized are four times as likely to be engaged at work. The inverse is the risk that matters more. A workforce that watches its observations go nowhere learns to stop observing. The organization does not lose the ideas. It loses the habit of offering them. And the people who thrive on solving problems (the exact people an improvement capability depends on) migrate to the places that let them solve problems. Neglect is not a pause; it is a compounding withdrawal from the account that funds adaptation.

A specific arc is worth naming, because so many organizations have lived it. A leadership team recognizes the decay (or catches the ambition of a new strategy cycle) and launches a program in response. The launch is the easy part, and it is exciting: executive sponsorship, a platform, a branded challenge, a first burst of ideas. But the program was designed around its launch rather than its operation. Nothing underneath the excitement decides which ideas matter. Nothing carries a validated idea into the business. Nothing reports what the effort produced in terms of what a CEO, CFO, or COO would accept. Adrenaline is not an operating model, and it wears off the way adrenaline always does. Submissions slow (nobody saw the first ideas go anywhere) and patience thins. Sponsors drift toward newer initiatives. The program falters under the same paralysis it was created to cure. Then the end comes quickly. The budget line is challenged. The program is cancelled. The team is released. And innovation is pronounced a failed exercise.

The pronouncement is half right; the exercise failed. The discipline was never tried. But the verdict does not make that distinction and the damage outlasts the program. The workforce learns that contributing ideas is effort spent for nothing. The next leadership team inherits proof that these programs do not work here. A half-built program does not merely waste its own budget. It salts the ground the real capability would have to grow in.

What separates the three percent from the zombies? Not a methodology purchase. Lean. Six Sigma. Design Thinking. Agile. The methods are proven, public, and available to everyone. Which is precisely why they differentiate no one. What the effective few have is a system. It is structured intake that pulls in every signal about what could be better (from everyone, continuously). Evaluation that decides which signals matter with the least friction. Governance that acts in priority order at the lowest level competent to act. Implementation with rigor, speed, and managed risk. And the discipline to sustain each gain, then go again. Staffed by people whose actual job it is. Funded like the capability it is. Measured like anything expected to produce a result.

The record for systems run that way is well documented (provided the documentation is read carefully). Improvement folklore is thick with spectacular percentages that dissolve on inspection. The numbers that survive scrutiny are the ones companies reported about themselves. General Electric's 1999 annual report credited its Six Sigma program with more than $2 billion in benefits in that single year. And Motorola (which invented the method and won the first Malcolm Baldrige National Quality Award) documented $16 to $17 billion in savings in the decades that followed. Ford's Consumer Driven Six-Sigma returned $52 million to the bottom line in its first year, then roughly $300 million and a two-point gain in customer satisfaction in its second. Amazon reduced unplanned equipment downtime across its fulfillment network by 69 percent with a predictive-maintenance program. And a Vermont flooring manufacturer raised production 29 percent with no capital investment. The scales differ by orders of magnitude; the mechanism does not. None of these results came from a suggestion box. None came from heroics. All came from a system, run on purpose, for years.

When is the capability most at risk? Not at its founding: at the handoff, the reorganization, the merger of teams, the leadership transition. All precede the moment when a structured program is broken apart and its responsibilities distributed into the business. The announcement always uses the same vocabulary: efficiency, streamlining, decentralization, empowerment. Innovation is everyone's job now. And for the first months the decision appears vindicated. This is because dismantling a system produces no immediate failure. The intake channel goes quiet, but quiet reads as calm. The evaluation standard disappears, but decisions still get made somewhere, by someone. The pipeline stops carrying validated improvements into operation, but the operation keeps running on the gains already banked.

The bill arrives later, and it arrives addressed to someone else. Distributed responsibility without structure is not empowerment; it is abdication with better branding. Every mechanism described above begins to run in reverse: signal is lost instead of collected, decay compounds instead of being corrected, and the workforce relearns silence. An organization that dismantles a working system of change has not reduced its risk. It has converted a visible line item into an invisible liability, whose size will be discovered at the worst possible time, by whoever is standing there when it comes due.

Change arrives on a continuum. At one end: thousands of small corrections to the way work gets done. At the other: transformation. Most organizations are bad at both ends and worse in the middle. The ones that endure absorb change at every point on that continuum (predictably, with managed risk, at the highest rate they can sustain). And that capacity is never an accident; never one leader's personality expressing itself through a budget. It does not belong to an administration. And it should not leave when one does. It is a standing capability, in the way finance is a standing capability: built, staffed, funded, measured, and operated, or else not real.

An organization that keeps its capability is not spending on optimism. It is maintaining the system that produces its next advantage. An organization that cuts it saves the line item, and begins, quietly, to pay for the decision everywhere else.