Stop Leading Like a PM: Adapting Your Leadership Style as a VP

The habits that made you an excellent PM — obsessing over details, deciding fast, staying hands-on in the work — become liabilities once you're leading leaders instead of a roadmap. Adapting your style means deliberately switching between directive, coaching, and delegating modes based on what a specific team, in a specific situation, actually needs from you right now.

Quick Answer: Use a directive mode only in real crises or with brand-new teams, coaching mode as your default with developing teams, and delegating mode with your strongest, most proven leaders. Match the mode to the team's maturity and the situation's stakes — not to your personal comfort zone.

Why the PM Instincts That Built Your Career Now Work Against You

Your PM strengths — relentless detail-orientation, fast and firm decisions, personal ownership of quality — scale down as you move up, because they were built for owning one product, not for building leaders who own many. Left unchecked, they read to your directs as micromanagement, impatience, and a quiet signal that you don't trust their judgment.

Ram Charan, Stephen Drotter, and James Noel named this problem directly in The Leadership Pipeline: every move to a new leadership level is a "passage" that requires letting go of skills that made you successful at the old level and picking up ones the new level actually values. A PM is rewarded for catching every edge case in a spec. A VP who keeps doing that on their directs' specs isn't adding rigor — they're signaling the spec isn't really theirs.

Decisiveness has the same trap. As a PM, deciding fast unblocked your own team and looked like leadership. As a VP, making the call for another leader's team on a decision that was theirs to make robs them of the judgment-building rep they needed — and quietly trains them to bring you decisions instead of options.

Marshall Goldsmith's core argument in What Got You Here Won't Get You There applies almost too neatly here: the very behaviors that get you promoted are frequently the exact ones you now need to dial back. Signs your PM instincts have curdled into VP liabilities:

• Directs bring you finished recommendations less often than they bring you half-formed questions, because they've learned you'll just tell them the answer.
• You've rewritten a document a direct wrote rather than sending comments and handing it back.
• Meetings you're in end with you having talked more than everyone else combined.
• You feel a flash of anxiety when you're not looped into a decision that isn't actually yours.
• Your best people are the ones pushing back hardest on how closely you're involved.

What Situational Leadership Actually Means for Product Leaders

Situational leadership, developed by Paul Hersey and Ken Blanchard, argues there's no single best leadership style — the right one depends on a person's competence and commitment for the specific task in front of them. For a VP of Product, that means running three or four different modes in the same week, sometimes the same day, depending on which leader and which problem you're facing.

The original Hersey-Blanchard model names four styles mapped to a follower's "readiness": directing for low competence, coaching for some competence but shaky confidence, supporting for high competence with variable commitment, and delegating for high competence paired with high commitment. Daniel Goleman's HBR piece "Leadership That Gets Results" arrived at a compatible finding from organizational climate data across six styles — and reported that the coercive and pacesetting styles, when leaned on as a default rather than an occasional tool, most reliably damaged team climate and results over time.

For day-to-day VP use, three collapsed modes are more workable than four or six:

Notice what's absent from that table: a mode where you do the work yourself. That's the PM instinct talking — as a VP, "doing it yourself" isn't a fourth option, it's a failure to pick one of the three.

Matching Your Mode to Team Maturity and Crisis Level

The two variables that should drive your mode are the team's maturity — their proven track record and confidence with this class of problem — and the crisis level: how much real time pressure and downside risk is actually in play right now, not how urgent it feels. Cross those two variables and the right mode falls out almost automatically.

Two rules keep this matrix honest. First, crisis level decays — the acute phase of an incident is not the same situation three days later, and staying directive after the emergency passes is how a VP trains a team to wait for orders permanently. Second, don't let your discomfort masquerade as team immaturity; a team can be highly mature on a decision you simply feel anxious about.

High-maturity teams in the delegating column deserve real ownership, not oversight with extra steps. That's the same instinct behind building a product operating model that runs without you: the goal isn't fewer meetings, it's a team whose judgment you'd trust even on a day you're not in the room. When a crisis does force a directive mode into a genuinely high-stakes moment — say, a date the organization has already committed to leadership — it's worth pairing the directive call with the same clarity you'd bring to building a board-ready product narrative, so the team understands not just what you decided but the constraint that forced it.

The Self-Audit: Is Your Detail-Obsession or Decisiveness Becoming a Liability

The traits behind most VP self-audits aren't flaws — they're strengths that never got recalibrated for a bigger team. The question isn't "should I stop caring about detail or being decisive," it's "where, specifically, is this trait now doing more harm than good."

Run this five-question self-audit honestly, ideally with input from a direct you trust to be candid:

1. When was the last time a direct brought you a fully-formed recommendation you simply approved, versus a half-formed question you had to finish?
2. How many of the last ten decisions in your group did you make that weren't actually yours to make?
3. If you took a two-week vacation with no laptop, which of your directs' workstreams would stall, and why?
4. Do you know the difference between a decision this team hasn't earned yet and one you just don't feel comfortable letting go of?
5. When you give feedback, does it arrive as a question that builds their judgment, or as the answer that replaces it?

Same Situation, Two Ways: A Concrete Example

The clearest way to see the difference between modes is the same facts run through both. Picture a launch two weeks out: a customer journey mapping exercise the team ran late in the cycle just surfaced a serious onboarding friction point, and now scope-cut versus slip is on the table.

Handled directively: You step in, review the friction point yourself, and make the call — cut the onboarding flow to the minimum viable version, hold the date, because this date was already committed in the narrative you presented to the board. You tell the team what to do and why in one short message, then check in daily until ship. This is the right call if the team is new, if the date is a genuine external constraint, or if this specific class of trade-off (scope versus date, with a hard external commitment) isn't one they've navigated before.

Handled through coaching: You frame the decision criteria — protect the launch date unless the friction point blocks a job the customer is clearly trying to get done — and ask the PM to bring a recommendation grounded in the team's jobs-to-be-done analysis of what onboarding is actually for. The team presents two options with trade-offs; you ask clarifying questions, pressure-test the weakest assumption, and let them decide. You ratify, you don't override. This is the right call if the team has handled scope-versus-date calls before and the crisis is self-inflicted rather than externally forced.

Same facts, same VP, same two weeks to launch — but two entirely different leadership acts. The choice of mode, not the underlying facts, is what determined which one was right, and getting that choice backwards in either direction is its own failure mode: directive on a team that had earned autonomy reads as distrust, coaching in a real fire reads as abdication.

Building the Muscle: How to Practice Range Without Losing Your Edge

Range is a practiced skill, not a personality overhaul — you don't need to become a different person, you need a bigger repertoire and the judgment to know which tool the moment calls for. Three habits build that faster than reflection alone.

1. Name your mode out loud. Tell the team explicitly — "I'm going to be directive on this one because of the deadline" — so they experience it as a deliberate choice, not a mood.
2. Attach a sunset clause to every directive intervention. Decide up front when you'll hand the decision back, and actually hand it back, even if it feels earlier than comfortable.
3. Ask directs which mode they experienced, not which mode you intended. The gap between those two answers is usually where the real feedback lives.

If you're still mapping the broader shape of the role beyond leadership style — the mandate, the metrics, the org design decisions that come with the title — the complete guide to the VP of Product role is a useful next stop, as is thinking through how you keep a dozen stakeholders aligned behind one roadmap rather than negotiating it fresh with each one.

The hard part of all this is that your default mode is largely invisible to you — it just feels like "how I lead," not a choice among several. That's the gap Prodinja's Leadership Suite is built around: its Leadership Styles module is designed to help you see your own default pattern and surface where it's likely helping versus where it's quietly working against you across different team and crisis situations, rather than relying solely on your own read of your reputation.

Key Takeaways

• Your PM instincts don't disappear at VP — they miscalibrate. Detail-obsession and decisiveness were strengths built for owning one product; unmanaged, they read as distrust once you're leading leaders.
• Situational leadership, from Hersey and Blanchard, means matching your mode to the person and task, not defaulting to whichever style feels most natural to you.
• Three practical modes cover most VP situations: directive (crisis, new teams), coaching (developing leaders — your default), and delegating (proven leaders on familiar problems).
• Cross team maturity with actual crisis level, not felt urgency, to choose the right mode — and let crisis-driven directive modes expire as soon as the acute phase passes.
• A five-question self-audit — who brings you finished recommendations versus half-formed questions, and what would stall if you vanished for two weeks — surfaces liabilities faster than intuition.
• The same facts can justify opposite leadership acts; the mode you choose, not the underlying situation, determines whether the outcome feels like support or a takeover.
• Range is a practiced skill: name your mode out loud, attach a sunset clause to directive interventions, and ask directs what mode they experienced rather than what you intended.