The Dinosaur Brain Product Review
Executives hold three facts. Bring a recommendation, not a catalogue — and leave with principles, not answers.
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 6
- Confidence
- 95%
Vora tells her teams to assume every executive in the room has a tiny brontosaurus brain that can only hold about three facts at once. Breadth buys pattern-matching and context; it costs depth. The presenter's job is therefore to do the depth work and arrive with a recommendation, and the review's job is to produce reusable decision principles rather than a single verdict.
Origin
Vora's own framing, developed across product reviews at Facebook, Instagram and WhatsApp. She credits Boz with having written about the taxonomy of different product-review types (philosophy vs strategic shift vs day-to-day decision), which she says she most agrees with.
Core principles
- 01My manager owns context. I own the recommendation.
- 02The executive's contribution is breadth — pattern matching, company context, industry context. It is never depth on your material.
- 03Reviews used to extract decisions add no capacity to the org; reviews used to calibrate principles do.
- 04The minimum information needed to make a clean recommendation is the correct amount, because it forces you to be opinionated.
- 05Fewer people means a more informal conversation, which means a faster one.
How to run it
- 1
Assume the dinosaur brain
Design the review for an audience that can hold roughly three facts and will never go as deep on the material as you have. Stop optimising for completeness.
Pro tip Include yourself in that bucket when you're the reviewer — it makes the framing honest rather than insulting, and it is true.
Watch out The instinct is the opposite: dump everything so the smart people in the room can reach the conclusion themselves. That is an abdication, and they cannot do it.
- 2
Do the work and form the recommendation
Go deep on the data, form a view, and stand behind it with conviction. Your depth plus their breadth is the complementarity that makes the meeting worth holding.
Pro tip Build the conviction for yourself first — do whatever work you need to genuinely believe the call, because the room will test it.
- 3
Write it all, then cut almost all of it
Draft whatever you need to think clearly, then strip the doc to the minimum information required to support one clean recommendation.
Pro tip Format that survives the cut: 'we looked at the data, three analyses suggest this, one suggests that, we think that one is inaccurate or worth the risk — let's go. Any objections or new context, tell me.'
Watch out Volume is where opinions go to hide. 'All these analyses seem to suggest' is a way of never taking a position.
- 4
Set the frame before content
Open by naming the problem you are solving and the timeline you are solving it on. Say whether this is a philosophy question, a strategic shift, or a day-to-day product decision — they are different meetings.
- 5
Run the room small and cross-functional
Keep attendance low so the conversation stays informal and fast. Make it cross-functional at both the leadership level and the presenting-team level so accountability is shared.
Pro tip Record or broadcast the review to anyone who wants to watch. The room stays small; the principles still reach everyone.
Watch out Cutting out the middle layer means a working team presents to senior leaders with their managers absent. That requires real trust in both directions, and it is extremely stressful for the manager whose success rides on a meeting they aren't in.
- 6
Extract principles, not verdicts
Interrogate the decision rather than just approving it: why did you make this call, what trade-offs did you weigh, who are you optimising for, what timeline, what risk tolerance? Leave with rules the team can reuse without coming back.
Watch out A review that only produces a decision gives you fast decision-making but changes nobody's ability to decide. The org's capacity stays flat.
In the wild
A PM brings a recommendation. Vora's contribution is not re-doing their analysis: it is 'that sounds like a reasonable pattern, I've seen other patterns like this, and it conflicts with this other outcome over here — let me tell you about that.' The PM supplies depth, she supplies breadth.
→ The meeting produces a decision plus a stated conflict the team didn't know existed, in a fraction of the time an information dump would have taken.
Because the goal was calibration on principles rather than approvals, Vora kept the review room itself small but recorded or broadcast the session to anyone who wanted to watch.
→ The wider org absorbed the decision-making principles without the meeting slowing down or becoming formal.
Common mistakes
Presenting a catalogue of information
The temptation is to show everything on the theory that smart executives will reach the right conclusion. They can't — they lack the depth and the working memory. You outsourced the one job only you could do.
Using reviews to harvest decisions
If every decision has to route through a review, you have built a bottleneck, not a capability. You get speed today and no distributed judgment tomorrow.
Wanting your manager to be a clone of you
Expecting a manager to take the same information and reach the same conclusion is a very narrow ask. Treating their view as complementary rather than confirmatory is what makes them useful.
Is it for you?
Best for
PMs preparing for executive reviews, and product leaders trying to make their review process build org capability instead of consuming it.
Not ideal for
Genuinely irreversible, one-way-door decisions where deep executive scrutiny of the underlying data is the point.
From the transcript
“assume that like Executives have like a a little tiny dinosaur brain like we all have like a little brontosaurus brain and we can really…”
“the best service you can do is to actually do the work of making a recommendation”
“I think we misuse product reviews sometimes as ways to get decisions and actually they should be ways to calibrate on principles”
“what you want is to come to a product review with one decision but the goal of that decision is to walk out with principles…”
“write whatever you need to write and then cut out almost all of it”
“the minimal amount of information that you need to make a clean recommendation because then you are forced to be opinionated”
From the episode
Making an impact through authenticity and curiosity
Ami Vora (CPO at Faire, ex-WhatsApp, FB, IG)