Strategy's role in performance management

From Strategy to Results: Building a Performance Management System That Actually Works

A performance management system is only as good as the thread that runs through it — from your organisation's big-picture ambitions all the way down to the daily actions of every team member. When that thread is clear and unbroken, people understand why their work matters. When it's missing, even the best measurement tools become noise.

This post explores how to design a system built around that thread: the traceable line that connects strategy → goals → objectives → key results.

The Hierarchy That Makes Measurement Meaningful

Think of performance management as a cascade. Each level translates the level above it into something more concrete and actionable.

Strategy is the organization's direction — the "why" and the "where." It answers: What are we trying to become, and what do we stand for?

Goals are the major themes or outcomes that must be achieved to deliver the strategy. They are broad, medium-to-long-term, and owned at the organisational or business-unit level. Example: Become the most trusted provider in our region.

Objectives make goals specific and time-bound. They describe what needs to change and by when. A well-written objective is ambitious but clear. Example: Reduce patient wait times to under 15 minutes by Q4.

Key Results are the measurable outcomes that tell you whether the objective has been achieved. They are specific, quantifiable, and typically 2–5 per objective. They answer: How will we know we got there? Example: Achieve a patient wait time average of 12 minutes across all clinics by 31 December.

This four-level hierarchy — Strategy → Goals → Objectives → Key Results — is the backbone of the OKR framework (Objectives and Key Results), which has become one of the most widely used approaches to performance management in organizations of all sizes.

OKRs vs KPIs: Understanding the Difference

These two terms are often used interchangeably, but they serve different purposes. Both matter — the key is knowing when to use each.

OKRs (Objectives and Key Results) are about change and improvement. They are used to drive progress toward a specific outcome over a defined period (typically a quarter or year). OKRs are aspirational — they push the organisation forward and are often set slightly beyond what feels fully comfortable. When an OKR is complete, it may be retired or reset with a new objective.

KPIs (Key Performance Indicators) are about monitoring ongoing health. They track whether core business operations are performing within acceptable ranges. KPIs tend to be stable over time — they don't disappear once a target is hit, because they reflect things you always need to watch, such as revenue, customer satisfaction, or staff retention rates.

A simple way to think about it:

KPIs tell you if the engine is running. OKRs tell you if you're heading somewhere new.

In practice, a key result within an OKR might become a KPI once the new performance level is established and needs to be maintained. The two frameworks work together rather than compete.

Designing a System With Clear Traceability

Traceability means that anyone in the organisation — from the executive team to a frontline staff member — can look at their work and answer: How does this connect to our strategy?

To build that traceability:

Start at the top. Define your strategy clearly before setting any goals or metrics. Every goal should be explicitly linked to a strategic priority. If you can't explain why a goal exists in strategic terms, reconsider it.

Cascade deliberately. Each level of the hierarchy should be derived from the level above it, not created in isolation. Business-unit goals flow from organisational strategy. Objectives flow from goals. Key results flow from objectives.

Keep it focused. A common mistake is measuring everything. Too many metrics dilute attention and make it impossible to know what actually matters. Aim for 3–5 objectives per level, each with no more than 5 key results. The discipline of choosing few metrics forces clarity.

Involve the people doing the work. When teams participate in setting their own objectives and key results, they develop genuine ownership of the outcomes. Measurement becomes a tool for their success, not a judgement imposed from above.

Make the links visible. Use dashboards, planning documents, or team meetings to show explicitly how team-level OKRs connect to organisational goals. Visibility reinforces alignment and helps people see the bigger picture.

Putting It Into Practice: Transformation Projects

Transformation projects — implementing new systems, restructuring services, entering new markets — are exactly the contexts where a strategy-to-results framework pays off. Change is uncertain, and a clear measurement hierarchy keeps the team anchored.

From the outset, define your project objectives in OKR terms: what are you trying to achieve, and how will you know you've achieved it? Link those objectives explicitly to the organisational goals driving the project.

During execution, automate data collection wherever possible to reduce manual effort and improve accuracy. Share results regularly — transparency keeps stakeholders aligned and surfaces problems early, when they're still solvable.

Set targets that are ambitious but achievable. OKRs are meant to stretch thinking, not break morale. A well-calibrated key result creates energy; an unattainable one creates cynicism.

Practical example: A healthcare provider implementing a new patient management system defined their objectives around patient experience and operational efficiency, with key results covering wait times, scheduling accuracy, and training completion. These key results were linked directly to their organisational goal of improving patient trust — and that goal was explicitly tied to their strategy of becoming the region's leading community health provider. Weekly automated reports tracked progress, and the project team reviewed results together, adjusting plans as needed. The result: clear accountability, demonstrated value, and a project that stayed on track.

Sustaining the System Over Time

A performance management system is not a one-time implementation. To remain useful, it needs to evolve with the organisation.

Review and refresh metrics regularly. As strategy shifts, objectives should shift too. Key results that no longer reflect current priorities become noise.

Invest in building capability. Staff need to understand not just what the numbers say, but why they matter and how to act on them. Training and ongoing coaching build this capability over time.

Use data for learning, not blame. The most effective performance cultures treat measurement as a tool for improvement. When results fall short, the first question should be what can we do differently, not who is responsible.

Celebrate progress. Recognizing achievements — especially where they can be traced back to strategic priorities — reinforces the behaviours and focus that drive results.

Conclusion

Effective performance management starts with a clear strategy and ends with measurable results — but only if the links between those two points are explicit, visible, and understood at every level of the organization.

The OKR framework provides a practical structure for building that traceability: from strategic goals, to focused objectives, to the specific key results that tell you whether you're succeeding. KPIs complement this by keeping a steady watch on operational health. Together, they give organizations both the compass and the dashboard they need to perform and improve.

When measurement is connected to meaning, people don't just track performance — they drive it.