Three Interventions That Change
When Your Organization Decides.

What gets lost when the meeting ends

My last essay changed the structure of your review form so what you wrote down about a person would separate objective observations from subjective evaluations. That was a change to the structure and content of the artifact itself: the words a performance record ultimately has to hold. This one changes something else, the timing and the mode of communication a decision is based on. Does it need to be said in real time in the room or can it arrive in writing afterward and still count, for example? Does it have to be a brief Teams chat, a longer email, a Word document, or even a PowerPoint? It is fundamentally about what happens to a read that does not move at the same pace as the meeting itself. It is not a reflection of preparation before the meeting. It is a mechanism to allow processing time for what happened in the meeting itself and the contribution that comes from that active participation, even when it does not show up in the room itself.

Think about the last time you asked a question in a meeting and then closed it after answers were provided. Some people may not have answered and you assumed they did not have anything to contribute or even more likely, that nothing was left at all to consider because others chimed in. Somewhere on your team there may have been a better answer than any of the ones you heard, and it finished forming later that night, and it had no way to get to you. Why? Because your organization does not have a method for decision making that arrives after the meeting.

I named this dimension timing when I laid out my six failure dimensions in my Cognitive Translation Protocol framework. Cognitive systems process and respond at different speeds, and formats that reward immediate response systematically disadvantage deliberate processors. The process interventions take you beyond the meeting and the artifacts to address these additional dimensions including timing.

In the previous essay, we talked about the agenda of a meeting starting with shared context. That is not the only artifact you own in the meeting. You also own the final meeting record with its related decision log. What the three process interventions share is one mechanism, and it has a name: asynchronous communication. Each of the three process interventions builds into a different artifact, and together they address one of the primary failure dimensions for organizational design of cognitive architecture: timing.

Signal persistence changes what happens to a read after the meeting

Signal persistence is the first of my three process interventions. It gives a read one place to go once the meeting has moved on.

Start with the late answer, the one that finished forming the night after your meeting ended. Today one of two things happens to it. It interrupts you as a hallway comment or an unexpected message, or it stays with the person who formed it and you never hear it. Neither is a method. The reads spoken inside the meeting are not doing much better. Someone on your team said, almost in passing, that the renewal forecast was looking soft. The agenda moved, the meeting ended, and your minutes captured the decisions and the action items. That is what minutes are built to capture. Three weeks later the renewal number comes in under the forecast. The room half remembers that somebody said something, and the search starts: old decks, old threads, your own memory of who was sitting where. You have run that search as a leader. It usually fails, because the read was never written down anywhere.

So where should a read go once the meeting has moved on? The change is a watch list: one line per read, holding what was said, who said it, and the date. It lives where your minutes already live. The note taker you already have owns it. Your program teams already run this discipline as the RAID log: risks, assumptions, issues and dependencies, kept current on a regular cadence. The watch list is the same practice, held at the leadership level and pointed at what your people read. My last essay’s outcome field reads a record like this backward at review time, scoring what a person’s calls turned out to be worth. The watch list is where a read gets written on the day it is made, and the outcome field later reads from it. A line gets written in the meeting when a read is spoken. A line gets written after the meeting when a read arrives in writing. That second line is the one your minutes have never had, and it sits in the same record the next meeting reads from.

Building the watch list costs you one line on a template. Running it costs the note taker one line per read, plus one announcement from you: reads that arrive after the meeting go to the watch list, and they will be read there. The expense sits in the first few cycles, while your team tests whether the watch list is real. It drops every time something written there shows up in a decision.

Then the search through old decks stops. The read is written where everyone knows to look, as it was said, not as the room remembers it three weeks later. A read is present in the next meeting even when its author is not, and it stays with the decision it belongs to until that decision closes. The person who flagged the forecast no longer has to re-raise it every time the subject comes back. Because a read sits in the same record as the decision it feeds, what the room decided and what each person understood it to have decided no longer drift apart between meetings: the next meeting reopens the record that holds the decision and the reads beneath it. And the late answer reaches you through the watch list instead of as a hallway interruption.

Pacing and timing controls change when a question is allowed to close

The second process intervention is pacing and timing controls. They set when a question is allowed to close, and they make that a choice instead of a side effect of the calendar.

The watch list gave the late answer somewhere to go. By the time an answer gets written there, though, the question it belongs to has usually already closed. The answer sits in the record while the decision moves on without it. Go back to the last question you closed because the meeting was ending. Nothing about that question needed an answer inside the hour. Look at the agenda of your next leadership meeting. Each question on it opens and closes inside the same hour, and nobody chose that. An agenda records topics and times, never a close date. So the hour became the deadline, and every answer that needs longer than the hour never gets counted.

So what does a timing control look like on an actual agenda? It is a decision window. A question opens when it is stated and closes at a stated time, and the two are written down as separate lines. Opens Tuesday in the leadership meeting, closes Thursday at noon. An answer that arrives inside the window goes in writing to the named owner of the question. The window fixes who the answer goes to and when it has to arrive. This is also where the mode of the answer gets decided. The person answering picks the form the answer actually needs: a few lines in a chat, an email, a one-page document when the reasoning needs a page, a short deck when the answer needs one. All of those channels already run in your organization today. The window is what gives a written answer arriving through them the same weight as one said aloud in the room. Some questions genuinely have to close in the room, and those keep closing in the room. The window is for the questions that only close inside the hour because the agenda ends there.

The cost is real and you should count it honestly. Decisions that used to close on Tuesday now close on Thursday, by design. The expense is felt hardest in the first few windowed decisions, while your team learns that a Thursday close is designed, not slipped. What you get for those two days is the answer that could not have existed on Tuesday. The run cost, once your agenda template carries the open line and the close line, is the two lines themselves.

The answer that needed a night then makes it into the decision it was formed for. The person who needed until morning now has a written Wednesday answer on the record, where before the record showed nothing from them. Silence reads differently too. Until the window closes, an unanswered question is still an open question, not a sign that nobody had anything to add. And the colleague whose capacity the meeting itself consumes gets a route into the decision that does not run through the room at all.

Decision traceability changes what a decision has to leave behind

Decision traceability is the third process intervention, and it sets what a decision has to leave behind before it counts as closed.

Look at what the first two interventions just did to the shape of your decisions. Reads now arrive across days and go onto the watch list. Answers come in as a chat message on Wednesday and a one-page document on Thursday. The decision no longer happens in one room in one hour with everyone watching. That is what you wanted, and it raises a question you should take seriously: how does anyone trust a decision they did not watch being made? Now go back to a decision that is being questioned today: the February build-versus-buy call, the headcount call, the reorganization. Try to reconstruct why your organization decided what it decided. The deck is archived, the thread is four months long, and the minutes say approved. Your organization keeps a record of what it decided and no record of what it knew when it decided. That was already true when every decision closed inside a room. Spread a decision across three days and several channels, and the reconstruction gets harder still.

So what does a decision have to leave behind before it counts as closed? The change is three lines, written at the moment the decision closes. The reads the decision used, by name and date, which the watch list hands you. The interpretation the room settled on. And the decision itself, with its owner and the date it closed.

Building this is one template edit: the three lines go onto the decision log if you keep one, and onto the minutes if you do not. The run cost is that someone writes three lines while the room wants to leave. The discipline is a rule: the decision is not closed until the lines exist. The expense sits in the first cycles, while the room tests whether you will hold the rule. That rule is the whole intervention. It is the kind of rule a leader can state once and a note taker can hold.

A decision can then be reconstructed, because the chain from what was known to what was concluded to what was done is on paper. A decision made across three days no longer runs on trust in whoever closed it: anyone can read the same chain. And when a failure repeats, you can see which step produced it: a read that never arrived, an interpretation that did not follow from the reads, or a decision that ignored both. When a read was available and went unused, the record shows that too. That is what next quarter’s review can actually learn from.

The Operating Brief: change when it closes

Why this works, and where it comes from

You have already been taught the thinking these three process interventions are built on. Think about how much of your leadership reading has been about fast thinking and slow thinking. Daniel Kahneman’s work may be on more executive shelves than any other behavioral science, and it earned the spot. The distinction between the fast, automatic answer and the slow, deliberate one is real and measurable, and knowing it makes you a better decision maker.

Look at what your organization did with that teaching. It taught leaders to slow their own thinking, in courses, in workshops, in the books themselves. The training worked on the person, one more time, and the meeting format kept its one speed. So slow thinking became a skill some of your leaders have, on the days they have the attention for it. The agenda that every question actually runs through was never given a close date of its own. The tacit assumption underneath, in Schein’s terms, is that a decision made at the end of the hour and a decision made well are the same decision. No one in your organization believes that when it is said out loud.

Your organization also already trusts asynchronous work in almost every place except the meeting where its decisions close. It runs on written updates and shared documents. Distributed teams settled long ago that a written decision reached across a day can be as sound as one reached in a single meeting. The tools went asynchronous and the meeting did not. These three interventions bring the same practice to the artifacts the decision actually runs through: the agenda, the meeting record, and the decision log.

The age of AI gives these three artifacts one more job. Your organization is already buying tools that summarize, answer questions, and write briefs. Those tools return only what got written down. A decision made in a room and closed in an hour gives them nothing to work with: the reasoning was spoken, and speech leaves no record for a tool to read. The watch list, the window answers, and the three-line records are exactly the kind of record those tools read well. More of what your organization knows gets captured, and it stays queryable. When a question comes back, the answer can be pulled up and summarized. And explaining a decision a quarter later, the work that used to take a post-mortem, starts with a question you can ask, because the records are thorough enough to hold the answer.

The window makes slow thinking a property of the agenda rather than a skill each leader has to remember to use. The three-line record is Kahneman’s decision journal kept by the organization: the decision, written at the moment of deciding, beside what was known. That is what lets you audit it a quarter later. And the watch list feeds that journal honestly, because the reads it preserves were written down when they were said, not reconstructed after the result came in. That is the pattern of this whole arc: the discipline your training already taught, moved out of the head that has to hold it and into the artifact the whole room is already completing.