Leading Product Leads (the Head of Product Role)¶
Amara has been VP Product at Meridian Logistics for three months. The job changed the day her five direct reports stopped being PMs and became Product Leads — Ravi, Sofia, Tom, Priya, and Dana, each now running their own pod of three to five PMs. Her instinct is still to ask "what does the roadmap look like" and "how's the pricing epic going." Both questions skip a layer. The actual job now is making Ravi better at the job Amara used to do for Meridian's four core squads — not doing it herself one layer removed.
What actually changes at this altitude¶
| Dimension | Managing PMs (Level 1-2) | Managing Product Leads (Level 3) |
|---|---|---|
| Unit of output | A roadmap, a launch, a metric | Another leader's judgment and their team's output |
| Your main lever | Coaching on the work | Coaching on how they coach, and what they escalate |
| Cadence of contact | Weekly 1:1s on specifics | Biweekly 1:1s on patterns; specifics only when escalated |
| Failure mode you fix | A bad prioritization call | A Lead who makes every call herself and burns out her PMs |
| What "good" looks like | A PM who ships the right thing | A Lead whose pod ships the right thing without her in every room |
| Your visibility into detail | Direct — you read the specs | Indirect — you read what the Lead chose to escalate |
The hardest habit to break is the third row. Amara spent four years building a reflex: hear a problem, dig into specifics, form an opinion. That reflex, pointed at Ravi's pod, produces a VP who re-does Ravi's job for him and a Ravi who stops making calls because Amara will make them anyway.
The delegation ladder¶
Use this with every Product Lead to calibrate how much rope to give, and to make the rope visible instead of a mystery they have to guess at.
| Rung | What the Lead does | What you do | When to use it |
|---|---|---|---|
| 1. Tell me the problem | Surfaces the issue, no recommendation | You decide | New Lead, or a genuinely novel problem class |
| 2. Tell me the options | Surfaces 2-3 options with tradeoffs | You pick | Lead is competent but the stakes are high or irreversible |
| 3. Recommend, I'll confirm | Picks one, states why, you can veto | You rubber-stamp unless something's wrong | Default for a proven Lead on familiar terrain |
| 4. Decide and inform | Decides and tells you after | You listen, ask questions for your own learning | Fully trusted Lead, reversible or contained-blast-radius decision |
| 5. Decide, I don't need to know | Decides, doesn't report unless asked | You audit occasionally | Routine operational calls only |
Every Lead should know which rung they're on for which decision types, and it should move up over time as trust is earned — not stay static. A Lead stuck at rung 1 for eighteen months is either being under-trusted or isn't ready for the role, and Amara owes them a direct conversation about which.
Diagnosing a Lead who's stuck, not a problem that's stuck¶
When a Product Lead brings Amara a recurring problem, the temptation is to solve the problem. The more useful move is to diagnose which of four things is actually broken:
| Symptom | Likely cause | What Amara does |
|---|---|---|
| Lead brings you the same category of problem every 1:1 | They haven't built a repeatable process for it | Ask them to design the process, not solve this instance |
| Lead's PMs escalate to Amara directly, over the Lead | Lead hasn't established their own authority | Redirect the PM to the Lead in front of both; talk to the Lead privately after |
| Lead makes good individual calls but their pod's output is inconsistent | Lead coaches unevenly across their own PMs | Sit in on one of the Lead's 1:1s, give feedback on the coaching, not the content |
| Lead is right on the substance but stakeholders don't trust their calls | Lead hasn't built credibility outside product | Actively sponsor them — bring them into rooms Amara used to attend alone |
Worked example: Ravi's carrier-onboarding pod stalls¶
Ravi's pod owns onboarding — the same squad from Amara's Level 2 portfolio review, now grown to four PMs under Ravi instead of Ravi being the sole PM. Six weeks in, Ravi brings Amara the same complaint twice: "Engineering keeps deprioritizing our data-migration tooling for Integrations' work." Old Amara would call Tom's Lead-equivalent directly and negotiate the sequencing herself. VP Amara does this instead:
- Names the rung. She tells Ravi: "This is a rung-2 decision — bring me two options with tradeoffs, I'll pick." This forces Ravi to actually scope the conflict instead of just reporting pain.
- Ravi returns with options. Option A: escalate to the eng director for a formal sequencing call, costs a week of process. Option B: Ravi and Tom's Lead trade — onboarding gets two sprints of migration tooling now, Integrations gets priority on the next incident-reduction push.
- Amara picks B, and states why out loud: "B keeps this at your level instead of mine, and it's reversible if it doesn't work." This is the coaching payload — not the decision itself, but making the decision criteria visible so Ravi internalizes it.
- Amara does not attend the trade conversation. Ravi runs it. She asks at the next 1:1 how it went, not before.
Three months later Ravi negotiates a similar trade with a different Lead without bringing it to Amara at all — rung 4. That's the actual success metric, not whether the onboarding tooling shipped on time.
The 1:1 shift: from status to pattern¶
A Level 2 PM 1:1 reviews this week's work. A Level 3 Product Lead 1:1 should spend most of its time one layer up:
| Old question (to a PM) | New question (to a Product Lead) |
|---|---|
| "What's blocking the launch?" | "What's blocking your PMs, and what have you tried?" |
| "Is the spec ready?" | "Which of your PMs needed the most coaching this month, and on what?" |
| "What did the customer say?" | "Where are your PMs making calls you'd have made differently, and did you let them?" |
| "What's the risk to the deadline?" | "What decision are you avoiding making yourself?" |
How It Actually Works¶
Managing managers changes the fundamental unit of your own leverage: your output is no longer measured by decisions you personally make but by the quality of decisions made two organizational layers below you, by people you may talk to only every other week. That distance means your primary tool shifts from direct coaching to calibrating the calibrators — making sure each Product Lead you manage is giving their own PMs feedback that's consistent with the org's actual bar, because if you only check the Product Leads' own performance and never sample how they're managing their PMs, inconsistency compounds invisibly two layers down and you find out only when a PM quits citing a manager problem you never saw coming. The mechanism that catches this early is deliberately sampling below your direct reports — a periodic skip-level conversation, a look at how a Product Lead ran their own team's calibration — not to override their authority but because at this altitude, the natural information flow upward gets progressively filtered and flattering at each layer, and without a countervailing sampling mechanism, a Head of Product's picture of org health is systematically two quarters stale by the time a real problem surfaces through normal channels.
Exercise¶
Pick a Product Lead (or, if you don't yet manage Leads, a senior PM you manage closely) and one recurring problem they bring you. Write down: which delegation rung are they currently operating at for this problem class, and which rung should they be at given their tenure and track record? Draft the exact sentence you'll use in your next 1:1 to move them one rung up, and name the one thing you will deliberately stop doing for them to make that happen.