Watch the recording of the webinar:
Listen to the recording via our podcast:
View the Slides:
Alternative download (PDF)
Quick name flag: the registration page lists the presenter as "Karen Friedenberg" in the bio header but as "Karen Fredenberg" elsewhere on the page, and the alternative slides download URL uses "Friedenberg." The transcript caught it as "Fredenberg." I'll use Friedenberg, which appears to be the correct spelling based on her firm's website naming convention. Flag if I have it wrong.
H1: Leveraging a Strategy-to-Execution Framework: A Journey of Transformation
Page title (60 chars): Strategy-to-Execution Framework Webinar with Karen Friedenberg
Meta description (155 chars): Karen Friedenberg on the seven-part framework for closing the gap between strategy and execution — and why people and culture have to be in from day one.
Focus keyphrase: strategy to execution framework
Slug suggestion: strategy-to-execution-framework-webinar (use existing recording slug if it ranks; otherwise migrate and 301 the registration page)
Tags: Strategy Deployment, Continuous Improvement, Hoshin Kanri, Change Management, Operational Excellence
A KaiNexus webinar with Karen Friedenberg, Founder and Managing Director of Performance Improvement Consulting
[Video embed]
[Slide deck embed or link]
[Podcast audio embed]
Most organizations have a strategy. Far fewer have a reliable way to turn the strategy into action. Initiatives compete for attention. Teams lose alignment as the year goes on. Improvement work stalls before it produces meaningful value. The plan that looked clean in January looks fragmented by Q3, and the gap between what was decided and what's actually happening keeps widening.
Karen Friedenberg has spent her career working on this gap from both sides. She's been in executive roles where having an executable plan is the difference between hitting commitments and missing them. She's also led consulting engagements that diagnose why strategies stall and rebuild the systems that connect strategy to execution. The framework she walks through in this session is the synthesis of that work.
It's a seven-part framework, but Karen is direct that it shouldn't be read as linear. It cycles. It iterates. It loops back on itself when new information surfaces. And one element — people and culture change — runs through all seven parts, not just the change management section near the end.
Karen opens with the same diagnosis most CI leaders have made privately. The strategy isn't usually wrong. The execution is what breaks down — and the execution breaks down because the conditions for it weren't built deliberately.
Two patterns show up repeatedly. The first is the strategy that lives only at the top. Senior leaders know the plan. Department heads have a general sense. The people doing the daily work have no clear line of sight from what they're doing to what the company is trying to achieve. When that line of sight is missing, daily work drifts toward whatever feels urgent rather than toward what matters strategically.
The second is the strategy that exists on paper but never becomes a system. The plan gets written, presented, filed, and consulted occasionally. The metrics that would make execution visible aren't there. The cadence that would force regular adjustment doesn't exist. The accountability for moving things forward is fuzzy. Six months in, the strategy has been crowded out by operational noise.
Both failures share a root cause. Strategy execution isn't treated as a system that needs to be designed, maintained, and adapted. It's treated as a one-time rollout that should somehow run itself. Karen's framework is the alternative — a deliberately designed system, with people and culture work running through it from the start.
The framework has seven elements arranged in a cycle. Each one connects to the others, and progress in any one is bounded by the strength of the others.
Strategy articulation. Karen leans on Stephen Covey's "begin with the end in mind." The work here goes deeper than mission and vision statements. It asks whether the strategy has been translated to the next level of detail — whether business units and departments have their own strategies aligned to the corporate strategy, and whether that strategy has been communicated clearly throughout the organization. Most companies have strategies on their websites. Far fewer have strategies that the people doing the work could articulate accurately if asked.
She uses design thinking to make strategy visible. The picture-building process happens with cross-functional teams, not just the C-suite, and it gets tested with people closer to the work. The North Star, the strategic imperatives, the connection to customer service, the structure of the scorecards — all become visible artifacts that teams can refer back to.
Organizational alignment. Once the strategy is articulated, alignment is the work of making sure everyone moves in the same direction. Karen uses the X-matrix from hoshin kanri as one approach, along with OKRs (objectives and key results) for cascading goals through the organization. The point isn't the specific tool — it's that strategy needs to flow not just top-down but laterally across functions and back up from the front line. She returns to a phrase that recurs through her work: "who's wearing the jacket?" Knowing who owns each initiative, and who they need help from to succeed, is the operational substance of alignment.
Initiatives and actions. This is where strategy becomes specific. Karen introduces the concept of a transformation management office (TMO) as the orchestrator of the change — not a traditional PMO focused on governance and timelines, but a team with real business acumen that can help solve problems and reprioritize as conditions change. Initiatives get defined at multiple levels: large programs, projects, smaller initiatives, kaizen events, weekly sprints. Impact gets measured to drive accountability and collaboration. Without this layer, strategy stays abstract.
Operational alignment. This is where lean and continuous improvement methods earn their place. Karen's observation: people without a lean background often jump from problem statement straight to solution without doing the analytical work in between. The five whys, root cause analysis, DMAIC — these tools belong in this phase, applied to making sure that operations and processes actually serve the strategy rather than working at cross-purposes to it.
Execute with excellence. This is where the transformation management office, or whatever equivalent the organization has, runs the cadence that keeps execution on track. Status tracking, roadblock removal, prioritization across competing demands, change management woven through every initiative, and performance monitoring against the original objectives. Karen makes a point worth lifting: projects don't exist to be on time and on budget. They exist to deliver business results. Tracking time and budget without tracking outcome value is how strategy execution slowly converts into expensive activity.
Review, adapt, improve. Strategy execution is not one-and-done. The internal landscape changes. The external landscape changes. Mergers, acquisitions, regulatory shifts, market shifts, pandemics — any of these can require pivoting the path even if the destination remains the same. Karen describes using agile sprints to break execution into 30-day cycles within the larger framework, which gives the organization regular chances to absorb new information, adjust course, and execute the next iteration.
Organizational change. Karen places this last in the framework but emphasizes throughout that it can't actually be last in practice. People and culture work has to start at the beginning, run through the middle, and continue at the end. She uses the Prosci ADKAR methodology — awareness, desire, knowledge, ability, reinforcement — paired with the three-phase prepare/manage/sustain approach. The structure is iterative, not sequential. You move back and forth between the elements depending on what's needed.
Karen's most useful framing toward the end of the session is that the framework isn't really a circle. It's closer to a figure-eight or an infinity loop, with constant return between elements.
You start in strategy articulation. You move into organizational alignment. You begin to define initiatives. As you go deeper into the operations, you uncover problems you didn't know existed when you started — which means alignment that looked solid at a high level isn't actually as tight as it needed to be. You loop back. You revise. You move forward again with better information.
This is why "review, adapt, improve" sits as its own element in the framework rather than being implied. The discipline of regular review isn't optional. It's how the system stays alive.
The implication for leaders: stop treating strategy execution as if uncertainty is a problem to be eliminated. Build the system to absorb new information, adjust deliberately, and keep moving. Organizations that try to lock in a perfect plan tend to discover the plan was wrong about something around month four — and then they don't know what to do because their system wasn't built to adjust.
A pattern Karen returns to throughout the session: most strategy work underweights the people side. Karen treats it as foundational, not residual.
Two specific tools she's used to build the cultural stage early in transformation work.
The first is leveraging videos and stories that create shared language. The "This Is Water" story from David Foster Wallace — two young fish swim past an older fish who asks "morning boys, how's the water?" and the young fish look at each other and say "what the hell is water?" — becomes a shared touchpoint. When teams find themselves in autopilot mode, someone can say "this is water" and the whole group recognizes the moment. The Apple "Think Different" video pulls the same role for innovative thinking. The Einstein quote about insanity being doing the same thing repeatedly serves as language for surfacing patterns the organization keeps repeating.
The second is the "test and learn" or "micro battle" framing. Large transformation can feel paralyzing. Breaking it into small, time-boxed experiments where failure is acceptable removes the fear that stops progress. The framing changes the conversation from "we have to get this right" to "let's run the experiment, see what we learn, and adjust."
Both tools feed the same goal: building the psychological safety and shared vocabulary that lets the rest of the framework actually function. Without that foundation, the technical work of strategy execution gets stuck in the same patterns the strategy was supposed to change.
A useful exchange in the Q&A worth surfacing because it shows the framework in motion.
Mark posed a hypothetical: a manufacturing company wants to grow market share from 20% to 30%. How does the framework apply?
Karen's response walked back from the goal to the strategy. Strategic growth is the imperative. How? New products? Penetrating existing customers with current products? International expansion? Different opportunities in different segments? Each option requires different operational alignment. New product introduction means R&D capability, commercialization through sales, manufacturing capability for the new products, and the technology to support all of it. Penetrating existing customers means a different set of work — sales effectiveness, customer relationship depth, possibly pricing and packaging.
The trap, Karen pointed out, is starting at the goal (30% market share) and skipping the strategy work that determines how. Without the why and the how, the initiatives that follow are arbitrary. The framework forces the question to be asked properly: what's the strategic imperative, what's the path to achieving it, what alignment does that path require, and what initiatives flow from that alignment?
Mark's reflection in the moment was that he had confused goal with strategy when he posed the question — which is exactly the move most organizations make when they jump from "we want to grow market share" to "we need a lean transformation" without the strategy work in between.
Another exchange worth lifting because every CI leader has lived through this. You're partway through a year. Performance against goals is underwhelming. Is the strategy wrong, or is the execution wrong?
Karen's approach: dive deeper into the data — financial and operational. Apply root cause discipline. Maybe the solution chosen at the start wasn't actually addressing the right problem. Maybe new information has surfaced that wasn't available when the plan was set. Maybe the execution has been correct but the assumptions behind the strategy were wrong.
The response depends on the diagnosis. Sometimes the answer is bringing in outside expertise to think about the problem differently. Sometimes it's getting deeper data. Sometimes it's recognizing that the organization has converged on a solution too early and needs to step back and consider alternatives.
The discipline that holds it together is the willingness to admit "we may need to do this differently" without treating that admission as failure. Strategy execution is iterative. Mid-year corrections aren't a sign that the plan was bad — they're a sign that the system is working as designed.
Two related practical questions in the Q&A.
On distinguishing imperatives from wants and nice-to-haves: what's truly imperative depends on what the organization is trying to achieve. If growth is the strategic imperative, operational efficiency might appropriately take a back seat for now. If saturation has been reached and profitability is the imperative, the priorities flip. The discipline is recognizing that "everything is a priority" is the same as "nothing is a priority." If you don't dig deep enough to identify the few true priorities, you don't really have a strategy.
On metrics: Karen leans on the balanced scorecard concept — the vital few across financial, operational, people, and customer dimensions. Not everyone in the organization can connect their daily work to the highest-level KPIs, which is where cascading metrics matter. But the ones at the top should stay limited and visible. A practical constraint: also consider what's actually measurable. Data is hard to get. Picking the few that you can measure cleanly and that drive impact on the higher-level KPIs is the operational version of the principle.
She named a related trap: organizations sometimes measure what's easy rather than what matters. Easy-to-measure metrics that don't move strategic outcomes produce activity reports that feel useful but don't change anything.
A question came in about how to bring bottom-up input into the X-matrix and avoid making strategy purely top-down. Karen's framing: the cascade should run both ways, with deliberate catchball at each level.
The strategy and high-level imperatives come from the top. But department leads work with their teams to translate those imperatives into what the work actually looks like at their level. Cross-functional dialogue at the "oval table" surfaces dependencies and trade-offs. Individual contributors bring ideas about how to execute the tactics, sometimes with insights that simply aren't visible from the top.
The practical move: start the cascade in the organizational alignment phase, but stay open to the bottom-up input through the initiatives and operational alignment phases. The best ideas about how to execute often come from people closer to the work than the leaders setting the strategy. Building the system to capture those ideas is part of the framework, not separate from it.
A few things the platform does that connect to what Karen describes.
KaiNexus supports the cadence Karen emphasizes throughout — the regular review, the adaptation, the iteration. Strategy execution that depends on someone remembering to follow up doesn't survive. Strategy execution embedded in a system that surfaces status, escalates issues, and tracks impact does.
The platform supports the cascade across organizational levels — from the corporate strategy down through department initiatives to individual contributions, with visibility flowing back up so leaders can see whether the daily work is actually producing the strategic outcomes that were intended.
It also supports the data discipline Karen returns to throughout the session. When metrics are integrated with the work, the conversation about whether to adjust strategy or execution gets grounded in evidence rather than opinion.
If your organization has a strategy on paper but is struggling to make it real in daily operations, the gap is usually the system that connects intent to action. That's the gap KaiNexus is built to close.
Karen Friedenberg is the founder and managing director of Performance Improvement Consulting. Having worked both in consulting and within industry — including in executive roles where executable plans that deliver results are non-negotiable — Karen brings a unique perspective to strategy execution. She has built and led strategic program management and operational excellence departments and has led large business and digital transformations across multiple industries. Karen is known for listening, connecting the dots, and bringing experience across lean, Six Sigma, change management, and design thinking to solve complex business problems and create sustainable change.
Why do most strategies fail at execution?
Most failures aren't strategy problems — they're execution system problems. The strategy gets articulated at the top but doesn't translate clearly to the work on the ground. Initiatives proliferate without prioritization. The cadence for review and adjustment doesn't exist. Six months in, the strategy has been crowded out by operational noise. The fix is treating strategy execution as a deliberately designed system rather than a one-time rollout.
What is the strategy-to-execution framework?
Karen Friedenberg's seven-part framework covers strategy articulation, organizational alignment, initiatives and actions, operational alignment, execute with excellence, review and adapt, and organizational change. The framework is iterative, not linear — closer to a figure-eight than a circle — with people and culture work running through all seven elements rather than being limited to the change management section.
Why does Karen Friedenberg emphasize that strategy execution isn't linear?
Because new information surfaces as you move through the work. Strategy that looked solid at a high level reveals gaps when you go deeper into operations. Initiatives that seemed right at the start need to be reprioritized as conditions change. Internal and external landscapes shift — mergers, market changes, regulatory updates, even global events like a pandemic. The framework is designed to absorb new information and adjust deliberately rather than locking in a plan that has to survive uncertainty unchanged.
What's a transformation management office and how is it different from a PMO?
A transformation management office (TMO) orchestrates strategy execution across initiatives — not just tracking timelines and governance like a traditional PMO, but bringing real business acumen to problem-solving and prioritization as conditions change. The TMO ensures alignment to strategic goals, removes roadblocks, manages competing resources, and embeds change management throughout. Some organizations call this role a transformation office, some embed it in a chief of staff function, and some adapt their existing PMO. The substance matters more than the title.
Why does Karen put people and culture work at the start, middle, and end of transformation?
Because transformation that depends on changing how people work won't succeed without addressing how people experience the change. Karen uses the Prosci ADKAR model — awareness, desire, knowledge, ability, reinforcement — paired with prepare/manage/sustain phases. The point is that culture change isn't a discrete project that runs in parallel with the technical work. It's woven through every stage of the framework, with iteration back and forth as the work surfaces new needs.
What's the difference between a strategic imperative and a goal?
A goal is a specific, measurable outcome ("grow market share from 20% to 30%"). A strategic imperative is the underlying direction the organization is committed to ("strategic growth"). The imperative answers "what are we trying to achieve at the highest level?" The goal answers "how will we know we're succeeding?" Strategy work that confuses the two tends to skip the question of how the goal will actually be achieved — which is where most strategies break down.
How should organizations decide which initiatives are truly imperative versus nice to have?
By being honest about what the strategy actually requires. If everything is a priority, nothing is. The discipline is identifying the few priorities that genuinely move the strategic imperatives forward and being willing to deprioritize work that doesn't — even when that work has internal advocates. Karen's framing: prioritization isn't an accounting exercise. It's a strategy exercise. Without it, you don't really have a strategy at all.
.svg)
Copyright © 2026
Privacy Policy