Part I — Opening the book
Chapter 3
What earns a row
In June 2026 a client of ours had a go-live call on the calendar. It would have been easy to write the entry ahead of time: the client goes live, the client can now run the new system, value landed.
On the call, the client decided they weren't ready, and moved the target date to August 1.
So there was no value to write down. When our rulebook later worked through real cases, it ruled there was nothing to record yet, and called this one "the textbook trap this book exists to catch." The moment hadn't happened. A row written ahead of that call, saying value had landed, would have recorded a promise as if it were a fact.
That's still the trap. What's changed is that there was one honest thing we could have written, and in November 2026 our book got a place for it. Before the call, the team doing the work could have written down what it expected one named person on the client's side to be able to do at go-live. That's an entry at Expected. When the client moved the date, we'd have added a revision with the new date and their reason, and left the first version readable. Go-live came on July 27, and what landed is on our book as its own entry, naming one person on the client's side as its receiver. If the expectation had named that person, the same entry would have moved to Witnessed, with what landed written from what actually happened, not from what we'd expected. Nobody wrote that expectation. Our rulebook walks the case through as an illustration and says so plainly: "No expectation was ever written for this go-live, and none is to be written now."
This chapter is about the test a moment has to pass before it gets a row, and about the two kinds of row you may open before anyone has said a word. They look alike, and they aren't.
What this is
A Value Entry is one moment where value landed for someone. Our rulebook gives four conditions, and a moment earns a confirmed entry only when all four hold. I ratified them on August 24, 2026: "Ratify 1-4."
- It's one moment. One identifiable moment, "not a state or a span." "[Our client's] engagement is healthy" is a span. A person doing something new on a particular day is a moment.
- It landed for a named receiver who didn't do the work. Usually that's a person. If you can't name who received it, it isn't an entry. (Chapter 4 is about the two hands.)
- You can point to it. There's a real record of the moment: a recording, a message, a document, a meeting. Never made up after the fact.
- It moves something forward. The first entry on a piece of work is the evidence that the work has started reaching real people. Later entries show it reaching them again. If you can't say what it moved, it's activity.
The third condition is the one I'd hold onto hardest. I said it this way on July 7, 2026, in the meeting where we wrote our vocabulary for this practice: "You cannot realize Value that has not been created. Even if you tried to claim Realization, you would need to point to a moment that Creation happened prior to Realization."
There's one more rule, and it changed how our book fills. On the same day I ratified the four conditions, I removed a list of things that could never count, and said this:
"Completion of Build/Roadmap Milestones/Goals that have already been agreed to should be able to be created and awaiting confirmation instead of waiting for additional confirmation to create the record itself. This makes it much easier to continue communicating the value that has been created instead of always focusing on the gap. Which often happens."
So when work someone already agreed to is finished, its row opens that day, marked as waiting. The agreement says who it was for and where the evidence is. The row claims nothing else. It becomes value only when the person it was for says so. Writing a row is open. Confirming one is the gate.
If you lead by KPIs today. You probably count milestones hit or projects delivered, and the count stops at finished. Because the agreement says who the work was for, this chapter gives you something to read in its place: whether that person has said it landed. Chapter 13 shows how to take one such count across.
The second kind of row that opens before anyone has said a word is newer, and it's a different thing. In July 2026 I ruled that an entry passes through four stages, with no fifth. On November 13, 2026, I reversed that and put a stage in front of the other four, Expected: "Someone wrote down what one person is expected to receive, before it happens." My reason: "…if we are going to be creating records prior to witnessing the value, then it needs to be the first stage of the pipeline."
An entry at Expected holds an expectation and nothing realized. It says nothing about what landed, because nothing has. There's no moment to point to yet, and nobody has confirmed anything. The four conditions above are the test for confirming value once it has landed, so an entry at Expected can't meet them yet. Our rulebook puts it in one line: "An expectation is not value until the person who received it says so." No entry at Expected is in the month's number or in any total of value.
Here are our rulebook's rules for it, in plain words.
- Whoever holds the expectation writes it, for work they're doing or have agreed to. Or it's written from the receiver's own words, and cited. Nobody writes down an expectation and puts it on someone who never said it.
- It's written before the moment it's about. One written afterwards is marked as written afterwards, with the date it was written.
- It names one receiver, who isn't the person doing the work. One entry, one receiver. An intention with no single person to receive it belongs in a CARE record, which Chapter 2 teaches.
- It's words, never an amount. Write it in the value's own kind, which Chapter 5 covers.
- The first version stays. If the expectation changes, add the new one with its date and the reason. Never write over the original.
- When the value lands, the same entry moves to Witnessed. What landed is written from the evidence, never copied from the expectation, and dated by the moment it landed. The expectation stays as it was written. The receiver confirms what landed, not what you expected. Value that reaches a different person, or a different thing, gets its own entry.
- When it doesn't land, the entry stays at Expected. It's never deleted. Someone who has looked at what happened adds a dated line saying so. If the receiver says it wasn't met, their words go on that line.
Write one only when someone actually expects a named person to receive something. A piece of agreed work starting isn't that by itself. When my team asked whether every piece of agreed work we track, which we call a Value Mission, should open an entry at Expected the day it starts, my answer was a question: "Why would a Value Mission start there?" We settled on no.
So the two early rows are different, and it matters which one you're writing. A waiting row is for agreed work that's finished: something real exists, the row says who it was for, and it waits on their word. An entry at Expected is for something that hasn't happened yet. Waiting on someone's confirmation is never an expectation, and a waiting row never moves to Expected.
How to tell where you are
- You have plenty of counts and plenty of finished work, and very few moments where you can name the person who got something.
- What you'd call your "value" reads like a status report: "[the] engagement is healthy," "20 episodes aired," "150 registrations."
- When something is scheduled or announced, your records already say it happened.
What to do
1. Test each candidate on the four conditions. If any one fails, it isn't an entry. Our rulebook says it plainly: "A near-miss is still a no."
2. Never write a count. "A count is still never an entry," the rulebook says, and it lists the kind of thing it means: "20 episodes aired," "150 registrations," "23 Orders." A count can sit beside an entry as context. It never becomes one.
We had a real case. A live session aired in June 2026 to a real audience, with more than 150 registrations behind it. The airing earned the row: real people received a session. The 150 stayed context.
3. One moment, one row. The same moment seen from two places is one row. Two different things received in one conversation are two rows. One thing said by two different people is two rows, because each names their own receiver.
4. Count a retold change. A person telling you, in their own words, what changed for them is a moment, even when the change happened before you spoke. The moment is the telling, at a time someone can check. This came up in September 2026, when two of the people I lead were retelling, on air, how they had learned AI. I was asked whether that counted, and I picked "Count them."
5. When agreed work finishes, open its row as waiting. This is one of the two kinds of row that open before anyone has said a word. Name who it was promised to. Point to where the work landed. Mark it as waiting on their word. Don't write what it changed for them, because you don't know yet.
6. When you expect a named person to receive something, write it at Expected, before it happens. A sentence or two, in words, about one person who isn't doing the work, with the date you wrote it. If it changes, add to it. When the value lands, move the same entry to Witnessed and write what landed from the evidence. If nobody expects anything of anyone yet, write nothing.
7. Date it by when it happened. Not by the day you got around to writing it down. Our rulebook found that one month's count of finished projects was mostly a tidy-up; Chapter 11 tells that one. The rule since: "Dated by the real moment, never by the administrative one."
How you know it worked
The person a row names recognizes the moment as theirs.
When they see the row, or describe the moment themselves, they'd say, in effect, yes, that's what happened to me. If they'd have to be told what the row is about, it was never one moment. If they'd say "that was you, not me," it named the wrong person. If the row started at Expected, what they recognize is what landed, not what you expected.
Where it goes wrong
A count posing as an entry. It always looks bigger than a moment, which is why it's tempting. Twenty episodes is not twenty people who received something.
Value written down before it landed. The go-live above. A promise, a plan or a date on the calendar is forward-looking, and nothing has been received yet. You may write down what you expect, at Expected, for one named person. What landed earns its place on the book the day it lands.
Finished work mistaken for value. We made this one at scale. On August 22, 2026, the first piece of software we pointed at the book wrote 91 rows in one pass, all from finished pieces of work. None of them could say what had happened for anyone, so each one carried a placeholder where that should be. One of those 91 rows cited a 2024 test Deliverable named Hawaiian Pizza. Delivery is not realization. Those 91 weren't expectations either. They were finished work, waiting for someone to witness what happened.
Opening a row when work finishes is cheap, and I want it cheap. But a row that says only "this was finished" is a claim about the work. Our vocabulary draws the line in one sentence: "Work in flight is effort, never realized value." Until somebody who received it says otherwise, that's all the row is.
Two of these, the count and the finished work, are the Measurement Trap at the size of one row. The Twelve Complexity Traps define it as "Optimizing for activity metrics that feel productive while missing outcomes that create value." A count of episodes and a finished deliverable are activity. A row is for what a person received.
Read further
- The Value Era, Chapter 14, on the three things the definition of Value refuses: what someone was sold, what was produced for them, and a promise about the future. This chapter keeps the first out of the book. The second may open a row, as waiting, and is never called value until the receiver says so. The third may now be written at Expected, as what one named person is expected to receive, and is never called value at all. What the receiver later confirms is what landed.
- The Value Creation Protocol, Chapter 14, "The Measurement Trap", the handbook for getting out of that trap.
- Back: Chapter 2, "Say what it's for", on the CARE record, and before it Chapter 1, "Start with one view".
- Next: Chapter 4, "Two hands: who received it, who did it".
- Later in this book, Chapter 14, "Correct the book", covers what to do when a row that's already written turns out to be wrong.