Quality Improvement Is No Longer Optional

Quality improvement has become a standing obligation

Across the country, the expectation that a health organization will measure and improve its own performance is now written into the rules it operates under. Accreditation Canada's Qmentum program assesses organizations on a four-year cycle against mandatory patient-safety practices, and accreditation is effectively a condition of standing. In Ontario the Excellent Care for All Act goes further, requiring every hospital to publish a quality-improvement plan each year and to tie a portion of its senior executives' compensation to meeting that plan's targets. Other provinces carry their own versions of the same expectation. Layered on top are the pressures that ministries and boards track in public: emergency-department waits, alternate-level-of-care days, surgical backlogs, patient safety, and patient experience, most of them now understood within some version of the Quadruple Aim.

The practical consequence is that no organization has opted out. Some are years into a structured improvement program; others are weighing how to begin, often while evaluating large, branded management-system models developed for other health systems. Both are subject to the same obligation, and both face the same question.

The question is how, not whether

That question is how to make an improvement program deliver, year after year, against priorities that an external body and the organization's own board are watching. It is a more demanding question than the one the field asked a decade ago, when the presence of improvement activity felt like progress in itself. An organization already running a program wants more from the investment it has made and cannot always see why the returns have plateaued. An organization considering its first serious program wants to begin in a way it will not have to unwind later, and is right to be wary of committing to a model built for a different system. Neither is well served by a generic methodology. What serves both is a clear view of what makes an improvement program hold its value over time, and a way to build that an organization can actually absorb.

It starts with your own people

The foundation of a program that delivers is capability: the people inside the organization who can see a problem clearly, run a disciplined improvement, lead others through it, and coach the next group to do the same. This is the element that is easiest to underrate, because it is less visible than a new dashboard or a redesigned unit, and it is the one that matters most. Capability is the part of an improvement program that an outside partner cannot install on the organization's behalf. A consultant can run a project and leave a result; only the organization's own staff can carry the method into the next problem, and the one after that. It is also why a gain built on capability tends to outlive the project that produced it, whereas a gain delivered to an organization tends to leave when the help does.

Building that capability is unglamorous and specific. In our work, an academic health centre developed more than a hundred of its own staff to lead improvement, drawn from across clinical and administrative roles, from emergency physicians and nurse educators to registration and scheduling leads. A long-term care organization built the same capability across all of its homes, so that improvement was no longer something done to a site by a central team but something each site could do for itself. The measure of either effort was not the count of people trained. It was that the organization came away owning the skill rather than renting it.

Capability needs a system to work within

Capability on its own, though, will not hold a result. Skilled people still need a structure that connects their daily work to the organization's priorities and keeps a standard in place once attention has moved elsewhere. That structure is a daily operating system: the tiered huddles where issues surface and escalate to the level that can act on them, the visual management that makes performance and problems plain where the work happens, the standard work that captures the current best way of doing a task, and the leader routines that keep all of it alive rather than letting it lapse under operational pressure. Capability and this system are the two rails of a program that delivers. Capability is the lead rail, the engine and the asset that remains; the operating system is what that capability runs on. Built together, the two turn a one-time improvement into the way the work is now done. Built apart, capability disperses for want of a structure to act within, and the structure becomes boards and meetings that no one has the skill to use well.

Where the field stands

The encouraging part is that the first rail is now broadly present. To see how far the field has come, we scored a benchmark of fifty-five Canadian health organizations that already invest in Lean and quality improvement, each rating its own maturity across the operating system on a five-point scale. Read as a picture of the committed end of the field rather than the sector at large, it shows real capability: structured problem solving, improvement skills, and quality practices are present in most of these organizations. What it also shows is that almost nothing has yet become embedded. The median organization sits at defined but uneven, and the single most common gap is the daily operating system itself. Only about one in three of these organizations has an embedded one, which means that for most, capability is running without the full structure that would let it hold.

The benchmark surfaces one further pattern worth a leader's attention. The closer a respondent sits to the daily work, the lower they rate the organization; frontline staff rated their organizations roughly a full point below their senior leaders on the same scale. Those who set strategy tend to see a more finished organization than those who run it experience day to day. The honest reading is that the gap an organization most needs to close is usually not the one visible from the executive office, and that it is rarely the same gap from one organization to the next.

Progress comes one gap at a time

This is why a program that delivers does not begin with a multi-year blueprint or a management system installed wholesale. It begins with an honest read of where the organization actually stands, gathered from the people closest to the work, that locates the single gap most holding it back. When a regional health organization we worked with took that kind of structured look rather than relying on leadership's impression, its binding constraint turned out not to be where the executive team had assumed, and directing effort to the real gap allowed it to earn external recognition for operational excellence. Seeing the gap accurately was itself the result that mattered.

From there the work is sequential and right-sized. The organization closes its largest gap with a focused effort measured in weeks, run on a single area and owned by the line rather than a central office, and designed so that the capability to sustain the change is built into the work itself. Then it moves to the next gap. Run this way, the results are concrete, and they hold. An Ontario hospital reduced falls with harm by about forty percent on the units involved. Another increased its surgical capacity by more than a third within the infrastructure it already had. A regional organization roughly halved the time it took to turn over an inpatient bed, and a hospital pharmacy reduced its inventory by about a quarter while improving availability. None of these was an enterprise program. Each was a bounded effort that delivered a real result and left capability and a daily structure behind to hold it.

The advantage is your people

The obligation to improve is not going to ease. For most organizations the honest position is that their capability is further along than the system meant to hold it, and that the gap worth closing first is not the one assumed at the top. None of this requires a transformation an organization cannot absorb. It requires building the program on its own people, giving that capability a daily system to work within, and closing one gap at a time from a clear view of where it stands. Whether an organization is launching its first program or working to get more from one already underway, that is the path, and it is within reach.

The benchmark draws on LEA's OpsScan of 55 improvement-engaged Canadian health organizations, self-assessed on a 1 to 5 scale and weighted toward Ontario; figures are perceptions, not audited scores, and the senior-leader subgroup is small and directional. Case examples are drawn from LEA engagements with identifying details generalized.