Buy the book & get over $1,000 of virtual tools.
Contact

12 Improvements Found. Zero Implemented

Your continuous improvement program produces no improvement because it was designed for analysis, not action. This episode takes apart why, then walks the 3A Method: Apprehend, Analyze, Activate, six weeks to implementation instead of six months. The 70% Rule that governs the first phase is documented in full on the blog. More operator teardowns live in the Stagnation Assassin Show archive.

Why does your continuous improvement program produce zero improvement?

Because organizations do not fail to identify improvements. They fail to implement them. A Six Sigma project runs four to six months, and by the time it lands the market has moved. Meanwhile the improvements everyone already agreed on sit in a deck waiting for a phase two that never arrives.

Here is the case that still bothers me. Eighteen months to launch a new product. Eighteen months of planning, analyzing, reviewing, revising, validating. By launch, the market had moved, competitors had similar features, and the revolutionary product looked ordinary.

During those eighteen months we identified twelve significant process improvements worth 280 basis points of margin and a 23 percent manufacturing cost reduction. How many were implemented during development? Zero. We will address those in phase two, after launch, when we have time. Phase two never happens. Everyone moves to the next crisis and the improvements die in PowerPoint purgatory while the organization keeps operating with known inefficiencies that everyone agreed needed fixing.

During those eighteen months we identified twelve significant process improvements. How many were implemented during development? Zero. We will address those in phase two, after launch, when we have time. Phase two never happens. The improvements died in PowerPoint purgatory.

What are the three fatal flaws in traditional continuous improvement?

Three flaws kill traditional improvement programs: the perfection trap, where teams wait for complete information before acting; the scale delusion, where only large projects are considered worth running; and the isolation error, where improvement capability is concentrated in a handful of certified specialists who become the bottleneck for everyone else.

The perfection trap

Organizations wait for perfect information before acting. One division spent six weeks analyzing whether to use stainless or aluminum for a bracket costing $347. Six weeks. A competent engineer could decide in thirty minutes at 70 percent confidence. While they analyzed, competitors moved.

The scale delusion

Most methodologies assume only large changes matter. Six Sigma targets 30 to 50 percent improvements and takes four to six months per project. That sounds impressive right up until you do the arithmetic, which is the next section.

The isolation error

Traditional approaches concentrate capability in specialists: black belts, lean experts, certified practitioners. Those specialists become the bottleneck, and everyone else waits for an expert to improve a process they run every day. You have 1,200 employees and maybe twelve improvement specialists. That is 1 percent of the workforce driving while 99 percent waits.

Toyota is the counterexample that matters. In its own 1992 account of the Toyota Production System, the company reported that employees at its Japanese operations proposed nearly two million improvements in 1990 and implemented 97 percent of them themselves. Recent figures are lower, around 810,000 ideas in 2023, but the mechanism is the point: the person who saw the problem was the person who fixed it. No committee, no black belt, no queue.

Do 52 small improvements really beat three large ones?

Run the arithmetic. Three improvements at 40 percent compound to roughly 2.7 times baseline. Fifty-two improvements at 5 percent compound to roughly 12.6 times. Small and constant beats large and rare, and it is not close. This is illustrative math on a single metric, not a forecast, but the direction holds.

The reason is structural rather than mathematical. A large project takes four to six months, which means you get two or three attempts a year and each one is a bet. A six-week cycle gives you eight or nine attempts a year per team, each one cheap enough to be wrong. Speed converts improvement from a wager into a process.

How does the 3A Method finish in six weeks instead of six months?

By replacing three habits: gathering all possible information becomes reaching 70 percent confidence, optimizing a process becomes asking whether it should exist, and documenting after the fact becomes standardizing during implementation. Apprehend runs weeks one and two, Analyze runs three and four, Activate runs five and six.

Apprehend, weeks one and two

Reach 70 percent confidence for intelligent action. Define the problem with hard boundaries: not “quality issues” but “Station 3 produces units requiring rework 23 percent of the time, consuming 47 engineering hours weekly.” Gather only the data that answers three questions. How bad is it? What is causing it? What constrains the solutions? You do not need statistical significance. You need directional clarity.

Analyze, weeks three and four

Eliminate before you optimize. This is the part most improvement programs skip entirely. Before designing a better process, ask whether it should exist at all, and ask of every step what actually breaks if you skip it. One inspection process had 17 checkpoints. Eleven had never caught a defect in five years. We have always done it this way is not a reason. It is an epitaph for common sense.

Activate, weeks five and six

Implement immediately, quick wins first, while the complex components are still being prepared. On day 21 of one project we eliminated redundant checkpoints and relocated equipment, and inspection time dropped from 23 minutes to 14 minutes before the complicated changes were implemented at all. Documentation happens alongside. Standardization is part of implementation, not a later activity.

One inspection process had 17 checkpoints. Eleven had never caught a defect in five years. Eliminating them improved cycle time 48 percent while maintaining quality. Do not improve unnecessary activities. Kill them.

The 3A Method staggered pipeline: two projects complete every two weeksThe 3A Pipeline: Staggered, Not SequentialSix projects live at once. Two finish every two weeks.WEEKS1 to 23 to 45 to 6DONEAPPREHENDANALYZEACTIVATE2Cohort AwaitingAPPREHENDANALYZEthenCohort BwaitingwaitingAPPREHENDthenCohort CEvery two weeks: two projects finish, two projects start.52 improvements a year instead of two to four.

How does the improvement pipeline run six projects at once?

Stagger the starts. Run six to eight short projects simultaneously, with two in Apprehend, two in Analyze, and two in Activate at any moment. Every two weeks, two projects complete and two begin. That cadence produces roughly 52 improvements a year instead of the two to four a traditional program delivers.

Participation rotates by design. Each cycle brings a new cohort onto active projects, and after four rotations the people who were participants are running projects themselves. That is the answer to the isolation error: instead of twelve specialists improving processes for everyone, you are building improvement capability across the organization one six-week cycle at a time.

What are the Seven Laws governing improvement velocity?

Seven laws govern whether an improvement program moves or stalls. They are the constraints I check first when a program has gone quiet, and six of the seven are about speed and ownership rather than technique. Most stalled programs are violating at least three of them simultaneously.

  • Momentum beats perfection. A moving program corrects. A perfect one never ships.
  • Proximity wins. Frontline workers have the best insights, because they have the problem.
  • Resistance is proportional to change size. Small changes meet small resistance.
  • Iteration is mandatory. First solutions are never optimal, so plan the second pass.
  • Focus 70 percent of effort on the top 20 percent of problems.
  • Speed depends on decision velocity, not on analytical horsepower.
  • Integrate within 60 days or the improvement regresses to the old process.

What else do operators ask about the 3A Method?

Four questions come up every time I walk a team through this: why identified improvements die before implementation, how six weeks is even possible, why the small-and-constant math works, and how you build improvement capability across a whole organization rather than concentrating it in a certified few.

Why do identified improvements die before implementation?

Organizations do not fail to identify improvements, they fail to implement them. The perfection trap makes teams wait for complete information. The scale delusion focuses attention only on projects large enough to take months. The isolation error concentrates capability in specialists who become bottlenecks. In one case I watched, twelve improvements were identified during an eighteen-month launch and zero were implemented, because phase two never arrives.

How does the 3A Method complete improvements in six weeks?

Apprehend, weeks one and two, reaches 70 percent confidence rather than perfect information. Analyze, weeks three and four, eliminates unnecessary steps before optimizing anything. One inspection process lost 11 of its 17 checkpoints because they had never caught a defect. Activate, weeks five and six, implements quick wins immediately while complex components are prepared, and standardizes during implementation rather than after.

Why do 52 small improvements beat three large ones?

Compounding. Three improvements at 40 percent reach roughly 2.7 times baseline. Fifty-two at 5 percent reach roughly 12.6 times. Beyond the arithmetic, large projects take four to six months each, so you get two or three attempts a year and every one is a bet. Six-week cycles give you attempts cheap enough to be wrong.

How do you build improvement capability across the organization?

Rotate participation through the pipeline. Each six-week cycle brings a new cohort onto active projects, and after four rotations those people can lead projects themselves. This is the direct answer to the isolation error, where twelve specialists improve processes on behalf of 1,200 employees while the other 99 percent of the workforce waits in a queue.

What is the verdict on traditional continuous improvement?

The failure is not the methodology. Six Sigma and lean both work when they run. The failure is deployment velocity: four to six months per project, capability locked inside a certified few, and a queue that guarantees most identified improvements never get implemented at all.

VERDICT: WEAPONIZE IT

Keep the analytical tools, throw out the calendar and the org chart around them. Six weeks, 70 percent confidence, eliminate before you optimize, and rotate participation until the whole building can run a project. Your assignment this week: name three problems you have been studying for more than 30 days, apply the 70% rule to each, and if you have enough understanding to act, form five-person teams with six-week deadlines and launch. Track completion rate. You will never confuse analysis with action again.

Where can you go deeper on this episode?

The frameworks named in this episode are documented in full on the blog, and the diagnostic toolkit is free. Start with the 70% Rule if the perfection trap is your bottleneck, and with the transformation team material if the isolation error is.

About the Stagnation Assassin

Todd Hagopian is a Fortune 500 transformation executive who has generated $3B+ in shareholder value across Berkshire Hathaway, Illinois Tool Works, Whirlpool, and JBT Marel, where he serves as VP of Global Product Strategy. Known as The Stagnation Assassin, he is the author of two published books: The Unfair Advantage: Weaponizing the Hypomanic Toolbox and Stagnation Assassin: The Anti-Consultant Manifesto. His blog is published in 15+ languages and read by operators worldwide.

Every organization has improvements sitting in a deck waiting for a phase two that will never arrive. Book an Improvement Velocity Audit and we will count what your teams have already identified and not implemented, then tell you which of the three fatal flaws is holding the queue shut. Start your Improvement Velocity Audit.