06 · Mentoring PMs¶
Mentoring is where the "multiplying" idea from Module 2 becomes concrete — it's the mechanism by which your judgment becomes your team's judgment, instead of a bottleneck they route every hard call through. This module covers structuring 1:1s for growth (not just status updates) and giving feedback that actually changes behavior.
1:1s: status update vs. growth conversation¶
Many new Product Leads default to using 1:1s as a mini status meeting — a waste of a tool meant for something 1:1s are uniquely good at.
| Status-update 1:1 | Growth-oriented 1:1 | |
|---|---|---|
| Typical opening question | "What's the status of X?" | "What's the hardest part of your week been?" |
| Who talks more | The Lead, reviewing a list | The PM, working through a problem |
| What it surfaces | Whether tasks are on track | Whether the PM is growing, stuck, or unsupported |
| Where status belongs instead | — | An async doc or dashboard the Lead reads before the 1:1 |
A simple fix: ask the PM to send you a short written update before the 1:1 (bullets on status, blockers, wins). That frees the actual meeting time for the harder, higher-value conversation — coaching, career growth, or working through a real decision together.
A 1:1 agenda template¶
| Time | Section | Purpose |
|---|---|---|
| 5 min | Wins & energy check | How are they actually doing, not just what shipped |
| 15 min | The hardest thing this week | Work through one real problem together — coach, don't solve |
| 5 min | Feedback (both directions) | Lead gives feedback; PM gives feedback on the Lead too |
| 5 min | Growth/career | One recurring thread across weeks, not a new topic every time |
The SBI feedback framework¶
Vague feedback ("be more strategic") doesn't change behavior. Situation – Behavior – Impact does, because it's specific and observable.
| Component | Prompt | Example |
|---|---|---|
| Situation | When/where did this happen? | "In yesterday's roadmap review with the VP..." |
| Behavior | What did they specifically do (not who they are)? | "...you presented three options without a recommendation..." |
| Impact | What happened as a result? | "...which meant the VP spent the meeting debating instead of deciding, and we lost the timeline discussion we needed." |
Compare to the vague version — "you need to be more decisive" — which gives the PM nothing concrete to change next time. SBI always names a specific moment, not a character trait.
Worked example: coaching instead of rescuing¶
A PM comes to their 1:1 stuck: a key engineering stakeholder is pushing back hard on a proposed roadmap, and the PM wants their Lead to "just tell engineering this is happening." The Rescuer instinct (Module 2) says step in and pull rank. Instead, the Lead asks: "What do you think is driving their pushback — is it a technical concern, a capacity concern, or something else?" The PM realizes, saying it out loud, that they never actually asked the engineering lead why — they'd assumed it was resistance to change. The Lead sends them back with one homework item: have that direct "why" conversation before the next planning meeting. Two weeks later, the PM reports the objection was a legitimate capacity concern the roadmap hadn't accounted for — and they'd solved it themselves by re-sequencing two items. That's a skill the PM now owns permanently; if the Lead had just "fixed" it by talking to engineering directly, the PM would face the exact same situation, unequipped, next quarter.
Cheat sheet¶
| Situation | Mentoring move |
|---|---|
| PM brings you a problem to solve | Ask what they've already considered before offering your view |
| PM's work has a specific, fixable gap | Use SBI feedback within a day or two, not saved for a review cycle |
| PM seems stuck in the same kind of problem repeatedly | That's a pattern worth naming directly and coaching toward, not re-solving each time |
| 1:1s keep turning into status readouts | Move status to an async pre-read; protect the live time for coaching |
How It Actually Works¶
Mentoring only produces growth when the feedback loop is short enough for the PM to still remember the reasoning behind a decision when the outcome lands — and in product work, that loop is often quarters long (a prioritization call made in January doesn't show its consequences until a metric moves in April), which is exactly why unmentored PMs plateau: by the time they'd have useful signal about whether their judgment was right, the context has evaporated and no lesson gets attached to the outcome. A mentor's actual function is to manufacture shorter feedback loops artificially — reviewing the PM's reasoning at decision time (not just the outcome later), asking "what would make you wrong about this" before the bet is placed, and then deliberately reconnecting the eventual outcome back to that original reasoning months later, since the PM won't do that reconnection on their own. Mentoring that's just praise-or-criticism after the fact, disconnected from the PM's reasoning at the time, teaches pattern-matching on outcomes ("that failed, don't do that again") rather than on decision quality — which is why some PMs who get lucky outcomes early develop bad judgment that isn't corrected until a much more expensive failure later.
Exercise¶
Write out an SBI feedback statement for a real (or plausible) piece of PM feedback you've wanted to give or receive — one sentence each for Situation, Behavior, and Impact. Then draft a 1:1 agenda for that same PM using the template above, and write the one open-ended coaching question you'd lead with instead of asking for a status update.