you are running too many improvement projects to improve anything

An organization serious about improvement tends to accumulate improvement projects. Each one is worthy, each addresses a real problem, and starting another feels like a commitment to getting better. So the list grows, and at some point it grows past what the organization can actually do, and something counterintuitive happens. More improvement projects start producing less improvement, because the projects are spread so thin that most of them stall, interfere with one another, and never actually finish. Past a certain point, adding improvement activity reduces improvement, and a lot of organizations are well past that point without realizing it.

thin is the enemy of done

Improvement projects need focused attention to reach completion, and attention is finite. When a few people are responsible for many simultaneous projects, each project gets a thin slice of their focus, and thin attention is exactly what improvement work cannot survive. A project that gets a little attention now and then does not progress, it lingers, half-done, consuming capacity without producing results. Ten projects each getting ten percent of the needed attention do not average out to reasonable progress. They mostly stall, because improvement is not linear in attention, and below a threshold of focus a project simply does not move. The organization is busy on all ten and finishing none.

projects interfere with each other

Beyond the dilution of attention, simultaneous projects actively interfere. They compete for the same people, the same resources, the same management bandwidth, and they change the same processes in ways that tangle together. When several improvement efforts are altering an operation at once, it becomes impossible to tell what is causing what, which change helped and which hurt, and the improvements step on each other in ways that undermine all of them. The interference is not additive, it is multiplicative, and a large portfolio of concurrent projects can generate so much mutual interference that the whole effort produces less than a fraction of it would have. Doing many things at once is not the same as doing many things.

why the list keeps growing

The list grows because stopping or refusing a project feels like giving up on something worthwhile, while starting one feels like progress. Every project on the list addresses a real problem, so removing any of them means consciously deciding not to fix a real problem right now, which is uncomfortable. And starting a new project is visible and satisfying in a way that finishing an existing one quietly is not. So the incentives all push toward accumulation, toward a longer and longer list of started-but-unfinished improvements, and against the discipline of limiting work in progress to what can actually be completed. The result is a portfolio that looks like tremendous commitment to improvement and delivers very little of it.

finishing beats starting

The counterintuitive discipline is to do fewer improvement projects at once, and to finish them. A small number of projects, given the focused attention they need to actually complete, will produce more real improvement than a large number that never land, because a finished improvement delivers value and an unfinished one delivers nothing but consumed capacity. This means limiting how much improvement work is in progress at any time, resisting the urge to start something new until something current is done, and accepting that some worthy problems have to wait. That waiting is uncomfortable, and it is the price of actually completing the improvements you do take on, which is the only kind that matters.

the honest look at your portfolio

It is worth counting how many improvement projects your organization has open right now, and honestly assessing how many are actually progressing versus lingering half-done. In most operations the number open far exceeds the number moving, and the gap is capacity spread too thin to finish anything. Cutting that list down to what can genuinely be completed, and holding the line against starting more until those are done, feels like doing less and produces more. The goal was never to have many improvement projects. It was to actually improve, and that comes from finishing, not from starting.

How many improvement projects does your organization have open right now, and how many of them are genuinely moving rather than quietly consuming capacity while going nowhere?