Managing Underperformance with Clarity and Kindness

There's a person on your team who isn't delivering, and you've known it for a while. You've dropped hints. You've quietly rerouted important work to others. You've vented to a peer manager. What you haven't done is say, plainly, "your performance isn't meeting the bar, and I want to fix that with you" — because it feels unkind.

Here's the reframe this entire article rests on: the avoidance is the unkindness. While you hesitate, the person is losing months they could spend improving (or finding a better-fitting job), your strongest people are absorbing the slack and quietly pricing your leadership, and the eventual conversation — because it always eventually happens — arrives with a year of accumulated frustration behind it, at maximum severity, with minimum runway. Clarity delivered early is the kind version. What follows is the full arc: diagnosis, the expectations reset, the support plan, documentation, and the two endings — done with enough structure that you can be honest without being brutal.

First, confirm it's real: the expectations audit

Before any conversation, interrogate your own side of the ledger, because a meaningful share of "underperformance" is manufactured by management. Ask yourself, honestly:

• Were expectations ever explicit? Not "they should know what senior means here" — did you state, in words, what good looks like for this role, this quarter? If the standard exists only in your head, the gap is a communication failure, not a performance one.
• Have they heard this before? If your feedback history with this person is a series of softened hints ("might be worth tightening up the testing a bit!"), they may genuinely believe things are fine. People cannot read your disappointment through a hedge.
• Is the bar consistent? Would you rate a favorite teammate's identical output the same way? Write down the standard first, then assess against it — in that order.
• Did the job change under them? The support engineer hired for ticket volume who's now expected to write automation didn't underperform; the role transformed and nobody renegotiated.
• Is it actually a performance gap, or a friction gap? Someone who annoys you in meetings but ships reliably is a style issue. Don't launder personal friction through performance language.

If the audit turns up your fingerprints — vague expectations, no prior feedback — the first move isn't a warning, it's a reset delivered with ownership: "I haven't been clear about expectations, and that's on me. I'm going to be clear now." The process from that point is the same; the framing is fairer.

Diagnose before you prescribe

"Underperformance" is a symptom with at least five distinct causes, and the treatment for each is different. Prescribing before diagnosing — the manager equivalent of "have you tried working harder?" — is why so many performance conversations produce hurt feelings and no change.

Cause	What it sounds like	What actually fixes it
Clarity — doesn't know what's expected	"I thought the priority was the refactor"	Explicit expectations, written priorities, examples of "good"
Capability — knows, can't yet do it	Effort is visible, output misses	Training, pairing, mentorship, scoped-down assignments that rebuild from wins
Capacity — could do it, but is drowning	Overload, meeting load, life events, health	Load rebalancing, temporary scope cut, leave — see workload triage
Motivation — could, but has stopped caring	Cynicism, minimum-viable effort, disengagement	Find the cause: stalled growth, unrewarded effort, broken trust, wrong work
Fit — wrong person-shaped hole	Chronic struggle despite effort and support	Role change or a well-managed exit

Three diagnostic notes from the field:

Capacity masquerades as capability constantly. The engineer "missing deadlines" who turns out to be on two on-call rotations, mentoring an intern, and caring for a parent doesn't need a performance plan; they need a manager who runs workload triage. Check load and life before questioning skill — the mechanics are in Burnout Prevention Is a Management Job.

Motivation problems are usually diagnostic of the system. A previously strong performer who has gone flat almost always has a reason: passed over, publicly overruled, promised something that evaporated, doing the same work for the third year. You can't feedback someone into caring; you have to find and fix (or honestly acknowledge) the cause.

Recency and singularity aren't patterns. One bad project after two good years is a conversation, not a process. Reserve the machinery of this article for sustained gaps — a quarter or more — or serious single events.

The diagnostic conversation itself is simple: describe the gap factually, then ask, and mean it: "That's what I'm seeing. Help me understand what's going on from your side." Then be quiet for as long as it takes. The answer determines everything downstream.

The expectations reset conversation

This is the pivotal conversation — the one where hints end. It has a structure, and the structure is what lets you be direct without being cruel.

Setup: private, unhurried (30–45 minutes), never an ambush appended to a routine sync. Scheduled as "I want to talk about how things are going — some of it will be direct." On a remote team this is a video call, always; performance conversations do not happen in chat.

The four movements:

1. State the gap, plainly, with instances. "I need to be direct: your performance over the last quarter isn't meeting the bar for your role, and I don't think I've said that clearly before. Concretely: the reporting migration slipped three weeks without a flag from you, the last two releases came back with bugs QA had already documented, and in planning you've committed to work twice and delivered neither time." Instances, not adjectives. A gap claim without instances is an accusation; with instances, it's a description the two of you can work on. Do not soften the headline — "not meeting the bar" must be said in words that cannot be misremembered as encouragement.
2. Diagnose together. "Help me understand what's going on." Listen. Genuinely update if new facts emerge — the reset conversation can end in load rebalancing instead of a plan, and that's a success, not a derailment.
3. Define the bar, specifically. "Here's what meeting expectations looks like in the next 30 days: committed work delivered on the date or flagged 48+ hours ahead; releases passing QA's documented cases; one written status update each Friday." Observable, countable, dated. "Be more reliable" is not a bar; it's a mood.
4. Offer real support and state the stakes honestly. "I'll meet you weekly on this specifically, and I'm pairing you with Ana on the release process. I want this to work — and I need you to know it's serious: if we're in the same place in 30 days, we'll be talking about whether this role is the right fit." The stakes sentence is the one managers skip, and skipping it is the cruelest available option — it produces the person who is stunned by a PIP because "nobody told me it was that serious."

Afterward, the same day, send a short written summary: the gap, the bar, the support, the check-in cadence, the timeline. Not as a legal maneuver — as clarity insurance. Memory under stress is unreliable in both directions.

If they push back

Some pushback is information ("the deadline slipped because sales added scope twice — here are the threads") — investigate before proceeding; you may owe an apology, and delivering it well costs you nothing and buys you enormous credibility. Some pushback is deflection ("everyone misses deadlines here"). Acknowledge and hold: "Other people's performance is my problem to manage with them. Right now we're talking about the pattern in your work, and the examples stand." You can be warm and immovable at the same time; in fact that combination is the whole skill.

The support plan: 30 days, structured, honest

Between "reset conversation" and "formal PIP" there should be an informal support plan — same clarity, lower stakes, real intent to succeed. Structure:

• Three goals maximum, each observable and dated. More than three means you haven't prioritized what actually matters. Good: "Ship the invoice export by June 27 with QA sign-off." Bad: "Improve ownership mindset."
• Named support per goal. Pairing sessions, a course, removed obligations, clearer specs — support is what makes the plan a plan rather than a countdown. If you can't name what you're contributing, you're not running a support plan; you're running out the clock.
• Weekly 30-minute check-ins, separate from (or a designated section of) the regular one-on-one, reviewing evidence against goals. These check-ins are where trajectory becomes obvious to both of you — which is the point. Nobody should be surprised at day 30. The check-in rhythm rides on your existing one-on-one discipline; if that's shaky, fix it first via One-on-Ones: The Manager's Most Important Meeting.
• A shared tracking doc. Goals at the top, weekly notes below, visible to both parties. Track it where work lives — a shared doc or a small board — so progress is evidence, not vibes. Openbook teams typically run this as a private Docs page plus the person's cards on the regular team board; the board matters because "delivered on commitments" should be verifiable from the same source of truth everyone else uses, not from a special surveillance apparatus.

Set the success criteria at "consistently meets the bar," not "walks on water." A common quiet injustice: the person on a plan gets held to a higher standard than their peers, guaranteeing failure. If your strongest performer would clear the plan's bar without noticing it, the bar is calibrated. Ownership norms that apply to everyone — visible commitments, honest status — are covered in Accountability Without Micromanagement.

And a hard rule for you: during the plan, route work to them normally. Managers who quietly divert everything important away from the person have already decided, and the plan is theater. If you've already decided, skip to the ending and be honest about it — theater wastes a month of everyone's dignity.

Documentation without dossier-building

Documentation has a deservedly bad reputation because most people encounter it as ammunition — the surprise folder of grievances produced at termination. Done honestly, it's the opposite: a shared, contemporaneous record that protects both parties from memory drift and ensures nothing said at the end is heard for the first time at the end.

Principles:

• Document as you go, not retroactively. A note written the week of the event is a record; six months of "incidents" reconstructed the week before a termination is a dossier, and courts, HR, and human beings can all tell the difference.
• Nothing in the file the person hasn't heard. Every documented item was said to their face first. The written summary after the reset conversation, the weekly check-in notes in the shared doc — the person has read all of it. Documentation that would surprise its subject is a process failure.
• Facts and quotes, not characterizations. "Committed to June 3, delivered June 17, no flag raised" survives scrutiny. "Continues to show poor ownership" is an opinion wearing a memo's clothing.
• Document the support too. The pairing sessions, the deadline relief, the training budget. A record showing only failures and no help describes a manager problem.
• Know your escalation point. The informal plan is between you two. The moment it becomes a formal PIP, involve HR and follow their process exactly — jurisdictions differ, and improvisation at the formal stage helps no one, including the employee.

Ending one: it works

Plans succeed more often than cynics expect — most often when the diagnosis was clarity or capacity, since those are management-fixable. When the 30 days end well:

Say so, unambiguously. "You hit all three goals, the last two releases were clean, and as far as I'm concerned we're done with this chapter. Thank you for how you took it on." The person has been living with a sword overhead; take it down visibly.

Then actually close the chapter. The improvement must be allowed to count. If, a year later, every disagreement gets refracted through "well, they were on a plan once," you've taught the team that recovery is impossible — which guarantees nobody ever tells you about a struggle again. Return them to normal footing: normal feedback cadence, normal shots at good projects, normal standing.

Keep one private thread of vigilance. Regression within a quarter is common enough to watch for, quietly, through the normal check-in signals. If the pattern returns, the next conversation is shorter and the formal stage closer — which is fair, and which the written record now supports honestly.

Ending two: it doesn't work

Sometimes the 30 days produce effort without results, or neither. Then you proceed to the formal stage — a PIP under HR's process — or, where the diagnosis is clearly fit, a direct conversation about parting ways. Three things distinguish a kind ending from a cruel one, and none of them is softness:

No surprise. By this point the person has heard the gap named plainly, seen the weekly evidence, and known the stakes for a month or more. The termination conversation should confirm a trajectory both of you can see — the cruelty of most firings is not the decision but the ambush, and the ambush is a management choice made months earlier.

No fake process. If the PIP is a formality with a predetermined end — as some are — the kind version is generosity elsewhere: a decent transition period or severance conversation instead of six weeks of doomed hoop-jumping. Whatever you do, don't run a fake plan while interviewing their replacement; people find out, and the whole team recalibrates its trust in you accordingly.

Dignity in the mechanics. The conversation is short, direct, and humane: the decision, the reasons (already familiar), the practical terms, genuine thanks for what was real. No relitigation — the decision is made, and reopening the case file at the end serves your comfort, not theirs. Afterward, tell the team the minimum with maximum class: "X is leaving us; their last day is Friday; here's the transition plan. We wish them well." The departing person's story is theirs to tell; your restraint here is also being watched, by everyone who now knows how they'd be treated.

One more reframe for your own conscience: keeping someone in a role where they chronically fail — visibly, to themselves and everyone — is not mercy. The strong version of kindness is honest standards, real help, and, when those don't converge, a respectful exit that frees them to find work where they're good again. Most people who exit a bad-fit role well say, a year later, that it was the push they needed. The ones who were strung along for two years say something else.

Special cases worth calling out

Three situations bend the standard playbook:

The struggling new hire. Inside the first 90 days, weigh onboarding failure heavily before performance failure. Did they get real documentation, a buddy, clear first-month goals — or a laptop and a wave? Run the diagnosis fast (weeks, not a quarter), fix the onboarding gaps you find, and give a genuinely clean second start. That said, serious early signals — misrepresented skills, behavior problems — should be acted on faster with new hires, not slower; the sunk cost is at its lifetime minimum and probationary frameworks exist for a reason.

The long-tenured decliner. A ten-year veteran whose performance has faded is the hardest case emotionally and the one managers defer longest. The bar doesn't change with tenure, but the diagnosis usually differs: the role often grew past them gradually, with nobody naming it. Be honest about that history in the reset ("the job you were great at and the job we need now have drifted apart — that happened on the company's watch too"), and consider role redesign seriously before plans: sometimes there is a genuinely valuable role shaped like what they still do excellently.

The remote report. Distance delays detection — you can't see the struggle forming, so gaps surface later and larger. Compensate with instrumentation you should have anyway: visible commitments on shared boards, written weekly updates, async check-ins. And be strict with yourself about evidence quality: "seems disengaged on video calls" is not an instance; "three committed cards slipped without a flag in two sprints" is. Remote performance management done on vibes reliably punishes the quiet and spares the charismatic.

What the rest of the team sees

You'll be tempted to treat all this as a private matter with one person. It is — and it's also the most-watched thing you do all year. Your team knows who isn't delivering; they knew before you acted. What they're learning from your handling:

• If you do nothing: standards here are decorative, and carrying a weak teammate is the strong performer's unpaid job. This is the single fastest way to lose your best people — they have options, and "my manager tolerates chronic underperformance" is on every exit-interview greatest-hits list.
• If you handle it harshly or gossip about it: struggling here is dangerous, so hide problems. Say nothing evaluative about the person to the team, ever; the discretion is the message.
• If you handle it with visible fairness — standards enforced, help genuinely given, dignity maintained, outcomes accepted: performance matters here and it's safe to struggle openly. That combination is precisely what psychological-safety research finds in high-performing teams — high standards and high safety are not a tradeoff; each makes the other credible. The feedback habits that keep small gaps from ever reaching this article's machinery are in Building a Feedback Culture That Does Not Sting.

Practical next steps

1. Name the person you've been avoiding. You thought of them in the first paragraph. Run the expectations audit on yourself this week — in writing.
2. Diagnose before acting. Book the diagnostic conversation: the gap with instances, then "help me understand," then silence.
3. Reset with all four movements — gap, diagnosis, bar, support-plus-stakes — and send the same-day written summary.
4. Run a real 30-day plan: three observable goals, named support, weekly check-ins, a shared tracking doc.
5. Pre-commit to both endings. Decide now what success and failure look like at day 30, so the day-30 conversation is a reading of evidence, not a fresh negotiation with your own conflict-avoidance.

Clarity and kindness are not opposing forces you balance. Delivered early, with evidence, support, and dignity, clarity is the kindness — and every month you delay it, you're choosing comfort for yourself over fairness to them.

If you want the infrastructure — shared one-on-one docs, boards that make commitments visible, and private notes that live next to the work — Openbook keeps all of it in one workspace. Start free at openbook.work.