Operational improvement has become a familiar investment across the Canadian health sector. Yet in a benchmark of operational maturity, only about one in three organizations reports the daily-management routines that would make improvement part of how work runs rather than a periodic campaign, and the typical organization rates itself as defined but uneven, with genuine strength in some areas sitting beside clear gaps in others. These are among the findings of the LEA OpsScan benchmark, a self-assessed survey completed by fifty-five Canadian health-sector respondents and scored across the fourteen dimensions of an operating system. Beneath the averages lies the more useful result: the organizations that score highest are distinguished less by standout strength in any single area than by consistency across all of them, while the rest are strong only in pockets. For most organizations the distance to that consistency is real but reachable, and the way to close it is to address the single largest gap first, then the next.
Several forces have raised the bar on operations in particular. Ontario hospitals have been required to publish annual Quality Improvement Plans since the Excellent Care for All Act took effect in 2010, with a portion of executive compensation tied to performance against the targets in them, and Accreditation Canada assesses organizations against its standards on a recurring multi-year cycle.
What sets the most mature organizations apart is consistency
The clearest pattern in the data is that the organizations at the top of the benchmark are not distinguished by a flagship strength. They are distinguished by the absence of weak spots. Across the fourteen dimensions of an operating system, an organization that rates itself above the median overall sits above the median on close to nine in ten of those dimensions; an organization below the median does so on roughly a quarter. The highest-scoring organizations are broadly strong, while the rest are strong in pockets, with real capability in one area sitting next to a clear gap in another.
This reframes what a strong operation looks like. A standout improvement function, a respected quality team, a set of well-regarded projects: none of these lifts an organization to the top of the benchmark if the rest of the operating model has not kept pace, because an organization's overall standing is set by its weakest dimensions rather than its best. The implication is clarifying rather than discouraging. Consistency, rather than brilliance in one place, is the thing to build, and consistency can be built deliberately.
The benchmark also shows how much room remains. Even among organizations that have invested in improvement, only about one in three reports an embedded daily-management system, the set of routines that makes improvement part of how work runs rather than an occasional event. Most rate themselves at a level the framework calls defined but uneven, where the intent is clear and the practice is inconsistent. That is the honest state of the field as these respondents describe it, and it is a starting line rather than a verdict.
The gap that matters is your own
If consistency is the goal, the natural question is where to begin, and here the data resists a single prescription. There is no universal practice to fix first. When each organization's single weakest dimension is identified, twelve of the fourteen dimensions appear as some organization's largest gap, and every one of the fourteen appears as some organization's greatest strength. The field does not share one weak point; it shares the condition of being uneven, with the location of the unevenness differing from one organization to the next. Although the location varies, two dimensions surface most often as the single largest gap: the value-stream and patient-flow practices that govern how work moves, which together are the weakest point for close to two in five organizations.
This is why, in our experience, the route to a more consistent operation is sequential and specific rather than programmatic. An organization that tries to advance on every front at once tends to dilute its effort and move on none, whereas an organization that identifies its largest gap, closes it with a focused effort, and then turns to the next builds breadth one dimension at a time. The benchmark's value is not in producing a rank; it is in naming the gap that is currently holding an organization back, which our work suggests is rarely the gap leadership would have named on its own.
The view from the top is not the view from the floor
The reason the gap is hard to name from inside is that maturity looks different depending on where one sits. In the benchmark, the further a respondent sits from daily operations, the higher they rate the organization. Frontline and supervisory respondents placed their organizations around the midpoint of the scale; managers placed them higher; the most senior respondents higher still. Those who set strategy and those who run the work are looking at the same organization from different distances.
This is less a failing of leadership than a property of distance. Senior leaders see the plan, the dashboard, and the initiatives under way; frontline staff see the handoffs that stall and the standard that is not followed on the third shift. Both views are real, and each is partial. An assessment formed only at the top will tend to read higher than one that also hears from the floor, which is why a benchmark that reaches below the executive suite is useful: it takes in more than one vantage and shows where the views diverge.
Capability is the engine of any improvement; the daily-management system is what keeps it running once the attention moves on.
The gaps are not random
While each organization's largest gap is its own, the benchmark shows that the gaps cluster in recognizable places, and two patterns recur. The first is the daily-management system. The dimensions that most separate the organizations at the top of the benchmark from those at the bottom are not the visible improvement projects but the quiet operating routines: improvement run as a regular, planned activity rather than a response to crisis; priorities translated into goals at the team level; a leadership review that resolves competing demands; managers following defined routines; and performance data used in daily decisions rather than reviewed after the fact. In practice these are unglamorous routines: a brief daily review at a visual board where a team compares the day's work against its targets, a standing forum where leaders resolve the trade-offs a frontline manager cannot, and a set cadence that schedules improvement rather than waiting for a crisis to prompt it. These are the components of a management system, and they are where the field is most divided.
Capability is the foundation beneath them, not a substitute for them. Trained people are the engine of any improvement, and in the benchmark, capability and the daily-management system rise together; an organization rarely scores well on one without the other. The distinction that matters is what capability is wired into. In our work, a roster of trained and certified people produces pockets of improvement, while the same people inside a daily-management system produce results that hold once attention moves elsewhere. Capability is also the rail an organization has to own itself, because it is what allows a gain to persist after any outside help has gone. The implication is not to train less; it is to pair capability with the system that puts it to work.
The second pattern is more humbling. One part of the operating model sits low for almost every organization, including the highest-scoring ones, and that is flow and capacity. Even organizations at the top of the benchmark rate themselves lowest on the practices that govern how work moves: plans that adjust when demand shifts, problems detected in process rather than after the fact, handoffs that hold, and workload balanced across teams. Across hospital, community, and long-term care settings, this is the familiar territory of patient and client flow, alternate-level-of-care, scheduling, throughput, and staffing. It is the part of the operating model the field has advanced on least, which makes it, for many organizations, both the largest gap and a place where focused work can produce visible results.
What closing one gap looks like
The work of closing a gap is more concrete than the language of operating systems suggests. In our experience, the most common and most productive first move is a daily-management effort on a single area, run as a short, scoped Sprint rather than a program. A team takes one unit, one clinic, or one service line, and stands up the routines the benchmark shows most organizations lack: a visual board that makes the day's work and the day's targets plain to everyone on the unit, a brief daily huddle in front of it, a defined path for escalating the problems the team cannot resolve on its own, and a small set of standard routines for the unit's managers. None of this is novel, and that is the point. The difficulty has never been knowing what a daily-management system contains; it is building one that the unit's own people run and keep running.
Done well, the effort is measured in weeks rather than years, and it changes what the unit can see and act on. A team that could previously describe its problems only in hindsight begins to catch them the same day, while they are still small. Capability is built in the same motion, because the people who will sustain the routine are the ones who design and run it, not an outside team that leaves with the knowledge. The gain holds because the structure that produced it stays in place, and the organization is left with a working model it can carry to the next unit and the next gap.
One gap at a time
The path that follows from this is deliberately modest, and that is its strength. An organization does not need to import a multi-year management system or commit to a transformation to close the distance to the most mature organizations in the benchmark. It needs to know where it actually stands, which a benchmarked diagnostic taken close to the work can provide, and then to close its largest gap with a focused effort before turning to the next. Each effort is scoped and local, run on a model area and owned by the line, and each builds two things at once: the capability that does the improving and the daily-management structure that, in our experience, makes the improvement hold. Over a sequence of such efforts, the pockets of strength join up, and the unevenness that describes most organizations today gives way to the consistency the benchmark finds at the top.
This is a different proposition from the one the field is often sold. It does not begin with a new strategy, because the benchmark shows that direction and intent are, for most organizations, already the strongest part. It does not begin with training in isolation, because in our experience trained people without a system produce gains that fade. It begins with an honest reading of where an organization stands, taken from close enough to the work to be accurate, and it proceeds one gap at a time. Progress, in the end, does not come from doing everything at once; it comes from doing the next right thing, and then the one after that.
Source: figures are drawn from the LEA OpsScan health-sector benchmark, a self-assessed survey of operational maturity across fifty-five Canadian health-sector respondents who completed the full assessment, scored on a one-to-five scale and grouped into the framework's operating dimensions. The sample is self-selected among organizations engaged in improvement and is weighted toward Ontario; figures are directional and strengthen as the benchmark grows. Reported maturity reflects respondents' perceptions.