Principles of Product Management: Coaching and Mentoring (GROW Model, SBI Feedback)

Coaching and Mentoring (GROW Model, SBI Feedback)

Coaching and Mentoring (GROW Model, SBI Feedback) – Study Guide

What This Is

Coaching and mentoring are leadership tools to develop your team’s skills, align on goals, and give actionable feedback—critical for shipping successful products. A PM who coaches well accelerates decision-making, reduces misalignment, and builds a culture of ownership.
Example: At a SaaS startup, a PM uses the GROW Model to help a designer stuck on a feature’s UX. Instead of dictating the solution, the PM asks, “What’s the user’s biggest frustration here?” (Goal) and “What’s one small test we could run?” (Options). The designer proposes A/B testing two layouts, leading to a 20% lift in conversions.

Key Terms & Frameworks

• GROW Model: A coaching framework to structure conversations. Goal (what do you want?), Reality (where are you now?), Options (what could you do?), Will (what will you do?).
• SBI Feedback: Situation (context), Behavior (observed action), Impact (result). Used for clear, actionable feedback.
• Active Listening: Fully focusing on the speaker, paraphrasing, and asking open-ended questions (e.g., “What’s the biggest blocker for you?”).
• Psychological Safety: A team environment where people feel safe to take risks and admit mistakes (key for coaching).
• Feedforward: Future-focused feedback (e.g., “Next time, try X to improve Y”) instead of dwelling on past mistakes.
• 1:1s (Effective): Structured meetings with direct reports, focusing on growth, blockers, and alignment (not just status updates).
• SMART Goals: Specific, Measurable, Achievable, Relevant, Time-bound. Used to set clear coaching objectives.
• DACI: Driver, Approver, Contributors, Informed. Clarifies roles in decision-making (useful for coaching on ownership).
• Radical Candor: Caring personally while challenging directly (Kim Scott’s framework for feedback).
• GROW + SBI Combo: Use GROW to explore solutions, then SBI to give feedback on execution.

Step-by-Step / Process Flow

1. Coaching with the GROW Model

Scenario: Your engineer is hesitant to push a feature to production due to “gut feeling” risks.
1. Goal: Ask, “What’s the outcome you’re trying to achieve with this feature?” (e.g., “Reduce churn by 10%”).
2. Reality: “What data or user feedback do we have about the current state?” (e.g., “Users drop off at Step 3 of the flow”).
3. Options: “What are 2–3 ways we could test this safely?” (e.g., “Canary release, feature flag, or a smaller pilot”).
4. Will: “Which option will you commit to, and what’s the first step?” (e.g., “I’ll set up a feature flag by EOD”).

2. Giving Feedback with SBI

Scenario: Your PMM presented a confusing product narrative in a stakeholder review.
1. Situation: “During yesterday’s roadmap review with leadership…” 2. Behavior: “…you described the new feature as ‘revolutionary’ without explaining how it solves the user’s pain point.” 3. Impact: “This led to questions about ROI and delayed approval.” 4. Follow-up: “Next time, let’s anchor the narrative in user problems first.”

3. Running a 1:1 for Growth

1. Prep: Review notes from last 1:1 and their recent work.
2. Open: “What’s top of mind for you this week?” (Listen for blockers or goals.)
3. Coach: Use GROW for any challenges (e.g., “What’s one thing you’d do differently next sprint?”).
4. Feedback: Give 1–2 SBI examples (positive or constructive).
5. Close: “What’s one thing I can do to support you?” (Document action items.)

Common Mistakes

• Mistake: Telling instead of coaching. Correction: Ask questions (GROW) instead of giving answers. Why? People own solutions they discover themselves.

• Mistake: Vague feedback like “Great job!” or “This needs work.” Correction: Use SBI to make feedback specific. Why? Vague feedback doesn’t drive improvement.

• Mistake: Skipping the “Will” step in GROW. Correction: Always end with a commitment (e.g., “What will you do by Friday?”). Why? Without it, coaching feels theoretical.

• Mistake: Giving feedback in public (e.g., Slack, team meetings). Correction: Deliver critical feedback 1:1. Why? Public feedback can shame and reduce psychological safety.

• Mistake: Assuming coaching is only for underperformers. Correction: Coach high performers too (e.g., “How can we scale your impact?”). Why? Top talent wants growth, not just praise.

PM Interview / Practical Insights

1. “How would you coach an engineer who’s resistant to your product vision?”
2. Trap: Jumping to “convince them” or escalating to their manager.

3. Answer: Use GROW to uncover their concerns (e.g., “What’s your biggest worry about this approach?”). Then align on shared goals (e.g., “We both want to reduce churn—how can we test this safely?”).

4. “Give an example of feedback you gave that changed someone’s behavior.”

5. Trap: Focusing on the outcome, not the feedback method.

6. Answer: Use SBI (e.g., “In the last sprint review [Situation], you interrupted stakeholders [Behavior], which made them disengage [Impact]. Next time, let’s pause after each section for questions.”).

7. “How do you handle a 1:1 where the report says everything’s fine?”

8. Trap: Accepting “fine” at face value.

9. Answer: Dig deeper with open-ended questions (e.g., “What’s one thing you’re curious to learn this quarter?” or “What’s a recent win you’re proud of?”).

10. “When would you use GROW vs. SBI?”

11. Distinction: GROW = exploratory (e.g., problem-solving), SBI = evaluative (e.g., feedback on past work).

Quick Check Questions

1. Your designer says, “I don’t know how to improve this onboarding flow.” How do you respond?
2. Answer: Use GROW: “What’s the user’s biggest drop-off point?” (Reality) → “What are 2–3 hypotheses for why?” (Options).

3. Why? Coaching starts with understanding the problem, not prescribing solutions.

4. Your data scientist says, “The A/B test results are inconclusive.” You think they’re overcomplicating the analysis. How do you give feedback?

5. Answer: SBI: “In the last test review [Situation], you spent 20 minutes on edge cases [Behavior], which made the team lose focus on the core metric [Impact]. Next time, let’s start with the primary KPI.”

6. Why? Feedback should be specific, actionable, and tied to impact.

7. Your PMM keeps missing deadlines. In your 1:1, they say, “I’m just overwhelmed.” What’s your next step?

8. Answer: Use GROW: “What’s one task you could delegate or drop?” (Options) → “What’s the first step to make that happen?” (Will).
9. Why? Coaching helps them self-diagnose and commit to a solution.

Last-Minute Cram Sheet

1. GROW Model: Goal → Reality → Options → Will (always end with a commitment).
2. SBI Feedback: Situation (context) + Behavior (observed) + Impact (result).
3. Psychological safety is the foundation for effective coaching.
4. Active listening = paraphrase + open-ended questions (e.g., “What’s the trade-off here?”).
5. Feedforward > feedback (focus on future actions, not past mistakes).
6. 1:1s should be 80% listening, 20% talking (ask, don’t tell).
7. SMART goals make coaching objectives clear (e.g., “Ship 3 user interviews by Friday”).
8. Radical Candor = care personally + challenge directly.
9. ⚠️ Avoid “sandwich feedback” (good-bad-good)—it dilutes the message.
10. GROW + SBI combo: Use GROW to explore, SBI to give feedback on execution.