A capability conversation becomes harder when it starts too late. By the time a manager speaks, frustration may have built on both sides and the employee may hear the meeting as a conclusion rather than an opportunity to improve.
The aim is not to make a difficult message soft. It is to make it clear, evidence-based and fair.
Prepare the facts, not the verdict
Before the meeting, separate observation from assumption. “The weekly report was submitted after the deadline on three occasions” is an observation. “You do not care about the team” is an interpretation.
Bring a small number of specific examples, the relevant expected standard and any earlier support or feedback. Check whether the employee has already raised a health issue, disability, workload problem, training gap or other factor that may require a different response.
Avoid preparing a script that leaves no room to listen. The manager should know the message that must be conveyed, but remain open to information that changes the next step.
Open with purpose and tone
A useful opening is direct and neutral:
This tells the employee what the meeting is about without presenting the outcome as fixed.
Describe impact without exaggeration
Explain why the issue matters. Link the example to customers, colleagues, safety, quality or delivery. Keep the impact proportionate. Inflated language can make a manageable concern feel disciplinary before the facts have been explored.
Then pause. Ask an open question such as, “What has been getting in the way?” or “Is there anything affecting your ability to meet this standard?”
Listen for practical causes: unclear priorities, changing instructions, an unrealistic workload, missing skills, poor handovers or a personal factor. Understanding cause does not remove accountability; it helps identify the right support and expectation.
Agree a small, observable improvement plan
“Improve communication” is too vague. A useful plan states what the employee will do, what the manager will provide and how progress will be reviewed.
For example:
- submit the weekly report by 3pm each Friday;
- use the agreed template;
- flag a likely delay by midday, with the reason and a revised time;
- attend a refresher session on the reporting system; and
- review progress after four weeks.
Confirm how success will be evidenced and what may happen if the required improvement is not achieved. Clarity about possible consequences is fairer than an ambiguous warning.
Close with a shared record
Summarise the concern, the employee’s explanation, agreed support, expected standard and review date. Invite the employee to correct factual inaccuracies in the note.
The record should show a balanced process, not simply build a case against someone. Include what the manager committed to do and any issues that need separate follow-up.
When to pause and seek advice
Take advice before proceeding if the conversation raises disability, pregnancy, family leave, whistleblowing, discrimination, a grievance, significant ill health or another protected or legally sensitive matter. Also pause if the situation may be misconduct rather than capability; the distinction affects the appropriate process.
A fair capability conversation is firm enough to make the standard unmistakable and open enough to understand what is really happening. That combination reduces unnecessary escalation and gives improvement a credible chance.
