Managing underperforming employees is one of the most challenging responsibilities a manager faces. Most managers handle it too slowly, too informally, or with language so softened that the employee genuinely does not understand the severity of the situation. The result: prolonged underperformance, a damaged team dynamic, and eventual escalation that feels sudden to the employee.

Identifying Underperforming Employees Early

Underperforming employees rarely become underperformers overnight. The signals appear gradually: missed deadlines quietly absorbed by colleagues, quality issues corrected without feedback, disengagement attributed to personality. The most common early indicators:

• Consistent pattern of missed deadlines or incomplete deliverables
• Quality of work noticeably below peers in similar roles
• Reduced responsiveness and decreasing participation in team discussions
• Colleagues beginning to work around rather than with the individual
• Repeated errors in judgment that go unacknowledged when raised

The First Conversation: Direct and Specific

The most important conversation about an underperforming employee is the first one — and it must be direct. Structure it around three elements:

• Specific observation: “In the last three sprints, your features had an average of four critical bugs at QA, compared to one for the team average.” Not: “Your code quality has been a bit of an issue.”
• Impact: “This is slowing down our release cycle and adding rework for the QA team.”
• Expectation and support: “I need to see you hit the team average on critical bug rate within the next sprint, and I want to pair you with Sarah on the most complex components.”

Documentation: Non-Negotiable from the Start

From the first performance conversation onward, document. Record the date, the concern raised, the expectation set, and the employee’s response. A written email summary sent after the conversation serves the same function as formal documentation and ensures the employee cannot later claim they were unaware of concerns.

When to Move to a Performance Improvement Plan

A performance improvement plan (PIP) is appropriate when coaching conversations have not produced the required improvement after a reasonable period — typically four to eight weeks. The PIP documents specific behaviors that must change, measurable success criteria, a timeline, and the support the organization will provide. See also: How to Write an Effective Performance Improvement Plan (PIP).

Root Causes of Underperformance

Before concluding that an employee is simply unwilling or unable to perform, investigate root causes. Underperforming employees are often the visible symptom of a systemic problem:

• Unclear expectations: The employee does not know what good looks like
• Missing skills: Role requirements changed and the employee was not developed to match
• Personal circumstances: Health, family, or wellbeing issues temporarily affecting performance
• Motivational mismatch: The role stopped aligning with what the employee finds meaningful
• Manager relationship: Breakdown in the working relationship reducing effectiveness

When Underperformance Cannot Be Turned Around

Some situations do not improve despite fair process and genuine support. When that happens, the most responsible outcome is separation — handled with dignity, clear documentation, and legal compliance. Tolerating persistent underperformance signals to high performers that results do not matter, and that drives top talent out over time.

What the Research Shows

According to SHRM’s research on performance management, the most common reason performance improvement efforts fail is not that the employee cannot improve — it is that the manager waited too long to raise concerns directly. Organizations where managers address underperformance within the first 30 days of identifying a pattern see significantly higher improvement rates than organizations where managers wait for the annual review cycle to surface concerns.

Early, direct, specific feedback is the most effective intervention for underperforming employees. The longer a performance gap persists without explicit acknowledgment, the more entrenched the behavior becomes and the more likely the employee is to be genuinely surprised when formal action is eventually taken. Building a practice of weekly performance observations and documented quarterly conversations reduces the probability of escalation by catching issues at the coaching stage rather than the formal action stage.