The organizations that improve the most are not the ones running the largest programs. They are the ones that solve the single problem that matters most, with their own people, and then do it again. The ambition is not smaller for being focused; it is more likely to be realized, because the work is sized to what the organization can actually absorb and owned by the people who have to live with the outcome. That is a different starting point from the familiar instinct to commission a broad program, and in our work across Canadian mid-market businesses, public-sector organizations, and investor-backed companies, it is the one that holds.
The intent is rarely the problem
In most of the organizations we work with, the will to improve is already present and the problem is already named. A hospital knows which quality indicator is slipping. A municipality knows which service is taking too long and frustrating residents. A mid-market manufacturer knows where margin leaks between the quote and the delivery. What is missing is not awareness or appetite; it is a structure for acting on what they already know, with the people they already have, without stalling the rest of the organization in the process.
Our own data says the same thing. In a benchmark of fifty-five improvement-engaged individuals across Canada's health sector, each scoring their organization against our operational-excellence framework, the practices that rated highest were about intent and direction: reviewing and updating strategic priorities averaged four out of five. The lowest were the daily mechanics that actually deliver on those priorities: running improvement as a regular, planned activity scored just below three, and acting on deviations from the standard scored about the same. These are respondents whose organizations already invest in improvement, and even they rate their priorities well above their ability to execute on them. The gap is one of execution, not intent.
The usual remedy makes the gap worse. The instinct is to commission a broad, organization-wide program, and that is precisely what these organizations cannot absorb. A mid-market business rarely has the slack to run everything at once, and a hospital cannot pause care in order to remake itself. The pressure compounds the problem: the average employee faced ten enterprise changes in 2022, against two in 2016, even as willingness to absorb more of them fell sharply (Gartner). Research on large-scale performance programs has long held that the difficulty lies less in deciding what to do than in doing it and making it hold (McKinsey, 2016). What these organizations need is not a bigger program. It is a repeatable structure that delivers a result without the disruption.
The gains that hold are taken one at a time
The organizations whose gains actually hold tend to follow a recognizable pattern, and it runs the other way from the broad program. They do not take on everything at once. They find where the value really is, take on the one problem that matters most, and solve it with the people who own the work, wrapping capability building, change management, and a daily-management rhythm around it so the gain stays. Then they do it again. Ambition is not abandoned; it is sequenced.
It holds for three reasons that a broad program rarely manages at once: it aims at the value that actually matters to the organization, it builds the result into the people who do the work so it lasts, and it puts technology in its proper place, after the process rather than before. Each is worth taking in turn.
I The value is the organization's own
What "the problem that matters most" means is deliberately not financial alone. For a manufacturer it may be margin or working capital; for a hospital it is more often a patient-safety or flow target, or a commitment made in a quality improvement plan; for a municipality it may be a service level residents actually feel; for an investor or operating partner it is earnings, working capital, and a result delivered inside the hold period; and for a growing number of organizations it is an emissions or sustainability goal. The method does not change with the metric. What changes is the scoreboard, and the scoreboard belongs to the organization.
This matters most in the public and health sectors, where "improvement" has too often arrived as a polite word for reductions. The work described here runs the other way. Its purpose is capacity creation rather than cost cutting: time returned to clinicians and caseworkers, throughput recovered without new headcount, the same team carrying more of the work that genuinely requires their judgment. Where the goal is financial, the gain shows up in the financials; where it is a safer ward, a faster permit, or a lower carbon footprint, it shows up there, measured the same way.
II The result is built within, not delivered to
If value is the organization's to define, the result is also theirs to own, and that choice is decisive. Improvement is frequently delivered to an organization by an outside team that designs the solution, reports a gain, and then demobilizes, which leaves the result dependent on the next engagement to sustain it. Improvement that lasts is built within the organization, by the people who run the work every day, so that the capability remains when the engagement ends. This is not a matter of taste. The work of a hospital, a public-works department, or a factory floor happens in thousands of small decisions that no external team is present to make, and only the people making those decisions can hold a gain in place.
A plan the owner did not build is a plan the owner will not run.
Our benchmark shows why this is where gains are won or lost. Even where respondents' organizations were already active in Lean and quality improvement, not one capability was rated at the level we would call embedded; the missing ingredient was consistency, not capability. What separated the higher-scoring organizations from the rest was the daily-management layer, the improvement cadence and performance visibility that a leading group had made routine and most had not. The wider evidence points the same way: programs that engage more than a third of the workforce in building new skills show materially better outcomes, including higher shareholder returns over the following eighteen months, and when senior leaders model the change themselves rather than delegate it, success becomes several times more likely (McKinsey, 2021).
Capability building is therefore not a course bolted on at the end. It is taught and then applied under coaching to a real problem the team owns, until the new way of working is simply how the work is done. In practice it means belts earned through the work, a daily-management system, and leader standard work, so the routine that sustains the gain outlives the engagement.
III The process comes before the technology
The costliest mistake is to reach for technology before the process is ready. Automating a process that has not been improved does not fix it; it encodes its faults and runs them faster, then adds a system to maintain. The evidence is stark: more than eighty percent of AI projects fail, roughly twice the rate of other technology projects, and seldom because of the technology itself (RAND, 2024). The counsel to improve a process before automating it is not new (Harvard Business Review, 2018); what is new is how cheap it has become to skip the improvement and buy the tool.
The sequence is what protects the investment, and it is built into how a Sprint runs. The Initiative Owner frames the change against a measured baseline, redesigns the process to the future state, and only then asks what should be automated, so that any technology lands on a clean process rather than a broken one. Rules where they will do, and AI only where the work genuinely requires it.
The method is deliberately spare
Those three principles are easy to name and harder to run. The method that carries them is a single assessment and one focused Sprint, in three steps, with capability and change built through all of them.
Assess, the OpsScan
A short, outside-in diagnostic that establishes where process, rather than effort, is the constraint and ranks the opportunities by what they are worth and how readily they can be captured. Its output is a prioritized, quantified list, not a report, so the organization can see which problem to solve first and what solving it is worth. It is useful on its own and carries no obligation to continue.
Prep, build the case with the owner
We frame the selected problem against a measured baseline, build the business case and a month-by-month plan tied to its KPIs, and name the person inside the organization who will own the result. Their capability building begins here. The plan is co-created, never handed over, because a plan the owner did not build is a plan the owner will not run.
Execute, deliver and make it stick
We run the change on a cadence, going after the quick wins first, and we stay in it: coaching the owner, holding the weekly rhythm, and confirming that value is flowing rather than sitting on paper. The owner finishes the Sprint having delivered the result and earned the credential through the work itself.
Running beneath all three is the part most often skipped: capability building and change management, the belts, the daily-management system, and the leader routines that turn one delivered result into a habit the organization keeps.
One result earns the next
Starting with one problem is not a limit on ambition; it is the mechanism that makes ambition affordable. A first result, delivered and visible, earns two things no proposal can: the confidence of the people who produced it, and the room, in both time and credibility, to take on the next problem. The owner who carried the first Sprint can carry the second with less help, so the organization holds both a gain on the board and a person who knows how it was won.
Consider a long-term care operator that began with a single kitchen. A dietary team, taught the method and coached through it, redesigned the workflow and brought a persistent monthly food overspend down to a small fraction of its former level, while improving rather than trading away the residents' dining experience. The result was visible and owned, and it did not stop there: the same team carried the method into overtime, into continence-product use, and into fall prevention, and the operator went on to certify dozens of its own staff who led improvements no consultant touched. No single project explains where that operator stands today; the capability that produced all of them does. Sequenced this way, focused efforts compound into a program of improvement the organization runs increasingly on its own, rather than a single large undertaking it must absorb all at once.
The same logic scales across a portfolio. For a private-equity owner, a sequence of focused Sprints compounds into measurable earnings improvement without betting the asset on one disruptive program, and because the capability is built into the management team rather than carried out the door by advisors, it strengthens the business in a way that survives the hold and supports the exit.
Where to begin
The first question is not where the organization needs a program. It is narrower and more useful: what is the one problem that matters most right now, and who on the team will own it? An organization that can answer that, and is given a structure to act on the answer, does not need to wait for the conditions to be right for something larger. It can start where it matters most, build the capability as it goes, and find that improvement has quietly stopped being something it buys and become something it does.
Case patterns are drawn from Leading Edge Associates engagements and are presented with identifying details generalized. Benchmark figures are from the Leading Edge Associates operational-excellence benchmark (2026), a directional self-assessment by fifty-five improvement-engaged individuals across Canada's health sector. Other sources: McKinsey & Company, "The how of transformation" (2016) and "How capability building can power transformation" (2021); RAND Corporation, "Why AI Projects Fail and How They Can Succeed" (2024); Harvard Business Review, "Before Automating Your Company's Processes, Find Ways to Improve Them" (2018); Gartner change-fatigue research (2022).