Week 4 Session: Week 4: The Meeting Before the Meeting

Where a decision may already be forming before the room convenes, and how you would tell that from the record itself, rather than from suspicion alone.

15 March 2027

Before the session#

Come with your two Week 3 agendas (the “settled” and “open” versions you wrote). Reread the “settled” one and list every word or structural choice that, on its own, would not prove pre-decision — but that, stacked together, starts to.

The case documents for this week#

Two new documents continue the Engagement Signal Pilot’s record, one week after the Steering Committee meeting Week 3 ended on.

Calendar invite, sent 10 March, Tomas Herrera to Priya Nandakumar and ClarityPulse’s delivery team only:

Rollout Working Session (small group) When: 11 March, 30 minutes Attendees: Priya Nandakumar, Tomas Herrera, ClarityPulse delivery team Agenda: “Align on phased rollout sequence ahead of Saturday’s LSS Working Group, so we’re not designing it live in a 40-person meeting.”

Agenda, LSS Rollout Working Group, 13 March — the meeting the invite above refers to as “Saturday”:

LSS Rollout Working Group — Item 2: Phased rollout sequence Purpose: confirm the sequence for rolling ClarityPulse out across LSS teams. Time allocated: 5 minutes. Attached: proposed sequence (3 phases, Circulation → Reference → Technical Services).

In the session#

This week turns Week 3’s single-document reading into a multi-document one. A single confirming agenda item proves very little by itself; a pattern across a calendar invite sent before a meeting and an agenda item with no real discussion time allocated is a different kind of evidence. Working in pairs, list every signal in the two documents above that would not prove pre-decision on its own, then discuss as a class which combinations of those signals raise the burden of proof furthest — and what a document that would lower it again might look like. The session is explicit throughout that a consistent pattern across documents is still not the same thing as a confession — it raises the burden the “genuinely open” reading has to meet, it does not retire that reading outright.

The session also names the honest counter-case directly: a small delivery-level group is allowed to resolve a technical detail before it reaches the full, 40-person Working Group, and a working group that confirms a well-prepared recommendation is not automatically evidence of a meeting-before-the-meeting. The skill is telling apart legitimate preparation from a decision relocated out of the record. The Week 4 lecture works through this same pair of documents in more depth if you want the fuller argument before the session.

After the session#

Keep your running list of “stacking” signals — Week 6 asks you to apply the strongest version of this reading against a real document set of your choosing, and the Decision Autopsy assessment is due at the start of that week, before the Week 6 session runs.