How to Handle Underperforming Employees Constructively

Dealing with an underperforming employee is one of the most challenging and emotionally taxing parts of being a manager. It's easy to ignore the problem, hoping it will resolve itself, but this is a disservice to the employee, the rest of the team, and the company.

Ignoring underperformance lowers the bar for everyone, creates resentment among high-performing team members who have to pick up the slack, and ultimately sets the underperforming employee up for failure.

The key is to approach the situation not as a punitive process, but as a diagnostic and supportive one. Your goal is to give the employee every opportunity to succeed while being clear about the required standard of performance.

Step 1: Diagnose the Root Cause (Don't Assume)

Before you can address the issue, you must understand it. Performance problems are rarely due to laziness or bad intent. They are often symptoms of a deeper issue. Your first job is to be a detective, not a judge.

During your next one-on-one, ask open-ended, non-accusatory questions to understand their perspective:

Is it a Skill Gap?
- Question: "I noticed some challenges with the recent data analysis task. How are you feeling about your SQL skills? Is there any training or support that would be helpful?"
- Possible Cause: The employee may lack the technical skills required for the role.
Is it a Clarity Gap?
- Question: "Let's review the goals for this project. From your perspective, what does success look like for your part in it?"
- Possible Cause: The employee may not have a clear understanding of what is expected of them.
Is it a Motivation Gap?
- Question: "I've noticed a shift in your engagement lately. How are you feeling about the work you're doing? Is it aligning with your career interests?"
- Possible Cause: The employee might be bored, burnt out, or feeling disconnected from the mission.
Is it a Personal Issue?
- Question: "I just wanted to check in. How are things going generally? Is there anything outside of work that's on your mind?"
- Possible Cause: The employee could be dealing with personal health issues, family problems, or other external stressors.

Often, you can resolve the issue at this stage by providing the right support—be it training, clearer goals, a more motivating project, or simply some empathy and flexibility.

Step 2: Provide Clear, Direct, and Documented Feedback

If the initial conversations don't lead to improvement, you need to be more direct. The worst thing you can do is be ambiguous. The employee must leave the conversation knowing that there is a performance issue that needs to be addressed.

Schedule a Formal Feedback Session: This is not a casual one-on-one. Signal the seriousness of the topic. "I'd like to schedule some time to discuss your performance and create a plan for success."
Use the SBI Framework: Rely on the Situation-Behavior-Impact model to keep the feedback objective and fact-based. Bring multiple, specific examples.
Be Direct: Avoid "feedback sandwiches" (praise, then criticism, then praise). This can dilute the message. Be compassionate but firm. "I'm bringing this up because your performance is not currently meeting the expectations for your role, and I want to help you get there."
Document Everything: After the meeting, send a follow-up email summarizing what was discussed, the gap between current performance and expectations, and the immediate actions you both agreed upon. This creates a paper trail and ensures there is no misunderstanding.

Step 3: Implement a Performance Improvement Plan (PIP)

If the behavior doesn't change after direct feedback, the next step is a formal Performance Improvement Plan (PIP). A PIP should not be a surprise, nor should it be a tool to push someone out. It is a final, formal opportunity for the employee to get back on track.

A well-structured PIP includes:

A Clear Statement of the Problem:
- "This document outlines a Performance Improvement Plan for [Employee Name] due to performance in the area of [e.g., Code Quality] not meeting the expectations for a [e.g., Senior Engineer] role."
Specific, Measurable Goals:
- Define exactly what success looks like. These must be objective and achievable goals, not vague statements.
- Instead of: "Improve your code quality."
- Try: "Over the next 30 days, 100% of your pull requests must have associated unit tests, and you must have fewer than 5 critical comments from senior reviewers per PR."
A Clear Timeline:
- A PIP typically lasts between 30 and 90 days. State the start and end dates clearly.
Defined Support and Resources:
- What will you, as the manager, do to help them succeed? This is crucial.
- Example: "We will provide a subscription to [SQL course], and you will have weekly paired programming sessions with [Senior Engineer]."
Regular Check-ins:
- Schedule weekly check-in meetings specifically to discuss progress on the PIP goals.
Clear Consequences:
- State clearly what will happen if the goals of the PIP are met, and what will happen if they are not.
- Example: "If the goals of this plan are met by [End Date], you will return to a standard performance management track. If the goals are not met, it may result in further disciplinary action, up to and including termination of employment."

A PIP should be created in partnership with HR to ensure it is fair, legal, and consistent with company policy.

The Difficult Decision

Throughout this process, you must be prepared for two outcomes. The best-case scenario is that the employee rises to the challenge, meets the goals of the PIP, and becomes a successful team member. This is a huge win for everyone.

However, you must also be prepared for the possibility that they will not improve. If you have provided clear feedback, ample support, and a fair PIP, and the performance issues persist, then the right decision for the team and the company is to part ways. While difficult, this is a necessary part of leadership.

Conclusion

Handling underperformance is a test of your leadership. It requires courage, compassion, and a commitment to a fair process. By diagnosing the root cause, providing clear and direct feedback, and using a formal PIP as a supportive tool, you give the employee the best possible chance to succeed while upholding the standards of performance for your team.

Frequently Asked Questions (FAQ)

Q: When is it too early to start this process?

A: It's never too early to have a supportive conversation about a potential issue. The diagnostic, informal feedback step should happen as soon as you notice a problem. You should only move to a formal PIP after several informal and direct feedback conversations have failed to resolve the issue.

Q: What if the employee becomes very emotional or upset?

A: Acknowledge their feelings with empathy. "I understand this is difficult to hear." Pause and give them space. It's important not to back down from the core message, but you can deliver it with kindness. Reiterate that your goal is to help them succeed.

Q: Can an employee ever recover from being on a PIP?

A: Absolutely. A well-executed PIP is designed to help someone succeed, not to push them out. Many employees who go through a structured PIP come out the other side as stronger, more self-aware team members. The key is that both the manager and the employee must be genuinely committed to the process.

Related Articles: