Most organizations have a strategic plan. Most also have the experience of watching that plan fragment as it moves downstream. Priorities stall. Initiatives compete for the same resources. Different parts of the organization work on the same problem in parallel without knowing it. Accountability fades as the distance from the executive review grows. The plan everyone agreed to in November becomes unrecognizable by March.

The plan isn't usually the problem. The infrastructure for executing it is.

PowerPoint is a presentation tool. Excel is a calculation tool. Word is a document tool. None of them were designed to hold strategy deployment -- the ongoing work of cascading a multi-year vision through dozens of teams, tracking thousands of activities against specific timelines, surfacing the items that are off track in time to recover them, and making the whole system visible enough that duplicate work surfaces before it ships. When you use a presentation tool to do execution work, you get presentations of execution work. You don't get execution.

This is the trap most CI and OpEx leaders end up in. The annual planning cycle produces a deck. The deck gets distributed. Each site or department builds their own version of the deck, tracked in their own files, reviewed in their own meetings. The executive team sees the pieces in series, one presentation at a time, with no view across the system. By the time the misalignment is visible, half the year is gone.

What the legacy stack actually costs you

The cost isn't the time spent building slides. It's the operational consequence of having no shared view.

Each site plans in isolation. Each site lists what they want to do, plus what they think the system wants them to do, plus what they assume other sites won't be doing. The system leadership sees four versions of "we're going to expand orthopedics" and has no way to tell whether they're four coordinated efforts or four duplicate ones. Two sites work on the same trauma program improvements in parallel, neither knowing the other is doing it. Timelines slip because nobody sees them slipping in time to intervene. The strategic plan exists, but the system isn't executing against it. It's executing against four loosely related interpretations of it.

The cost shows up in three places. First, in the duplicate work itself -- the effort spent solving problems someone else has already solved or is currently solving. Second, in the delay -- every month a proven improvement sits at one site while others struggle with the same issue is a month of preventable cost, error, or dissatisfaction. Third, in the credibility of strategy deployment as a discipline. When the previous year's plan visibly failed to come together, people stop investing in next year's planning. The cycle gets shorter and the ambition gets smaller until strategy deployment becomes an annual ritual that everyone tolerates and nobody believes in.

Broward Health: 400 strategies down to 95

Bill Griffith, VP of Integration and Standardization at Broward Health, walked through this exact transition in a KaiNexus webinar. Two years before the session, his four-hospital system was running strategy deployment the way most organizations do. PowerPoint. Excel. Word. Individual hospital presentations to the executive team. Each hospital owned its piece. Each hospital tracked its piece locally. The executive team had no view across the system.

Then the team built a shared template in KaiNexus and consolidated all four hospitals' plans in one place for the first time.

The aggregate count was striking. Over 400 growth strategies. 288 finance strategies. Other pillars at a comparable scale. The numbers weren't a sign of ambition. They were the predictable output of four organizations planning in isolation, each unable to see what the others were doing.

The system leadership ran a consolidation session that asked three questions. Where are hospitals working on the same thing in parallel? Where can strategies be combined into a single system-level effort? What's on the list that isn't realistically going to happen in three years?

The trauma program was the clearest case. Two of the four hospitals are trauma centers. Both had independent trauma improvement strategies. Both were working on substantially similar problems. The consolidation paired them, replaced two parallel efforts with one coordinated effort, and freed capacity in both hospitals for other work. The same pattern repeated across pillars and service lines.

After consolidation, the growth pillar dropped from over 400 strategies to 95. Finance dropped from 288 to 69. Bill was clear that some duplicate work remains and the cleanup is ongoing. The trajectory is what matters. The system went from being unable to see its duplicate work to being able to see and address it.

The consolidation wasn't possible before. Not because the team lacked the will. Because the duplicate work was hidden inside separate documents that nobody read side by side.

The monthly review that actually works

The piece that holds strategy deployment together over time is the monthly operating review. At Broward Health, that meeting used to be finance-focused. Variance to budget. Revenue and expense items. The state of the financial statements. Strategic priorities came up occasionally but weren't the focus.

The current version inverts the emphasis. Roughly ten minutes still go to financial performance. The bulk of the meeting focuses on the status of the strategic plan across the five pillars (quality, service, people, growth, finance). The team comes to the meeting with updates already in the system rather than reporting them verbally. The pillar boards in KaiNexus show each strategy, its owner, its last update, its status, and the activities underneath it. Green items get verified briefly. The meeting's actual time goes to the red items -- strategies overdue or behind plan -- and action plans are built during the meeting to recover them.

The platform turns items orange when they're within five days of going overdue. The visual cue starts the conversation before the item is technically late. By the time something is red, the recovery plan is already a week into being built.

The meeting works because the data lives in one place that everyone can see. Bill's team didn't invent the practice of monthly strategy reviews. They made the practice operationally real by removing the friction that used to consume the meeting. When the review starts, the status is already current. The conversation is about the work, not about reconciling everyone's spreadsheets.

What changes when the infrastructure changes

Bill's framing was that the work could be done without a platform. Broward Health did strategy deployment for years using PowerPoint, Excel, and Word. The visibility and consolidation that made the work materially better required infrastructure that the legacy tools couldn't provide.

His direct comparison: ten years ahead of where they could be using PowerPoint.

The specific capabilities map to the specific failure modes. Visibility across the system makes consolidation possible. The template structure encodes the discipline -- every strategy has a pillar, a status, three years of activities, a KPI, an executive sponsor, and a team. The cascade from system to hospital to department requires a platform to capture all three levels and their relationships. Huddle board integration lets local and strategic work share a common system, so a pattern of local issues can be escalated into a system-level effort rather than remaining invisible.

None of this changes what strategy deployment fundamentally is. The leaders and the teams still do the work of defining the right strategies, cascading them, measuring progress, holding people accountable, and adapting when conditions change. What changes is how much of the effort goes into the work itself versus into consolidating information that should already be consolidated. Without the right infrastructure, too much of the effort goes into the consolidation. With it, the system's default state is consolidation.

The question worth asking before next year's cycle

If you're about to start another planning cycle on top of the same PowerPoint stack you used last year, the question is straightforward. What specifically do you expect to be different this time?

The same tooling tends to produce the same outcomes. The duplicate work surfaces in May. The timelines slip in August. The November review notes the same gaps it noted the year before. Next November's review will note the same gaps again, with slightly different proper nouns, unless something structural changes.

The structural change isn't a methodology. Broward Health was running strategy deployment before. It isn't an executive mandate. The executives were already engaged. It's the infrastructure that lets the methodology and the mandate actually scale across the organization without losing fidelity in the cascade.

See KaiNexus in action →