The 'Safe Space' Product Review Protocol
by Brian Tolkin • Head of Product and Design at Opendoor
Brian is the Head of Product and Design at Opendoor. Previously, he was Employee #100 at Uber, where he led the global launch of uberPOOL and established the original Product Operations function.
🎙️ Episode Context
Brian Tolkin shares deep insights on building products that bridge the physical and digital worlds, drawing from his experiences scaling Uber and Opendoor. He discusses the evolution of operational processes into scalable software, how to run non-threatening product reviews, applying Jobs-to-be-Done for low-frequency use cases, and how to rigorously experiment when you lack high transaction volume.
Problem It Solves
Product reviews that feel like 'firing squads,' leading to defensive teams and suppressed innovation.
Framework Overview
A specific meeting structure designed to balance executive accountability with genuine collaborative problem-solving, ensuring the meeting improves the product rather than just judging the PM.
🧠 Framework Structure
Principle 1: Dual Goal Definition. Ex...
Principle 2: The 'Pull' Cadence. Inst...
Principle 3: Small Audience. Keep the...
Principle 4: Artifacts as Assets. Use...
Principle 5: Leader as Prober. Leader...
When to Use
Scaling organizations where leadership is becoming disconnected from ground-level details, or when cultural surveys indicate fear of leadership.
Common Mistakes
Inviting too many spectators, making the meeting a status update rather than a working session, or leaders delivering feedback as absolute mandates.
Real World Example
Opendoor's implementation of sign-up based review slots where PMs bring a standardized template covering 'Context, Problem, Solution, Risks, and Measurement'.
Product reviews hopefully are not feeling like firing squads. That's a scary environment to be in and not necessarily one that's conducive to how do we make the product better.
— Brian Tolkin