Week 6: Week 6 lecture: What minutes leave out

Silence in a meeting record is not the absence of a position — it can be one, or it can just be how minutes compress a meeting; read through the minutes of the 13 March working group and learn to tell the difference.

29 March 2027

A record of what was said is also a record of what wasn’t#

Minutes are written as if they are a transparent window onto a meeting — whoever wasn’t in the room reads them to find out what happened. They are never that. Every set of minutes is a compression: someone decided what counted as “discussion” worth recording, what counted as noise, and what counted as nothing at all. This week’s document is the minutes of the same 13 March LSS Rollout Working Group meeting that Week 4 introduced through a calendar invite and an agenda. Read them, and a gap becomes visible that neither of those two documents could show on its own.

The story continues: the minutes of the 13 March meeting#

This week’s document is the minutes of the same 13 March LSS Rollout Working Group meeting that Week 4 introduced through a calendar invite and an agenda. The full excerpt is reproduced on the session page; read it there before continuing, since the reading below assumes you have.

What the minutes do, and don’t, record#

Sanjay Okoro’s question is in the minutes — that much the record does show. What the record does not show is any answer to it. “The sequence was confirmed as presented” sits directly after the question with nothing between them: no response, no discussion, no vote noted, no dissent recorded either for or against. Read narrowly, that is simply how minutes work — they record outcomes, not every exchange. Read against Week 4’s agenda, which allocated five minutes to this item and described the sequence as something to “confirm” rather than “discuss,” the silence starts to look like the agenda’s plan playing out exactly as scheduled: a question was asked, no space had been allocated for it to be answered, and the item closed on time.

This is the week’s central distinction. A minuted silence is not proof that a concern was ignored — the minute-taker may simply not have recorded a verbal response that did happen, which is a failure of note-taking, not of process. It is also not proof that nothing happened — a chair moving straight from a question to a confirmation, in a room, in real time, is a choice, whether or not anyone in the room experienced it as one. The minutes alone cannot tell you which. What they can tell you is that the gap exists, and that whoever wrote the agenda controlled how much room there was for it to be filled.

Why this belongs next to the Decision Autopsy#

The Decision Autopsy asks you to make exactly this kind of call on a real decision: to look at what a record does and doesn’t show, name the gap honestly, and argue a specific, evidenced conclusion rather than retreating into “the record is ambiguous” as a way of avoiding the work. A rigorously argued indeterminate finding is one of the assessment’s three acceptable conclusions — alongside “the record supports a specific distortion” and “the record shows no material distortion” — not a weaker fallback, provided it does real work: it names the specific missing evidence that would settle the question if it existed, states a specific, plausible alternative explanation, and says what would change the judgment if that missing evidence turned up. Ruling an alternative explanation out is not what makes a finding indeterminate — if you can rule one out, you have resolved the question in favour of whatever remains, which is a determinate conclusion, not an indeterminate one. What makes a finding genuinely indeterminate is being unable to rule a plausible alternative out with what the record actually contains. What doesn’t meet the mark is the undeveloped version of the same word: “it’s ambiguous, so I can’t say,” offered with no named missing evidence, no specific alternative, and no account of what would resolve it.

A little further reading#

Morrison and Milliken’s paper works at a different scale than one meeting’s minutes — it asks why employees across an organisation systematically withhold ideas, concerns and objections from people who could act on them, a climate effect built up over time, not a single meeting’s recording choice. Read it for one purpose: their distinction between a “structural” barrier to voice (no channel or moment built into a process for a concern to be raised) and a “motivational” one (employees judging that raising it would be pointless or risky). The gap this week’s minutes reveal — five minutes allocated, the item described as confirming rather than discussing — is a structural barrier in their sense; nothing in the record here tells you whether a motivational one was also at work, and blurring the two into one larger claim is exactly what the evidence doesn’t support.

Before Week 7#

Nothing new to bring. Week 7 goes back to this same meeting a third time — not the agenda that shaped it, not the minutes that summarised it, but a transcript of what was actually said in the room.