01 · What Is a Product Lead?¶
"Product Lead" is one of the fuzziest titles in tech — it can mean a senior IC PM with a fancy title, a first-line manager of 2-4 PMs, or (at a startup) someone doing both jobs at once. This module draws the lines clearly so the rest of this track has a fixed target: a Product Lead is someone whose primary job is multiplying the output of other PMs, not just producing their own. Everything after this module assumes that definition.
The three roles, side by side¶
The confusion mostly comes from three genuinely different jobs sharing overlapping titles. Knowing which one you're in (or hiring for, or being promoted into) changes what "good" looks like.
| Dimension | Individual-Contributor PM | Product Lead | Head of Product / CPO |
|---|---|---|---|
| Primary unit of work | A product area or set of features | A team of PMs (typically 2-6) | Multiple Product Leads / the whole product org |
| Main deliverable | Roadmap, specs, shipped features | Team's collective roadmap, PM growth, team rituals | Company-wide product strategy, org design |
| Where their time goes | ~80% product work (discovery, specs, launches) | ~40-50% still hands-on product, ~50-60% coaching/coordinating/hiring | ~10-20% hands-on, mostly strategy, org, exec/board work |
| Success measured by | Did their features move the metric? | Did their team's collective output improve, and are their PMs growing? | Did the product org's strategy and structure serve the company? |
| Typical span of control | 0 direct reports | 2-6 PM direct reports | Multiple Product Leads, dozens of PMs total |
The critical shift, and the one this whole Level 1 is built around: a Product Lead's job is no longer to have the best ideas — it's to make sure their team has good ideas, executes on them, and grows while doing it. An IC PM who becomes a Product Lead but keeps operating like the smartest IC in the room (making every call, writing every spec themselves) hasn't actually made the transition — they've just added management overhead to their old job.
A quick self-check: are you (or should you be) a Product Lead?¶
Use this as a gut-check, not a strict test — real orgs blend these.
| Question | If "yes," you're leaning toward... |
|---|---|
| Do you have PMs reporting to you, or are you about to? | Product Lead |
| Is your calendar mostly 1:1s, planning, and cross-team syncs rather than user interviews and spec-writing? | Product Lead |
| Do you set the vision for a product area covering several squads? | Product Lead or Head of Product |
| Do you spend more time in board decks and org charts than in Figma or a backlog tool? | Head of Product / CPO |
| Do you still ship your own features end-to-end with no one reporting to you? | Individual-Contributor PM |
Worked example: the same person, two jobs, six months apart¶
Priya, IC PM (before): Owns the checkout product area at a mid-size e-commerce company. Her week: two user interviews, a spec for a one-click reorder feature, a sprint planning session with her one embedded engineering squad, and a metrics review of last month's A/B test. She has zero direct reports. Her manager is a Product Lead who reviews her roadmap monthly.
Priya, Product Lead (after promotion): Now owns the same checkout area but through three PMs — one on one-click reorder, one on saved payment methods, one on cart abandonment recovery. Her week: three 1:1s (one per PM, reviewing their roadmaps and unblocking them), a rituals-and-alignment meeting she runs for all three squads, an hour coaching the newest PM through their first stakeholder conflict, a hiring interview for a fourth PM, and a strategy memo up to her Head of Product on how checkout's roadmap ladders into the company's Q3 revenue goal. She still occasionally jumps into a spec review, but she doesn't write specs herself anymore — she reviews her PMs' specs and asks the questions that make them better.
The product area didn't change. The job did, completely.
Cheat sheet — what actually changes at each transition¶
| You're moving... | You stop doing | You start doing |
|---|---|---|
| IC PM → Product Lead | Owning one roadmap end-to-end personally | Setting direction for several roadmaps through other PMs |
| IC PM → Product Lead | Writing every spec | Reviewing specs and coaching the PM who wrote them |
| Product Lead → Head of Product | Managing PMs directly day-to-day | Managing Product Leads who manage PMs |
| Product Lead → Head of Product | Team-level rituals and hiring | Org design, cross-org strategy, board/exec communication |
How It Actually Works¶
The title confusion described above isn't a naming accident — it's a consequence of how compensation bands and reporting lines get set at most companies. HR levels titles off years-of-experience and scope of people managed, but the actual job changes off a different variable: whether your output is measured by what you personally shipped or by what your team shipped without you in the room. That mismatch is why a company can have a "Senior PM" doing Product Lead work with no direct reports (because no headcount was approved) and a "Product Lead" who still writes every spec (because no one taught them to stop). The real signal isn't the title on the org chart, it's where the escalation path terminates: if a stuck PM's problem routes to you and stops there because you decide, you're doing IC work with a management label. If it routes to you and you route it back to the PM with a sharper question, you've made the shift. Companies that get this transition right build an explicit "decision rights" checklist into the promotion itself — naming which calls the new Product Lead must stop making personally — because without that forcing function, old habits (and the dopamine hit of personally solving a hard problem) pull people back into IC mode for years after the promotion is official.
Exercise¶
Write a half-page "role clarity memo" as if you just accepted a Product Lead role (real or hypothetical). Answer three questions in your own words: (1) What was I doing as an IC PM that I need to explicitly stop doing? (2) What new skill do I most need to build in the next 90 days? (3) How will I — and my manager — know in 90 days whether I've made the transition successfully? Keep every answer to 2-3 sentences; you'll revisit this memo again at the end of Level 1 when you write your team charter.