In this topic 15 sections
- 35Monitor delivery and results together
- 36Make each measure usable
- 37Use the balanced scorecard as a strategy tool
- 38Build dashboards around decisions
- 39Understand what a digital twin can contribute
- 40Keep checking the outside world
- 41Turn monitoring into an adaptive review cycle
- 42Align rewards with the work the strategy needs
- 43Check the behaviour an incentive could create
- 44Diagnose barriers before demanding more effort
- 45Handle power and disagreement constructively
- 46Keep sponsorship active
- 47Develop strategic agility
- 48The CPA's contribution to implementation leadership
- 49Sources and further reading
Monitor delivery and results together
Implementation monitoring asks whether agreed work is happening and whether that work is producing the intended change. These are connected questions, but they require different evidence. A completed activity is not automatically a successful outcome.
| What to examine | What the evidence can establish |
|---|---|
| Delivery | Whether the promised service, system or capability has been provided, at the required standard. |
| Efficiency | How much resource is used in producing a defined output. |
| Effectiveness | Whether the activity is achieving its intended purpose. |
Concept sources: Australian Department of Finance — What to include in a corporate plan — Output, efficiency and effectiveness measurement; original comparison for learning, not a statement that Commonwealth planning rules apply to every organisation.
Make each measure usable
A key performance indicator, or KPI, should help someone make a decision. Before collecting more data, agree what success means, the starting position and the action a concerning result should trigger.
| Measurement decision | Practical requirement |
|---|---|
| Define the result | Specify the population, calculation, unit and period; identify exclusions. |
| Establish a comparison | Record a baseline, target or other justified reference point. |
| Make the evidence traceable | Identify the data source, collection method and person responsible for checking it. |
| Connect it to action | Name the accountable manager, review frequency and escalation route. |
Concept sources: Australian Department of Finance — Reliable and verifiable — Clear methods, data sources and evidence; the decision-oriented table is an original application.
Keep definitions consistent across teams. A delivery rate that excludes difficult orders cannot be compared fairly with one that includes them. Explain revisions to a measure rather than quietly replacing an unfavourable trend. Combine quantitative results with appropriate qualitative evidence where a number alone misses important effects.
Use the balanced scorecard as a strategy tool
Kaplan and Norton's balanced scorecard connects strategic objectives with measures, targets and initiatives. Its familiar four perspectives help prevent short-term financial results from becoming the only view of performance.
| Perspective | Illustrative evidence for a repair service |
|---|---|
| Financial | Contribution from work completed and cash required to sustain the service. |
| Customer | Whether customers receive a dependable repair and would return. |
| Internal business process | Repeat work caused by repair defects and time waiting for parts. |
| Learning and growth | Demonstrated repair skills and access to useful technical knowledge. |
Concept sources: Robert S. Kaplan — Conceptual Foundations of the Balanced Scorecard — Four perspectives and links between objectives, measures and implementation; original table and repair-service application.
Start with the strategy, then select measures. Sorting an existing collection of statistics into four boxes does not establish strategic alignment. Explain the proposed connections: improved diagnosis may reduce repeat repairs, improve customer experience and protect contribution. These are relationships to investigate, not proof that one favourable indicator caused another.
A scorecard should communicate priorities across functions. It should not require every department to copy identical targets when their contributions differ.
Build dashboards around decisions
A dashboard presents selected information together so a user can identify developments worth investigating. Its usefulness depends on user needs, maintenance and the quality of its underlying data, not visual sophistication.
- Project view
- Track a particular initiative's milestones, expenditure, risks and unresolved issues.
- Programme view
- Examine dependencies and combined progress across related initiatives.
- Strategic view
- Connect implementation progress with organisational outcomes and relevant external developments.
Concept sources: UK Government Analysis Function — Data visualisation: building and managing dashboards — User needs, data maintenance and interpretation; the three management views are original applications.
Show reporting dates, definitions and limitations. Allow useful investigation by location, service or period without obscuring the overall result. A green status is only as meaningful as its threshold; stale or incomplete data can make it misleading.
Dashboards may combine several systems. Reconcile definitions and document transformations rather than assuming all displays share one source. Include explanatory comments and accessible alternatives where needed. A periodic report can be more useful than a dashboard when the result needs substantial interpretation.
Understand what a digital twin can contribute
A digital twin uses a digital representation of a real system to support monitoring, analysis or experimentation. Depending on its purpose, the representation may cover a machine, process or connected system.
Managers can use a suitable model to explore changes before making them operational. That can reveal bottlenecks or consequences that are difficult to see from separate departmental reports. Predictions still depend on the model's purpose, assumptions and data. A realistic-looking simulation is not evidence that it accurately represents behaviour.
Concept sources: NIST — Digital twins — Monitoring, simulation, validation and manufacturing-system applications; the ceramics example is original.
Keep checking the outside world
Implementation takes place while customers, competitors, technology, regulation and supply conditions continue to change. Horizon scanning looks beyond routine reports for emerging developments and weak signals that may affect the strategy.
Assign responsibility for important assumptions. A signal log can record what changed, its source, the assumption affected, possible consequences and the next review. Use varied sources and perspectives; an internal team can otherwise keep confirming its existing view.
Do not treat every headline as a reason to redesign the plan. Assess relevance, credibility and potential impact. Equally, do not wait for the annual planning cycle when evidence undermines a critical assumption. The appropriate response may be a small implementation adjustment, a contingency action or reconsideration of the strategy itself.
Concept sources: UK Government Office for Science — The Futures Toolkit — Horizon scanning, diverse evidence and implications for decisions; original application.
Turn monitoring into an adaptive review cycle
Collecting information is only useful when it changes understanding or action. Review actual results against the intended outcome, investigate material differences and decide who should respond.
- Compare results and assumptions
- Check data and investigate causes
- Decide whether delivery or strategy needs adjustment
- Assign an action and owner
- Check the result at the next review
Concept sources: Australian Department of Finance — Basis for assessment over time — Consistent measurement, learning over time and justified changes to measures; original review flow.
Avoid changing a target simply to disguise poor performance. Record what has changed, why the response is justified and how it affects resources, deadlines and expected benefits. Conversely, continuing to pursue an obsolete target is not discipline.
Public, private and not-for-profit organisations all need this learning process. Their purpose determines the emphasis: commercial viability, public outcomes or a charitable mission. Financial discipline remains relevant in each. Social or environmental commitments also need suitable evidence where they are part of the strategy; activity counts alone may not show the promised impact.
Align rewards with the work the strategy needs
Strategic reward connects recognition and reward decisions to the organisation's longer-term direction and employees' needs. Explain what contribution is valued, how it will be assessed and when it will be recognised.
Total reward includes financial and non-financial elements. Pay and benefits matter, but development opportunities, recognition, meaningful responsibility and the experience of work can also influence motivation. Different people may value these elements differently.
| Strategic need | Reward-design consideration |
|---|---|
| Cross-team service | Recognise shared results and useful cooperation, not only individual output. |
| Learning and innovation | Recognise disciplined experiments and knowledge sharing, including useful learning from unsuccessful trials. |
| Dependable execution | Acknowledge milestones and sustained quality, rather than only a final launch. |
Concept sources: CIPD — Strategic reward and total reward and CIPD — Reward: an introduction — Strategic and total-reward concepts; original design considerations.
Ensure the criteria are understandable and applied consistently. Recognition should reinforce the organisation's stated values. Announcing teamwork as a priority while rewarding only internal competition sends an opposing signal.
Check the behaviour an incentive could create
An incentive changes what people pay attention to. Ask how a person could achieve the measured target while damaging the underlying purpose. Use this question before introducing a scheme and when reviewing its effects.
Measure important outcomes and the way they are achieved. Review exclusions, complaints and unusual changes around target dates. Avoid severe rewards or penalties based on evidence too weak to distinguish an individual's contribution from external conditions.
Feedback should help people improve, not encourage concealment. A reported problem can provide valuable information; rewarding apparent perfection can discourage the reporting needed to correct it.
Concept sources: UK National Audit Office — The use of sanctions and rewards in the public sector — Perverse incentives, multiple motivations and limits of attribution; original bicycle-service example.
Diagnose barriers before demanding more effort
Successful implementation requires continuing leadership attention. People responsible for delivery should help shape the plan, because they understand dependencies, available capacity and practical constraints.
| Warning sign | Constructive response |
|---|---|
| People cannot connect tasks to the purpose | Explain the intended outcome and each team's contribution; invite questions. |
| Many priorities compete for the same people | Sequence commitments and decide which work will stop or wait. |
| A decision waits for endless additional analysis | Identify the decisive uncertainty, set a review date and consider a bounded trial. |
| One team changes while others keep incompatible routines | Resolve handovers, information needs, incentives and authority across the whole process. |
| Actions repeatedly remain unfinished | Check ownership, skills, resources, deadlines and follow-through. |
Concept sources: Knowledge at Wharton — Got a Good Strategy? Now Try to Implement It — Hrebiniak's first-person discussion of execution, priorities, coordination and accountability; original diagnostic table.
Paralysis by analysis substitutes repeated study for a decision. Strategic inertia preserves familiar routines even when circumstances change. Resistance may also reflect legitimate concerns about workload, capability, security or fairness. Diagnose the issue instead of labelling every objection disloyalty. A budget or presentation can support implementation; neither replaces coordinated action.
Handle power and disagreement constructively
Implementation redistributes resources, influence and responsibilities. People may resist losing authority even when a proposal benefits the organisation overall. A technically persuasive plan therefore also needs an understanding of whose interests and relationships it changes.
Disagreement about the work can improve a decision. Personal conflict and coalitions organised around status can prevent useful evidence from being considered. Leaders should identify the underlying concern, avoid taking sides automatically and intervene before a dispute spreads.
Discuss alternative proposals against agreed outcomes and evidence. Give relevant specialists a meaningful voice, clarify decision rights and record the reason for the decision. Listening to different views does not require waiting for unanimous agreement on every issue. Where the leader is personally involved, an impartial facilitator may help.
Concept sources: Lindred Greer, Stanford Graduate School of Business — How Conflict Goes Viral — Author explanation of conflict research, underlying interests and early intervention; original resource-allocation application.
Keep sponsorship active
A sponsor provides senior ownership of the purpose and business case. Sponsorship continues through the work and its benefits; it is more than endorsing the launch.
The sponsor connects the initiative to organisational priorities, helps resolve obstacles beyond the delivery team's authority and challenges whether the investment still makes sense. The project or programme manager coordinates delivery within the agreed governance arrangements. Clear roles reduce both neglect and unnecessary interference.
Maintain a route for escalating unresolved dependencies, resource shortages and changed assumptions. Senior support should include time and decisions, not only public encouragement. When ownership changes, transfer the rationale, commitments and open issues so that accountability survives the handover.
Concept sources: Association for Project Management — What is project sponsorship? — Continuing governance, business-case validity and benefits accountability; original application.
Develop strategic agility
Doz and Kosonen identify three connected capabilities for adapting business models. They help explain why seeing a problem is insufficient if the organisation cannot decide or redirect resources.
- Strategic sensitivity
- Notice significant developments and reconsider established assumptions with fresh evidence.
- Leadership unity
- Make coherent decisions across the senior team without allowing competing interests to obstruct action.
- Resource fluidity
- Redeploy resources and reconfigure capabilities when priorities change.
Concept sources: Yves L. Doz and Mikko Kosonen — Embedding Strategic Agility — Original research's three capabilities; concise original explanations and card design.
Agility does not mean changing direction every week. Leaders need enough consistency for people to act and enough openness to recognise that their assumptions may be wrong. Productive disagreement can precede a shared decision; leadership unity does not require suppressing evidence. Moving resources also requires practical attention to skills, commitments and the work that will be interrupted.
The CPA's contribution to implementation leadership
Finance professionals help connect strategic priorities, operating decisions and evidence. Their contribution extends beyond reporting whether expenditure matches the budget.
They can test affordability, compare alternatives and align funding with the capabilities the strategy needs. They can distinguish short-term cash requirements from longer-term investment, identify where funding is insufficient and question resources tied up in low-value activities. Cost control should support the strategy rather than automatically favour the lowest immediate expenditure.
CPAs also help define credible measures, reconcile information across functions and interpret the reasons behind results. They should challenge unsupported claims of success and explain uncertainty in language decision makers can use. Technical accuracy, ethical judgement, communication and collaboration work together.
Concept sources: IFAC — CFOs and Finance Functions: from Business Partnering to Value Partnering — Capital allocation, trustworthy information, strategic contribution and cross-functional partnership; original application.
Sources and further reading
- Australian Department of Finance — What to include in a corporate plan
- Australian Department of Finance — Reliable and verifiable
- Robert S. Kaplan — Conceptual Foundations of the Balanced Scorecard
- UK Government Analysis Function — Building and managing dashboards
- NIST — Digital twins
- UK Government Office for Science — The Futures Toolkit
- Australian Department of Finance — Basis for assessment over time
- CIPD — Strategic reward and total reward
- CIPD — Reward: an introduction
- UK National Audit Office — The use of sanctions and rewards in the public sector
- Knowledge at Wharton — Got a Good Strategy? Now Try to Implement It
- Lindred Greer, Stanford Graduate School of Business — How Conflict Goes Viral
- Association for Project Management — What is project sponsorship?
- Yves L. Doz and Mikko Kosonen — Embedding Strategic Agility
- IFAC — CFOs and Finance Functions: from Business Partnering to Value Partnering
