newsfilter.io
Interview, Fireside Chat

Brian Tolkin, Head of Product @Opendoor: How to Hire the Best Product Teams | E1257

Uber Product Decisions & Launch Challenges

  • Upfront Pricing for UberPool identified as the single best product decision made.
    • Previously, pricing was variable and calculated post-hoc based on match quality, minutes, and miles.
    • Implementation shifted the user experience to display definitive costs before confirmation, reducing friction and uncertainty.
  • China Launch (Chengdu) Experience involved simultaneous infrastructure and product deployment.
    • Launched during rush hour in a city of 20 million people, relying heavily on ride liquidity for efficient matching.
    • Critical technical failures occurred the day before launch, with the team sleeping only ~30 minutes on the office floor to resolve issues before a 5:30/6:00 AM go-live.
    • Data Dependency: Lack of high-quality mapping/routing data (absence of Google Maps) and complex road infrastructure (massive highways/overpasses) significantly hindered initial match quality.
    • Cultural Design Mismatch: Initial underestimation of Chinese user preferences, which favor colorful interfaces with large buttons over the sleek, minimal design prevalent in the US.

Product Failures & Strategic Lessons

  • Default UberPool UI Toggle classified as the worst product decision due to accidental user selection.
    • The interface defaulted to UberPool even for returning UberX users, causing confusion when passengers arrived with unrelated ride partners.
    • Root Cause: Prioritized business liquidity needs and testing bounds over user choice and experience clarity.
    • Lesson: Product managers must balance business objectives with explicit respect for user preferences; aggressive testing should not compromise core user trust.
  • Opendoor Multi-Product Expansion revealed strategic misalignment.
    • Early focus heavily favored the buyer side (retail buyer business, mortgage), attempting to enter the "new customer set / new capability" quadrant.
    • Correction: Shifted focus to the "existing customer set / new capability" quadrant, targeting seller tools to leverage core strengths in the real estate market.
  • Technical Debt vs. Growth prioritization in early-stage funding (e.g., $2M to $8M ARR).
    • Early-stage companies in "land grab" phases must prioritize growth and new product validation over paying down technical debt, as debt reduction does not directly generate revenue.
    • CEO as CPO is deemed necessary in early stages to protect the core product asset; outsourcing this role becomes challenging as the company scales.

The Evolving Product Manager (PM) Role in an AI Era

  • Core Skills vs. Tools: AI will collapse the traditional design triad (PM, Design, Engineering) and accelerate prototyping, but the core PM responsibility—defining problems and aligning solutions with business/user needs—remains unchanged.
    • Artifact Shift: Reduced reliance on PRDs (Product Requirement Documents) in favor of collaborative prototyping; PMs and designers may work directly on functional prototypes rather than flat files.
    • Skill Compression: The "end product design triad" converges, with PMs needing to engage more directly in prototyping and implementation.
  • One-Pagers & Problem Definition:
    • Best Practice: One-pagers must define the problem and the "why" (user/business insight) rather than the solution, which should remain under-explored at this stage.
    • Common Failure: Treating the one-pager as a solution description rather than a problem statement.
  • Prioritization Frameworks:
    • Standard "Impact, Confidence, Effort" (ICE) must be adapted to include company time horizons (e.g., new features vs. tech debt vs. stability).
    • OKR Management: Teams should limit objectives to 3–5 items to ensure focus; success is measured by the ability to articulate what was not done.
    • Time Horizons: Short-term execution discipline (quarterly) earns the right to set long-term (annual) strategic goals.

Hiring, Team Dynamics, and Leadership

  • "True Product Teams" vs. Generalists: Hiring should prioritize specific functional backgrounds (engineering, data, design, ops) to fit the specific team's strategic needs ("hire your strategy").
    • Internal Transfers: Deeply undervalued; engineers/designers moving to PM roles bring superior context and domain knowledge.
  • Dictatorial vs. Consensus Leadership:
    • Pure consensus leads to suboptimal middle-ground decisions; "dictatorial" leadership (making the final call after gathering input) is often necessary for velocity.
    • "Disagree and Commit" is valid for short sprints, but frequent disagreement indicates a misalignment with company direction.
  • AI's Impact on Skills:
    • Engineering: Commoditization of average engineering challenges reduces the value of median engineers; top 1% system architects remain critical.
    • Design: AI may lower the quality floor ("good enough" design), increasing the value of top-tier designers who can craft distinct, high-quality experiences.
    • PMs: Strategic mastery becomes more valuable as tactical execution becomes automated.
  • Managing Momentum: Leaders should intentionally ship "unnatural" low-effort, high-confidence wins to boost team energy after breaks, layoffs, or setbacks, allowing positive momentum to compound.

Consumer Trends & Future Outlook

  • Globalization of Design: A convergence is occurring between Western and Asian product designs, driven by shrinking attention spans and the influence of apps like TikTok, though Western design principles still heavily influence the trajectory.
  • Real-World Entropy: Physical product businesses (e.g., Opendoor, Uber) face challenges from "real-world entropy" (human unpredictability) that pure software cannot control, requiring product adaptation to physical realities.
  • Favorite Products: Meta glasses and Suno (AI music generator) cited as recent consumer "wow" moments; ChatGPT's multimodal analysis capabilities noted as significant.
  • Advice for New PMs: Join relatively early-stage startups to balance learning operational successes with the freedom to make mistakes; long-term tenure at a single company increases effectiveness through context and relationship depth.

Key Metrics & Frameworks

  • UberPool Success Metric: Trip count and match quality.
  • Prioritization Trade-off: Distinguishing between "Type 1" (reversible) and "Type 2" (irreversible) decisions remains a core PM skill unaffected by AI.
  • Sprint Duration: Two weeks is standard, with growth teams potentially operating on one-week cycles.
  • Velocity vs. Taste: High velocity with a minimum viable bar is preferred over slow perfection; "throwing shots on goal" with rapid feedback loops is superior to prolonged refinement in uncertain markets.