Underperformance is a sustained pattern where an employee's output, behavior, or decision-making falls short of the expectations set for their role, with measurable impact on team results.
The word 'sustained' matters. A missed deadline is an incident. A pattern of missed deadlines is underperformance. The distinction matters because the management response is different: an incident requires a conversation, a pattern requires a plan.
Key takeaways
- Underperformance identified early is almost always recoverable. The same issue identified six months later usually is not.
- The manager's role is to name the gap clearly and create the conditions for improvement, not to hope the problem resolves itself.
- Ambiguity is the enemy of correction: the employee must understand specifically what is not meeting the bar and what meeting it looks like.
- Documenting underperformance conversations is not punitive; it is the record that makes future decisions defensible.
Why it matters
Most underperformance situations that end in termination were visible six to twelve months before anyone acted. The manager saw the pattern, felt uncertain about naming it, hoped for improvement, and delayed. By the time the conversation happened, the situation was entrenched and the employee had often concluded that their performance was acceptable because no one had said otherwise.
Delayed intervention is expensive in multiple directions. The team absorbs the gap in output, often silently and resentfully. Other employees conclude that underperformance is tolerated, which affects their own standards. And the employee who is underperforming is denied the information they need to make a real choice about whether they want to meet the bar or move on.
Addressing underperformance is an execution function, not an HR compliance exercise. The manager who handles it well keeps the team's output intact, signals that commitments matter, and sometimes recovers a valuable person who simply needed clarity.
How it works in practice
How to address underperformance without letting it become a crisis
-
Name the pattern, not the incident
Cite the specific pattern you have observed over time, not just the most recent event. 'The last three sprints delivered below the agreed scope' is a pattern. 'Last week's delivery was late' is an incident. One requires a plan; the other requires a conversation.
-
Separate observation from judgment
Describe what you have seen without attributing cause. 'I've noticed delivery time has increased and two items from Q2 remain unresolved' opens a conversation. 'You seem disengaged' closes one.
-
Set a specific standard for improvement
Tell the person exactly what meeting the bar looks like over the next 30 to 60 days. Vague encouragement is not a plan. Specific outcomes with a timeframe are.
-
Document the conversation the same day
Write down what was said, what was agreed, and what the consequence of continued underperformance is. Do not wait. Memory degrades and the written record is what makes later decisions defensible.
-
Check in weekly, not at the 30-day mark
Weekly check-ins during a recovery period serve two purposes: they give the person feedback in real time, and they give you early signal on whether the plan is working before the formal deadline.
Common mistakes
Hoping the person will self-correct
They almost never do without feedback. If the behavior has been visible for more than a few weeks without a direct conversation, the person has likely concluded it is acceptable.
Framing criticism as praise
'I know you can do better' is not feedback. It tells the person they have failed without telling them how to succeed. Name the gap directly.
Skipping documentation
An undocumented performance conversation is a conversation that, legally and operationally, did not happen. Document every substantive exchange about performance, even if it was informal.
Setting a plan without a consequence
A performance improvement plan without a stated consequence for continued underperformance is not a plan. It is a request. Name what happens if the plan does not succeed.
What it sounds like
Team retrospective follow-up. Daniel manages a product team. Merav is a mid-level PM whose two recent launches both slipped by more than three weeks.
Daniel: “Merav, I want to be direct with you. The last two launches both slipped by three-plus weeks. I’ve traced both back to dependency sign-off that wasn’t chased until it was too late. That’s the pattern I need us to address.”
Merav: “I didn’t realize that was visible as a pattern. I thought each situation was its own thing.”
Guy: “That’s actually helpful to hear, Merav, and it tells me we need a clearer system for flagging dependency risk earlier. Daniel, what’s the specific checkpoint you’d want Merav to own for the next cycle?”
Questions managers actually ask
How do I know when I'm dealing with underperformance versus a bad quarter?
A bad quarter is time-bounded and has an identifiable external cause. Underperformance is a pattern that persists across quarters and is not fully explained by external factors. If you can point to a specific root cause that has since changed, it may be a bad quarter. If the pattern continues regardless of circumstances, it is underperformance.
Do I need HR involved before I have the conversation?
For an initial performance conversation, no. For a formal improvement plan or any conversation that might lead to termination, yes. Get HR aligned before you set formal consequences.
What if the underperformance is partly my fault as a manager?
Almost all underperformance has a management component: unclear expectations, insufficient feedback, the wrong role assignment. Acknowledge your contribution without letting it become an excuse to avoid naming the gap. 'I haven't given you clear enough feedback on this, and I'm correcting that now' is both honest and effective.
How long should a performance improvement plan run?
30 to 60 days for most roles. Long enough to demonstrate meaningful change, short enough to maintain urgency. 90 days is usually too long: the situation drifts and the plan loses its structure.
What if the person is a high performer in some areas and underperforming in others?
Treat each dimension separately. Acknowledge the strength areas specifically, and name the gap areas with equal specificity. A mixed review that averages the two is less useful than one that is honest about both.
What if my underperforming employee disagrees that there's a problem?
Show them the evidence. Specific examples are harder to dispute than general assessments. If they continue to dispute the evidence, document the disagreement alongside your assessment and proceed with the plan. Consensus is useful but not required.
See how Leap improves execution in your meetings
Leap sits in your meetings, captures decisions and owners in real time, and shows you where execution breaks down before the week is out.