What 90 companies told us about CI software

Before we built OpX we went and listened. Over six months we held in-depth conversations with 90 companies about continuous improvement software: what they were using, what they wanted, and what had let them down. This is not a feature comparison or a ranking, it's what 90 real organisations told us when we asked what they needed from the tools meant to support their improvement work.

The pattern was clearer than we expected. Across all those conversations, the same three problems came up, and none of them were the ones the software market tends to shout about. If you've been told to go and find CI software and come away underwhelmed by everything you've seen, there's a good chance one of these is why.

CI software rarely fails from a lack of knowledge

The first thing we heard surprised people when we repeated it back. Teams almost always know what to do. The methodology is understood, the training has happened, the frameworks are in place. It was evident that knowledge was rarely the constraint.

Execution and proof were. 

Again and again, leaders told us they could run the improvement work but couldn't show, cleanly and on demand, that it had worked. The Lean Enterprise Institute has called this out as one of the least-developed disciplines in operational improvement. The gap sat between doing the work and evidencing it, which is exactly the gap that decides whether a programme keeps its funding. We went deep on it separately, in why your CI reporting doesn’t survive the boardroom, because it surfaced in almost every conversation. Most continuous improvement software is built to run the work, but very little of it is built to prove the work.

Admin pressure is quietly crushing CI teams

The second pattern was about where CI leaders' time actually goes. In theory it goes on improvement, however, in practice, a punishing amount of it goes on coordination and reporting: pulling numbers together, chasing updates, reconciling figures that were never designed to connect, and rebuilding the same status picture every quarter.

The people we spoke to were spending more time justifying the programme than running it. That’s a tooling problem. More projects and more sites mean more admin, and the software most teams had was adding to the load rather than lifting it. Operations software that generates coordination work instead of removing it is, for a stretched CI team, part of the problem rather than the fix.

Buyers want ownership, not a blank slate

The third finding was the most practical, and the one the market gets most wrong. Buyers didn't want infinite flexibility. A blank-slate platform you can configure into anything sounds appealing until you're the one who has to configure it, maintain it and stop it breaking. The admins and platform owners we spoke to wanted control, governance and an audit trail, but they did not want a construction project.

What they described was closer to the IKEA effect. They wanted to build it themselves, but with structure, shortcuts and sensible defaults, not a box of parts and no instructions. The CI tools that disappointed them sat at the two extremes: rigid systems that couldn't bend to how the organisation actually worked, or empty platforms that could become anything and so arrived as nothing. What was missing in the middle was ownership with guardrails.

What good continuous improvement software should solve for

Put the three findings together and the brief writes itself. Good continuous improvement software should prove the work, not just run it. It should take admin off the CI team rather than adding to it. And it should give buyers real ownership without handing them a blank slate to assemble alone.

See how OpX was built around what we heard

We'll let you draw your own conclusion about how well the tools you're evaluating meet that bar. The reason we can describe it with any confidence is that we didn't guess it. It came from 90 companies telling us, in their own words, what the market had so far failed to give them. That's the same evidence-first approach we brought to scaling continuous improvement with Rob Regan, whose two decades in the field kept pointing at the same execution and proof gap the research surfaced.

If you're evaluating options and want to see what CI software built around those three findings looks like in practice, OpX is the place to start.

Request access and book a demo