Executive Summary
Organizations invest significant effort in defining group-level strategy. The value of this effort is realised only when strategic direction is reflected in day-to-day decisions and actions across the organization. When this translation is done well, daily operations naturally align with organizational priorities, enabling consistent execution and better use of management attention. When it is not, strategy remains conceptually sound but practically disconnected, resulting in effort that does not meaningfully advance the organization’s direction.
In many organizations, this execution gap does not arise because strategy is unclear. Leadership often articulates direction, priorities, and desired outcomes with reasonable clarity. The challenge emerges because outcomes are defined at the top of the organization, while the operational drivers that influence those outcomes sit across multiple teams, functions, and levels. When these links are not clearly translated, strategy becomes difficult to execute even when it is well understood.
In large, multi-business organizations, strategic intent is often articulated at a high level to allow flexibility. As this intent moves closer to execution, it frequently loses clarity. Teams struggle to understand what truly matters, how success will be measured, and how their actions contribute to broader objectives. This lack of alignment leads to conflicting decisions, delayed course correction, and uneven performance across operating units.
This article focuses on closing this execution gap. It explains how group strategy can be translated into clear, actionable expectations that align daily operations with organizational direction. It also explains the role of Key Performance Indicators (KPIs), which track ongoing performance, and Objectives and Key Results (OKRs), which help drive focused, time-bound execution.
When cascaded thoughtfully to the operating level, these mechanisms do more than measure performance. They clarify ownership of outcomes, connect strategic priorities with operational drivers, and make strategy visible in how work actually gets done.
Strategy Execution: Overview
Strategy sets direction, but execution determines outcomes. In practice, the execution gap often emerges when strategic outcomes are defined at the top of the organization while the operational drivers that influence those outcomes sit across multiple teams and levels.
Organizational strategy is usually expressed in broad terms. It sets priorities and desired outcomes while leaving room for management teams to exercise judgment in how those outcomes are achieved. Execution, however, requires a different form of clarity. Teams closer to delivery need to understand what the strategy means for their scope of work, what trade-offs they are expected to make, and how success will be assessed.
Execution is therefore not simply a communication exercise but a process of translating intent into decisions and actions. Alignment is rarely achieved simply by articulating strategy through presentations or stated objectives. Strategy becomes meaningful only when it shapes how decisions are made and actions are taken across the organization.
At a high level, execution can be understood through a simple model:
Strategy → Drivers → Execution
Strategic direction defines the outcomes the organization wants to achieve. Operational drivers represent the factors that most influence those outcomes. Execution consists of the initiatives and everyday actions that improve those drivers.
To operationalize this logic across an organization, strategy typically moves through a more detailed translation chain.
The Strategy Translation Chain
Strategy becomes actionable when each step in this chain is clearly translated into the next. Execution weakens when links in this chain become unclear or misaligned.
Execution also rarely unfolds exactly as planned. Once teams begin acting on strategic priorities, practical realities start to surface. Capacity constraints, dependencies between teams, sequencing challenges, and competing demands become clearer during execution than they ever are during planning.
Organizations that execute well recognise this and respond by adjusting priorities, revisiting targets, aligning team objectives with strategic focus areas, or reallocating resources, rather than continuing to measure progress against assumptions that no longer reflect how work is actually happening.
Why Strategy Translation Often Breaks Down
When the links between strategic outcomes and operational drivers are unclear, organizations tend to fall into a small number of recurring execution patterns. These patterns rarely reflect poor strategy design. Instead, they reflect breakdowns in how strategy is translated into operational expectations.
-
Outcome-Driver Disconnect
(Outcomes defined, drivers unclear)
Leadership often defines outcomes at the enterprise level without clearly identifying the operational drivers that influence those outcomes.
For example, leadership may track portfolio returns or overall profitability. Yet the operational drivers of these outcomes sit across multiple parts of the organization: leasing teams influence occupancy, asset managers influence tenant mix and lease terms, and property management teams influence operating costs and tenant experience.
When these relationships are unclear, outcome metrics provide visibility but not operational direction. Teams understand what the organization is trying to achieve but lack clarity on how their actions contribute to those outcomes.
-
Metric Replication
(Outcomes copied rather than translated)
In an attempt to maintain alignment, organizations sometimes cascade the same KPI downward across multiple levels.
While the intent is alignment, teams at lower levels rarely control the enterprise-level outcomes leadership tracks. A store manager, for example, may be evaluated on overall profitability even though profitability is influenced by pricing strategy, procurement costs, product mix decisions, and corporate overhead allocations determined elsewhere.
When the same KPI is replicated across levels, teams become accountable for outcomes they cannot meaningfully influence. Over time, performance discussions shift toward explaining results rather than improving them.
Effective cascading therefore requires translation rather than replication. Enterprise outcomes must be translated into the operational drivers each level of the organization can influence.
-
Local Optimization
(Drivers optimized independently)
Even when operational drivers are identified, execution problems can still arise when teams pursue improvements independently rather than in coordination with broader strategic outcomes.
Teams naturally optimize for the drivers they control. If those drivers are not clearly linked to enterprise outcomes, local improvements may create unintended trade-offs elsewhere in the organization.
For example, leasing teams may focus on maximizing occupancy, property management teams may focus on reducing operating costs, and development teams may focus on accelerating project delivery timelines. Each objective appears reasonable in isolation. However, maximizing occupancy may require tenant incentives that reduce portfolio returns, aggressive cost reductions may affect tenant satisfaction, and accelerated project timelines may increase development costs.
Without coordination, operational improvements do not necessarily translate into strategic progress.
Execution problems rarely originate in strategy design. They usually emerge in the translation between strategic outcomes and the operational drivers teams actually control.
From Strategic Direction to Operational-Level Execution
Strategic direction defines intent, but intent does not automatically translate into action. Between organizational strategy and day-to-day execution sits a layer of interpretation that determines whether direction becomes focused delivery or diffuses into disconnected effort.
As strategy moves through an organization, it must become progressively more concrete. Broad direction must be narrowed into priorities. Priorities must be translated into measurable outcomes. Those outcomes must then be linked to operational drivers and translated into team-level goals.
Senior leadership defines direction and the outcomes the organization is trying to achieve. Management teams interpret that direction by identifying the operational drivers that influence those outcomes. Operating teams then translate those drivers into specific goals and initiatives.
Performance measurement plays an important role in making this translation visible.
At the organizational level, performance is commonly tracked through Key Performance Indicators (KPIs). These measures provide continuity and help leadership understand whether the organization is moving in the right direction over time.
Closer to execution, organizations often use Objectives and Key Results (OKRs) to provide sharper focus on near-term improvements that influence those outcomes.
Cascading Strategy into Impactful Actions
Cascading is often misunderstood as simply pushing metrics downward through the hierarchy. In practice, effective cascading is a process of translating strategic intent into performance expectations that make sense at each level of the organization.
A helpful way to think about this distinction is through the relationship between outcomes and drivers.
At the top of the organization, performance is typically expressed in terms of outcomes. These outcomes reflect what success looks like at an organizational level and are usually tracked through a small number of KPIs.
As strategy moves closer to execution, attention shifts from outcomes to the drivers that influence those outcomes. Teams focus on improving the activities and processes that ultimately move the organizational KPIs.
For example, consider a real estate holding company with a strategic priority to improve portfolio returns.
Leadership may track return on invested capital or net operating income at the enterprise level. Asset management teams may focus on improving occupancy levels, leasing spreads, and cost discipline. At the operating level, asset teams may set OKRs focused on reducing vacancy in specific buildings, accelerating tenant fit-outs, or renegotiating service contracts.
Although the measures differ, they all contribute to improving the same strategic outcome.
Designing Effective KPIs and OKRs
Once strategy has been translated into performance expectations, the quality of execution depends heavily on how those measures are designed.
Many organizations treat performance measures primarily as reporting tools. Metrics are added because they are easy to track or historically used. Over time, this can lead to dashboards that track large volumes of data without necessarily improving decision-making.
The challenge in designing effective KPIs is rarely technical. Most organizations already have access to extensive data and reporting systems. The more difficult question is whether the measures being tracked genuinely reflect the outcomes the organization is trying to achieve.
Strong KPIs therefore focus on outcomes that matter strategically and that meaningfully reflect organizational performance. Weak KPIs often track activity, historical reporting conventions, or metrics that are easy to measure but only loosely connected to strategic priorities.
In practice, organizations rarely fail because they cannot measure performance. They fail because they measure outcomes that do not meaningfully guide decisions or behaviour.
For example, a KPI such as improve asset performance may sound aligned with strategy but remains too vague to guide action. A stronger alternative might be increase net operating income by a defined percentage year on year, which clearly defines the outcome the organization is trying to achieve.
Similarly, tracking the number of projects completed may indicate activity but does little to reflect execution quality. A stronger measure might track the percentage of projects delivered within approved budget and timeline, which better reflects disciplined execution.
While KPIs provide stability and continuity, OKRs serve a different purpose. They translate strategic priorities into focused, time-bound improvements that teams can act on directly.
Example:
Objective
Reduce delays in handover of completed projects
Key Results
- Reduce average handover delay from X days to Y days
- Achieve on-time handover for Z% of projects this quarter
These key results define measurable change rather than activity. They allow teams flexibility in how they achieve results while remaining clear on what success looks like.
When designed well, KPIs and OKRs complement each other. KPIs provide continuity and strategic guardrails, while OKRs focus teams on improving the operational drivers that influence those outcomes.
Conclusion
Organizational strategy creates value only when it meaningfully shapes how work gets done. Direction, no matter how well articulated, has limited impact if it remains confined to presentations, planning documents, or leadership discussions.
The challenge of execution is not simply one of communication or measurement. It is fundamentally a problem of translation. Strategy is defined at the level of outcomes, while execution happens through operational drivers and everyday decisions.
Organizations that execute well bridge this gap deliberately. They translate strategic priorities into clear outcomes, identify the operational drivers that influence those outcomes, and align team objectives with those drivers.
Performance measures such as KPIs and OKRs play an important role in this process, but they are tools rather than the objective. When designed well, they clarify what matters, anchor discussions in outcomes rather than activity, and ensure that everyday actions reinforce strategic intent.
This is how strategy moves from direction to delivered, impactful results.
Leave a Reply