Part 2: Two frameworks that drive performance: Balanced Scorecard and OKRs

In Part 1, we explored why owner-managed businesses often lack the systematic performance management that their larger competitors use as standard. We talked about the cost of flying blind—discovering problems too late, working hard but not always on the right things, and missing the opportunities that data could reveal.

But what does “systematic performance management” actually look like in practice?

Today, we’re introducing you to two frameworks that have transformed how thousands of businesses measure and manage performance: the Balanced Scorecard and OKRs (Objectives and Key Results). If you’ve heard these terms but never quite understood what they mean or how they’d work in your business, this post will change that.

Why you need a framework (not just more data)

Before we dive into the frameworks themselves, let’s address a common misconception: more data doesn’t equal better performance.

Many field services businesses are drowning in data. Your job management system spits out dozens of reports. Your CRM tracks every customer interaction. Your accounting software produces pages of analysis. The problem isn’t a lack of information—it’s a lack of structure.

A framework gives you:

• Focus: What actually matters amongst all the noise
• Balance: A complete view, not just financial outcomes
• Alignment: Everyone working towards the same goals
• Consistency: The same language and approach across your business
• Clarity: Decisions based on what you’ve agreed to measure

Think of it like this: data without a framework is like having all the ingredients for a meal scattered across your kitchen. A framework is the recipe that turns those ingredients into something valuable.

Framework 1: The Balanced Scorecard

What it is

The Balanced Scorecard was developed by Harvard professors Robert Kaplan and David Norton in 1992. Their insight was simple but powerful: if you only look at financial metrics, you’re only seeing part of the story. And by the time financial problems show up, it’s often too late to prevent them.

The Balanced Scorecard looks at your business through four perspectives:

1. Financial Perspective The traditional view: revenue, profitability, margins, cash flow. This tells you what happened, but not why it happened or what’s coming next.

2. Customer Perspective
How are your customers experiencing your business? Metrics like customer satisfaction scores, retention rates, Net Promoter Score (would they recommend you?), repeat business percentage, complaint resolution times.

3. Internal Process Perspective How well are your operations actually running? For field services businesses, this might include: average job completion time, first-time fix rates, schedule adherence, materials wastage, health and safety incidents, quote-to-order conversion rates.

4. Learning & Growth Perspective Is your business getting better? This covers: employee training hours, skill certifications, employee satisfaction and retention, system improvements, innovation initiatives.

Why it’s “Balanced”

Here’s the crucial insight: these four perspectives are connected.

Let’s say your financial results are slipping. The Balanced Scorecard helps you understand why:

• Your customer perspective shows satisfaction scores dropping
• Which traces back to your internal process perspective showing first-time fix rates declining
• Which relates to your learning and growth perspective showing high engineer turnover and insufficient training

Let’s say your financial results are slipping. The Balanced Scorecard helps you understand why:

Without the framework, you just see the financial problem weeks after month-end. With it, you can spot the leading indicators (training, turnover) before they impact customers and ultimately profit.

Real-World Success: Apple

Apple famously uses the Balanced Scorecard to align product development with business strategy. They track customer satisfaction through Net Promoter Score and retention rates, whilst measuring internal processes like product development cycle times and supply chain efficiency. This balanced view is one reason they’ve maintained both innovation and profitability whilst scaling globally.

The principle works at any scale. You don’t need to be Apple—you just need the discipline to look beyond the P&L.

Framework 2: OKRs (Objectives and Key Results)

What it is

OKRs were developed at Intel in the 1970s by Andy Grove, then popularized when John Doerr introduced them to Google in 1999. Google still uses them today—from 40 employees then to nearly 140,000 now.

The structure is elegantly simple:

Objectives: Qualitative, ambitious, inspiring goals. What you want to achieve.

Key Results: Specific, measurable, time-bound outcomes that prove you’ve achieved the objective.

Here’s an example for a heating and plumbing contractor:

Objective: Become the most reliable emergency callout service in our region

Key Results:

1. Reduce average response time from 4 hours to 2 hours
2. Achieve 95% first-time fix rate (currently 78%)
3. Increase customer satisfaction score from 7.2 to 8.5 (out of 10)
4. Reach 80% of callouts resulting in booked annual service contracts

Notice how the objective is aspirational (“most reliable”), whilst the key results are concrete and measurable. You can’t debate whether you’ve achieved them—the numbers tell you.

The Google principles

When John Doerr introduced OKRs to Google, he brought several principles that made them powerful:

Transparency: Every OKR is publicly visible to every employee. Your engineers can see the Managing Director’s OKRs. Your estimating team can see what operations is working towards. This creates alignment and helps everyone understand how their work contributes.

Ambitious targets: At Google, scores between 0.6 and 0.7 are considered successful. If you’re consistently hitting 1.0, you’re not being ambitious enough. OKRs should stretch you, not just confirm what you were going to do anyway.

Bottom-up and top-down: About 60% of team goals are developed by the teams themselves and then aligned with company goals. This creates ownership whilst maintaining strategic direction.

Quarterly cycles: OKRs typically run in 3-month cycles, allowing you to adapt quickly rather than being locked into annual targets that may no longer make sense.

Real-World Success: LinkedIn

When Jeff Weiner became CEO of LinkedIn in 2008, he implemented OKRs across the organisation. The framework contributed to LinkedIn’s growth from a struggling social network to a $20 billion company (acquired by Microsoft in 2016). Weiner credits OKRs with creating the alignment needed to scale rapidly whilst maintaining focus on what mattered most.

Balanced Scorecard v OKRs: Which one is right?

You might be wondering: which framework should I use?

The honest answer is that they’re complementary, not competing:

Balanced Scorecards give you a complete view of business health across all dimensions. They’re excellent for ensuring you’re not over-indexing on any single area. Many businesses use them for ongoing performance monitoring.

OKRs drive focused progress on strategic priorities. They’re excellent for rallying teams around ambitious goals and creating urgency. Many businesses use them for quarterly or annual improvement initiatives.

Some successful businesses use both: a Balanced Scorecard for “running the business” metrics (the heartbeat) and OKRs for “changing the business” initiatives (the strategic push).

For a field services business, you might have:

• Balanced Scorecard: Monitoring your core operational metrics continuously
• Q4 OKRs: “Reduce materials wastage by 30%” with specific key results that your operations and procurement teams work towards

The real power: cascading goals

Here’s where both frameworks become transformational—when goals cascade through your organisation.

At company level: “Achieve 25% revenue growth whilst maintaining 20% net margin”

Cascades to operations: “Improve job profitability by reducing average completion time by 15% without compromising quality”

Cascades to individual site manager: “Achieve 95% schedule adherence and reduce engineer overtime hours by 20%”

Cascades to individual engineer: “Complete advanced heating systems training and maintain 4.5+ customer satisfaction rating”

Everyone can see how their work connects to the bigger picture. The site manager understands that schedule adherence drives profitability. The engineer understands that training enables faster, better work that improves margins. It’s not just “do your job”—it’s “here’s how your job contributes to our growth.”

At Google, this cascading creates both vertical alignment (everyone working towards company goals) and horizontal visibility (teams can identify where they need to collaborate). The same principle works in a 50-person contracting business.

Why in-house implementation often falls short

By now, you might be thinking: “This makes sense, but we don’t have the systems to support it.”

You’re not wrong. This is where most owner-managed businesses hit a wall.

Your finance team—if you have one—is focused on compliance, reporting, and managing cash. They’re looking at financial outcomes, probably in Excel, probably weeks after month-end. They don’t have visibility into operational metrics like job completion times or customer satisfaction scores. And they certainly don’t have time to pull data from your job management system, CRM, and accounting software, reconcile it all, and present it in a meaningful dashboard.

Your CRM might have nice dashboards, but they only show sales pipeline. Your job management system has reports, but they don’t connect to financial data. Your accounting software tells you what happened last month, not what’s happening today.

The Balanced Scorecard requires data from across your business. OKRs need regular tracking—weekly or fortnightly reviews, not month-end reports. Neither framework works if you’re still manually piecing together spreadsheets.

This is the integration challenge that stops most businesses from implementing systematic performance management.

And it’s exactly what we’ll address in Part 4 when we talk about implementation. But first, there’s a crucial measurement principle you need to understand…

What’s coming in part 3

You now understand the frameworks. But which metrics should you actually track? More importantly, should you measure the things you want (outcomes) or the things you do (activities)?

This question, activities versus outcomes, is the most common measurement mistake businesses make. Get it wrong, and you’ll demotivate your best people whilst rewarding luck. Get it right, and you’ll focus effort on what actually drives results.

In Part 3, we’ll show you why smart businesses measure inputs, not just outputs, and how this transforms both performance and motivation.

Next in this series: Part 3: The input imperative: Why smart businesses measure activities, not outcomes

Previously: Part 1: Why large, successful companies outperform: It’s not just scale, it’s systems