A note before we start. The firm in this case study is an illustrative composite. I assembled it from the practices in this series so you can see every layer working in one place. It is not a single client, and its details are examples, not reported results.
It is a Tuesday in March, a little after six in the evening. At a forty-five-person accounting firm, most of the lights are off.
One system is still working. The firm calls it the document chaser. It is an AI assistant that emails clients when a tax form is missing. Tonight it has drafted a third reminder to a longtime client.
The draft is polite. It is also wrong. Three weeks ago, a preparer added a note to that file. The client's husband died in February.
The reminder never goes out. It sits in a held queue with a flag on it. At 6:20 the evening lead reads it, deletes it, and writes two lines in a log. On Thursday, someone calls the client instead.
Nothing happened. That is the story.
You can't judge a system by its parts. Follow one decision through it.
Why Look Inside One Firm
Last week I gave you the Alignment Operating System. It has four layers: Reason, Rules, Readings, and Rhythm. A framework on a page is one thing. A Tuesday evening is another.
So this week we follow that one held email through all four layers. I call this a One-Decision Trace. You pick one ordinary thing your AI did, and you ask what carried it at each layer. Where the trace holds, you have a system. Where it breaks, you have found your next fix.
Here is the firm. Forty-five people. Two partners. Three AI systems: an intake assistant that answers new-client questions, the document chaser, and a drafting assistant that sorts bookkeeping entries for a person to review. There is no AI team and no ethics officer. There is an office manager who owns more than her title says.
Layer One: The Reason
Start at the bottom. Why did that email deserve to be stopped?
Because of a sentence. Months earlier, the partners ran a Values Clarification Session with the whole staff. After two hours and many crossed-out lines, they had this:
No client is ever surprised by us, and no client is ever handled like a file.
It hangs by the copier. It is not elegant. The staff wrote it, and so they use it.
A chase email to a grieving client breaks the second half of that sentence. Everyone in the building would say so. That is the job of the Reason layer. It makes the right answer obvious.
Layer Two: The Rules
An obvious answer is not enough at six in the evening. Someone has to have written it down.
The firm had. The document chaser has a one-page charter. It says what the assistant is for, what it may never do, and who owns it. One of its bright lines reads:
No automated message goes to a client whose file carries a life-event note until a person has read it.
That line did not come from a workshop. It came from a near miss the year before, with a client who was in the hospital. The partners added it that same week.
A rule also needs a holder. During the day, that is the client's preparer. After five, it is the evening lead, by name, on a rotation taped inside the charter. She holds the Veto Power. She does not need permission to delete the draft.
Layer Three: The Readings
Here is where most firms would stop. The email was caught. Go home.
This firm takes a reading. The evening lead writes two lines in the Close Call Log: what was held, and why. It takes her under a minute.
That entry feeds two other pieces. The count of held messages is one of the firm's Friday wires. And the log is a source for the people line on its one-page Integrity Scorecard.
Their first Scorecard, by the way, had nineteen lines. Nobody read it. The one they use now has six.
Layer Four: The Rhythm
A reading that nobody hears is only paper. So follow the entry forward.
On Friday, the office manager runs her checks. It takes ten minutes. She sees the held message, and one more like it. On Monday she reads both aloud at the staff huddle, in under a minute. That is the rhythm at work.
Two in one week is a pattern. A preparer asks the useful question. Why did the chaser draft those emails at all?
By Wednesday the charter has a new line. The chaser now skips any file with a life-event note. It puts a task on the preparer's list instead: call, don't email.
One held email on a Tuesday became a better rule by the next Wednesday. No meeting was called. No consultant was hired.
What the Trace Shows
Look at what carried that one decision.
- Reason: a sentence the staff wrote, which made the right answer obvious.
- Rules: a bright line in a charter, with a named holder after five o'clock.
- Readings: a two-line log entry that fed a wire and a Scorecard.
- Rhythm: a Friday check and a Monday read-aloud that changed the charter.
Each layer handed the decision to the next. That handoff is what makes it a system.
Now the honest part. The firm did not build this in a month. It took most of a year, and it went in this order. The promise sentence came first. Then one charter, for one assistant. Then the log. Then the Friday checks. The Scorecard came last. They built one layer at a time and let each one earn the next.
They also got things wrong. For the first tax season, the after-hours holder was "the evening team." Nobody on the evening team knew that meant them. Last week I called that an Ownerless Rule. They found it by asking who would have stopped a message at six. No one could say. So they wrote down a name.
One more honest thing. A composite cannot prove a result, and I won't hand you a made-up percentage. What a case like this can show is the wiring. Four small layers passed one decision along, and the owner was not in the room.
Run a One-Decision Trace This Week
You need twenty minutes and one real example.
- Pick one thing your AI did last week. A quote, a reply, a reminder, a summary. Ordinary is better than dramatic.
- Ask the Reason question. Which promise did this serve, or put at risk? Say it in one sentence.
- Ask the Rules question. Which written line covered it? Who could have stopped it at that hour? One name.
- Ask the Readings question. Where was it recorded? What number moved?
- Ask the Rhythm question. Who heard about it, and when?
- Mark the first blank. The first question you cannot answer is your next piece of work. Fix that one, and stop there.
If every answer is blank, don't be discouraged. Start where this firm started. Write the sentence.
Earlier in This Series
- The Alignment Operating System: A Year in Review: the four layers this case study walks through.
- The Values Clarification Session: where a promise sentence comes from.
- Building Your First Values-Driven AI Agent: the one-page charter.
- Bright Lines and The Veto Power: the rule, and the person who holds it.
- The Close Call Log: the two-line entry.
- Leading Indicators and Building Your Integrity Scorecard: the wires and the one-page reading.
- The Rhythm of Alignment: the Friday check and the read-aloud.
Where This Leads
Last week you saw the year as one system. This week you saw one system from the inside.
Next week we look ahead. The tools are changing fast. The question is which parts of this will still hold.
For now, pick one decision and follow it.
Make today your masterpiece. And let your promise show in the work.