Broadcast How Leaders Think (Mental-Model Transparency)
Teach your team how key leaders think — not just what they decided — via weekly verbatim-plus-interpretation notes.
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 4
- Confidence
- 90%
A communication practice that removes the 'why do 10 people have to sign off?' bottleneck. Sign-off gauntlets are not process problems but transparency problems: people approve things because nobody shares a working model of how the CEO and strategic leaders think. Gridley sits in rooms with senior leaders, reads the 'note behind the note,' and relays it to her team weekly — verbatim quotes plus her interpretation plus what she'll do differently — so the whole team internalizes the same models and can act autonomously.
Origin
Developed by Hilary Gridley at Whoop, informed by advice from the former Chief Product Officer of Coinbase (founder of Bridge) that a CPO's job is to understand and operationalize the CEO's vision, not to impose their own.
Core principles
- 01Understanding how a leader thinks is far more useful than understanding what they think, because static artifacts (a strategy doc from six months ago) go stale in dynamic environments.
- 02Approval bottlenecks are a downward/outward communication problem, not a process problem.
- 03When you're confident a person understands how you think, you no longer need to review their emails or approve their work.
- 04Listen for the 'note behind the note' — the insight a leader brings that isn't stated explicitly.
- 05Model people's feedback as principles per person (e.g. 'this has to feel like the future').
How to run it
- 1
Get into the rooms and take verbatim notes
Be present in meetings with senior leaders and capture what they actually say, word for word.
Pro tip Use a transcriber or write copious notes so you can quote leaders verbatim rather than paraphrasing.
- 2
Interpret the note behind the note
For each important statement, ask why they said it and what insight or worldview it reveals that might not be obvious on the surface.
- 3
Broadcast weekly to your team
Send a short weekly Slack (or voice-over your notes in a team meeting) with: the most important conversations, what the person said verbatim, your interpretation of why, and what you'll do differently as a result.
Pro tip Keep them short. If you're pressed for time, just read through your week's notes in a team meeting and editorialize live.
- 4
Distill recurring feedback into per-person principles
When you hear the same type of feedback across several meetings, name it as a principle for that leader and translate it into concrete guidance for the team.
Pro tip Frame it precisely to avoid misreads — e.g. 'feels like the future' means high-impact, low-cost magical touches, not maximal scope on everything.
Watch out Vague leader feedback is easily misconstrued (e.g. 'this doesn't feel like the future' misread as 'blow up the scope'); do the interpretation for your team.
In the wild
Whoop's CEO Will obsesses over pixels and gives feedback like 'this doesn't feel like the future.' Many people hear that as 'we can never cut scope.' Gridley reinterprets it: with the product's AI coach and rich personal data, every screen is a chance to show users something that never existed before, via small high-impact, low-cost touches — like explaining VO2 max conversationally using the person's own data. She noticed this feedback recurring across several design reviews, brought it back to her team, and reframed it as a principle: find high-impact/low-cost ways to make the experience feel magical.
→ Her team could satisfy the CEO's bar without over-scoping, because they understood the underlying model rather than reacting to surface feedback.
Common mistakes
Treating sign-off bottlenecks as a process problem
Adding approval steps doesn't fix the real issue — that people lack a shared model of how leaders think — and only makes things slower.
Relying on stale artifacts
Understanding strategy from a document written six months ago leaves the team working from outdated information in a fast-changing environment.
Is it for you?
Best for
Middle managers and product leaders who sit between senior leadership and an execution team and want the team to move fast without constant approvals.
Not ideal for
Highly confidential contexts where you cannot relay what leaders said, or very small teams where everyone is already in every room.
From the transcript
“understanding how your CEO thinks”
“here's what that person said verbatim”
“when I feel confident that people on my team understand how I think like I don't need to read their emails, I don't need to…”
From the episode
How to build a team that can “take a punch”: A playbook for building resilient, high-performing teams
Hilary Gridley (Head of Core Product, Whoop)