Defining KPIs That Survive Contact With a Board Meeting
A marketing KPI has to hold up under questioning from people who do not care about marketing. Most do not. Here is how to build ones that do.
There is a specific and slightly brutal test for a marketing KPI: it has to survive twenty minutes of questioning from people who do not care about marketing.
Not hostile people. Just a board, or a CFO, or a founder under pressure — people whose job is capital allocation and who reasonably want to know whether money going into marketing comes back out larger. Most marketing KPI frameworks do not survive that conversation, and the failure is usually predictable.
Having sat on both sides of it, in enterprises and in startups, here is what holds up.
The three ways KPIs die in the room
Death by proxy. You present engagement rate. Someone asks what it is worth. You explain that engagement correlates with retention. They ask how strongly, and over what period, and whether that held last quarter. You do not have it, because the correlation was asserted in a deck two years ago and never re-tested.
Proxy metrics are not inherently wrong — sometimes a proxy is all you can measure in-period. But an unvalidated proxy is a liability, and you should know which of your metrics are proxies before someone else finds out.
Death by attribution. You present channel-attributed revenue. Someone asks whether those customers would have converted anyway. The honest answer is that you do not fully know, and the moment you say so, every number on the slide loses weight — including the ones that were solid.
Death by denominator. You present a percentage that improved. Someone asks about the absolute number, and it turns out the rate went up because the base shrank. This is the most common one, and it is fatal to credibility because it looks like you were hiding it. Sometimes you were. Often you just hadn't checked.
Build a hierarchy, not a list
The fix is structural. A flat list of fifteen KPIs cannot survive scrutiny, because nothing in it explains how the items relate. A hierarchy can.
I use three levels, and I insist on the arithmetic between them.
Level 1 — the business outcome. One metric. Not a marketing metric. A business metric that marketing materially influences. Net revenue retention, new ARR, contribution margin, whatever the model runs on. One. If you cannot pick one, the strategy is not settled yet, and that is the real conversation to have.
Level 2 — the drivers. Three to five, and they must multiply out. This is the part most frameworks skip. The level 2 metrics should compose, arithmetically, into level 1. If new ARR is the outcome, drivers might be qualified pipeline, win rate, and average deal size — and their product should approximate the outcome.
The arithmetic matters enormously. It means when someone asks "why did the outcome miss", you can answer structurally instead of narratively. Pipeline held, win rate dropped four points, here is where. That is a different quality of answer than "the market was tough".
Level 3 — the operating metrics. Owned by individuals. Everything the team manages weekly, each mapped to exactly one level 2 driver. Email conversion under lifecycle. Landing page conversion under pipeline. If a level 3 metric cannot be mapped to a level 2 driver, you have found either a missing driver or a metric nobody should be optimising.
Rules I have learned to apply
Every KPI gets a target set before the period, not after. Retrofitting targets to results is the fastest way to lose a board's trust, and everyone can tell. Setting them in advance also forces the useful argument about what good looks like while it is still cheap to have.
Every rate gets its absolutes shown alongside. Always. Conversion rate next to conversions and sessions. This costs nothing, pre-empts the denominator question, and signals that you are not curating.
Name the proxies out loud. Say "this is a leading indicator, here is the correlation we have measured and over what window". Volunteering the weakness is what buys credibility for the rest. Boards are far more comfortable with an acknowledged uncertainty than a discovered one.
Pick a defensible attribution stance and hold it. Any model — first touch, last touch, data-driven, incrementality testing — is defensible if applied consistently and if its limits are stated. What is not defensible is switching models between quarters, which reliably looks like you shopped for the flattering answer.
Cap it at one page. If the KPI framework does not fit on one page, it will not be internalised, and a framework nobody remembers has no influence on behaviour.
The metric nobody wants to own
Every marketing organisation has one metric that is genuinely important and genuinely nobody's job. Usually it lives between marketing and product, or marketing and sales. Activation. Onboarding completion. Lead response time. Trial-to-paid.
These sit in the gap, so they drift for quarters. Meanwhile they are often the highest-leverage numbers in the business, precisely because nobody has been optimising them.
When I build a KPI hierarchy, I look for those first. Assigning an owner to an orphaned high-leverage metric frequently produces more improvement in a quarter than any campaign, for the simple reason that it starts from a baseline of total neglect.
What good looks like in the room
The version that survives is unglamorous. One outcome metric. Four drivers that multiply into it. A dozen operating metrics, each owned by a named person, each mapped upward. Targets set in advance. Absolutes shown next to rates. Proxies labelled as proxies. Attribution stance stated once and held.
When the outcome misses, you walk the hierarchy and show exactly which driver broke and which operating metric explains it. When it beats, you show the same thing in reverse and can say whether it is repeatable.
That is the whole trick. Not better metrics — better structure between them. Boards do not lose confidence in marketing because the numbers are bad. They lose confidence when the numbers cannot explain themselves.
Got a version of this problem?
I work with teams on exactly this — CRM, analytics and marketing operations that need to start producing results.