Key Performance Indicator

There used to be two ways to answer the question "is the company doing well?" One was the revenue ledger that closed at the end of the month. The other was whatever each team lead said in the meeting. Revenue reported things that had already happened, so it arrived after the moment to act had passed, and the team leads were all working from different standards. About the same month, one would say things felt good and another would say things were dangerous, and neither was lying — they were looking at different things.

So the monthly meeting always took the same shape. Each team spent half an hour describing what it had done, and the people listening had no basis for telling which part was a problem, so they nodded. Trouble surfaced when a customer got angry or the revenue line bent, never before.

A KPI reverses that order. Instead of deciding what to look at after something has gone wrong, you decide in advance which numbers would hurt if they slipped, and you leave those few switched on. A company can produce hundreds of numbers, but no more than ten ever get read in the same place week after week. Agreeing on which ones take those slots is what setting KPIs means.

Setting up a KPI doesn't end with picking a number. Each one carries four lines with it.

1. Pick what hurts when it slips. Pagedeck is a product where teams start free and then pay to keep using it, so if the rate at which paying teams leave gives way, every other number follows it down. Numbers in that position are KPI candidates.
2. Write the formula and the collection cadence in one line. For paid team churn, that is teams that cancelled this month divided by the paid team count at the end of last month, collected on the first of each month. Whether the denominator is taken at the start or end of the month changes the value, so it gets pinned down.
3. Write the normal range and the line that must not be crossed. A KPI is chosen to be watched rather than raised, which makes the threshold more useful than a target. Monthly churn up to 3 percent is normal; above 5 percent someone looks for the cause that week.
4. Decide where it gets read and by whom. Unless it is fixed that Grace reads it in the Monday operations meeting, even a well-built dashboard becomes a screen nobody opens two months later.

One more distinction shows up while picking. A value like revenue that reports something already finished is a lagging indicator; a value that moves ahead of the result — the share of teams that create three or more documents in their first week — is a leading indicator. Lagging numbers alone tell you too late, leading numbers alone never confirm the result arrived, so a KPI list usually mixes both.

Some numbers should not be picked at all. Cumulative signups can only go up, and a value like that is a vanity metric: pleasant to read aloud, but with no action attached when it moves. Giving it a KPI slot wastes the slot.

KPIs turn up in four places.

Executive review is the first. The same numbers are read in the same order in the weekly operations meeting and the monthly investor update. A list that changes every month can't show a trend, so once it's set it tends to stay for close to a year.

Team operations is the second. If paid team churn is the company KPI, customer success takes the share of teams that finish onboarding within 30 days and engineering takes the document save failure rate. Each step down, the number gets closer to something that team can actually move.

Third is the promise made to customers. A service level agreement (SLA) states in a contract what level of service will be maintained, and the uptime or response time written there becomes an internal KPI unchanged. Because breaking it means refunding money, its threshold is the clearest of any.

Fourth is evaluation and compensation, which is also the place to be most careful. Once someone's pay depends on a number, there are several ways to raise it besides doing the work well.

"Let's not make that a KPI — make it a key result for the quarter. It's a number you move once and then you're done."

It isn't something to watch forever, so it belongs in a different slot.

"Response time has been over the line for two days and nobody looked."

The KPI exists, but the fourth line — where it gets read and by whom — was never filled in.

"Please don't hand our team a KPI we have no way to move."

Accountability arrived without any lever attached to it.

At Pagedeck, Grace reads an eight-line list from the top on Monday morning: paid teams, paid team churn, first-week activation, document save failure rate, onboarding completion, monthly recurring revenue, uptime, new inbound requests. Each line carries last week's value and its threshold, so only the lines over the line show up red.

Last month, first-week activation dropped below its threshold. Nobody concluded anything in the room; Mia took it away to find the cause, and it turned out invitation emails were landing in spam. Revenue still looked fine at that point, so a team watching only revenue would have learned about it two months later, when payments started stopping.

The easiest assumption is that more KPIs mean tighter management. Leaving out something important feels risky, so a longer list feels safer. But a KPI list earns its keep when the person reading it can see what went wrong this week within ten seconds. With thirty lines, the meeting is spent deciding which line matters, and two months later nobody opens the screen.

Reading a KPI as a target is just as common. A number on the board looks like something to raise, and tying it to evaluation looks like it will make people try harder. But these numbers almost always have a hole somebody can reach. A team measured on response time finds a way to exclude slow requests from the count; a team measured on tickets closed passes the hard tickets to someone else. The number gets cleaner while the customer's experience stays the same. The name for a measure breaking down the moment it becomes a target is Goodhart's law. A KPI is closer to a thermometer: when the room is cold, the thing to do is turn on the heat, not push the needle up with your finger.