Strategy Execution and Performance Management

Introduction

Strategy creates value only when it is translated into coordinated decisions, funded work, accountable behaviour and measurable results. Many organisations do not fail because their strategy is analytically weak; they fail because strategic intentions remain disconnected from budgets, operating routines, incentives and learning systems. Strategy execution is therefore the disciplined process of converting strategic choices into initiatives, capabilities, actions and benefits.

Performance management complements execution. It establishes how an organisation will define success, measure progress, allocate attention, correct deviations and learn. Effective performance management is not synonymous with producing more reports. It is a leadership system that links purpose, priorities, resources, behaviours and outcomes.

This chapter examines strategy maps, the Balanced Scorecard, Objectives and Key Results (OKRs), portfolio governance, management control systems and benefits realisation. It also considers common execution gaps, ethical risks, technology-enabled performance management and the role of leadership in maintaining strategic coherence.

Learning Objectives

By the end of this chapter, readers should be able to:

1. Explain the relationship between strategy, execution and performance management.
2. Construct a strategy map and translate it into Balanced Scorecard objectives and measures.
3. Distinguish KPIs, targets, milestones, OKRs, leading indicators and lagging indicators.
4. Design a portfolio governance process for selecting and controlling strategic initiatives.
5. Diagnose execution gaps using evidence rather than symptoms alone.
6. Establish accountabilities, controls and benefits-realisation practices.
7. Evaluate ethical, behavioural and technological risks in performance systems.

1. From Strategic Intent to Organisational Action

A strategy normally specifies a desired position, a theory of how value will be created and a set of choices about where to compete and how to win. Execution adds the operating architecture required to make those choices real. This architecture includes:

• Initiatives: time-bound programmes or projects intended to produce strategic change.
• Budgets: financial and non-financial resources assigned to priorities.
• Structures: roles, decision rights, reporting relationships and coordination mechanisms.
• Capabilities: skills, processes, technologies, data and relationships required for performance.
• Measures: indicators that reveal progress, outcomes, risks and unintended consequences.
• Accountabilities: named owners with authority to act and obligations to report.

Execution is not a linear cascade in which senior leaders issue targets and lower levels comply. It is a process of vertical alignment and horizontal integration. Vertical alignment connects enterprise priorities to business-unit and individual work. Horizontal integration prevents functions from optimising their own measures at the expense of the whole system.

A useful execution logic is:

Strategic choice → strategic objectives → initiatives and capabilities → outputs and behaviours → outcomes → realised benefits.

The arrows represent hypotheses, not guarantees. For example, investing in analytics capability may improve decision quality, but only if managers use the information and if decisions affect customer or operational outcomes. Performance management must therefore test causal assumptions rather than merely record activity.

2. Strategy Maps and the Balanced Scorecard

2.1 The strategy map

A strategy map is a visual representation of the organisation’s value-creation logic. In the classic Balanced Scorecard approach, objectives are arranged across four perspectives:

1. Learning and growth: people, culture, leadership, technology and organisational capabilities.
2. Internal processes: processes that must excel to deliver the strategy.
3. Customer or stakeholder: value experienced by customers and important stakeholders.
4. Financial or mission outcomes: economic sustainability, public value or mission achievement.

The perspectives are not rigid categories. A public organisation may place mission outcomes above stakeholder value, while a social enterprise may use social impact and financial sustainability as parallel outcomes. The essential feature is an explicit chain of contribution.

For example, skilled service teams and reliable digital systems may improve process speed and first-contact resolution. Those process improvements may increase customer trust and retention, which may improve revenue and margin. The map makes the assumed relationships visible and therefore discussable.

2.2 Balanced Scorecard design

A Balanced Scorecard translates the map into a manageable set of objectives, measures, targets and strategic initiatives. A good scorecard avoids two errors:

• measuring everything, which creates noise and weakens attention; and
• measuring only financial outcomes, which reports consequences after corrective action may be difficult.

Measures should be strategically relevant, understandable, controllable or influenceable, timely and resistant to gaming. Each measure requires a clear definition, data owner, source, frequency, baseline, target and interpretation rule.

A measure is not automatically a KPI. A KPI is a measure judged sufficiently important to receive regular leadership attention and action. A target is the desired level or range of performance by a specified date. A milestone is a significant point in the delivery of an initiative, such as pilot completion or regulatory approval.

2.3 Leading and lagging indicators

A lagging indicator records an outcome after it has occurred, such as annual profit, market share or employee turnover. A leading indicator provides earlier evidence about activities or conditions likely to influence that outcome, such as qualified sales opportunities, defect-prevention checks or training application.

Leading indicators are not automatically causal. Training hours, for instance, may correlate weakly with performance if training is irrelevant or not applied. Leaders should periodically test whether leading indicators predict useful outcomes and discontinue measures that merely create activity.

3. Objectives and Key Results

OKRs provide a focused method for expressing ambitious objectives and measurable results. An objective describes what should be achieved in clear, motivating language. Key results specify observable evidence that the objective has been achieved. Initiatives are the actions used to influence key results; they are not themselves key results.

Example:

• Objective: Make onboarding simple and trusted.
• Key result 1: Reduce median onboarding time from 10 days to 4 days by the end of Q3.
• Key result 2: Increase successful first-time applications from 72% to 90%.
• Key result 3: Raise post-onboarding trust rating from 3.8 to 4.4 out of 5.

OKRs are particularly useful where learning, innovation and cross-functional focus are important. They should not be treated as a mechanical replacement for all performance systems. Individual compensation tied too tightly to ambitious OKRs can encourage sandbagging, manipulation or concealment of uncertainty. A sound practice is to use OKRs primarily for alignment, prioritisation and learning, while using broader evidence for performance and reward decisions.

The Balanced Scorecard and OKRs can coexist. The scorecard normally provides the stable strategic architecture and enterprise outcomes; OKRs provide time-bound focus within teams or strategic themes. Both require disciplined definitions, review routines and honest conversations.

4. Translating Strategy into Initiatives and Budgets

Strategic initiatives are the principal bridge between objectives and change. An initiative should have:

• a clear strategic objective and problem statement;
• an accountable executive sponsor;
• a delivery leader and cross-functional team;
• expected outputs and benefits;
• an estimated cost and resource profile;
• dependencies, risks and decision points;
• a benefits owner who remains accountable after delivery;
• a review date and closure criteria.

4.1 Initiative selection

Organisations commonly have more proposed initiatives than they can fund or manage. Selection should therefore consider strategic contribution, urgency, feasibility, risk, regulatory necessity, interdependence and opportunity cost. A scoring model can structure judgement, but it should not disguise political decisions as mathematical certainty.

If a weighted score is used, a common form is:

Here, S is the initiative’s total score, wᵢ is the weight assigned to criterion i, and rᵢ is the initiative’s rating on that criterion. Ratings must use a defined scale, such as 0–5, and weights must be non-negative and sum to 1. The score supports comparison; it does not establish that benefits will occur or that risks are acceptable.

4.2 Budget integration

A strategic budget links resources to choices rather than simply extrapolating last year’s spending. It should distinguish:

• run costs: resources required to maintain current operations;
• change costs: resources required to implement new capabilities;
• transition costs: temporary costs during migration or restructuring; and
• benefit effects: expected changes in revenue, cost, risk exposure, quality or mission outcomes.

A portfolio may appear affordable when only project costs are counted, but become unaffordable when operating costs, data migration, training, cybersecurity and post-launch support are included. Leaders should also identify capacity constraints: money may be available while specialist skills, leadership attention or technical integration capacity are not.

5. Portfolio Governance and Decision Rights

Project management controls delivery of an individual initiative. Portfolio governance controls the collection of initiatives as an investment system. Its purpose is to ensure that the portfolio is strategically coherent, affordable, risk-balanced and capable of producing benefits.

A practical governance model contains:

• an executive portfolio board that sets priorities and resolves conflicts;
• a portfolio management office that maintains standards, data and assurance;
• sponsors who own strategic outcomes;
• delivery leaders who manage scope, schedule, quality and risks;
• finance, risk, technology, legal and operational representatives where relevant; and
• business owners who adopt outputs and realise benefits.

Decision rights should be explicit. The board may approve funding and stop initiatives; a sponsor may approve scope within delegated limits; a delivery leader may sequence work within an approved baseline. Escalation thresholds should cover budget variance, schedule slippage, risk exposure, benefit deterioration and material changes in assumptions.

Portfolio reviews should ask more than “Is the project on time?” They should ask:

1. Is the initiative still strategically relevant?
2. Are the critical assumptions still credible?
3. Is the organisation ready to adopt the output?
4. Are benefits likely, measurable and owned?
5. Should the initiative be accelerated, redesigned, paused or stopped?

Stopping a weak initiative is not failure. It can be evidence of effective governance when the decision protects scarce resources and prevents sunk-cost bias.

6. Management Control Systems

A management control system is the integrated set of mechanisms through which leaders influence behaviour and performance. It includes formal and informal controls:

• Diagnostic controls: compare results with plans and highlight exceptions.
• Interactive controls: use frequent dialogue to explore uncertainty and emerging threats.
• Boundary controls: specify prohibited actions, risk limits and compliance requirements.
• Belief systems: communicate purpose, values and strategic direction.

This classification highlights a central leadership challenge: control must create discipline without suppressing learning. Excessive diagnostic measurement can produce bureaucratic compliance, while insufficient control can permit drift, fraud or uncontrolled risk.

A control is effective when it is timely, reliable, understood, proportionate and connected to a decision. A dashboard that displays dozens of measures without decision rules is an information artefact, not a control system.

Accountability and responsibility

Accountability means being answerable for a result; responsibility refers to performing or contributing to work. They should not be confused. A cross-functional result may have one accountable owner but several responsible contributors. A RACI matrix can clarify whether a party is Responsible, Accountable, Consulted or Informed, but it should not replace judgement about authority, capability and workload.

7. Diagnosing Execution Gaps

An execution gap is the difference between intended and achieved strategic performance. Diagnosis should separate symptoms from causes. Common symptoms include missed milestones, cost overruns, low adoption, stagnant customer outcomes and repeated emergency interventions.

A structured diagnosis examines six dimensions:

1. Clarity: Do people understand the strategic choice and expected outcomes?
2. Translation: Are objectives converted into feasible initiatives and operating priorities?
3. Capacity: Are funding, skills, time and technology sufficient?
4. Coordination: Are dependencies, hand-offs and decision rights working?
5. Commitment: Do incentives, leadership behaviour and culture support the strategy?
6. Learning: Are data and review routines identifying and correcting problems early?

A useful distinction is between a delivery gap and a strategy gap. A delivery gap occurs when a sound objective is poorly implemented. A strategy gap occurs when the assumed value proposition, market logic or causal model is no longer valid. Treating every failure as a delivery problem can lead to more effort being invested in an obsolete strategy.

Root-cause methods such as process mapping, stakeholder interviews, variance analysis and the “five whys” can support diagnosis. However, causal claims should be tested against multiple sources of evidence. A single dashboard indicator rarely explains a complex organisational outcome.

8. Benefits Realisation

Benefits realisation is the disciplined practice of ensuring that change produces intended improvements. It extends beyond project closure because outputs are often delivered before users adopt them and before outcomes appear.

A benefits register should identify:

Benefits may be financial, operational, customer-related, strategic, social or risk-reducing. They should not be double-counted across initiatives. A finance function may validate monetary benefits, while operational and stakeholder owners validate service or mission outcomes.

A simple net benefit expression is:

This is an evaluative identity, not a universal valuation method. Costs and benefits must use consistent time periods, attribution rules and valuation assumptions. Where benefits occur over several years, discounted cash-flow methods may be appropriate; where outcomes are non-financial or highly uncertain, qualitative and multi-criteria assessment may be more defensible than false precision.

9. Technology, Data and Artificial Intelligence

Digital platforms can integrate financial, operational, customer and workforce data into near-real-time performance views. Process mining can reveal bottlenecks, while predictive analytics can identify risks or forecast demand. AI may support anomaly detection, scenario analysis, forecasting and the summarisation of performance commentary.

These tools do not remove managerial responsibility. Important safeguards include:

• data definitions and ownership;
• lineage, quality and access controls;
• model validation and monitoring for drift;
• explainability appropriate to the decision;
• human review for consequential decisions;
• privacy, cybersecurity and records management; and
• controls against metric manipulation or automated discrimination.

An algorithm optimising a narrow target can damage the wider strategy. For example, optimising call duration may reduce service quality if complex customers are rushed. Technology should therefore be governed by the strategy map and balanced with countermeasures for quality, equity, resilience and long-term effects.

10. Illustrative Case: Meridian Health Network

Background

Meridian Health Network, a fictional regional provider, sought to reduce avoidable hospital readmissions while improving patient experience and financial sustainability. Its existing strategy was widely communicated but execution was fragmented. Clinical, digital and finance teams each managed separate projects and reported different definitions of success.

Problem

Readmission reduction was treated as a technology project. A new patient portal was delivered on schedule, but adoption was low. Clinicians complained about duplicate data entry, patients reported confusing discharge instructions and the finance team could not verify claimed savings. The project dashboard showed green status because scope, schedule and expenditure were within tolerance.

Analysis

A strategy-map workshop identified the causal logic:

• train care teams in coordinated discharge planning;
• redesign discharge and follow-up processes;
• improve patient understanding and access to support;
• reduce avoidable readmissions and improve trust;
• release capacity and improve financial sustainability.

The analysis showed a delivery gap in adoption and process integration, but also a design gap: the original initiative measured portal deployment rather than patient outcomes.

Approach

The network created a portfolio rather than a single technology project. It appointed a clinical executive as benefit owner, a digital lead as delivery owner and local hospital managers as adoption owners. The Balanced Scorecard included:

• learning: percentage of relevant staff completing applied discharge training;
• process: percentage of eligible patients receiving a completed follow-up plan;
• patient: comprehension and trust scores;
• outcome: risk-adjusted 30-day readmission rate;
• financial: validated cost avoided, with explicit attribution rules.

OKRs were used for a 90-day improvement cycle. The portfolio board required evidence of clinical adoption before approving further portal expansion. Patient representatives reviewed communications, and a data-quality audit established a common baseline.

Outcome

In this illustrative case, adoption improved after the process was redesigned around clinical workflows rather than portal deployment. Early outcome evidence was promising but not treated as proof of causation. The board continued monitoring for unintended effects, including delayed care for patients with limited digital access. Financial benefits were reported only after finance and clinical owners agreed on attribution.

Learning points

1. A delivered output is not the same as a realised benefit.
2. Strategy maps expose dependencies between capability, process, stakeholder and outcome measures.
3. Portfolio governance should review adoption and value, not merely project status.
4. Equity and access are performance concerns, not optional ethical additions.
5. A green dashboard can conceal strategic failure when its measures are poorly designed.

11. Challenges, Ethics and Best Practices

Performance systems can create dysfunctional behaviour. Common risks include target gaming, data manipulation, local optimisation, excessive surveillance, short-termism and the exclusion of difficult-to-measure outcomes. High-pressure cultures may discourage bad-news reporting, precisely when leaders most need accurate information.

Ethically responsible systems apply proportionality, transparency and contestability. People should understand how important measures are defined and used. Data about employees or customers should be collected lawfully and only for legitimate purposes. Automated ratings should not become unchallengeable judgements. Leaders should examine distributional effects: an average improvement may conceal declining outcomes for vulnerable groups.

Best practices include:

• maintain a small number of strategically important objectives;
• define measures, baselines, owners and decision rules before reporting begins;
• combine leading, lagging, quantitative and qualitative evidence;
• separate learning measures from punitive individual surveillance where possible;
• review causal assumptions and stop obsolete initiatives;
• connect budgets to strategic priorities and capacity constraints;
• make benefits ownership continue beyond project closure;
• use independent assurance for material claims;
• encourage escalation of risks and bad news; and
• treat strategy execution as an adaptive leadership process, not a one-time cascade.

Chapter Summary

Strategy execution converts strategic choices into coordinated initiatives, resources, capabilities, behaviours and outcomes. Strategy maps clarify the organisation’s theory of value creation, while the Balanced Scorecard translates that theory into objectives, measures, targets and initiatives across learning, process, stakeholder and financial or mission perspectives. OKRs provide focused, time-bound objectives and measurable results, but should not be confused with initiatives or used as the sole basis for rewards.

Portfolio governance ensures that initiatives remain strategically relevant, affordable, coordinated and benefit-oriented. Management control systems combine diagnostic, interactive, boundary and belief controls to create discipline while supporting learning. Execution-gap diagnosis distinguishes problems of clarity, capacity, coordination, commitment and learning from failures in the underlying strategy. Benefits realisation extends accountability beyond project delivery and requires baselines, owners, attribution and post-implementation review. Technology and AI can improve visibility and prediction, but they also create risks involving data quality, privacy, bias and narrow optimisation. Effective leaders therefore design performance systems that are strategically coherent, ethically defensible and capable of learning.

Key Terms

Strategy execution: Converting strategic choices into coordinated action and results.

Performance management: Processes for defining, measuring, reviewing and improving organisational performance.

Strategy map: A visual model of objectives and assumed cause-and-effect relationships.

Balanced Scorecard: A framework linking strategy to objectives, measures, targets and initiatives.

Strategic initiative: A time-bound programme or project intended to advance a strategic objective.

KPI: A measure selected for sustained leadership attention because of its strategic importance.

Leading indicator: An earlier signal associated with future performance.

Lagging indicator: A measure of an outcome after it has occurred.

OKR: An objective paired with measurable key results.

Portfolio governance: Oversight of a collection of initiatives as an integrated investment system.

Management control system: Formal and informal mechanisms used to influence behaviour and performance.

Accountability: Being answerable for a result or decision.

Benefits realisation: The practice of ensuring that intended improvements are achieved and sustained.

Benefits owner: The person accountable for achieving a stated benefit.

Baseline: The measured pre-change position used for comparison.

Execution gap: The difference between intended and achieved strategic performance.

Diagnostic control: A control that compares results with plans and highlights exceptions.

Boundary control: A control that defines prohibited actions or acceptable risk limits.

Disbenefit: An unintended negative consequence of an initiative or change.

Review Questions

Short Answer Questions

1. What is the purpose of a strategy map?
2. Distinguish a leading indicator from a lagging indicator.
3. What is the difference between an initiative and a key result in an OKR system?
4. Why should benefits ownership continue after project closure?
5. Name two ethical risks associated with performance management systems.

Long Answer Questions

1. Explain how the Balanced Scorecard translates strategy into execution, including the role of objectives, measures, targets and initiatives.
2. Discuss how portfolio governance differs from project management and why both are necessary.
3. Evaluate the advantages and limitations of using OKRs in a post-graduate management context.
4. Explain the six dimensions that can be used to diagnose an execution gap.
5. Discuss how management control systems can support both strategic discipline and organisational learning.

Analytical / Application Questions

1. An organisation reports that 95% of a digital transformation project is complete, but customer adoption and service outcomes have not improved. Diagnose the likely execution gaps and propose a revised performance system.
2. Design a compact strategy map and scorecard for a university seeking to improve graduate employability. Include one objective and one measure for each relevant perspective.
3. A portfolio board must choose between three initiatives with different strategic benefits, risks and resource demands. Explain how you would structure the decision, what evidence you would require and when you would recommend stopping an initiative.

Multiple Choice Questions with Answers

Question 1

Which statement best describes the purpose of a strategy map?

A. To display an organisation’s complete operational budget

B. To represent the assumed relationships through which strategic value is created

C. To rank employees according to individual performance

D. To replace all project plans with a single diagram

Correct Answer: B. To represent the assumed relationships through which strategic value is created

Question 2

Which is a leading indicator of future service performance?

A. Last year’s operating profit

B. Annual market share

C. Percentage of staff applying newly learned service procedures

D. Final customer-retention rate

Correct Answer: C. Percentage of staff applying newly learned service procedures

Question 3

In an OKR system, which item is a key result?

A. Launch a redesigned mobile application

B. Create a cross-functional implementation team

C. Reduce median application-processing time from 10 days to 4 days

D. Appoint an executive sponsor

Correct Answer: C. Reduce median application-processing time from 10 days to 4 days

Question 4

What is the primary focus of portfolio governance?

A. Managing the detailed daily tasks of one project

B. Ensuring that the collection of initiatives is coherent, affordable and benefit-oriented

C. Calculating employee payroll deductions

D. Writing technical specifications for every system

Correct Answer: B. Ensuring that the collection of initiatives is coherent, affordable and benefit-oriented

Question 5

If initiative ratings use a 0–5 scale and the criteria weights sum to 1, what does a weighted score represent?

A. A guaranteed financial return

B. A structured comparison based on selected criteria

C. The probability that the initiative will succeed

D. The number of months required for delivery

Correct Answer: B. A structured comparison based on selected criteria

Question 6

Which statement correctly distinguishes accountability from responsibility?

A. Accountability means being answerable for a result; responsibility concerns performing or contributing to work

B. Accountability applies only to finance; responsibility applies only to operations

C. They are always identical and require the same person

D. Responsibility is held by the board, while accountability is never delegated

Correct Answer: A. Accountability means being answerable for a result; responsibility concerns performing or contributing to work

Question 7

What is a benefits baseline used for?

A. To establish the pre-change position against which improvement can be assessed

B. To guarantee that projected benefits will occur

C. To eliminate the need for a benefits owner

D. To record only the project’s staff attendance

Correct Answer: A. To establish the pre-change position against which improvement can be assessed

Question 8

A dashboard shows that a project is on schedule, but intended users rarely adopt its output. What does this most clearly illustrate?

A. Successful benefits realisation

B. A possible gap between delivery and outcome adoption

C. The irrelevance of stakeholder measures

D. The need to remove all leading indicators

Correct Answer: B. A possible gap between delivery and outcome adoption

Question 9

Which control type defines prohibited actions and acceptable risk limits?

A. Belief control

B. Interactive control

C. Boundary control

D. Diagnostic control

Correct Answer: C. Boundary control

Question 10

Why should AI-supported performance systems include human review for consequential decisions?

A. Because automated systems can never process data

B. Because human review helps address uncertainty, bias, context and contestability

C. Because dashboards cannot display numerical information

D. Because AI removes the need for data governance

Correct Answer: B. Because human review helps address uncertainty, bias, context and contestability