How to Manage Underperformance Constructively
Managing underperformance is one of the tasks that managers most consistently avoid and organisations most consistently handle badly. The avoidance is understandable: the conversations are uncomfortable, the outcomes are uncertain, and most managers have not been properly trained to have them. The consequence of avoidance is invariably worse than the conversation itself: underperformance that is not addressed demoralises the wider team, creates legal risk when the organisation eventually decides to act, and often results in a worse outcome for the underperforming employee than early intervention would have produced.
The starting point for any underperformance conversation is definition. What specifically is not meeting the required standard? Vague feedback — "your work isn't quite right" or "we need you to step up" — is both unfair and ineffective. The manager must be able to describe, with specific examples, what the performance shortfall looks like and what meeting the standard would look like. Without that clarity, the employee cannot meaningfully improve, and any subsequent formal process will be procedurally weak.
An informal conversation is almost always the right starting point before a formal process. Many underperformance situations arise from factors that a conversation can address: unclear expectations, insufficient training, personal circumstances affecting concentration, or a mismatch between the role and the person's actual skills. A manager who genuinely tries to understand what is getting in the way, and addresses those factors, often resolves the situation without needing a formal process at all. The informal conversation is not a procedural step to be ticked — it is the first real attempt to solve the problem.
Where informal intervention has not worked, a formal performance improvement plan (PIP) is the standard tool. The PIP should define the specific performance standard required, the period for improvement (typically four to twelve weeks), the support available to the employee during that period, and the consequences if the standard is not met. The employee should have input into the plan where possible, and it should be reviewed regularly — weekly or fortnightly — rather than set and forgotten until the deadline.
The support element of a PIP is the one most organisations get wrong. A plan that identifies a performance gap, sets a target, and provides no meaningful support for achieving it is a managed exit in disguise. If the organisation genuinely wants the person to improve, the plan must identify what the manager will do differently, what training or coaching will be provided, and what resources are available. This good-faith effort also matters legally: tribunals and courts look unfavourably on PIPs that appear designed to document an exit rather than enable improvement.
Documentation throughout the process is critical. Every conversation about underperformance should be followed by a written record — a brief email confirming what was discussed, what was agreed, and the timeline for review. This documentation exists not to build a case against the employee but to create a shared record that prevents misunderstanding and demonstrates that the process was fair and that support was offered.
Mellow's performance module supports the full underperformance cycle: informal conversation logging, PIP creation and review scheduling, manager reminders, and case closure recording. The system ensures that the documentation is complete before any formal outcome is reached, protecting both the employee and the organisation. For HR teams juggling multiple active cases, having all of this in one place — rather than in email chains and shared drives — reduces the risk that something falls through the cracks.