Coach Product Managers

Instructions

Step 1: Define Good Before Coaching Anything

This is where most coaching fails. You tell a PM "get better at stakeholder alignment" without defining what that means. Does it mean communicating more? Communicating earlier? Making better decisions with stakeholders? Including stakeholders in decision-making? The PM doesn't know, so nothing changes.

Create an explicit competency framework for product managers in your organization. This includes:

• Core competencies (required for the role): Strategic thinking, execution, decision-making, communication, ownership
• Specific standards for each competency: "Strategic thinking means understanding market dynamics, competitive landscape, and how our bets create defensibility. It means articulating how quarterly work fits into multi-year vision."

For each competency, define what excellence looks like (level 3-4) and what needs improvement (level 1-2). Be specific. "Communication" is vague. "Communication means writing strategy documents that get stakeholder buy-in with minimal clarification, running meetings where silent participants actually speak, and explaining decisions in ways the audience understands" is actionable.

This framework becomes your coaching reference. When you coach, you're helping PMs move up this competency ladder, not moving some vague "goodness needle."

Step 2: Diagnose Current State Using Bloom's Taxonomy

Don't assume a PM's weakness is lack of skill when it might be lack of understanding. Bloom's taxonomy gives you a diagnostic framework:

• Remember: Do they know what good looks like? (If not, start with teaching.)
• Understand: Do they understand why this matters? (If not, start with context.)
• Apply: Can they do it in their own work? (If not, start with practice and feedback.)
• Analyze: Can they recognize the pattern in different situations? (If not, they haven't internalized it yet.)
• Evaluate: Can they judge quality and make decisions based on it? (This is mastery.)

When a PM struggles with stakeholder alignment, diagnose: Do they not know what good alignment looks like (remember)? Do they not understand why stakeholders matter (understand)? Can they analyze stakeholder concerns but fail to apply that analysis to decisions (apply)? Can they recognize patterns but judge trade-offs poorly (analyze)?

Your coaching changes based on diagnosis. If they don't know what good looks like, your job is teaching. If they can analyze but judge poorly, your job is helping them learn how to make better trade-offs.

Step 3: Get Aligned on What Good Looks Like

In your first coaching conversation with a PM, don't jump to what they're doing wrong. Get aligned on what right looks like. "Here's what I think excellent product strategy means in our context [share framework]. Here's what I see you doing well [specific, observed evidence]. Here's where I think you're below where you need to be [specific gap]. Do you agree with where you sit on this framework?"

This conversation sets the stage. You're not imposing standards—you're inviting them to see themselves against an explicit standard. Many PMs will self-assess lower than they actually are. Some will disagree with the framework itself ("I don't think competitive analysis is important"). Address that disagreement now, not after months of trying to coach them toward a standard they don't accept.

Step 4: Create Shared Vision of Growth

Once you've diagnosed where a PM is and aligned on standards, create a vision together of where they're growing. Not "be better at strategy" but "you're going to write quarterly strategy briefs that help the team understand our three bets and how they compound. In six months, I want leadership reading your briefs and not needing follow-up conversations."

The vision should be:

• Specific: What will improvement look like in observable terms?
• Time-bound: When will you reassess? (Monthly, quarterly, at next promotion cycle?)
• Motivating: Help them see how this growth unlocks what they want (more leverage, promotion, leading larger team)

Write this down. Revisit it regularly so you both know if you're making progress.

Step 5: Build a Development Plan with Clear Activities

The development plan is where coaching becomes real work. It should include:

Coaching conversations: Weekly or bi-weekly 1:1s focused specifically on growth. Not status updates—time devoted to skill development. Structure these around current projects: "Let's look at your stakeholder alignment on the Q2 roadmap. Here's where I see gaps. Let's talk through how you'd approach this differently."

Assignments and practice: Real work that stretches the PM into the area they're developing. "For next month's vendor evaluation, I want you to lead the competitive analysis. Let me review your draft and give feedback before it goes to stakeholders."

Feedback cycles: Feedback delivered soon after the event. Not "you struggled with stakeholder communication" six months later. But "I sat in your strategy session with engineering. Here's what happened well, here's where alignment broke down, here's what I'd do differently."

Reading/reflection: Specific resources that teach the skill. Not random "here's a good product book." But "read this chapter on competitive strategy, then tell me how it changes your thinking about our positioning."

Reverse coaching: Have the PM teach you or others. "You're getting really strong at pricing strategy. Can you walk the team through your thinking on the enterprise pricing model?" This forces them to articulate frameworks clearly.

Accountability: Review progress regularly. Monthly: "Are we seeing improvement? What's blocking progress? Do we need to adjust the plan?"

Step 6: Follow Up Relentlessly

This is where most coaching dies. You create a plan, have a few good conversations, then everyone gets busy and the PM falls back into old patterns. You have to follow up.

Every week, think about how this PM is doing on their growth area. Did they take the action you discussed? Did they implement the feedback? Are you seeing behavior change? Call it out: "I see you applying the competitive analysis framework to the new feature evaluation—that's exactly what we worked on. What made the difference?"

Celebrate progress publicly. "In the all-hands, mention that Sarah's stakeholder alignment has visibly improved—she got buy-in from the tough customer group." This signals that growth is valued.

When they backslide (and they will), don't shame them. "I notice the last strategy brief didn't have the competitive landscape analysis we discussed. What happened?" Maybe they forgot. Maybe something took priority. Maybe they didn't actually understand the framework. Address the actual reason.

Step 7: Coach Differently Based on Trajectory

Not all PMs develop the same way. Some need more structure, some more autonomy. Some need permission to take risks, some need guardrails. Adjust your coaching:

• High potential, new to role: More structure, more feedback, stretch assignments, clear framework for decision-making
• Solid performer, stable: More autonomy, focus on leveling up specific skills, consider technical depth vs. breadth
• Struggling: More observation, more feedback, more check-ins, maybe smaller scope while they develop
• Veteran capable of leading other PMs: Shift focus to how they're coaching their own reports

Your coaching method should match their readiness and the gaps.

Step 8: Know What Not to Coach

Not every gap is a coaching problem. Coaching works for skills. It doesn't work for:

• Misaligned values: If you believe in data-driven decisions and they fundamentally believe in intuition, coaching won't close that gap. Hiring and fit matter more than coaching.
• Lack of motivation: If they don't actually want to improve, coaching is theater. Have a direct conversation: "I see potential in you, and I also see you're not engaged in developing it. What's going on? Do you want to be a PM?"
• Capability gaps that are too wide: If they've never managed a large program and you need them to run a $50M bet now, coaching isn't enough. They need ramp time and possibly a different role first.

Output Format

Your coaching framework and plan should include:

Competency Framework (2-3 pages):

• 5-7 core competencies for PMs in your organization
• For each: definition, excellence indicators, development progression
• Tools: Bloom's taxonomy diagnostic, example behaviors at each level

Individual Coaching Plan (2-4 pages):

• PM name and assessment date
• Current state on competency framework (assessment for each area)
• Growth focus (1-2 priority areas, not trying to fix everything)
• Shared vision of improvement (specific, observable, time-bound)
• Development activities (coaching conversations, assignments, feedback cycles)
• Success metrics (how you'll know improvement happened)
• Monthly check-in schedule

Coaching Conversation Notes (ongoing):

• Date, topic, what you observed
• What you discussed and feedback you gave
• Assignment for PM before next conversation
• Progress on previous assignments
• Next focus area

Feedback for Growth (after key moments):

• Specific observation (what happened in the meeting/decision)
• What worked well (be specific, not generic praise)
• Where there's opportunity (frame as growth, not criticism)
• One thing to try differently next time
• Offer of support ("I'm here to help you practice this. Want to think through the next customer conversation together?")

Example

Scenario: Davit is VP of Product at Quantum Leap, a B2B analytics company. He has four product managers reporting to him. One, Keiko, is a solid performer with strategic chops but struggles with execution and detail—she misses important edge cases, ships with incomplete spec work, and her team says she's sometimes unclear about priorities. Davit wants to develop her into a director-level PM. He's creating a coaching plan.

Step 1 - Competency Framework (excerpt):

Quantum Leap PM Competencies:

1. Strategic thinking: Understanding market, competitive landscape, multi-year vision. Can articulate how quarterly work compounds.
2. Execution: Turning strategy into shipped product. Writing clear specs. Managing dependencies. Unblocking teams.
3. Decision-making: Gathering input. Making calls with incomplete information. Explaining trade-offs.
4. Stakeholder alignment: Including stakeholders early. Explaining decisions. Handling disagreement.
5. Communication: Writing strategy briefs. Running meetings where people actually engage. Explaining clearly across audiences.

For Execution, excellence means:

• Specs are detailed enough that engineering ships without questions
• Edge cases are identified proactively
• Dependencies are surfaced before they become blockers
• Team knows priorities clearly

Step 2 - Diagnosis (Bloom's Taxonomy):

Davit observes:

• Remember: Keiko knows what good execution looks like (she complains about her own specs)
• Understand: She understands why detail matters (she's seen bad specs blow up)
• Apply: She struggles to apply this to her own work (her specs lack edge cases)
• Analyze: She sometimes recognizes when specs are insufficient but not consistently

Diagnosis: This isn't a knowledge gap. It's an execution habit gap. She needs practice and feedback cycles, not teaching.

Step 3 - Aligned on Standards:

Davit: "I want to talk about execution. You're strategically sharp, but I see specs going out that are missing edge cases, and your team tells me priorities aren't always crystal clear. Here's what I think good execution looks like: [shares framework]. I see you at level 2 here—you understand what's important but aren't consistently hitting it. Does that match how you see it?"

Keiko: "Yeah, I know my specs could be more detailed. I get impatient to ship and feel like I'm over-engineering sometimes."

Davit: "That's one view. The other view is that clarity upfront saves rework later. You're fast and I don't want to slow you down. But I do want to help you be fast and clear. What would help?"

Keiko: "More structure probably. And feedback on my specs before they go to engineering."

Step 4 - Shared Vision:

Davit: "Here's what I'm imagining. In three months, your specs are clear enough that engineering ships the first time without clarifications. Your team knows priorities clearly because you've documented them and revisited them weekly. You've kept your speed. You're just adding a layer of clarity that actually makes things faster because there's less rework. Does that sound like the right direction?"

Keiko: "Yeah, that's the goal."

Step 5 - Development Plan:

Activities:

1. Weekly spec review: Keiko's spec draft reviewed by Davit 24 hours before engineering review. Feedback focusing on completeness and edge cases. ("What happens if customer has 10,000 users and the system slows? What happens on the free tier?")
2. Monthly priority documents: One-pager per product area showing top 3-5 priorities for the next 6 weeks. Shared with team. Revisited monthly.
3. Bias for documentation: Keiko writes down decisions and edge cases as she thinks through features. Review these docs in 1:1s.
4. Reading + reflection: "Cracking the PM Interview" chapter on requirements. Rewrite one spec using the framework.
5. Observation: Davit sits in one engineering kickoff per month to hear if specs are landing clearly.
6. Celebration: When engineering ships with zero spec clarifications, Davit mentions it: "Keiko's clarity on the new dashboard made this ship clean."

Step 6 - Follow Up:

Week 1: Keiko submits spec draft for feedback. Davit notes: "The core flow is clear. Missing: what happens if user has >100 charts to organize? What's the performance assumption?" Keiko revises.

Week 3: Keiko creates first quarterly priority document. Davit reviews. Good strategic framing, good prioritization, slightly unclear on Q3 scope. Feedback: "This is the direction. For Q3, can you say explicitly: 'We're shipping X and Y, we're not doing Z because [reason]'? Clarity on what we're NOT doing helps everyone."

Week 5: Engineering lead mentions specs have been clearer last month. Davit tells Keiko: "I heard from engineering that your recent specs have been more detailed and they're shipping faster because of it. That's the direction we wanted."

Month 2: Keiko is still rough on one feature spec. Davit: "This one's unclear on the filtering logic. I know you want to ship fast. What if we spend one more day on the edge cases here?" They work through it together. Keiko sees how depth now prevents rework later.

Month 3: Reassessment. Specs are notably clearer. Priority documents are being used by the team to say no to things. Keiko says: "I realized the upfront work saves me time overall because I don't spend weeks reworking." Davit: "Exactly. You've moved from fast to fast-and-clear. Next level: can you teach the other PMs how you're thinking about edge cases?"

Step 7 - Adjust for Growth:

As Keiko improves, Davit shifts coaching. Instead of reviewing every spec draft, he spot-checks. Focus moves to: How is she thinking about multi-quarter roadmap? Is she ready to mentor newer PMs? Can she take on larger scope?

Edge Cases

A PM doesn't want to be coached: This is a real problem. Coaching requires trust and openness. If a PM resists, first try to understand why. "I sense you're not interested in this development conversation. What's going on?" Maybe they feel criticized instead of supported. Maybe they don't agree with the framework. Maybe they're burned out. Address the real issue, not the surface resistance.

You lack credibility as a coach: You can't have been a PM 15 years ago and coach modern PMs on digital products effectively. Either develop credibility (work in the role yourself, stay deeply involved) or bring in external coaching. Don't pretend to know things you don't.

The PM's weakness is something you're also weak at: Great. Coach them anyway. "I also struggle with writing clear specifications. Here's what I'm learning..." This builds vulnerability and shows that growth is continuous. You're coaches together, not you perfect and them flawed.

The PM plateaus and stops improving: This could be a mindset issue. "Do you still want to grow here? Because I'm not seeing the improvement we discussed." Could be they hit their ceiling. That's okay—help them excel at their level rather than pushing for promotion. Could be external stress. "How are you doing? Is something blocking your focus right now?"

Multiple PMs have similar gaps: This suggests a framework or hiring issue, not individual coaching issues. Maybe your onboarding is weak, maybe you're hiring for the wrong traits, maybe your culture doesn't value execution. Address the system, not just the individuals.

A PM improves in coaching but reverts when you're not watching: They haven't internalized the behavior. They're performing for feedback, not actually changed. Coaching needs to continue until they own the change. "I see you've been slipping back on spec detail. What happened?" Help them understand what triggers the backslide and plan to handle it.