The organizations that improve the most are rarely the ones that attempt the most at once. They are the ones that identify the single problem that matters most to them, solve it with their own people, and turn that result into the capability to solve the next one. 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.
That gap is easy to underestimate, because recognizing a problem and running a disciplined effort to fix it are different capabilities, and the second is the rarer one. 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). Leaders sense this when they hesitate, having watched initiatives that opened with energy and a deck and then dissolved as attention moved elsewhere, leaving the underlying problem roughly where it began. If anything the pressure has grown: the average employee faced ten enterprise changes in 2022, against two in 2016, even as willingness to absorb more of them fell sharply (Gartner). Doing fewer things, and finishing them, is the discipline the moment rewards. What these organizations lack is not motivation but a repeatable way to convert intent into a delivered, measured result.
Value is measured on the organization's own scoreboard
"The problem that matters most" is deliberately not defined in financial terms 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 rather than after it; 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 client.
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 money is the goal, the method delivers money; where the goal is a safer ward, a faster permit, or a lower carbon footprint, it delivers that, measured the same way.
Improvement that lasts is built within, not delivered to
The decisive choice is who owns the result. 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.
Building capability this way is closer to apprenticeship than to a course. A method is taught, then applied under coaching to a real problem the team owns, until it becomes the ordinary way the work is done rather than a separate initiative layered on top. Research on large-scale performance programs points to the same conclusion: the efforts that engage a meaningful share of the workforce in building new skills are markedly more likely to sustain their results, and programs that involve more than a third of the workforce show materially better outcomes, including higher shareholder returns over the following eighteen months (McKinsey, 2021). When senior leaders model the change themselves rather than delegate it, success becomes several times more likely (McKinsey, 2021). The value is not in the teaching; it is that the people who produced the result can produce the next one.
Find the problem, then solve it with your people
In practice the work has two movements. The first is 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. We call it an OpsScan, and its output is a prioritized, quantified list rather than a report, so that 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.
The second movement is a Focused Value Sprint: a bounded, fixed-scope effort that takes one selected problem to a delivered result. It opens by framing the change against a measured baseline and naming the person inside the organization who will own it, and it closes with that owner having delivered the improvement and earned a recognized Lean Six Sigma credential through the work itself. The preparation and the execution are deliberately joined, because a plan the owner did not build is a plan the owner will not run. Where the problem calls for technology, the order is fixed: improve the process first, then automate the improved version. This is long-standing counsel (Harvard Business Review, 2018), and the evidence on AI projects underscores it: more than eighty percent fail, roughly twice the rate of other technology projects, and seldom because of the technology itself (RAND, 2024). Throughout, capability and the management of change are part of the work rather than a phase appended to the end.
Why one problem becomes many
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, and entirely on its own terms, 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.
This is also why the approach suits organizations that cannot, and should not, stop operating in order to remake themselves. A mid-market business rarely has the slack to absorb a wholesale change effort, and a hospital cannot pause care to redesign itself. Improvement that proceeds one owned problem at a time respects that reality and reaches the same destination by a route the organization can actually travel.
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. 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).