When Everyone Knows That Everyone Knows
What changes is not what people know but what they know others know.
Essence (why this landed for me)
A dense, layered book that will take a second pass to fully absorb. What drew me in was the exhaustiveness: Pinker does not mention a concept without mapping every subtype, every edge case, every category. That thoroughness gave me a new lens for thinking about coordination, why teams align or stall, why markets move, why public signals carry so much more weight than private ones. The idea that common knowledge is the invisible architecture behind money, authority, and social norms is one I want to sit with longer.
Insights (mapped to mental models)
Takeaways grouped by mental models, with a short action you can use now.
Common knowledge is what people know others know.
Coordination requires visible signals, not just information.
Eye contact is instant common knowledge.
Indirect speech protects relationships from common knowledge.
Regimes fall when private doubt becomes public.
We know they are lying and they know we know.
Bubbles survive private doubt but pop on public doubt.
Hoarding is coordination failure, not irrationality.
Super Bowl ads sell common knowledge, not just reach.
Rituals manufacture shared awareness, not just sentiment.
Exhaustive categories make the invisible visible.
Benign hypocrisy keeps the social fabric intact.
Cancel culture is a common knowledge weapon.
Natural selection favors not dying over winning.
Absorption Notes (short essay)
The practice I want is noticing the gap between what people know and what they know others know. Before a conversation stalls or a group freezes, ask: is the information missing, or is it just not public yet? Sometimes saying the obvious thing out loud is the move that unsticks everything. The emperor's clothes logic applies everywhere: families, friendships, decisions with money, not just meetings. Keep Pinker's exhaustive style close. When something feels confusing, list every type before reacting. Is this a coordination problem, a face-saving ritual, strategic ambiguity, or pluralistic ignorance? Naming the category changes how I respond. The book is dense and deserves a second pass. Return to it when a real situation puzzles me. Simple moves, steady rhythm.
Reflection Prompts (product × design × engineering)
Questions to apply the ideas across projects. Pick one or two and use them today.
Public signal
What does my team know privately that needs to be said out loud
Common KnowledgeSay it in the open.
Coordination check
Where are people waiting for each other because nobody made the first public move
Focal PointsCreate the signal.
Strategic ambiguity
Am I being indirect to protect a relationship or to avoid accountability
Strategic AmbiguityName the real reason.
Open secret
What does everyone know but nobody will say
Pluralistic IgnoranceBe the child.
Ritual design
What shared ritual creates alignment on my team
Commitment DevicesMake it regular.
Cascade risk
Where could one public signal trigger a cascade of changed behavior
Information CascadesTrace the chain.
Category check
Have I listed all the types before choosing one
MECEBe exhaustive.
Hypocrisy audit
Where is benign hypocrisy actually helping and where is it hiding a real problem
Social ContractSeparate the two.
Preference truth
Where am I performing agreement instead of voicing doubt
Preference FalsificationSpeak the doubt.
Second read
Which idea from this book do I not yet understand well enough to explain
Feynman TechniqueReturn to it.