Naomi Gleit on Facebook Growth, Canonical Thinking, and the Naomi-isms

Naomi Gleit is Head of Product at Meta and one of the longest-tenured employees in the company’s history (employee #29). She built some of Facebook’s foundational growth infrastructure and has developed a set of operating principles — the “Naomi-isms” — that she now shares publicly as a guide to high-functioning product management.

Key ideas

7 friends in 10 days: Facebook’s core growth insight. New users who connected with seven friends within ten days retained at dramatically higher rates than those who did not. The metric turned activation from an abstract concept into a concrete target.
Growth accounting (new − stale + resurrected) measures network health more honestly than raw user counts. A product with many new users but collapsing retention is declining; this formula makes the collapse visible.
Canonical everything: one authoritative version of each document, nomenclature, meeting, and communication channel. Duplicates breed confusion; canonical structures eliminate it.
PM as conductor: the PM does not play an instrument but is responsible for the performance. The frame clarifies accountability without claiming expertise the PM does not have.
Disagreeableness as a managerial value: the best feedback comes from people who will tell the truth regardless of how it lands. Naomi prizes “disagreeable givers” (Adam Grant’s term) — people who give honest, critical feedback without ego or political hedging.

Episode content

Facebook growth work

Naomi joined Facebook when the company had fewer than 100 employees. Her early growth work was foundational — developing the analytical frameworks and product interventions that Facebook used to drive global expansion.

The 7-friends-in-10-days metric emerged from analysing retention cohorts. The analysis found a sharp threshold: users who connected with seven friends in their first ten days retained at rates qualitatively higher than those who did not reach that threshold. The specific numbers are less important than the structure: a concrete activation target that the entire growth team could aim at.

Growth accounting was a companion framework. Rather than measuring users as a single stock, it decomposed the user base into flows: new users joining, stale users who had stopped using the product, and resurrected users who had lapsed and returned. Net growth = new − stale + resurrected. This formula forces an honest view of product health: a company whose net growth is positive only because new users are masking collapsing retention will see the masking clearly in the stale line.

Understand → identify → execute

Naomi’s three-stage approach to PM work:

Understand: before proposing solutions, build a genuine mental model of the problem space. This is not a formal research phase; it is an intellectual discipline — refusing to jump to “we should build X” before you can explain why the problem exists at all.

Identify: within the problem space, find the specific opportunity worth acting on. The problem space is large; the opportunity should be specific. Identifying is the skill of knowing which subset of a problem is the right target.

Execute: build the thing. Execution is last, not first.

The failure mode: teams that skip to execute, propose solutions before understanding, and end up building the right thing the wrong way.

The Naomi-isms

Over her career Naomi has collected a set of operating principles she applies consistently. In the episode she shares a dozen:

Extreme clarity: ruthlessly eliminate ambiguity in every communication, document, and decision. Ambiguity at the top becomes confusion at every level below.

Canonical everything: one canonical document, one canonical meeting, one canonical chat thread. When multiple versions exist, time is spent reconciling them rather than using them. Canonical structures are expensive to maintain and valuable to create.

Numbered lists over bullet points: numbered lists create priority ordering and make items referenceable (“item three”). Bullet points suggest equivalence. When priority matters — in decisions, recommendations, and action items — use numbers.

Three options with a recommendation: when presenting a decision to a leader, offer three options and recommend one. Two options suggest you have not done the work; more than three creates decision fatigue. The recommendation should be clear and defended.

Traffic light decisions: each option gets a colour — green (recommend), yellow (acceptable but suboptimal), red (inadvisable). The traffic light makes the PM’s view visible without forcing a binary choice on the decision-maker.

Pre-reads 24 hours before meetings: send the material at least 24 hours before the meeting. People who have read in advance can engage in dialogue; people who are reading during the meeting cannot. Pre-reads are a prerequisite for a useful meeting.

Reply-all notes after meetings: after a meeting, send a reply-all summary with decisions made and next steps. This creates accountability, surfaces misalignment, and is searchable six months later.

PM as conductor: the PM is responsible for the quality of the output but is not the source of every idea. Like a conductor, the PM’s job is to bring out the best performance from each contributor, not to play every instrument.

Teen Accounts

Naomi led the Teen Accounts project at Meta — a significant privacy and safety initiative for under-18 users across Facebook and Instagram. The challenge was translating an abstract goal (“protect teens”) into a specific, buildable product without creating a surveillance experience that would destroy trust with the user group it was designed to protect.

She describes using what she calls the “school pyramid” simplification approach: when a problem is complex, draw the simplest possible diagram that captures the key relationship. The school pyramid mapped the relationships between teens, parents, and the platform — a simple frame that kept the team aligned on who was being served at each decision point.

Small group as operating infrastructure

Naomi runs two recurring meetings with Meta’s senior leadership team:

A weekly strategic meeting: open-ended, no fixed agenda, designed to surface the issues that do not fit neatly into any other forum. The structure is minimal by design; the purpose is to think together, not to report.

A weekly operational meeting: highly structured, pre-reads mandatory, focused on decisions and blockers. The two meetings serve different cognitive modes and should not be merged.

Developing a first-party perspective

A recurring theme across the episode: Naomi believes product managers must develop genuine first-party perspective — not just collecting data about what users want but forming their own view about what is right. A PM who can only report what users said is a researcher; a PM who can synthesise user data into a view about what users need is a product leader.