Scaling yourself as a senior PM means your leverage shifts from what you personally ship to how many good decisions other PMs can make without you. You do this by trading directives for coaching questions, matching your support style to each mentee's readiness on a given skill, and giving feedback that targets behavior, not identity.

Quick Answer: Stop giving answers and start asking the questions that surface the reasoning behind a decision. Use the situational leadership model to match your coaching style (directing, coaching, supporting, delegating) to each mentee's skill level per task, and use the SBI framework (Situation-Behavior-Impact) to deliver feedback that changes behavior without triggering defensiveness.

Most senior PMs hit this wall around their fifth or sixth year: the org keeps handing you more surface area, but you only have one brain and one calendar. The instinct is to work harder or work faster. Neither scales. The only lever that compounds is teaching other people to make the calls you'd make — which is a fundamentally different skill than making the calls yourself, and one most PMs are never explicitly taught.

Why "Just Give Them the Answer" Fails at Scale

Giving a mentee the answer feels efficient in the moment, but it trains dependency instead of judgment, so the same question comes back next week wearing a different outfit. Answers transfer conclusions; coaching transfers the reasoning process that generates conclusions repeatably.

Every time you fix a mentee's decision by telling them what to do, you're optimizing for a local outcome (this PRD gets better) at the cost of a global one (this PM gets better). The math is brutal if you run it out: a senior PM who mentors five PMs and only ever gives answers has, at best, six people's worth of one person's judgment. A senior PM who coaches those same five people into independent, well-calibrated decision-makers has effectively multiplied their own strategic thinking across five sets of hands.

This is the same shift covered in the complete guide to senior PM responsibilities: the job stops being measured by what you personally shipped and starts being measured by the quality of decisions happening in rooms you're not in. Mentoring is the mechanism, not a side project you do when you have spare time.

The Three Failure Modes of Well-Intentioned Mentors

Most senior PMs don't mentor badly on purpose — they fall into one of three traps, usually because nobody modeled a better way for them.

  • The Fixer: Rewrites the mentee's doc, prioritization call, or roadmap slide directly. Ships a better artifact today; produces a PM who can't self-diagnose next quarter.
  • The Abstainer: So worried about being a Fixer that they withhold any real input, leaving the mentee to guess at standards nobody stated out loud.
  • The Lecturer: Explains the "right" framework at length but never asks what the mentee already thinks, so the mentee nods along without internalizing anything.

The fix for all three is the same move: ask a real question before you offer an opinion, and calibrate how much structure you provide to what the mentee is actually ready to handle.

Coaching Questions: The Core Mechanic of Scaling Yourself

Coaching questions work because they force the mentee to articulate reasoning they may not have fully formed, which is where the actual learning happens — not in hearing your answer, but in doing the cognitive work themselves. A well-timed question does more for long-term judgment than a well-crafted directive.

The shift is from telling to asking, but not just any asking — leading questions that smuggle in your preferred answer ("don't you think we should prioritize the enterprise segment?") don't count. They're directives wearing a question mark. Genuine coaching questions are open, non-leading, and aimed at the mentee's reasoning rather than your conclusion.

Useful patterns to keep in your back pocket:

  1. "What outcome are you optimizing for here?" — surfaces whether the mentee has a clear success metric or is pattern-matching on activity.
  2. "What would have to be true for this to be the wrong call?" — forces them to name their own assumptions and risk.
  3. "Who else needs to agree with this, and what would change their mind?" — builds stakeholder awareness without you naming names.
  4. "What's the cheapest way to find out if you're wrong?" — nudges toward validation instead of conviction.
  5. "If you had to defend this to your skeptic, what's the weakest part of your argument?" — trains self-critique before a review does it for them.

Ask, then genuinely wait. Silence is uncomfortable, but filling it with your own answer defeats the exercise. If the mentee's answer reveals a real gap, that's your cue for a follow-up question, not a lecture.

A Worked Example: The PRD You Want to Fix

A mentee brings you a PRD that recommends building a self-serve onboarding flow to reduce support tickets. You can see immediately that the underlying problem is poorly defined — the ticket volume could stem from five different root causes, and self-serve onboarding only fixes one of them.

The Fixer move is to rewrite the problem statement yourself and hand it back "improved." Instead, try this sequence:

  • "Walk me through how you landed on self-serve onboarding as the solution."
  • "What other explanations did you consider for the ticket volume, and why did you rule them out?"
  • "If we shipped this and tickets didn't drop, what would that tell us?"

This mirrors the discipline in handling ambiguity tax on undefined problems: the real cost isn't a weak PRD, it's a PM who hasn't yet learned to interrogate a fuzzy problem before reaching for a solution. If your questions reveal the mentee jumped straight to a familiar pattern without diagnosing the ticket categories, that's the actual coaching moment — not the PRD's prose.

Resist the urge to measure success by "did the PRD get better this week." Measure it by "did the mentee's next PRD need fewer of my questions."

Sometimes the mentee's answers reveal they genuinely don't know a method — say, they've never used a Jobs to be Done lens to separate the job from the current solution. That's when you teach the framework directly, briefly, then hand the tool back to them to apply. Coaching questions and direct instruction aren't opposites; you choose based on whether the gap is reasoning or knowledge.

The Situational Leadership Model: Match Your Style to Their Readiness

Situational leadership, developed by Paul Hersey and Ken Blanchard in the 1970s, says your leadership style should shift based on a person's competence and confidence on a specific task — not on their tenure, title, or how much you generally trust them. The same PM might need directing on stakeholder negotiation and delegating on user research.

This single reframe fixes a common mentoring bug: treating "junior PM" as a fixed global setting instead of a per-skill variable. A PM who's been in the seat two years might already run rings around you on data analysis while still needing real structure on cross-functional influence.

StyleMentee readinessWhat you doCommon mistake
DirectingLow skill, variable confidence (new to the task)Give explicit steps, check work closelySkipping this stage out of a desire to seem hands-off
CoachingSome skill, still needs confidenceExplain the "why," ask questions, decide togetherReverting to pure directing once things go slightly wrong
SupportingSolid skill, confidence wavers under pressureAsk questions, listen, let them decide, back them publiclyWithholding a decision when they actually need reassurance, not more autonomy
DelegatingHigh skill, high confidenceSet the outcome, get out of the wayHovering out of habit after they've earned full autonomy

The practical use of this table is diagnostic. Before your next 1:1, name the specific skill you're discussing (not "PM skills" broadly — something like "writing a PRD problem statement" or "running a prioritization tradeoff") and place the mentee on this ladder for that skill alone. Then pick your style deliberately instead of defaulting to whatever mood you're in.

Moving Someone Up the Ladder Without Dropping Them

The failure mode isn't picking the wrong starting style — it's freezing there. A mentee who's ready to move from Coaching to Supporting on a skill will feel micromanaged if you keep asking permission-seeking questions designed for someone with lower confidence. Watch for two signals that it's time to shift:

  • They start pre-empting your questions in their own draft ("I considered X but ruled it out because Y").
  • They push back on your input with a reasoned counter-argument instead of just accepting it.

Both are evidence the skill has moved up a rung. Downshift the amount of structure you provide and see if performance holds — if it does, you've successfully delegated; if it dips, drop back one level rather than all the way to directing.

The SBI Feedback Framework: Making Feedback Land

The Situation-Behavior-Impact model, developed by the Center for Creative Leadership, structures feedback around a specific moment, the observable behavior in that moment, and its concrete effect — which keeps feedback about actions instead of character. That specificity is what makes feedback actionable rather than defensiveness-triggering.

Vague feedback ("your stakeholder communication needs work") gives the mentee nothing to change. SBI forces you to anchor on a real instance:

  • Situation: "In yesterday's roadmap review with the VP of Sales..."
  • Behavior: "...you presented three options without a recommendation..."
  • Impact: "...which meant the VP made the call instead of you, and it took an extra 20 minutes of debate to get there."

Applying SBI to a Mentoring Relationship

The same structure works just as well for positive feedback, which mentors chronically under-deliver relative to correction. Catch a mentee doing something well and name it with the same precision:

  1. Situation: the specific meeting, doc, or moment.
  2. Behavior: what they actually said or did — observable, not inferred.
  3. Impact: what changed because of it — for the stakeholder, the team, or the decision.

Deliver SBI feedback close to the event, privately for correction and often publicly for reinforcement, and always followed by a question ("what's your read on how that landed?") rather than a verdict. That question turns feedback back into coaching instead of a one-way pronouncement.

A mentee who consistently jumps into solutioning before the problem is scoped, for instance, benefits from SBI feedback paired with a pointer to a concrete method — like walking a customer journey to locate where the emotional friction actually lives before proposing a fix. Feedback names the pattern; the framework gives them a repeatable way to correct it themselves next time.

Mentoring Without Formal Authority

Most mentoring happens without a reporting line, which means your leverage is entirely earned through the value of the conversation, not organizational power. This makes coaching questions even more important, because you have no directive authority to fall back on if the mentee simply ignores your advice.

The dynamics here overlap heavily with leading peers you don't manage: you're influencing through credibility, curiosity, and the quality of your questions rather than through hierarchy. A mentee who feels coached rather than corrected is far more likely to seek you out voluntarily — which is the actual signal that the relationship is working.

A few practical norms that keep informal mentoring sustainable:

  • Set explicit boundaries on time and scope — a standing 30-minute biweekly slot beats ad hoc pings that erode your own capacity.
  • Ask what kind of help they want before giving it — "do you want me to just listen, ask questions, or give a direct opinion?" saves both of you friction.
  • Resist becoming their only sounding board — point them toward peers and other seniors too, so your absence isn't a single point of failure.

Where Prodinja Fits Into the Coaching Conversation

One recurring friction in mentoring is vocabulary: you know what "good stakeholder management" or "strong prioritization judgment" looks like, but describing it consistently across multiple mentees, over months, is hard to do from memory alone. Prodinja's Growth competencies are designed to give mentor and mentee a shared, structured vocabulary for exactly this — naming the specific skills you're coaching toward so a conversation about "getting better at tradeoffs" has the same reference points across every 1:1, rather than being reinvented each time. It doesn't replace the coaching conversation; it just gives the conversation a shared spine to hang progress on.

Key Takeaways

  • Coaching questions transfer reasoning, not conclusions — the mentee's answer, not yours, is where the learning happens.
  • Diagnose readiness per skill, not per person; use the situational leadership ladder (directing, coaching, supporting, delegating) to pick your level of structure deliberately.
  • Watch for signals a mentee is ready to move up a rung — pre-empting your questions or offering reasoned pushback — and downshift your structure accordingly.
  • Use SBI (Situation-Behavior-Impact) feedback for both correction and praise, anchored to a specific moment rather than a general trait.
  • Resist the urge to fix a mentee's artifact directly; interrogate the decision behind it instead, and only teach the framework directly when the gap is knowledge rather than reasoning.
  • A shared vocabulary for the competencies you're coaching toward — like Prodinja's Growth competencies — makes recurring mentoring conversations more consistent over time.

Frequently Asked Questions

How do I mentor a junior PM without micromanaging them?

Match your involvement to their actual readiness on the specific skill in question, using the situational leadership model, rather than defaulting to close oversight out of habit. Ask coaching questions before offering opinions, and deliberately shift toward supporting or delegating once you see them pre-empting your feedback in their own work.

What's the difference between coaching and mentoring a PM?

Coaching is a technique — using questions to help someone find their own answer — while mentoring is the broader relationship that might include coaching, direct instruction, sponsorship, and modeling. In practice, strong PM mentors lean on coaching questions as their default mode and switch to direct teaching only when the gap is missing knowledge rather than missing reasoning.

How often should senior PMs meet with the PMs they mentor?

A consistent, bounded cadence — commonly a biweekly 30-minute session — works better than ad hoc check-ins because it protects your own capacity and gives the mentee a reliable space to bring real decisions, not just quick questions. Reserve unscheduled time for genuinely urgent items rather than letting it become the default channel.

What should I do when a mentee pushes back on my feedback?

Treat pushback as a readiness signal rather than a problem to shut down — a reasoned counter-argument often means they're ready to move from coaching to supporting on that particular skill. Ask them to walk you through their reasoning before restating your view, since the disagreement itself may reveal the mentee has a valid point you hadn't fully weighed.

How do I give feedback to a mentee without damaging the relationship?

Use the SBI framework (Situation-Behavior-Impact) to anchor feedback to a specific, observable moment instead of a general character trait, which keeps the conversation about actions rather than identity. Follow it with a question about their own read on the situation so the feedback becomes a two-way coaching moment instead of a one-way verdict.