Part I — Opening the book
Chapter 6
Hear it
At the end of October 2026 I was in a client's monthly meeting, the kind where we go through what was delivered and what comes next. It was recorded. Afterwards one of the AI agents on my team read the transcript, the way it reads our recorded conversations, and listened for one thing: someone on the client's side saying, in their own words, that something had landed for them.
It found two moments. In one, a person described getting a result straight from data they already had, with nothing new built. In the other, someone described an AI tool flagging the records that had been left blank and rating each one, and what that had done for them. Each was written up with the exact sentence and the point in the recording where it was said.
It held five more out, each with its reason written beside it. One was someone saying they understood a lot more now, which is understanding, not receiving something. One was praise that never said what it was about. One described using a tool without saying what it gave them. One said they'd used something for a brand new purpose without naming the purpose. And one was said in the middle of an argument about what to build, and hung on an "if."
That's what hearing looks like when it's done well.
Hearing is half of it. Keeping what you heard, in the book, is the other half, and this chapter is about both.
What this is
Our vocabulary calls this Value Witnessing: "Recording value by pointing to the moment it actually happened — witnessed, timestamped, cited — rather than asserting value without pointing to where it landed." Then it gives the reason in one line: "The citation is the thing a nice-sounding claim cannot fake."
The rule we listen by starts with one sentence: "value is recognized when the person who received it says so, in their own words, at a moment you can point to." What they say is their Value Statement, which Chapter 4 introduced.
I set the shape of this in a ruling on July 19, 2026: "the value CAN be created at a scale and speed no human can keep up with. there must be some kind of dynamic listening in place but not 'always on'." The answer we settled on in August was simple. Listening happens when we're already reading a conversation. Nothing runs all the time.
Our rules need a moment you can point to, so what gets heard comes from recorded conversations and from people's own written words: a post, a message, a note. The listening itself can be done by an AI agent. Chapter 15 is about that; the moves below are the same if you do them yourself.
How to tell where you are
- People tell you what changed for them, and nothing writes it down.
- When you try to remember what a client said, you remember the gist, never the sentence.
- Your notes from a call say "they were happy." Those are your words, about their feelings.
What to do
1. Listen inside the conversations you already have. Don't add a new channel. If you record your calls, read the recordings. If you don't, start with what people already write to you: messages, emails, posts, notes in their own words. Our rules need a moment you can point to, so a sentence nobody recorded or wrote down doesn't meet them.
2. Listen for the receiver saying something landed. Our rule lists the shapes it takes: an outcome achieved ("that fixed it"), a capability they now have ("I can build these myself now"), time or effort saved, a decision unlocked, relief, a thing that now works for them. The test, in the rule's words, "is not 'did value land' — it is 'did the person who got it say so.'"
3. Copy the sentence exactly, and note where it was said. The time in the recording, the date of the message. Don't tidy it. The rule is blunt about why: "A cleaned-up quote is a fabrication, not a tidy quote." If the recording is garbled and you'd have to guess what they meant, hold it out. Guessing is where this goes wrong.
4. Hold the near-misses out, and write down why. These are the ones that will tempt you:
- your own claim that you helped;
- a promise or a plan, because nothing has been received yet;
- politeness ("Great session," "Cool, thank you very much");
- understanding or surprise ("That makes sense," "Interesting");
- your own announcement that something is finished.
When the person themselves tells you what they hope the work will do for them, you may write that down as an expectation, at Expected, in their own words and cited (Chapter 3 has the rules), and it still isn't value heard.
On politeness the rule says: "It costs nothing to say and means nothing on the record." A thank-you on its own is politeness. A thank-you that says what changed is a moment. A near-miss you wrote down with its reason is still useful. Someone can look at it again later without reading the whole conversation.
5. When someone tells you about value somebody else received, write down both. Who said it, and who received it. They're different people, and the row needs both.
6. Count a retold change. A person telling you what changed for them a while ago is a moment, at the time they told you. That's in Chapter 3.
7. One moment, one row. The same thing said twice in one conversation is one row, dated by the first time. Two different things are two rows. Watch the totals, too. Our rule: "A session that produces a dozen entries is almost certainly counting politeness." And the other way: "A long engagement that produces none is a real signal about the engagement…"
If you lead by KPIs today. A long engagement can look fine on every number you track: renewed, on time, on budget. What this chapter gives you to read in their place is whether anyone in it has said, in their own words, that something landed. Chapter 13 shows how to take one of those numbers across.
8. Write it into the book. A heard moment that stays in your notes isn't in the book. Write the row, with the sentence and where it was said, and mark it as waiting on their word.
How you know it worked
The entry carries the receiver's sentence, word for word, at a moment you can point to.
Anyone who opens the recording at that point, or the message on that date, finds the same words in the same order, said by the person the row names. If they find something close but not the same, the row is wrong, however good it sounds.
Where it goes wrong
Politeness or understanding promoted to confirmation. This is the line that's hardest to hold. Our listening rule lists a one-word "Marvelous" as politeness that doesn't count. A note a client writes in a portal you keep for them can use nearly the same word, add a request to close it down, and have a ticket on your side of the work backing up what was accepted. Both readings have a case. Decide where courtesy ends and confirmation starts, and write it down, so the rule you listen by follows it.
The heard moment never reaching the book. A moment can be heard, written up with its exact sentence, and still never be written into the book. A moment that never reaches the book can never be confirmed. That is why step 8 is a step.
The smoothed quote. Fluent writing tidies by default, and a tidied quote reads better than the real one. The script that stages a heard moment for our book says so about itself: it "refuses on a MISSING quote and cannot refuse on a smoothed one." Only going back to the recording catches it.
Read further
- The Value Era, Chapter 16: why a thank-you is where a confirmation starts, and why it isn't the confirmation.
- Back: Chapter 5, "Name it in its own kind".
- Next: Chapter 7, "Show it", on putting a recorded moment in front of the person it's about.
- Later in this book: Chapter 15, on letting AI do the listening without letting it confirm.