Leadership and AI6 min read
Designing Human-Only Rituals
If every conversation can be summarized, the ones worth protecting need a design. Three rituals, four rules, and the signs of theater.
By Jerald Lee
In brief
Recording is now cheap and default. The conversations that build trust and make decisions need to be deliberately protected from it.
If a bot can summarize a conversation, the conversation needs a reason to happen in a room. The reason is not sentiment. It is the part that does not survive transcription: the hesitation before someone disagrees, the decision made by looking at each other, the thing said that nobody would write down. Recording is now cheap and default. Very few organizations have decided which conversations are worth protecting from it. Three earn the room: decisions that change something, the conversation after a failure, and the first month of a new team. Everything else can be assisted.
# Designing Human-Only Rituals
The calendar is fully recorded now. Every meeting has a summary, every summary has actions, every action has an owner.
And something has gone missing that is hard to name. Not information. The information is better than it has ever been. Something about the quality of the conversations themselves, which have become slightly more careful, slightly more presentable, slightly less true.
That is not a coincidence, and it is not nostalgia. It is what happens when a conversation acquires a permanent audience.
What a summary loses
A transcript records what was said. A summary records what someone decided mattered. Both are useful. Neither is the meeting.
What is lost is the room. Who spoke first. Who did not speak. Where the energy changed. Which sentence made two people look at each other. Whether the decision felt like a decision at the time.
These are not soft details. They are how a group knows whether it has actually agreed, and they are the first thing a summary removes.
There is a second loss that matters more, and it is the one leaders underestimate.
When people know a conversation will be summarized, they speak for the summary. The record becomes an audience, and the room becomes a performance. Not consciously, and not dishonestly. People simply produce the version of themselves that reads well in a document, and the difficult half of the conversation moves somewhere else, usually to a corridor.
That is not a failure of the tool. It is what happens when any conversation acquires a permanent audience. The tool just made the audience free.
Three rituals worth protecting
Not every meeting needs to be human-only. Most should be assisted. These three earn the room.
The decision that changes something. When a group is choosing between real options with real consequences, the value is in the argument, not the record. Put the bots away, state the options, and do not leave until someone has said which one and why.
The conversation after a failure. A project that did not work, a hire that did not land, a quarter that missed. The useful part is the hesitation before someone says the true thing. A summary makes that hesitation expensive, because it might be recorded.
The start of a new team. The first month of a group that has to trust each other. Trust is built in the unrecorded parts: the aside, the joke, the moment someone admits they do not know. A team that only meets on the record will take much longer to become one.
Why the obvious objection is reasonable
Three objections come up, and each one has a fair point inside it.
"This is nostalgia for how work used to be." It would be if the argument were about technology. It is not. It is about audience. A conversation with no audience behaves differently from one with an audience, and that was true before anyone built a transcription tool.
"We are distributed. We cannot have a room." Then make the call as close to a room as the format allows: cameras on, no side channels, everyone speaking, nobody multitasking. The constraint is attention, not geography.
"People will think we are hiding something." They might, which is why the rule has to be stated out loud and the output has to be shared. A protected conversation that produces nothing shareable becomes a rumor.
The Human-Only Agenda
Four elements. Miss one and the ritual either fails or becomes theater.
A room. Not a call if it can be helped, and not a hybrid where half the group is on a screen. The point is the whole group in the same attention. If the room is impossible, use the closest format available and say why.
A sequence. Open with the question, not the update. Updates fill the time and postpone the decision. The order is the design.
A rule. Say the rule out loud at the start. No recording, no summary, no minutes. What is said here stays in the room unless someone agrees to write it down. A rule that is not stated is not a rule.
A close. Two minutes at the end: what did we decide, who owns it, what do we tell people who were not here. That last question matters. A human-only ritual that produces nothing shareable becomes a rumor.
How to keep it from becoming theater
The failure mode is a ritual that feels meaningful and changes nothing.
Three signs.
The same people speak. If the room has a dominant voice, the ritual is a monologue with better lighting.
The decision is made somewhere else, before or after. If the real conversation happens in a smaller group, the ritual is a ratification.
The ritual is described as important and cancelled when the quarter gets busy. What gets cancelled first is what the leader actually believes is optional, whatever the language around it.
The fix is to tie each ritual to an output. A decision, a commitment, a piece of truth that changes a plan. If the ritual produces none of those, it is a meeting with a better name.
What to automate instead
Almost everything else.
Status updates. Project summaries. Action tracking. Notes for the meetings that are genuinely about coordination. The administrative layer of organizational life should be as cheap as it can be, so the expensive conversations have room.
The mistake is treating all meetings the same. Some are for information. Some are for decisions. Some are for the thing that makes a team able to make decisions. Only the last two need a room, and only the last one needs protecting.
A useful test for the calendar. For each recurring meeting, ask what would be lost if it were summarized and nobody attended the summary. If the answer is nothing, automate it. If the answer is a decision, a relationship, or a truth that would not otherwise be said, it belongs on the protected list.
What this is really about
Here is the part that does not get said often enough about efficiency.
An organization is not a set of outputs. It is a set of people who have decided, more or less explicitly, to trust each other with something.
Trust is not produced by better records. It is produced by being in a room when something is hard, and watching what the other person does. That experience cannot be summarized, because the summary is the part that was never the point.
Which means the protected conversations are not a luxury to be scheduled when the quarter is calm. They are the mechanism by which the rest of the work becomes possible.
The experiment
Pick one recurring meeting and remove it from the recording.
State the rule at the start. Open with the question rather than the update. Close with the four lines.
One meeting. One rule. One close. Then ask the room, a week later, whether the conversation was different. They will tell you, and the answer will be more useful than any policy on meeting hygiene.
Where this connects
[Ownership Is a System](/ownership-system) is about the conditions that make people act without being asked. Trust is one of them, and trust is built in rooms.
[The Meeting of the Bots](/meeting-of-the-bots) is the argument for the decision minute. This is the argument for the meetings that should not have a minute at all.
If your operating rhythm has more meetings than decisions, the [our engagements page](/engagements) is where we start.
Frequently asked questions
Does a human-only meeting mean no notes at all?
It means no recording and no circulated summary. One person can still capture the decision and the owner on a single page, agreed in the room. The point is to protect the conversation, not to leave the meeting with nothing.
How many meetings should be human-only?
Few. Three recurring rituals is usually enough: decisions that change something, the conversation after a failure, and the first month of a new team. Everything else can be assisted.
What if the team is remote by default?
Protect the format rather than the room. Cameras on, one conversation at a time, no side channels, and the same four elements. A distributed team can still have a conversation with no audience, as long as nobody is recording it. ## A five-minute reflection Which conversation in your calendar would change if nobody were allowed to read a summary of it? ---

Jerald Lee
Commercial Systems Advisor
Jerald Lee is a Hong Kong-based Commercial Systems Advisor, founder of Curiosity At Work and Operating Partner of The Growth Coach Hong Kong. He spent 13 years at Google APAC and helps founder-led companies build predictable revenue systems.