The Executive Review Rules of Engagement
Make decision power, meeting purpose, reasoning, and cadence explicit.
- Difficulty
- Advanced
- Time to result
- ~weeks to results
- Steps
- 6
- Confidence
- 99%
Begin every executive review by making the rules of engagement explicit. State where the topic sits on a spectrum from low interest to a direct founder or CEO mandate, then explain the beliefs and assumptions behind that stance. The team should know both how much discretion it has and what evidence could change the executive's mind. Next, label the meeting: an update calls for listening and recognition, while a decision calls for options, trade-offs, and a clear owner. Watch for teams presenting a hard problem merely to push accountability upward; ask directly whether they want the executive to decide for them. Basic hygiene supports the system: a pre-read, the necessary people but not everyone, full attention, and space for each relevant voice. Finally, use a regular cadence so disagreements surface early instead of exploding during a career-defining hero meeting.
Origin
Krishnan drew the method from product reviews with Mark Zuckerberg and Andrew Bosworth at Facebook, plus Gokul Rajaram's warning about rare, high-pressure hero meetings.
Core principles
- 01Teams need to know how strongly the executive intends to steer the outcome.
- 02Explaining the logic gives a team a legitimate route to change the executive's mind.
- 03Updates and decisions require different behavior and should not slide into each other.
- 04Executives should expose attempts to transfer accountability upward.
- 05Regular reviews are safer and more useful than rare hero meetings.
How to run it
- 1
Set the intervention level
Tell the team whether you are merely curious, prefer a direction but can be overruled, or are making a final executive decision. Remove the need to infer authority from tone.
Pro tip Use a consistent spectrum so teams learn how to interpret each level.
Watch out Unstated power makes every comment from a senior leader sound like an order.
- 2
Expose the reasoning
Explain why you hold the position and which assumptions support it. Identify the legs of the logic that evidence could disprove.
Pro tip Tell the team what would have to be true for you to update your view.
Watch out A conclusion without reasoning teaches compliance rather than judgment.
- 3
Name the meeting type
Declare whether the session is an update or a decision. Align the agenda, materials, and expected output to that purpose.
Pro tip If the purpose changes, pause and explicitly reset the meeting.
Watch out An update that unexpectedly becomes a decision catches the team unprepared and damages trust.
- 4
Clarify accountability
Ask for the team's recommendation and decision owner. If members cannot decide and want the executive to do it, make that transfer explicit.
Pro tip Separate a request for advice from a request to assume ownership of the choice.
Watch out Quietly accepting upward delegation teaches teams to outsource every hard call.
- 5
Apply meeting hygiene
Send a pre-read, invite all essential viewpoints without overcrowding, pay full attention, and ensure each relevant person can speak. Record the resulting decision or update.
Pro tip Use the pre-read to reserve meeting time for the actual uncertainty.
Watch out Missing a key stakeholder can invalidate an otherwise clean decision.
- 6
Install a review rhythm
Hold reviews often enough that context and disagreements accumulate gradually. Use the cadence to reduce preparation theater and last-minute surprises.
Pro tip Match the interval to the decision cycle, such as weekly or monthly.
Watch out Rare hero meetings concentrate too much risk in one deck and one conversation.
In the wild
In Facebook reviews, Zuckerberg would place a topic on a spectrum ranging from not caring to issuing a founder-and-CEO directive. He also explained the logic behind his view. When Krishnan pitched Facebook Audience Network, this structure clarified both Zuckerberg's objections to poor mobile ads and the reasoning Krishnan would need to overturn.
→ The team could distinguish a preference from a mandate and respond to explicit assumptions rather than executive guesswork.
Krishnan described high-stakes go-or-no-go reviews where teams spend weeks on a deck, only for the first unexpected executive reaction to derail the session. A regular check-in brings the same context forward in smaller increments and makes review part of the operating rhythm.
→ Frequent reviews reduce surprise, wasted preparation, and the career-threatening pressure concentrated in one event.
Common mistakes
Making every opinion sound mandatory
When intervention strength is implicit, teams over-index on casual executive comments and stop exercising judgment.
Letting updates become decisions
A sudden purpose change produces missing analysis, surprise conflict, and regret that the topic was raised at all.
Accepting hidden upward delegation
Teams may surface a hard choice without a recommendation so the executive unknowingly absorbs accountability.
Is it for you?
Best for
Executives and product leaders reviewing strategies, launches, or trade-offs with teams that need both direction and room to exercise judgment.
Not ideal for
Routine information sharing that can be handled asynchronously without a decision, discussion, or leadership intervention.
From the episode
Hot takes and techno-optimism from tech’s top power couple
Sriram and Aarthi