KPI Design
Advanced 13 min read KPI Design

Scorecards and Cascades

One glance, one status, one escalation path

A scorecard is a compact status device: name, value, delta, trend, band — one row per KPI. Cascades extend it down the org: each level's scorecard rolls into the parent.

scorecardcascadestatustraffic lightroll-upcomposite
Prerequisites: KPI Fundamentals Targets and Thresholds
Before we start

What you will learn

  • Design a scorecard row (value, delta, trend, band)
  • Roll scorecards up a cascade with weighting rules
  • Keep composite scores honest about masking
Introduction

What is this?

A scorecard turns each KPI into a one-row status card: name, value, delta vs target, sparkline trend, and a traffic-light band — scannable in one pass. Cascades roll scorecards up the hierarchy so a team scorecard feeds a divisional one feeds the board's. The design arts: weighting, composite scoring, and preventing a good average from hiding a failing dial.

Motivation

Why do you need it?

  • One-row status beats 'here's 40 charts' for a standup or a board.
  • Cascades keep executive views built from validated bottom-up facts.
  • Composite scores need good semantics (weighting/masking) or they lie flat.
  • Scorecards are the KPI artifact senior analysts actually ship.
Think about it

Mental model

Imagine

A multi-function watch face and the sports standings

Think of

Scorecard rows and cascades

A watch face shows one glance: time, a couple of dials — status without paperwork. Sports standings roll each team's record up to a league table: win/loss rows, weighted, and visible to everyone. A combined view tells you who's leading and why in one screen.

Mechanics

How it works

  • Scorecard row: name + value + delta vs target + trend spark + band.
  • Band derivation from the threshold bands you already defined.
  • Roll-up: a parent scorecard sums/aggregates its children (reconcilable) or blends score bands.
  • Composite index: weighted blend with explicit weights; masking optional (ALL red flags).
  • Escalation: red band routes to the owner path from the cascade.

One scorecard row and its cascade roll-up.

Team rows
Division roll
Composite
Board row
Escalate
Hands-on

Examples

A scorecard row definition

A scorecard row definition
Row: Revenue (EU)      Value 96k    Δ -4%    Trend↘  Band AMBER
Row: Revenue (US)      Value 125k   Δ +4%    Trend↗  Band GREEN
Row: Revenue (Corp)    Value 221k   Δ 0.4%   Trend↗  Band GREEN
                                 (reconciles: 96k+125k=221k)
 
Composite Score = 0.5*Revenue + 0.3*Margin + 0.2*SLA
Mask rule: composite cannot exceed worst red band member.

Each row is a decision card; roll-ups reconcile; composites weight and can't bury a red.

Real world

In production

  • A weekly exec scorecard: one table, every KPI family as a row with owner path.
  • A division cascade publishes team scorecards that aggregate to the divisional sheet.
  • A masked composite blocks a failing support SLA from being averaged away.
Guidelines

Best practices

  • Keep the scorecard one screen; extend detail via click-through.
  • Make roll-ups reconcile bottom-up; audit the math.
  • Publishing composite masking rules so an average can't hide an outage.
  • Band and delta render the decision; trend spark shows momentum.
Watch out

Common mistakes

  • A scorecard full of 'value only' — no target, no band, no decision.
  • Cascade sums that don't tie because grain differs.
  • Composite that averages a red into a green shrug.
  • Status rows nobody can act on (no owner path when red).
When things break

Debugging tips

  • Composite green, red tiles below → implement masking or re-weight.
  • Roll-up doesn't reconcile → the cascade grain differs; verify per-row grains.
  • Scorecard row misbanded → threshold band config stale; route to the band table.
Interviews

Interview checkpoint

Test yourself

Quick quiz

0/2
1

What keeps a composite score from hiding a failing KPI?

2

A cascade's roll-ups must reconcile to their parents.

Go deeper

Official documentation

Balanced scorecard institute - cascading
docs