Value Accounting

Part III — Keeping the book

Chapter 13

From KPIs to KVIs


In June 2026 my team's records showed 18 projects realized that month.

Fourteen of the eighteen came from one bulk close-out, between June 6 and June 8. Somebody had tidied up. The number was accurate. It counted exactly what it said it counted. And it told us nothing about what anyone had received in June.

That's a key performance indicator doing what KPIs do. It measured our activity, it was easy to produce, and it could go up without a single person outside the team being better off.

I've been pushing against that for a while. In May 2025 I told a colleague that "one of my boldest things is to try and move from key performance indicators to key value indicators." The following spring I put it more bluntly, in my written answers to a brand questionnaire: "100 calls is a KPI. 'Did we create a genuine connection?' is a KVI."

What I didn't have then was a way to answer the second kind of question honestly. This handbook is that way. This chapter is for the leader who runs on KPIs today and wants to cross over without pretending the numbers never mattered.

What this is

Our vocabulary has said it since September 2026, as one of the practices of Value-First Measurement: "Use Key Value Indicators (KVIs) over KPIs." The shift it names is from "Control metrics (optimize for measurable activities)" to "Value indicators (recognize genuine value creation)."

A Key Value Indicator is a question about value that a leader steers by. It is answered from confirmed entries, which carry the receiver's own say. And it is read beside the CARE record for that work, so the answer is about whether the value served what you set out to do.

Three things follow from that, and they are what keep a KVI from being a KPI with a kinder name.

  • It's a question, and the answer is in words first. "Did we create a genuine connection?" has an answer you can read. If a count helps, it sits beside the words and never replaces them.
  • It reads backward. It tells you what happened. It is never set ahead of time as something to hit.
  • It is never about one person. No score, no rate and no ranking for anyone doing the work.

Some of what I wrote about KVIs in 2025 doesn't pass that test. I listed KVIs with names like scores, indexes, rates and velocities, each one a percentage we would work out about other people. I wrote those before this practice existed. They're part of how I got here, and I'm not teaching them. What I'd keep from them is that every one was written as a set of questions.

How to tell where you are

  • Your leadership meeting opens with a dashboard, and the conversation is about why a number moved.
  • You can report what your team did last month to two decimal places. You can't report what one named customer can now do.
  • Somebody's pay or review depends on a number, and the number has become unusually reliable.
  • A report is green and the business feels flat.
  • When you ask "is this what we set out to do?", nobody can find where what you set out to do was written down.
  • You've already tried swapping in a "better" metric, attached it to a goal, and watched it get managed like the last one.

What to do

Take one KPI across. Not the whole dashboard.

1. Pick one number you already report, and leave it running. Don't switch it off. You're going to read something beside it for a while.

2. Take it out of pay and reviews first. The Protocol's chapter on the Measurement Trap is plain about the order: "Take that number out of pay and reviews before you change anything else. You can't ask people to stop managing a number their income depends on."

3. Ask what the number was for, and write that down. Who is supposed to be better off because of the activity it counts, and what should they now be able to do? That is a CARE record, and Chapter 2 is how you write one. This is the step where what leadership meant finally gets written where the work is recorded. If you can't name anyone, the Protocol's instruction stands: "stop reporting the number."

4. Turn it into a question. "Requests closed this month" becomes "Could the people who sent those requests do what they were trying to do?" "Projects realized" becomes "What can someone do now because of a project we finished?" Write the question on the CARE record. That question is your KVI.

5. Go and get the answer the way this book teaches. If there's a particular person you expect to receive something, open their entry at Expected and say so in a sentence. Then hear it, write what landed, show it, and take their word. There's no shortcut here. A KVI has nothing to read until there are confirmed entries.

6. Read the confirmed entries beside the CARE record. Open the intention. Open what the people said. Ask the question from Chapter 12: did the value that emerged serve the care behind the work? Write the answer in a sentence. Some of what you find will be value nobody intended. Some of what you intended won't be there. Both are the reading.

7. Put that sentence where the KPI used to lead. In the meeting, in the report. The Protocol describes the goal as "that person's sentence, in your report, in the place where the activity count used to be."

8. Decide what happens to the old number. There are three honest outcomes.

  • Keep it as context. "Keep the activity numbers that help you run the work. An activity count is a fine thing to know. It only becomes the trap when it is asked to stand for value."
  • Keep it beside the reading for a while. An organization in the middle of changing still needs some of the old structure while the new one earns trust. When the KPI and the reading disagree, say out loud which one you're going to act on.
  • Retire it. If nobody would decide anything differently without it, stop producing it, and give the person who built it that time back.

9. Don't count the crossing. How many KPIs you've converted is a KPI.

How you know it worked

A decision changes because of something a customer said, and the person who made the decision can point to the entry.

Someone on your team brings you a reading you didn't want, and the meeting spends its time on what to do about it, not on whether the number is right.

The people doing the work stop asking how they're being measured. They start telling you what they heard.

They're what I'd look for.

Where it goes wrong

The KVI becomes a count of confirmations. It's the nearest number to hand, and it has "value" in its name. Then people go and collect confirmations. Chapter 8 says it for the whole practice: "Nobody is measured on how many entries get confirmed."

It gets a goal attached. The Protocol watched this happen with the last good idea: "You replace calls made with customer outcomes, attach a bonus to it, and it gets managed exactly like the old one." Its conclusion holds here: "The problem was never which number you picked. It was what the number was used for."

It becomes a dashboard. Somebody builds a tile for it. Now it's a number on a wall again, and the words behind it are two clicks away where nobody goes.

It's used on a person. The moment a KVI appears beside someone's name, in a review or a ranking, it's a performance indicator, whatever you call it.

The old KPIs are switched off overnight. People still need to know whether the work is running. Take them out of pay first, read the KVI beside them, and let the old ones go when nobody is deciding from them.

Read further

Stop 1 of 6: What this is

Back to contents