Your CEO shows you a dashboard. 47 KPIs on a single screen. "These are the numbers that matter." She turns to you for approval.
Here's the moment that defines a CFO: do you nod and play along, or do you have the honest conversation that 47 KPIs aren't KPIs — they're noise?
KPI design is exactly that conversation. It's the discipline of choosing the few numbers that actually move the business, putting owners on them, connecting them to decisions, and killing everything else.
By the end of this module you'll have it cold. Let's go.
Your CEO asks for ONE KPI to measure business health this quarter. Which do you pick?
The plain-English version
Before any framework, the four basic questions.
Why do we do this?
So the business moves in the right direction. A good KPI changes behavior. A bad KPI distorts it — people chasing the wrong number, or gaming it to look good.
Who uses it?
FP&A teams design KPIs in collaboration with business leaders. Used by: CEOs and boards to allocate resources, operating managers to execute, and the entire team to understand what they need to deliver.
When does it come up?
Designing the annual plan. Launching a new initiative. When an existing KPI clearly isn't working. Every performance review. If a team doesn't have a clear KPI, they're flying blind.
What if we skip it?
The team chases the wrong thing for a full year. They optimize the proxy and destroy the real thing. When the result lands, no one can explain what happened — the metrics they had didn't measure the decisions they made.
Meet Andina S.A. (again)
Same Andina from Module 2.6. The LATAM coffee company. The CEO now wants to "improve the management dashboard."
The FP&A team shows what it has: 47 KPIs on a single page. Revenue, GP, GM%, EBITDA, EBITDA%, Volume, Price, Mix, Inventory, DSO, DPO, FX, Headcount, Cost per bag, Cost per kilo, Cost per SKU, NPS, Churn, CAC, LTV, Repurchase rate, Complaints per customer, Call-center wait time… and 24 more.
The CEO looks at the page. "Okay. Which one do I have to move this week?"
Silence.
That silence is the problem KPI design solves. A good KPI system isn't measured by how many numbers it has — it's measured by how many decisions it enables. 47 KPIs without hierarchy and without owners isn't a dashboard. It's an excuse.
In this module we're going to redesign Andina's CEO dashboard. We start by decomposing the driver tree.
- Is it actionable? Is there someone who can do something different tomorrow because of this number? If not, it's not a KPI — it's interesting trivia.
- Is it measurable with discipline? Same calculation, same period, same data source. If the number changes depending on who calculates it, it's not a KPI — it's an opinion.
- Does it tie to value? Does the action it motivates improve the business result? Some KPIs move without moving anything real (vanity metrics).
- Does it survive gaming? If the team is smart enough to game it, does the business still win? KPIs that create perverse behavior are the most dangerous.
Decomposition: the driver tree
The first design step is decomposing the top-line metric into operational drivers — and those drivers into sub-drivers — until you reach something a manager can move on Monday morning.
Look at the tree below. Hover any node: the branch lights up and the detail appears for the specific KPI to monitor and who owns it.
KPI driver tree
Hover any node — the whole branch lights up and the details appear below.
The top-line. What everyone watches. By itself, it tells you nothing about why.
A KPI without an owner isn't a KPI — it's a wish. A KPI without a sub-driver tree is a number you can't move. Top-line revenue is everyone's KPI, which means it's no one's. Decompose until each leaf has a name.
That's the tree. It started at "Revenue" — everyone's KPI, which means no one's — and ended at concrete leaves: "Net Revenue Retention," "Net realised price as % of list," "Avg orders per customer per quarter."
Each leaf has an owner. Each leaf has a clear calculation. Each leaf moves with specific decisions. That's what separates a KPI system from a graveyard of numbers.
Vanity vs actionable
Vanity vs actionable. Same data, two KPIs.
Here's the contrast that changes careers. The left side is the KPI that strokes ego; the right is the one that moves the business.
Total customers
We sum every customer we've ever had.
Big metric, easy to present to the board: "We have 45,000 customers."
Impossible to move down (dead customers don't resurrect), always grows, says nothing about business health.
Active customers (90 days)
Customers who purchased at least once in the last 90 days.
If it drops, you know something is happening now. If it rises, something is working that's worth understanding.
Decomposes into: new vs retained vs reactivated. Each has an owner and an action plan.
The North Star metric
Beyond the tree, every serious organization has ONE number that represents "the business is healthy." For Spotify it's Time Spent Listening. For Airbnb it's Nights Booked. For your business, it might be Net Revenue Retention, or Active Customers, or Margin per Order. A single number that, if healthy, everything else falls in line. Designing this number is the most strategic KPI decision you make as CFO.
Adversarial check
Adversarial check
1.Your marketing team presents: "We grew +35% in Instagram followers this quarter." The CEO is happy. You're the CFO. What do you say?
2.A call-center manager has this KPI: "average call time — target: cut 15%." She hits it. Customer complaints on social media rise 40%. What happened?
3.The CEO asks you to simplify the executive dashboard. It currently has 47 KPIs. What's your recommendation?
Exit checklist
Suggested re-review: 6 months. KPIs evolve with strategy — re-evaluate the tree every time the annual plan changes.
Optional
Go deeper
Sources and books to dig into the original material