Turning Around an Underperforming PM (Before You Reach for a PIP)

Most PM underperformance gets treated as a talent verdict when it's actually a diagnosis problem. Before any formal process, identify whether the gap is a skill deficit, a motivation issue, unclear expectations, or a role mismatch — each demands a different fix. Skip the diagnosis and even a well-intentioned PIP just formalizes a failure you may have caused.

Quick answer: Diagnose before you formalize. Sort the gap into skill, will, clarity, or fit — each has a different remedy. Run a structured 30-60-90 day plan with explicit expectations and real support first. A PIP should document a failed turnaround, not substitute for one.

Why "Not Meeting the Bar" Is Usually a Diagnosis Failure

"Not meeting the bar" describes a symptom, not a cause. It tells you output has fallen short without telling you why — and most managers jump straight from that symptom to a remedy without separating "can't" from "won't" from "doesn't know what I actually want."

Gallup's decades of manager research put a number on how much this matters: across business units, managers account for a large share of the variance in team engagement and performance — directionally somewhere around two-thirds to three-quarters of it, by Gallup's own repeated estimates. That's not a reason to blame yourself for every gap on your team. It's a reason to rule out your own contribution before concluding the problem sits entirely with the PM.

A manager's job in a turnaround isn't to render a verdict on a person's talent. It's to figure out, with evidence, which of a small number of fixable things is actually broken.

The Hersey-Blanchard Situational Leadership Model is a useful, if old, lens here. It separates a person's competence (can they do the task) from their commitment (do they want to do it), and argues the right response differs for every combination. A PM low on both needs directive coaching. A PM high on skill but low on commitment needs a completely different conversation than one who's enthusiastic but genuinely under-skilled. Collapsing every case into one generic "step it up" conversation is where turnarounds fail before they start.

In practice, four root causes cover nearly every real case of PM underperformance:

• Skill — the PM doesn't yet have the capability the role requires.
• Will — the PM has the capability but isn't applying it, for reasons that may or may not be about the job.
• Clarity — the PM doesn't actually know what "good" looks like here, because nobody has defined it clearly.
• Fit — the PM is capable and motivated, but this specific role, team, or company shape is wrong for their strengths.

Misdiagnose any one of these as another and the intervention will look reasonable on paper while doing nothing. Coaching a fit problem just delays an outcome both sides already sense. Disciplining a clarity problem teaches a PM to fear ambiguity instead of resolving it.

The Four Root Causes: Skill, Will, Clarity, or Fit — and Why Each Needs a Different Remedy

Skill gaps call for training and paired execution. Will gaps call for a direct conversation about what's actually driving disengagement. Clarity gaps call for you to rewrite and re-communicate the standard before blaming the PM for missing it. Fit gaps call for an honest conversation about whether the role can ever work for this person. Apply the wrong remedy and you burn weeks of goodwill without closing anything.

Skill: the capability gap

A skill gap looks like a PM who tries, cares, and still produces weak prioritization calls, thin specs, or discovery that doesn't hold up under questioning. The fix is targeted training and paired execution — not more pressure, and not a longer to-do list.

Watch for specific tells instead of a vague "their work isn't good enough." A PM who can't distinguish a customer's underlying job to be done from a surface-level feature request will keep building the wrong things no matter how many hours they put in. A PM who can't sketch a customer journey to find where the real emotional low point sits will keep prioritizing polish over the moment that's actually costing you retention. These are teachable, learnable skills — not fixed traits.

The remedy: name the specific sub-skill, pair the PM with a stronger practitioner on the next two or three real artifacts, and review the work together rather than judging only the outcome. Common skill gaps worth naming explicitly:

• Applying prioritization frameworks (RICE, Kano, or a weighted-scoring model) consistently rather than by gut feel
• Writing specs that survive contact with skeptical stakeholders
• Running discovery that produces disconfirming evidence, not just validation of a favorite idea

Will: the motivation gap

A will gap looks like a PM who clearly can do the work — you've watched them do it before — but isn't. The honest first move is a direct conversation about what changed, not a quiet assumption that they've stopped caring.

Radical Candor, Kim Scott's framework for feedback, is useful precisely because it names the trap most managers fall into here: Ruinous Empathy — caring about someone so much you avoid telling them the plain truth, which lets a solvable motivation problem fester into a formal one.

The alternative isn't harshness; it's caring personally enough to ask directly what's driving the disengagement — burnout, a bad teammate match, a life event, or genuine disagreement with the team's direction. Then challenging directly enough to name what you're observing, without softening it into mush.

Will gaps resolve fastest when the manager treats them as a conversation to have, not a performance number to track. A PM who's disengaged because they've quietly checked out of the company's direction needs a different response than one who's disengaged because a reorg buried their strengths under work they never wanted.

Clarity: the expectations gap

A clarity gap looks like a PM who is working hard toward a target that was never actually defined — and discovers that only when the review lands. This is the root cause managers most often misattribute to the PM, because it's the one that implicates the manager.

Gallup's Q12 employee engagement survey has tracked this for decades, and one single item — "I know what is expected of me at work" — consistently shows up as one of the strongest predictors of performance and retention on the whole instrument.

If you've never written down, in observable terms, what "good" looks like for a spec, a prioritization call, or a stakeholder update, you don't have grounds to call a PM's version of it a failure. Setting product standards without becoming the bottleneck is the actual fix — a small number of explicit, written standards the PM can self-check against, rather than a standard that only lives in your head until it's violated.

Fit: the role-person mismatch

A fit gap looks like a PM who was genuinely strong somewhere else — a 0-to-1 team, a technical platform, a founder-led org — and is now struggling in a shape of role that draws on different strengths: heavy stakeholder navigation, a mature product with incremental gains, a matrixed org with five approvers per decision. Competence doesn't automatically transfer across role shapes, and a PM can be excellent and still be a poor fit for the specific job in front of them.

The table below separates the four causes by what they actually look like day to day, so you're diagnosing observed behavior rather than a gut read.

The Manager's Mirror: How Much of This Gap Did You Create?

Before you formalize anything, audit your own inputs. Did this PM receive a written definition of "good," a worked example to calibrate against, regular feedback on specific artifacts, and enough real time with you to course-correct before the gap became a review-cycle surprise? If the honest answer is no, part of this gap is a management gap — not only a talent gap.

This is uncomfortable precisely because it's easiest to skip. A PIP is an artifact you can point to; admitting your 1:1s became status updates instead of coaching is not. But the transition from doing the work yourself to enabling a team to do it is exactly where this failure mode originates for newer managers — you know what "good" looks like because you used to produce it, and you assume that knowledge transferred by osmosis instead of by explicit teaching.

Run this self-audit honestly before you write a single formal document:

• Have I put the standard in writing anywhere the PM can reference it, or does it only exist in my head until they miss it?
• Have I given specific feedback on their last three real artifacts (a spec, a prioritization call, a stakeholder update) — or only general sentiment ("good," "needs work")?
• Have I protected enough 1:1 time to actually coach, or have our 1:1s quietly become status-report theater?
• Would this PM be surprised to hear the word "underperforming" applied to them right now?
• Have I set product standards in a way that guides rather than bottlenecks their independent judgment?

If the last question's honest answer is "they'd be surprised," stop. You don't have a performance problem yet — you have a communication gap wearing a performance problem's clothes.

Building a Structured Turnaround Plan Before Any Formal Process

A turnaround plan is a written, time-boxed agreement — typically spanning 30, 60, and 90 days — that names the specific gap, states what "closed" looks like in observable terms, commits you to specific support, and sets checkpoints. It's what should exist before a PIP, not instead of one, and it's what makes a later formal process defensible if it becomes necessary.

Build it in this order:

1. Name the gap using the diagnosis above — skill, will, clarity, or fit — in one sentence, not a paragraph of adjectives.
2. Define "closed" in observable terms: not "be more strategic" but "the next three specs include an explicit tradeoff section with alternatives considered and rejected."
3. Commit to specific support, in writing: paired review sessions, a named peer to shadow, protected 1:1 time, or access to training — whatever matches the diagnosed cause.
4. Set a realistic timeline — 30/60/90 days is a common default, but scale it to how deeply embedded the gap is; a clarity gap can close in weeks, a skill gap often needs a full quarter.
5. Schedule checkpoints, not just a final verdict — a monthly review where both sides can see the trend, not a single pass/fail moment at the end.
6. Write down what happens if it doesn't close — plainly, so neither side is surprised later, and so the plan reads as support rather than a trap.

Naming the gap specifically, not vaguely

Vague framing is the single most common way a turnaround plan fails before it starts. "Be more strategic" or "raise your bar" gives a PM nothing concrete to act on, and it gives you nothing concrete to check against sixty days later.

Once the gap is named specifically, the conversations that follow get easier, too — including the ones about genuinely hard calls, where coaching a PM through a difficult tradeoff rather than making the call for them is often the fastest way to tell whether a skill gap is actually closing.

When Parting Ways Is the Kinder Choice

Sometimes real support over a real timeline still doesn't close the gap. When that happens, the kindest thing — for the PM and for the team around them — is to say so plainly rather than let a low-grade, unofficial PIP cycle drag on for two more quarters. The tell isn't manager impatience; it's a plateau below the bar despite genuine, documented support.

Delay has its own cost, and it isn't zero. SHRM's research on turnover has repeatedly estimated the cost of replacing an employee at roughly half to twice their annual salary once recruiting, onboarding, and lost productivity are counted. Letting a mismatch run indefinitely to avoid a hard conversation isn't kindness; it's cost deferral dressed as patience — and it rarely stays contained to just the one PM.

A few signals reliably separate a genuine fit problem from a turnaround still in progress:

• The gap hasn't moved across at least one full checkpoint cycle, despite a correct diagnosis and real, documented support.
• The PM's roadmap is visibly slipping, and the team is quietly losing confidence in calls that aren't landing.
• Peers or stakeholders have independently raised the same concern, unprompted, more than once.

The clearest of these is the first: the gap doesn't move even when the diagnosis was right and the support was real. At that point, a direct conversation about parting ways — with real notice, real support finding the next role, and honesty about why — respects the person more than another quarter of quiet disappointment.

This is one of the harder judgment calls a manager makes. It's covered in more depth as part of the complete guide to being a group lead PM, alongside the rest of what the role demands beyond any single report's turnaround.

Key Takeaways

• "Not meeting the bar" is a symptom, not a diagnosis — sort every case into skill, will, clarity, or fit before choosing a remedy.
• Skill gaps need paired execution and named sub-skills, not more pressure or a longer list of expectations.
• Will gaps need a direct conversation about what changed, using something like Radical Candor to avoid Ruinous Empathy — not a silent assumption of apathy.
• Clarity gaps are often the manager's own gap — Gallup's data on "knowing what's expected" makes this one of the highest-leverage fixes available.
• Run the manager's-mirror check before any formal process — if the PM would be surprised to hear "underperforming," you have a communication failure, not (yet) a performance one.
• A structured 30-60-90 day plan belongs before a PIP, with a specific gap named, support committed in writing, and checkpoints — not just a final verdict.
• Naming the specific competency that's breaking down — rather than a vague catch-all — is what makes both the plan and, if it comes to that, the formal process defensible.
• Sometimes the diagnosis is fit, and the kind choice is parting ways sooner rather than letting an unwinnable situation run for the sake of avoiding a hard conversation.