Part III — Keeping the book
Chapter 12
Read it backward
Reading it backward means reading the month as a record of what happened, and only that. Not a score. Not next month's goal. Not a ranking of who did best.
What this chapter adds is what you read the month beside: what the work was for.
What this is
Our vocabulary calls reading the month beside what the work was for Return on Intention, and it's one question: "Did the value that emerged serve the care behind the work?" It also asks it as two shorter ones: "What returned? Whom did it serve?" It's a question, not a ratio. Nothing gets divided by anything, and the answer is a sentence. When I introduced it in public, I put it this way: "Care gives rise to intention. Value accounting helps us see what came back and how it served that care."
What the work was for lives in a CARE record, and Chapter 2 is how you write one. A CARE record is what the work was for, written when it started. It isn't next month's goal, and it holds no number. So reading the month beside it doesn't turn the month into a score. The month is still a record of what happened. You're reading it next to what you meant.
The book you keep has a name in our vocabulary, the Value Ledger, and the definition says the whole thing in one line: "The honest book of value that actually reached people — read backward to see what happened, never a score to climb or a leaderboard to win."
My team ruled four things about how a month gets read, and they're the spine of this chapter:
- Two numbers, side by side, never added. One for the outside lane, one for the inside lane. Adding them builds a number that can climb while nobody outside received anything new. Chapter 9 makes that case.
- Each number counts confirmed moments by the month the value happened. Not the month someone wrote the entry, and never the month someone tidied up the records.
- The number is information, never a target, and never a leaderboard. Our rulebook adds one sentence I'd put on the wall: "A quiet month is information too, not a failing row."
- Every number opens back up to the moments and the people inside it.
In the article I published about this practice in September, I described what an honest month looks like on paper. It still holds: "It reads like a short memo. One sentence stating plainly what actually happened this month: good, bad, or quiet. Beneath it, the list of moments still waiting on someone's word, visible and un-hidden, because an open question isn't a failure. It's just still open. At the bottom, two numbers: client value and internal value, never combined into one." What the article calls client value and internal value, this book calls the outside lane and the inside lane.
Here is what that looks like in numbers: my team's book of value, month by month, as it stood on November 12, 2026. Each number counts moments that someone confirmed, placed in the month the value actually happened. The first column is value that reached people outside the team. The second is value that reached the team itself.
| Month the value happened | Outside | Inside |
|---|---|---|
| July 2026 | 2 | 5 |
| August | 9 | 5 |
| September | 1 | 3 |
| October | 7 | 7 |
| November, through the 12th | 1 | 0 |
| No date recorded | 2 | 1 |
Look at September. One.
The pull is to explain it right away, or to set a number for October so it doesn't happen again. Hold off on both. A quiet month is telling you something, and you can't hear it while you're busy defending it or fixing it.
One more thing about that table: every number in it can still move, because a confirmation can still arrive for any month until it's closed.
Why a number turns into something people chase the moment it becomes a goal is an argument, not a practice, and The Value Era makes it. Its Chapter 5, "Back into money, gamed on arrival", is the one to read.
How to tell where you are
- Someone asks what next month's number should be.
- The number shows up in somebody's review, or next to their name.
- A quiet month gets explained before anybody has read it.
- You can't open the number and see the moments and the people inside it.
- You can say what happened this month, and nobody can find where anyone wrote down what the work was for.
- A month jumps right after somebody cleaned up the records.
- The pile of entries still waiting on someone's word gets treated as a backlog to burn down.
- The number gets read every month, and nothing anyone does changes because of it.
What to do
1. Read a month as finished only once it's closed. Closing the month is Chapter 11's job. Until a month is closed, say so wherever you show its number: it can still move, because a confirmation can still arrive. How a closed month is marked, so that someone reading it later can tell it's closed, is a decision to make before your first close, and Chapter 11 lists it with the other two.
2. Count by the moment. Each confirmed entry goes in the month its value happened. If an entry has no real date, put it in its own pile, where it can be seen, and go find the date. Don't let it fall into whatever month you happen to be in.
3. Put the two numbers side by side, and stop there. Outside and inside. No third number underneath that adds them.
4. Read the words before you write the sentence. Open the month's confirmed entries and read what the people said, in their own words. Then open the CARE record for the work beside them, and ask the question: did the value that emerged serve the care behind the work? Where an entry started at Expected, what was expected is still on it, in the words it was first written in, so you can read it beside what landed. Some value will be there that nobody intended. Some of what was intended won't be there. Both are the reading. If nobody wrote down what the work was for, the reading says that too, and Chapter 2 is how you start one for the next piece of work. Then write one plain sentence about what happened. Good, bad or quiet. If it was quiet, the sentence says it was quiet.
If you lead by KPIs today. The KPI you'll recognize in this chapter is a monthly count read for whether it beat last month, like our own June count of realized projects, most of which came from a three-day tidy-up. What this step gives you to read in its place is the people's own words, beside what the work was for. Chapter 13 shows how to turn one number you report into a question those words can answer, which is what we mean by a Key Value Indicator.
5. List what's still waiting, in the open. The entries nobody has ruled on yet go under the sentence, visible. They aren't a failure, and they aren't debt. I said it this way to my team in August 2026, and it still stands: "If it stays open, it stays open. It should only come out of the queue if we get confirmation that it did or did not add value." The count of open entries is not a number to bring down.
Entries at Expected go in a list of their own, apart from those. An entry waiting on someone's word holds value somebody saw land. An entry at Expected holds what one person was expected to receive, and it hasn't landed. They aren't the same thing, and neither one is in the month's number. Our rulebook says it in one line: "An expectation is not value until the person who received it says so." If something expected this month didn't land, its entry stays at Expected, with a dated line saying what happened.
6. Make every number open. Anyone reading the month should be able to point at a number and get the entries behind it, and from each entry the person and the moment. If a number can't be traced to a name and a moment, don't produce it.
7. Compare months only to learn something. Our rulebook puts it plainly: "'Beats prior month' says something about where value is flowing — it is not a quota."
8. Decide something, or say you didn't. Ask what you'll do differently because of what this month says, and write the answer beside the month. "Nothing" is an allowed answer. Writing it down is how you notice when the reading has stopped mattering. If the reading taught you something about what the work was for, add it to the CARE record as a dated line, and leave what it said at the start as it was.
9. Refuse the shapes that turn reading into steering. No target. No leaderboard. No score or rate for any one person. No total across the two lanes. Don't just leave them off the page. Build the refusal into whatever produces the number, so no report can bring them back. Chapter 16 shows where my team put that refusal.
How you know it worked
The person the value reached is inside every number. Open any figure in the month and you find their own words, or something they did under their own name.
And the people you read the month to do something because of it. That might be you, your team, or a client. They change a plan, start a conversation, stop something that isn't landing. A month that's read and changes nothing hasn't been read backward. It's just been reported.
Here is what a good reading sounds like. On October 16, 2026, an AI agent on my team prepared a reading of a single day. It opens on a single sentence: "Real value in direction, capability, and learning; follow-through remains open." Underneath it, it says what landed and for whom: "Those outcomes matter without a revenue figure or a time-saved claim." And it says what didn't count: much of the wider work "still awaits use, review, access, or implementation", and its volume "does not establish additional realized value." That's the register. It reads what happened, names what's still open, and claims nothing it can't point to.
Where it goes wrong
The number becomes a target. Somebody sets next month's goal, and within a cycle people are producing confirmations instead of value. This is the Measurement Trap, one of the twelve Complexity Traps, which canon describes as "Optimizing for activity metrics that feel productive while missing outcomes that create value." A count of confirmed moments isn't safe from it just because the word "value" is in the name. The moment it's a goal, it's activity.
A leaderboard, or a count per person. Rank people by how many confirmations their work earned and they'll go and collect confirmations. The Value Era's Chapter 16 says the same about thank-yous.
Burning down the open pile. Treat the waiting entries as a backlog and people will push them closed one way or another. An entry leaves the open pile one way only: somebody whose word counts rules on it.
Dating by the tidy-up. My team has seen this one, and Chapter 11 tells it: most of one June's realized projects came from a three-day bulk close-out. Read backward, a month counted by the day the records were closed shows a spike when nothing happened and a gap when plenty did.
Adding the two lanes. One number that climbs because your own people got more capable, while nobody outside received anything new, looks exactly like a good month for your clients. You can't tell which one happened.
Reading an open month as finished. Take the September row in the table above. A confirmation that arrives next week, about something that happened in September, changes it. What the pass does with a confirmation that arrives after its month has been closed is a decision to make before your first close (Chapter 11).
Read further
- The Value Era, Chapter 5, "Back into money, gamed on arrival", on how a measure meant to replace money gets gamed. And Chapter 15, "In its own kind", on why value is never summed.
- The Value Creation Protocol, Chapter 14, "The Measurement Trap", the handbook for getting out of that trap.
- The AI-Native Shift, Chapter 15, "Counting What Counts", on what an organization working with AI should watch instead of hours saved.
- In this book: Chapter 2, on the CARE record you read the month beside; Chapter 9, on keeping the two lanes apart; Chapter 11, on closing the month; Chapter 13, on taking a KPI across to a question about value; and Chapter 16, on building the refusals into the software.