The Value Creation ProtocolContents
Part III — The Core Framework Traps
Chapter 14
The Measurement Trap → Value-First Measurement
Danielle Urban and I talked through this trap in June 2025.
In this trap nobody is fooled. The person reporting the number knows what was done to it. The person receiving it knows too. The meeting goes ahead anyway, and decisions get made on a figure nobody in the room believes.
Where does your brain go with that? Mine goes to the effort. Good people work hard to produce a number for other good people, who will quietly discount it. None of them chose this. They were handed the number and told it mattered.
What this is
The Measurement Trap:
Optimizing for activity metrics that feel productive while missing outcomes that create value.
Activity is easy to count. Calls made, emails sent, tickets closed, hours logged. Whether anything changed for the person on the other end is harder to count, so it gets counted less, and after a while the easy numbers are the only ones on the page. Then people do what people do with a number they are judged on. They make it go up.
This trap holds a particular place among the twelve. Every other trap in this book produces activity, and activity is what most reports count. So this is the one that keeps the others hard to see.
The belief it breaks is Natural Value Flow over Artificial Control: "Value exists and wants to flow naturally through human systems, independent of our efforts to control it." A number used to control people stops telling you the truth about them.
The alternative is Value-First Measurement, and it comes as four short instructions: "Measure outcomes, not activities. Track value created, not tasks completed. Align metrics with actual customer impact. Accept that meaningful measurement is harder but worth it."
Don't skip the fourth one. It is harder, and this chapter won't pretend otherwise.
Those four lines leave out the practice our vocabulary lists first under Value-First Measurement: "Use Key Value Indicators (KVIs) over KPIs." A Key Value Indicator is a question about value, answered from what the people who received it have confirmed, and never a score. Value Accounting, Chapter 13 is the handbook for crossing over.
How to tell where you are
Take the last report you sent upward, or the last one that was sent to you, and put it on the table.
- Go down it line by line. Does each number count something your people did, or something that changed for someone? Mark each one.
- Is there a number on the page that everyone privately discounts? You will know it by the look people exchange when it is presented.
- Whose pay or review depends on each number? Wherever the answer is a name, assume the number is being managed.
- How long did the report take to build? If someone gives up a day every month to assemble a picture of last month, that day is part of what this trap costs you.
- Is the report green while the business feels flat?
- Think of the last number your team celebrated. Can anyone say what was different for a customer because of it?
What to do
- Put every number you report on one page, in two columns. What we did. What changed for someone. Most of them will land in the first column. That is normal, and now you can see it.
- Find the gamed one. Ask your team which of your numbers they don't believe. Ask it somewhere an honest answer is safe, and protect the first person who gives one.
- 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.
- Give every remaining activity number a person. Beside each one, write who is supposed to be better off because of that activity, and what they should now be able to do. Kept where the work is recorded, that note is what Value Accounting, Chapter 2 calls a CARE record. If you can't name anyone, stop reporting the number.
- Go and ask those people. Not with a survey score. Ask one question of one person, and keep the answer in their words.
- Retire a report. Pick one nobody would miss, stop producing it, and give the person who built it that time back.
- Say what you can't measure yet. Say it in the leadership meeting, out loud. Admitting you don't know yet is a more honest entry than a precise number nobody believes.
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.
How you know it worked
This is where the chapter hands you to another book, so I'll keep it short.
You know it worked when a person who received something from your work can say, in their own words, what they can do now that they couldn't do before. That is the definition of value all five of these books use. It belongs to The Value Era, and here it is word for word:
What a person or organization can now do that they could not before. Not what they were sold, not what was produced for them, not a promise about the future — value is the real change in what someone can do, and only the person who received it can say it happened.
Only the person who received it can say it happened. So the proof of better measurement isn't a better number. It is that person's sentence, in your report, in the place where the activity count used to be.
Inside your own walls, look for two more things. Someone brings you a number that makes their own team look worse, without being asked, because numbers are now for learning. And a decision gets changed because of something a customer said.
How to keep that account properly is a practice of its own: writing an entry, showing it to the person who received the value, letting them confirm or dispute it, settling the month, and reading what they confirmed beside what the work was for. That is Value Accounting (Book 4), and I'm not going to teach it here. Go there next.
Where it goes wrong
The new number becomes the next thing to hit. You replace calls made with customer outcomes, attach a bonus to it, and it gets managed exactly like the old one. The problem was never which number you picked. It was what the number was used for. The Value Era spends a chapter on how replacement measures get gamed.
Hours saved. This one arrives with AI. I wrote this in 2025 and I'd write it again today: "Please stop focusing on how much time you are saving me and ask me how much additional value you are helping me to create." Counting what you removed from someone's day is still counting your own activity. If the person on the receiving end tells you they got time back, that is theirs to say. A provider claiming the hours as its own result is the trap.
Measuring nothing. Some teams see all of this and give up on measurement. That isn't the alternative. The fourth instruction says meaningful measurement is harder. It doesn't say it is optional.
The trap beside this one is the Authority Trap (Chapter 16). Many gamed numbers exist because someone far from the work needs a way to control it. If the real job of a report is to let the top check on the bottom, cleaner numbers won't fix it. Move the decision closer to the work, and a good deal of the reporting stops being needed.
Read further
- Value Accounting (Book 4) is the handbook for keeping the account: what an entry is, how the person who received the value confirms it, how a month is settled, and how what they confirmed is read beside what the work was for.
- The Value Era (Book 0). Chapter 14, "Only the person who received it", is where the definition of value is argued. Chapter 5, "Back into money, gamed on arrival", shows how a replacement measure gets gamed.
- The AI-Native Shift (Book 3). Chapter 15, "Counting What Counts", is the long answer to this trap in an organization working with AI. Chapter 1, "The One Everyone's Afraid to Lose", explains why hours saved is the wrong first question.