F FulcrumGrid

Home / Blog / KPI Scorecard Guide

Operations

How Do You Build a KPI Scorecard Your Team Will Actually Use?

A KPI scorecard only works if people open it. Learn how to pick 5 to 8 metrics, assign owners, set targets and RAG thresholds, and choose a review cadence.

· 6 min read

Most KPI scorecards start with enthusiasm and end as a forgotten spreadsheet. The problem is rarely the tool. It is usually too many metrics, no clear owners and no regular moment when anyone looks at the numbers together. This guide walks through how to build a scorecard that is small enough to read in two minutes and useful enough to change decisions.

What is a KPI scorecard?

A KPI scorecard is a one-page view of the handful of numbers that tell you whether your team or business is on track. Each metric has an owner, a target and a status, so a reader can tell at a glance what is healthy, what is slipping and who is responsible for it. It is not a full report. It is the page that tells you which report to open next.

How many metrics should it have?

Between five and eight. Fewer than five and you miss important trade-offs; more than eight and nobody remembers them. Choose metrics that cover different sides of the work, so that improving one does not quietly damage another. A balanced set usually includes:

  • Outcome metrics. The results you ultimately care about, such as revenue against plan or customer satisfaction.
  • Driver metrics. The activities that lead to those results, such as pipeline coverage or on-time delivery.
  • Health metrics. Signals about sustainability, such as staff turnover or cash position.

For each candidate, ask three questions. Can we measure it reliably every period? Can someone on the team actually influence it? Would we act differently if it turned red? If the answer to the last one is no, drop it.

A worked example

Here is a six-metric scorecard for a mid-sized services company. Treat the numbers as illustrations and replace them with your own.

  • Revenue vs. plan (owner: finance lead). Target 100% of monthly plan.
  • Pipeline coverage (owner: sales lead). Target 3x next quarter’s quota.
  • On-time delivery (owner: operations lead). Target 95% of projects or orders.
  • Customer satisfaction (CSAT) (owner: support lead). Target 4.5 out of 5.
  • Days sales outstanding (owner: finance lead). Target 45 days or fewer.
  • Voluntary staff turnover (owner: HR lead). Target under 10% annualised.

Why every metric needs one owner

An owner is not the person who types the number in. It is the person who explains it and proposes a fix when it slips. Give each metric exactly one name. Shared ownership means nobody speaks up in the meeting. Also write down the data source and the definition, for example “on time means delivered on or before the date confirmed with the customer”. Arguments about definitions waste more meeting time than arguments about performance.

Setting targets and RAG thresholds

A target is the value you are aiming for. A threshold is the line that decides the colour. Keep the colours simple and agree the rules before the numbers arrive:

  • Green. At or above 95% of target. No action needed.
  • Amber. Between 85% and 95% of target. The owner explains the cause and the plan.
  • Red. Below 85% of target. The owner brings a recovery plan and asks for help if needed.

For metrics where lower is better, such as days sales outstanding, flip the logic. Base targets on past performance and what the business needs, not on wishful thinking. A target that is always green teaches people to ignore the page, and one that is always red does the same. Show the trend too: a small arrow or the last three periods tells you whether amber is improving or getting worse.

Choosing a cadence

Match the review rhythm to how fast each metric moves. Weekly for operational drivers such as delivery and pipeline, monthly for outcomes such as revenue and satisfaction, quarterly for slow-moving health metrics and for reviewing the targets themselves. Keep the scorecard meeting to 30 minutes, focus the discussion on amber and red items, and end with named actions and dates. Green items get a nod, not a presentation.

Common pitfalls

  • Too many metrics. If the page needs scrolling, it is a report, not a scorecard.
  • Vanity metrics. Page views and sign-ups look good but rarely drive a decision.
  • No owner. A red metric with no name next to it stays red.
  • Stale data. If numbers arrive two weeks late, the meeting is about history, not control.
  • Never changing it. Review the set every quarter. Retire metrics that no longer matter and add ones that do.
  • Using it to blame. If red means punishment, people will quietly adjust the numbers. Treat red as a request for help.

Start small: build the first version in an afternoon, run it for a month, and improve it from what the team actually says in the room.

Frequently asked questions

How many KPIs should a scorecard have?

Aim for five to eight. That is enough to cover results, drivers and health, and few enough that everyone can remember them without opening the page.

What is the difference between a KPI and a metric?

A metric is any number you can measure. A KPI is a metric that is tied to a goal, has a target and an owner, and is important enough to review regularly.

How do RAG thresholds work?

RAG stands for red, amber, green. You agree in advance how far from target a metric can be before its status changes, for example green at 95% of target or better, amber from 85% to 95%, red below 85%.

How often should we review the scorecard?

Review fast-moving driver metrics weekly and outcome metrics monthly. Revisit the metrics and targets themselves every quarter.

Back to the blog

FulcrumGrid Command Center

Keep your scorecard in one place

FulcrumGrid Command Center lets you track KPIs, owners and projects together, so your scorecard stays current without manual copy and paste.