Recognising the Early Signs of Employee Underperformance

What this Guide will help you do

Managers will be able to recognise credible early indicators, establish the facts and choose a proportionate response before a manageable issue becomes a formal performance problem.

Understand the problem or objective

Underperformance rarely begins with one dramatic failure. It usually appears as a pattern: deadlines start to slip, standards become less reliable, customer issues increase or the person needs more prompting than before. Each event may look minor. Together, they tell a different story.

Managers can make two costly mistakes. The first is waiting until frustration has built and the evidence is difficult to reconstruct. The second is deciding too quickly that the employee has a poor attitude when the real cause may be unclear expectations, missing capability, low confidence, personal pressure or a barrier in the working environment.

The purpose of early intervention is not to build a case against someone. It is to understand what has changed while there is still time to help them recover. Fair early action protects both the employee and the business.

Assess the current position

• Compare current performance with an agreed standard, not with the strongest person in the team.
• Look for a pattern across quality, output, reliability, behaviour and customer impact rather than relying on one incident.
• Check whether the expectation was clearly explained and whether the person had the tools, training, time and authority to meet it.
• Separate what you observed from what you inferred. ‘Three orders were entered incorrectly’ is evidence. ‘They no longer care’ is an assumption.
• Consider what else changed: workload, role boundaries, systems, team relationships, health, confidence or management support.

Use a fair early-warning framework

Review five areas before deciding that underperformance exists: clarity, capability, capacity, conduct and context. Clarity asks whether the standard, priority and deadline were understood. Capability asks whether the person has the knowledge and skill. Capacity asks whether workload, systems or resources make the standard achievable. Conduct covers choices and behaviours within the employee’s control. Context considers relevant changes such as role design, team relationships, confidence, health or personal pressure.

The framework prevents a manager from jumping from a disappointing result to a conclusion about attitude. More than one factor may be present. A capable employee may be overloaded; a willing employee may not understand the standard; a previously reliable employee may be working around a process failure. The response should address the evidenced cause, not the manager’s first assumption.

Build an evidence record that is useful and proportionate

Keep notes factual, relevant and brief. Record the date, the agreed standard, what happened, the effect on work or customers, the employee’s explanation, support agreed and the review point. Include improvement and examples of acceptable performance as well as gaps. Avoid private speculation, medical conclusions or comments that would be unfair if read by the employee.

Use comparable evidence. If the issue is order accuracy, compare against the person’s role standard and a reasonable period, not one unusually strong colleague. If the concern is reliability, distinguish an isolated event from a pattern. Where records may become part of a formal employment process, follow company policy and obtain appropriate HR or legal advice.

Follow the recommended steps

1. Define the standard. Write down what satisfactory performance looks like in clear, observable terms.
2. Gather a balanced picture. Use recent examples, relevant measures and direct observation. Include what is still going well.
3. Start early and privately. Raise the pattern before it becomes a grievance shared with everyone except the employee.
4. Ask before concluding. Explain what you have noticed, then ask for their view and listen for causes you may not see.
5. Agree the immediate correction. Set a small number of clear expectations, support actions and a review date.
6. Follow through. Check progress when promised. Recognise improvement and address continued gaps directly.

Avoid these common mistakes

• Using labels such as lazy, negative or unreliable instead of describing behaviour and impact.
• Saving several months of frustration for one heavy conversation.
• Confusing a capability gap with unwillingness, or a workload problem with poor attitude.
• Making vague requests to improve without defining what must change by when.
• Offering support but failing to confirm whether it was used or effective.

Choose the right level of response

• Coaching response: use when the standard is understood but confidence, judgement or technique needs development.
• Support response: use when training, workload, tools, role clarity or a process barrier is contributing to the gap.
• Clear management expectation: use when the person can meet the standard but behaviour or follow-through remains inconsistent.
• Formal advice or process: consider when the concern is serious, repeated, disputed or may involve conduct, health, discrimination, capability procedure or dismissal risk.

Early action should be proportionate. The aim is not to make every concern formal. It is to stop avoidable drift, give the employee a fair opportunity to improve and protect the business if the position does not recover.

Structure the first conversation

Open with the purpose: to understand what has changed and agree what needs to happen next. Describe two or three recent examples, the expected standard and the practical impact. Ask for the employee’s view before offering your interpretation. Summarise the points you agree, clarify any disagreement, then record the actions, support, measures and review date.

A useful close is: ‘We have agreed what good looks like, what support is available and when we will review progress.’ The employee should leave knowing the required result and how improvement will be judged. The manager should leave with a small number of actions rather than an unfocused list of frustrations.

Example: from assumption to useful action

A counter colleague who was normally dependable begins making pricing errors and avoiding complex customer enquiries. The manager initially assumes motivation has dropped. A private conversation shows that a recent system change was explained during a busy shift and the colleague is unsure how to check overrides. The manager arranges focused coaching, provides a clear check process and reviews accuracy after two weeks. If the standard returns, the cause was capability and confidence, not attitude. If it does not, the manager now has a fair evidence base for the next response.

Put the approach into practice

Choose one live situation rather than trying to change everything at once. Apply the steps, record what you observed and agree a clear review point. The purpose is to improve the quality of the next decision, conversation or management routine before extending the approach more widely.

Review whether it is working

• Is the required standard now understood by both people?
• Has the agreed behaviour or result improved consistently, not only immediately after the conversation?
• Has any training, resource or process barrier been addressed?
• Is the manager keeping fair notes based on evidence?
• Does the matter require a more formal process or appropriate HR advice?

Move from guidance to implementation

Use this Guide to recognise and clarify the issue. If structured improvement management or a difficult formal conversation is needed, use the linked Toolkits for the complete planning documents, meeting structure, evidence controls and review process.

About the author

Nick Summers is a Business Growth Coach and trade merchant specialist with more than 25 years of leadership, operational and commercial experience across branch, regional and board-level roles.