The Underperformer Turnaround Playbook: From Warning Signs to Solid Contributor
Most managers intervene with underperformers too late and too formally.
They tolerate declining performance for months while hoping it self-corrects. Then , frustrated and out of options , they pull out the PIP template, which at that point feels more like a termination countdown than a genuine improvement effort.
The result: the employee feels blindsided, trust breaks down, and the "improvement" period is spent managing an exit instead of actually developing someone.
This playbook is for the gap between "I'm noticing a pattern" and "I need to write a formal PIP." That gap , typically 4–8 weeks , is where most underperformer situations are won or lost. Done well, this recipe resolves the majority of underperformance situations without escalating.
The Recipe at a Glance
Outcome you're trying to achieve: Move a person from declining or below-expectations performance to solid contribution, without a formal PIP , and if escalation is ultimately needed, do so with complete documentation and genuine attempts already on record.
Ingredients:
- Early detection signals (not just intuition)
- Root cause diagnosis before intervention
- A direct but non-threatening initial conversation
- A self-directed improvement plan (theirs, not yours)
- Short feedback loops
- A clear decision point at week 6
When to use this: When you've noticed a pattern of underperformance for 2–4 weeks and haven't yet addressed it directly.
When NOT to use this: Conduct violations, serious compliance failures, or situations where HR must be involved from the start.
Step 1: Catch the Warning Signs Early
The biggest mistake: waiting until the underperformance is undeniable before acting.
By then, the pattern is entrenched. The employee has rationalized it. Your other team members have adjusted around it. Reversing it requires more force and creates more disruption.
Early warning signals to watch for:
- Output quality drops first, then volume. People start cutting corners before they start missing deadlines. Catch quality issues early.
- Responsiveness shrinks. Slower replies to messages, slower turnaround on tasks. This often precedes more visible declines.
- Network contraction. In Confirm's ONA data, you can see this before it shows up in output , an employee who's becoming less central to their team's communication patterns is often disengaging before anyone's noticed.
- 1:1 energy changes. Less initiative in your meetings. Fewer questions. Less investment in conversations about their own growth.
- Peer signals. You'll often hear it sideways before you see it directly: "Is everything okay with [name]?" from teammates.
None of these alone means underperformance. A pattern across two or three is a signal to act.
Step 2: Diagnose Before You Intervene
Don't assume you know why performance is declining. You probably don't.
The four most common root causes:
| Root Cause | What It Looks Like | What Works |
|---|---|---|
| Skills gap | Can't do the work at the required level | Training, coaching, role adjustment |
| Clarity gap | Doesn't fully understand what's expected | Explicit expectations conversation |
| Motivation gap | Has stopped caring about this work | Career conversation, role redesign |
| Personal/external | Life situation affecting performance | Accommodation, time, support |
Most managers assume skills gap when the real issue is clarity or motivation. The intervention for each is completely different.
Diagnostic questions to ask yourself before the conversation:
- Have I been explicit about what success looks like in this role?
- Has anything changed about their workload, team composition, or work conditions recently?
- Do I know what's actually important to them about this job?
- Are they doing this consistently or is it concentrated in certain areas?
If you can't answer these, you don't have enough information to intervene effectively.
Step 3: The First Conversation , Early, Direct, Low-Stakes
This conversation is not a formal warning. It's a manager noticing a pattern and creating space to understand it.
Don't: Schedule a meeting with "I want to discuss your performance" in the subject line. That triggers defense mode.
Do: Bring it up in your next 1:1, in the last 10 minutes: "I want to share an observation and get your reaction."
Script:
"Over the last [X weeks], I've noticed [specific pattern: e.g., 'that the last three deliverables needed revisions I wouldn't have expected from you, and your response times to the team have gotten longer']. I'm not raising this as a formal concern , I want to understand what's going on from your side first. What's your read on how things have been going?"
Then stop talking. Let them respond.
Most people in this situation know the performance has dipped. They're often relieved someone named it. What they say next tells you the root cause and what's needed.
Do not: offer a solution in this first conversation. Your job here is to name the pattern, hear their response, and agree that you're both seeing it.
End with: "I appreciate you being straight with me. I'd like us to talk about what would help you get back to where you were. Can we spend 20 minutes on that this week?"
Step 4: Build the Improvement Plan , Theirs, Not Yours
The difference between a PIP and a development conversation isn't formality , it's ownership.
A PIP is a document HR prepares. A turnaround is a plan the employee creates.
In your follow-up conversation, after diagnosing the root cause:
Ask: "What would need to be different for you to consistently hit the standard we talked about?"
Let them build the plan. Your job is to react to it, push for specificity, and make sure it's achievable. Not to hand them a form.
The self-directed plan should include:
- The specific behavior they'll change (not the outcome , the behavior)
- What they need from you to do it (resources, clarity, reduced load, etc.)
- How they'll know they're improving
- A check-in structure they feel accountable to
Example: "I'll send you a quick Friday summary of what I shipped that week , that'll keep me accountable to showing up consistently instead of catching up in bursts. I'd also find it useful if you're more explicit when a deadline is truly hard versus flexible, because I've been guessing and getting it wrong."
That's a real plan. Write it down. You own the commitment to give them what they asked for from you. They own the rest.
Step 5: Short Feedback Loops for 3 Weeks
Monthly check-ins don't work for turnaround situations. The feedback loop has to be shorter.
Week 1–3 framework:
- Acknowledge positive moments in real time: "This is the turnaround we talked about , I noticed it."
- Address misses quickly, not at the end of the week: "Hey, that report came in two days late. I want to flag it now rather than wait. What happened?"
- Keep the weekly 1:1 10 minutes shorter than normal and end with: "How are you feeling about the plan we set?"
The goal of this phase is to break the old pattern with high-frequency evidence of the new one. Three weeks of consistent small wins resets what feels normal for the employee.
Document every check-in briefly , one to three sentences in Confirm or a notes file. You need this record.
Step 6: The Decision Point at Week 6
By week 6, you have enough data to make a clear decision.
Scenario A: Clear improvement The pattern has reversed. Keep reinforcing. Move to normal cadence. Note the recovery in your performance system so the next review reflects what actually happened.
Scenario B: Partial improvement with momentum Some things have changed, some haven't. Have an honest conversation: "Here's what I've seen improve. Here's what's still not there. I want to give you two more weeks, but I need to be transparent , if we're still here after that, I'll need to involve HR." This is still recovery territory.
Scenario C: No meaningful change You've had direct conversations, built a plan together, provided support, and documented throughout. The performance hasn't moved. It's time for a formal PIP , but you now have 6 weeks of documentation, genuine effort on both sides, and a clear record that this wasn't an ambush. That's a better position legally, morally, and interpersonally.
Why Most Managers Skip This Playbook
"It takes too long." Six weeks feels like a long time to tolerate underperformance. But most people who are turned around do it in weeks 3–5. The first two weeks are often the pattern bottoming out, not reversing.
"I don't want to be too soft." This recipe is direct, not soft. You're naming the problem in week one. The difference from a PIP is you're investing in recovery before escalating.
"I tried talking to them and it didn't help." One conversation isn't this recipe. This recipe is a structured 6-week intervention with documentation, root cause analysis, and short feedback loops. That's different from a single "you need to step it up" conversation.
Using Confirm for Underperformer Turnarounds
If you're running performance management in Confirm, three features make this recipe easier to execute:
-
ONA signals as early warning: Instead of waiting for output to decline, you see network contraction data before the performance dip shows up in deliverables. This lets you have the first conversation 3–4 weeks earlier , when it's much easier to address.
-
Continuous feedback logging: Every conversation and check-in goes into the employee's record, tied to their performance cycle. If you escalate to a formal PIP, HR has context , not a blank slate.
-
Goal tracking: The improvement plan from Step 4 can live as goals in Confirm, visible to both you and the employee. That transparency creates natural accountability without the surveillance feel of a PIP.
The Bottom Line
Most underperformance situations are resolvable. The people who become strong performers after a dip usually had one thing in common: a manager who caught it early, had a direct conversation, and built a plan together rather than waiting until the only tool left was a formal warning.
The recipe is six weeks. The first conversation is the hardest part. Everything after that is execution.
If your team's performance data lives in Confirm, you can set up continuous feedback and ONA monitoring → to catch these patterns before they become performance problems.
