02 · Leading a Product Team¶
The hardest part of becoming a Product Lead isn't learning something new — it's unlearning the instincts that made you a great IC PM. This module covers the specific traps new Product Leads fall into during their first few months, and the habits that replace them.
The four traps of a new Product Lead¶
| Trap | What it looks like | What to do instead |
|---|---|---|
| The Rescuer | You jump in and solve your PM's problem yourself because it's faster | Ask "what have you tried?" and "what do you think we should do?" before offering your own answer |
| The Ghostwriter | You rewrite your PM's spec/doc instead of giving feedback on it | Comment on the doc with questions, not rewritten paragraphs; let them own the next draft |
| The Bottleneck | Every decision routes through you because you haven't said what's delegated | Publish a decision-rights list (Module 4) so PMs know what's theirs |
| The Invisible Manager | You're so hands-off that your PMs get no signal on how they're doing | Schedule regular, structured 1:1s and give direct feedback on a cadence, not just when something breaks |
The shift from "doing" to "multiplying"¶
A useful mental model: as an IC PM, your output was your work. As a Product Lead, your output is the sum of your team's work, improved by your involvement. Concretely, that means every hour you spend should do one of three things:
| Activity type | Example | Why it's leverage |
|---|---|---|
| Unblock | Removing a stakeholder conflict, getting budget approved, resolving a dependency between two squads | One hour of yours saves many hours across the team |
| Develop | Coaching a PM through a hard prioritization call instead of making it for them | Builds a skill they'll use on the next 10 similar calls without you |
| Set direction | Clarifying which of three initiatives matters most this quarter | Prevents the team from spending weeks on the wrong thing |
If you find your week is mostly none of these — mostly you doing IC-shaped work yourself — that's the clearest sign you've slipped back into the old job.
The first 90 days: a simple framework¶
| Phase | Weeks | Focus |
|---|---|---|
| Listen | 1-2 | 1:1s with every PM and key stakeholder; no changes yet — just understand current state, in-flight work, and where the team is stuck |
| Diagnose | 3-4 | Identify the 2-3 biggest gaps (unclear vision? no rituals? a struggling PM? unclear decision rights?) — resist fixing everything at once |
| Act | 5-8 | Fix the top 1-2 gaps visibly — e.g., stand up a missing ritual, clarify decision rights, have the hard conversation you've been avoiding |
| Reinforce | 9-12 | Check whether the fixes stuck; ask the team directly what's better and what's still broken |
Worked example: diagnosing a struggling team¶
Dev takes over as Product Lead for a 4-PM team at a fintech startup. In his first two weeks of 1:1s, he hears the same three complaints from three different PMs, phrased three different ways: "I don't know if my quarterly plan actually matters to the company," "engineering keeps deprioritizing my work and I don't know why," and "I found out about a competing initiative from another team, not from you." Dev's diagnosis: this isn't four separate problems — it's one root cause (no clear cascaded vision, see Module 3) with three symptoms. Rather than solving each PM's individual complaint, he spends week 5 writing and socializing a one-page team vision doc that ties each PM's roadmap explicitly to the company goal it serves, and creates a biweekly cross-squad sync so initiatives stop colliding silently.
Cheat sheet¶
| Old (IC) instinct | New (Product Lead) instinct |
|---|---|
| "I'll just do it myself, it's faster" | "What would it take for you to do this without me next time?" |
| Measure your week by what you shipped | Measure your week by what you unblocked, coached, or clarified |
| React to whatever's loudest today | Spend deliberate time diagnosing root causes, not just symptoms |
| Give feedback only when something goes wrong | Give feedback on a fixed cadence, good and bad |
How It Actually Works¶
Team leadership breaks down less from bad intentions than from a bandwidth math problem: a Product Lead with four PMs and 45 minutes of 1:1 time per week per PM has roughly 3 hours of individual contact time, but each PM generates 5-10 hours of decisions, blockers, and stakeholder friction that could use the lead's input. The mechanism that makes leadership scale isn't more hours — it's converting synchronous judgment calls into standing defaults the PM can apply without asking. A lead who says "always loop in legal before promising a launch date to enterprise customers" once, in writing, removes dozens of future 1:1 minutes and future Slack interruptions. The leads who stay bottlenecked are the ones who keep answering the same category of question personally because writing the general rule down feels like extra work in the moment. The compounding effect goes the other way too: every ad-hoc judgment call a lead makes instead of codifying a default teaches the team that judgment calls go up the chain, which increases the volume of the next quarter's escalations — a self-reinforcing bottleneck that looks like "just needing to hire another PM" when the actual fix is delegation infrastructure.
Exercise¶
Pick one real (or realistic) week from your current or a past role. List every hour of meaningful work you did. Sort each item into "Unblock," "Develop," "Set direction," or "IC-shaped work I could have delegated." If more than a third of your hours land in that last bucket, write two sentences on what you'd delegate first, and to whom, if you had a team today.