a builder's codex
codex · operators · Claire Hughes Johnson · ins_make-the-implicit-explicit

In every meeting, name the why, the decider, the criterion, and the informed

By Claire Hughes Johnson · Former COO, Stripe; author, Scaling People · 2026-04-28 · podcast · Scaling people, the company operating system, force for positive momentum

Tier B · TL;DR
In every meeting, name the why, the decider, the criterion, and the informed

Claim

At the top of every meeting, make four implicit things explicit: why we are meeting, who is deciding, what the decision criterion is, and who needs to be informed of the outcome. Default to writing these down before the meeting starts.

Mechanism

Most meetings stall because participants have different unstated models of what the meeting is for. One person believes it is a decision; another believes it is a discussion; a third believes they are the decider. Naming the four elements collapses the ambiguity and saves the next 50 minutes. Over time, the practice teaches the org which kinds of meetings to call and which to replace with async.

Conditions

Holds when:

Fails when:

Evidence

"Why are we meeting? Who's deciding? What's the criterion? Who's informed?"

Claire's meeting hygiene rule from Scaling People and the practice she carried from Google self-driving (Waymo) into Stripe.

— Claire Hughes Johnson on Lenny's Podcast, 2026-04-28

Signals

Counter-evidence

For high-trust small teams, the formality can feel performative. For exploratory or creative sessions, naming the decider too early shuts down divergent thinking. The rule is conditional on the meeting type.

Cross-references

Open the interactive view → View original source → Markdown source →