💡

InsightHunt

Hunt the Insights

N

Naomi Gleit

Episode #219

Head of Product

Meta

📈Growth & Metrics⚡Execution🎯Product Strategy

📝Full Transcript

18,196 words
Naomi Gleit (00:00:00): I really believe in frameworks for things that helps drive extreme clarity. I work on a lot of different projects. A lot of times I'm ramping up a new project, I'm like, "Where can I learn what I need to learn about this project?" I ask five different people, get five different answers. That is unacceptable. Of course, I'm sure there's hundreds of docs associated with the project, but there needs to be one canonical doc. Everyone should know exactly where the canonical doc is. That's the one place I can go to get all the information I need about a project and it will link to all the other docs, things on the canonical doc are. Lenny Rachitsky (00:00:33): Today my guest is Naomi Gleit. Naomi is head of product at Meta. Other than Mark Zuckerberg, she's the longest-serving executive at Meta. She joined what was then called Facebook as employee number 29 and has been at Meta for almost 20 years. She's seen the company scale from 30 employees to the one and a half trillion dollar business that it is today. Naomi does very few podcasts and interviews and so I was really excited to chat with her and have her on this podcast. In our conversation, we dig into the many lessons that she learned from Facebook's early and legendary growth team, her superpower of taking really complex and gnarly problems and projects, simplifying them and delivering results. We also get into leadership lessons she's learned from Zuck, including his recent transformation into possibly the coolest CEO in tech. Also, why PMs are the conductor of product teams, some very tactical tips for running meetings, writing docs, working out, getting better sleep, and even how to get more protein in your diet. (00:01:31): This was such a fun conversation and such a wide-ranging conversation and whether you are in product or growth or any other tech function, you will get something useful out of this conversation. If you enjoy this podcast, don't forget to subscribe and follow it in y...

💡 Key Takeaways

  • 1Growth is a product and engineering function, not just marketing.
  • 2Use 'Canonical Documents' to create a single source of truth for every project.
  • 3Simplify complex problems by breaking them down from 'PhD level' to 'Kindergarten level'.
  • 4PMs act as conductors: they don't make the music, but ensure the tempo and harmony.
  • 5Use numbered lists instead of bullet points to allow for precise referencing in discussions.
  • 6Establish an activation metric (like 7 friends in 10 days) primarily to align the team on a shared goal.

📚Methodologies (3)

📈 Growth & Metrics

A fundamental growth framework emphasizing that you cannot grow what you cannot measure. It shifts focus from acquisition to retention and engagement by removing barriers systematically.

Core Principles

  • 1.Understand: Instrument everything. If you don't have data, stop the roadmap and build logging (e.g., 'I guess when you can know').
  • 2.Identify: Find macro barriers (access, language) and micro barriers (UI friction, 20% drop-off at email confirm).
  • 3.Execute: Build product solutions to remove these barriers rather than marketing around them.

"The insight that we had is actually the product is the biggest lever to drive growth."

#understand-identify-execute#cycle#growth
View Deep Dive →
⚡ Execution

A rigorous operational framework ensuring every project has a single source of truth. It standardizes language, documentation, and decision-making processes to reduce cognitive load and misalignment.

Core Principles

  • 1.Canonical Doc: One master document linking to all workstreams, owners (Single Threaded Owners), and processes.
  • 2.Canonical Nomenclature: Define terms precisely (e.g., Accuracy vs. Consistency) so teams don't talk past each other.
  • 3.Visual & Real-Time Editing: Project decisions on a screen and edit them live to confirm agreement before leaving the meeting.

"There needs to be one canonical doc. Everyone should know exactly where the canonical doc is."

#canonical#everything#extreme
View Deep Dive →
🎯 Product Strategy

A meeting tool to force a decision. Instead of text lists, use a visual table where rows are options and columns are criteria/functions, colored red/yellow/green.

Core Principles

  • 1.Structure: 3 Options + 1 Recommendation.
  • 2.Columns as Criteria: Columns represent specific constraints (Legal, Eng, UX) or goals.
  • 3.Visual Density: Look for the 'Green' path; rule out options with critical 'Red' blockers instantly.

"I don't love pros and cons. It's a flat list of text... Oftentimes we'll use a traffic light."

#traffic#light#decision
View Deep Dive →
← Browse All Episodes