Blitzscaling 17: Marissa Mayer on Scaling Google and Yahoo

Executive Summary:

  • Marissa Mayer has a strong technical background from Stanford and teaching experience, joining Google in 1999 to work on AI and then transitioning to product management.
  • At Google, Marissa Mayer helped scale the organization, including pioneering the Associate Product Manager (APM) program to quickly build a strong PM team.
  • As Yahoo CEO, Marissa Mayer focused on empowering employees, using data and feedback to drive cultural change, with advice to set direction and remove obstacles.
  • Marissa Mayer emphasizes the importance of personal growth, taking on stretch assignments, and working with exceptional people to continually develop.

Meeting Notes:

Early Life and Education

  • Marissa Mayer majored in Symbolic Systems at Stanford University (graduated in 1997 with a B.S. and 1999 with a M.S.)
  • Worked as a teaching assistant and lecturer for CS106A and CS106B, teaching the courses
  • Actively involved in residential life as an RA and the debate team at Stanford

Joining Google

  • Initially worked on developing AI algorithms for related queries, ad matching, etc. at Google after joining in 1999
  • Transitioned into a product management role, helping establish Google's product management function
  • Provided insights on challenges Google faced while rapidly scaling:
    • Marissa Mayer described how at certain company size thresholds (e.g., 100 people, 1000 people), existing processes and systems tended to break down, requiring complete reinvention
    • To control rapid hiring growth, Eric Schmidt instituted a system using laminated cards with Larry Page and Sergey Brin's faces ("Larry and Sergey dollars") that had to be submitted for every new hire approval
    • Scaling engineering and product management teams at the right ratio was a challenge (initially 1 PM for every 32 engineers hired)

Running the Associate Product Manager (APM) Program

  • Marissa Mayer started the APM program at Google after making a bet with Jonathan Rosenberg that she could hire and train new PMs faster than hiring experienced ones
  • Key traits looked for in APM candidates:
    • Technical excellence
    • Ability to understand and apply technology trends ("seeing the implications of new technologies")
    • Humility and willingness to start from the bottom to earn engineers' respect
    • Data-driven mindset to convince engineers vs relying just on instincts
  • Mentorship, career development, and providing broad exposure across PM roles were core focuses
  • First APM hired was Brian Rutkowski, who now runs the program
  • The program enabled hiring batches of pre-trained PMs to quickly scale the PM team as Google grew

Becoming CEO of Yahoo

  • Approach to changing Yahoo's culture and processes:
    • Instituted "PB&J" (Process, Bureaucracy, and Jams) program to identify and fix inefficient processes based on employee feedback
    • Focused on empowering employees and removing obstacles rather than top-down directives
    • Used internal data and feedback to drive improvements
    • Gradual approach to drive cultural shift as employee base turned over
  • Viewed her role as listening, setting direction, and removing distractions for employees (advice from Eric Schmidt)
  • Asked probing questions to understand pain points and priorities from employees' perspectives

Personal Growth and Development

  • Importance of finding one's own "rhythm" and accommodating personal commitments ("finding your rhythm")
    • Learned from colleagues at Google the value of having non-negotiable personal time
    • Marissa Mayer's own rhythm changed over time (e.g. from prioritizing travel to family time)
  • Embraced different career phases and stretch assignments that made her feel unprepared ("do things you don't feel ready to do")

Advice and Reflections

  • Value in working with exceptionally smart people who challenge you
  • Importance of taking on stretch assignments outside one's comfort zone to grow
  • In hindsight at Yahoo, Marissa Mayer would have paced some changes faster and others more gradually
  • Emphasized asking people directly about their needs rather than making assumptions