Week 12: Week 12 lecture: Redesigning the decision

Bringing the semester's separate threads — invite lists, agendas, timing, minutes, leverage — together into criteria for a process worth trusting.

10 May 2027

What the semester actually built up#

Eleven weeks have looked at one long-running fictional case from a series of separate angles: who was invited and on what terms (Week 2), how an agenda argues before anyone speaks (Week 3), what forms before the formal meeting does (Week 4), what timing does to a document regardless of its content (Week 5), what a minuted silence does and doesn’t prove (Week 6), how a room sorts contributions by whether they help or complicate (Week 7), and what a dissent needs to survive being written down (Week 8). None of these were separate flaws to fix one at a time. They are seven views of the same underlying object: a decision process, and the specific points in it where accountability can quietly leak out.

Redesigning a process means naming that object directly rather than patching the view you happened to look through last. A redesign that fixes the invite list but leaves the agenda’s naming and timing untouched has not actually made the process more accountable — it has moved the leak somewhere else in the same pipe.

Three questions any redesign has to answer#

• Who is invited, and on what right? Not everyone affected needs a vote — Week 2 already showed that “advise” and “vote” can both be legitimate, depending on the seat. A redesign has to state the right explicitly, rather than leaving it implied by who happens to show up.
• What record survives, and who controls what goes in it? Weeks 6 through 8 showed how much a decision’s memory depends on who writes it down and what they choose to compress. A redesign names who takes the record, what it must include (not just outcomes — unanswered questions, dissent, and who raised it), and who can contest it afterwards.
• What informal channel still exists, and is it visible? Week 4’s “meeting before the meeting” is not automatically a problem — informal coordination before a formal meeting is often exactly how disagreement gets worked through in a room too small or too public to do it live. The redesign question is not whether an informal channel exists, but whether its existence and its limits are visible to the people it affects, rather than something they have to infer from a pattern of documents the way you have spent this semester learning to.

Bringing your own Alignment Lab audit into it#

Your Decision System Redesign, due two weeks from today, is explicitly asked to use evidence from your own Alignment Lab decision autopsy — not just the pilot case. You now have two data sets: eleven weeks of someone else’s decision, read from the outside, and one decision you were inside of yourself, with a role card, real leverage, and a record you helped write. The strongest redesigns in past years have used the second data set to catch something the first one alone could not show — what a process actually feels like to operate inside of, not just to read afterwards.

A little further reading#

Garvin and Roberto draw their own version of this week’s opening claim — that decisions are made by a process, not a moment — around a contrast between an “advocacy” model (participants argue for a preferred position from the start) and an “inquiry” model (participants test multiple views before anyone commits to one). Read it for one purpose: decide which model the 13 March Working Group’s phase-order discussion actually resembles, using only what you’ve read across the semester, and check whether your own Alignment Lab group’s meeting resembled the same model or its opposite. That comparison, not the article’s own case studies, is what your redesign should be built from.

After this session#

There is no Week 13. The Decision System Redesign is due two weeks from today, giving you time away from the weekly schedule to write it properly.