Poor employee performance can be difficult to address because the problem is often described too broadly. “Not committed,” “has a bad attitude,” or “is not a team player” may express frustration, but those labels do not tell an employee what must change. Effective performance management starts with observable behavior, fair expectations, and a reasonable opportunity to improve. The following poor employee performance examples show how to identify specific concerns, discuss them professionally, and establish practical next steps without turning a performance conversation into a personal attack.
Poor Employee Performance Examples and Practical Ways to Address Them
#1. Missing Deadlines Repeatedly
An employee who regularly misses deadlines can delay other people’s work, frustrate customers, and make planning unreliable. Before addressing the issue, distinguish between an occasional missed deadline caused by changing priorities and a recurring pattern that the employee has not communicated. Review specific assignments, agreed due dates, and whether the employee raised obstacles early enough for the situation to be managed.
Discuss the impact without assuming the employee is careless or unmotivated. Ask whether the workload, instructions, resources, or competing priorities contributed to the delays. Then agree on a practical system, such as breaking large assignments into interim milestones, confirming priority order, or requiring progress updates before a deadline is at risk.
“The client summary was due Friday, but it was not submitted until Tuesday. This has happened with three recent assignments, and it has affected the team’s ability to complete its review. What obstacles are making these deadlines difficult to meet?”
A useful expectation might be that the employee confirms priorities at the start of each week and flags any likely delay at least one business day in advance.
#2. Producing Work With Frequent Errors
Frequent errors may involve incorrect figures, incomplete forms, poor proofreading, inaccurate data entry, or instructions that are only partly followed. The manager should identify the type and consequence of the mistakes rather than making a general statement that the employee’s work is “sloppy.” A few minor errors require a different response from errors that create financial, operational, or customer-facing problems.
Review examples privately and look for preventable causes. The employee may need clearer instructions, training, a checklist, additional review time, or a better understanding of quality standards. Set a measurable expectation, such as reducing avoidable corrections or completing a quality-control check before submitting work. Arrange a follow-up date so improvement can be evaluated fairly.
“I found four incorrect account numbers in the report submitted yesterday. Because this report goes to the billing team, those errors create additional correction work. Before submitting future reports, please use the account-verification checklist and review the final entries against the source document.”
Avoid treating every error as proof of poor effort. Focus on recurring, preventable errors and provide reasonable support for correction.
#3. Failing To Follow Instructions
An employee may repeatedly ignore a required process, omit steps, use an outdated form, or substitute a personal method without discussing it. Sometimes this reflects confusion or an inefficient procedure rather than deliberate refusal. The manager should first confirm that the instruction was clear, accessible, and relevant to the employee’s responsibilities.
Describe the specific process and explain why it matters. If the employee believes the procedure is inefficient, invite that feedback separately from the immediate expectation to follow it. Employees can raise legitimate concerns, but they should not unilaterally disregard an established process when doing so creates risk or inconsistency.
“The purchasing procedure requires approval before an order is placed. Two orders were submitted without that approval this month. If you think the process needs improvement, I am willing to discuss that, but until it changes, the approval step must be completed before placing an order.”
Document the instruction and confirm the employee’s understanding. If the employee continues to disregard a clear and reasonable requirement, follow the organization’s normal performance or conduct process.
#4. Showing Poor Attendance or Frequent Lateness
Frequent lateness, unexplained absences, or leaving early can affect coverage and place additional pressure on colleagues. However, attendance concerns require care. Do not assume that every absence reflects irresponsibility, and do not discuss personal details with the wider team. Review the attendance pattern, applicable policies, and any information the employee has already provided.
Hold a private conversation focused on reliability and work impact. Ask whether there is a work-related obstacle that needs to be addressed, while avoiding demands for unnecessary personal information. Clarify the expected schedule, call-out procedure, and notification requirements. If the employee raises a health, family, or other sensitive concern, involve the appropriate internal resource rather than trying to manage the issue informally.
“You were scheduled to begin at 8:30 but arrived after 9:00 on four occasions this month. This leaves the service desk without the expected coverage. Is there an obstacle affecting your schedule that we should discuss, and can you meet the required start time going forward?”
Keep records factual. Note dates, times, communication, and operational impact—not judgments about the employee’s character.
#5. Communicating Poorly With Customers or Colleagues
Poor communication may appear as unanswered messages, unclear instructions, abrupt responses, incomplete handoffs, or failure to share important information. The concern should not be framed as a personality conflict unless the employee’s behavior is genuinely affecting work. Focus on what was said or omitted, who was affected, and what a better communication standard looks like.
Use specific examples and explain the practical consequence. For instance, an unanswered customer message may cause a missed commitment, while an incomplete handoff may force a colleague to repeat work. Ask the employee for their perspective, then establish a clear expectation about response times, tone, documentation, or escalation.
“The customer emailed on Monday and did not receive a response until Thursday, after contacting the service desk again. In future, please acknowledge customer requests within one business day, even if the full answer will take longer. If you cannot resolve the issue, route it to the appropriate person and explain the next step.”
Do not demand constant availability when the role does not require it. Set communication expectations that match the position and the organization’s actual workflow.
#6. Failing To Take Responsibility for Mistakes
A performance concern may arise when an employee hides errors, blames others without examining their own part, or refuses to correct a problem. Accountability does not mean requiring an employee to accept unfair blame. The manager should establish what happened using available facts and separate responsibility from speculation about intent.
When discussing the issue, ask the employee to describe the sequence of events. Identify what was within their control, what was not, and what corrective action is needed. A useful response may include notifying an affected colleague, correcting the work, updating a checklist, or escalating an issue sooner. The goal is reliable problem-solving, not humiliation.
“The shipment was entered with the wrong delivery address, and the error was not reported until the customer called. Let’s review how the information was entered and what you can do when you notice a mistake. Going forward, report address errors immediately so we can correct them before dispatch.”
If the employee raises a legitimate system problem, address that as well. Accountability includes improving the process when the process contributed to the outcome.
#7. Failing To Meet Productivity Expectations
Low productivity can involve completing substantially fewer tasks than expected, spending excessive time on routine work, or failing to maintain a reasonable pace after training and support. Productivity should be evaluated in context. Quality, task complexity, interruptions, staffing levels, and changing priorities all matter. Comparisons with colleagues may be misleading if their assignments differ.
Define the expected output in concrete terms. Instead of saying “work faster,” specify the typical workload, quality standard, priority order, and available resources. Ask the employee to explain how they currently organize their work. You may discover a training gap, unclear priorities, or an inefficient process that can be corrected.
“Over the past three weeks, you have completed about half of the standard daily queue, while the accuracy of the work has remained acceptable. Let’s review how you are allocating your time and identify where tasks are getting delayed. For the next two weeks, we will track completed items and discuss progress twice a week.”
A short review period can make expectations visible without creating an arbitrary deadline. Adjust the plan if the work or circumstances change.
#8. Being Unprepared for Meetings or Assignments
An employee may arrive at meetings without required information, fail to review materials, or begin assignments without understanding the objective. Occasional lack of preparation is normal, especially when priorities change. A recurring pattern, however, can waste meeting time and make it difficult for others to rely on the employee’s contribution.
Explain what preparation is required and when it must be completed. This might include reviewing an agenda, bringing updated figures, preparing questions, or confirming the status of assigned work. Make the expectation proportionate; not every meeting requires extensive preparation. If the employee has too many competing demands, help establish which preparation tasks take priority.
“For today’s project meeting, the updated risk list was not available, so the team could not make the planned decisions. Before future meetings, please review the agenda and bring the information listed in the preparation notes. If you cannot complete it, let me know before the meeting so we can adjust the agenda.”
Preparation improves when responsibilities are explicit. Send concise agendas, identify owners, and avoid assuming that everyone interprets “come prepared” in the same way.
#9. Resisting Reasonable Feedback or Coaching
An employee does not have to agree with every piece of feedback, but they do need to engage with reasonable performance discussions. A concern arises when the employee repeatedly dismisses specific feedback, refuses coaching, or makes no effort to apply agreed changes. Managers should also examine whether previous feedback was clear, timely, and supported by examples.
State the performance issue, invite the employee’s response, and distinguish disagreement from refusal to improve. The employee may identify inaccurate information or a conflicting expectation, which should be considered fairly. If the feedback is valid, agree on one or two observable changes and schedule a follow-up rather than relying on a vague instruction to “do better.”
“You do not have to agree with every part of my assessment, and I want to hear your perspective. The specific concern is that project updates have omitted current risks. We need that information included in future updates, even if your view of the project’s overall progress is more positive.”
Document the discussion and the agreed actions. If the employee continues to reject clear expectations without a valid reason, the matter may move from coaching to formal performance management under established procedures.
#10. Behaving Disruptively During Teamwork
Disruptive behavior can include interrupting repeatedly, speaking over colleagues, refusing to share necessary information, derailing meetings, or making dismissive comments. A disagreement is not automatically poor performance; healthy teams can challenge proposals. The concern is the observable conduct and its effect on the team’s ability to complete work.
Address the behavior promptly and privately. Describe what occurred, explain the impact, and state the expected alternative. If the problem occurs in meetings, set practical rules such as allowing speakers to finish, recording unresolved issues for later discussion, or directing disagreements toward evidence and proposed solutions.
“During the last two meetings, you interrupted three colleagues before they finished explaining their recommendations. The discussion became difficult to follow, and two agenda items were left unfinished. Please allow people to complete their points, then raise your questions or objections. We will review how this is going at our next team meeting.”
Avoid labeling the employee as “toxic” or “difficult.” Behavioral descriptions are more accurate, more defensible, and more useful for improvement.
How to Address Poor Employee Performance Fairly
A sound performance conversation connects four elements: the observed behavior, its effect on the work, the expected standard, and the next opportunity to improve. This structure prevents the discussion from becoming a debate about personality. It also gives the employee enough information to respond meaningfully.
Before the conversation, collect specific examples and check whether the expectation has been communicated consistently to others in comparable roles. During the discussion, allow the employee to explain relevant circumstances, but do not let the conversation lose its focus. Agree on actions that can actually be observed, such as meeting a particular deadline, following a required process, responding within an established timeframe, or using a quality checklist.
A practical performance discussion may follow this sequence:
- Describe what happened using dates, assignments, or direct observations.
- Explain the effect on customers, colleagues, deadlines, quality, or operations.
- Ask for the employee’s perspective and listen for relevant obstacles.
- Clarify the standard that must be met.
- Agree on support, actions, and a reasonable review date.
- Record the discussion and follow up consistently.
“I want to discuss the last two weekly reports. Both were submitted after the agreed deadline, which delayed the team’s review. Can you help me understand what affected the timing?”
“The expectation is that the report is submitted by noon each Friday. For the next three weeks, please send me a progress note by Thursday afternoon and flag any obstacle before the deadline. We will review the results at the end of that period.”
Fairness does not mean avoiding difficult conversations. It means using accurate information, applying expectations consistently, considering relevant circumstances, and giving the employee a reasonable chance to respond and improve.
When Performance Problems Require Additional Support
Some performance concerns can be resolved through clearer instructions, coaching, training, workload adjustments, or closer follow-up. Others may involve a more complicated situation, such as a sustained failure to meet essential duties, repeated refusal to follow reasonable instructions, or conduct that affects safety, customer trust, or the rights of others.
Managers should not try to investigate or resolve every serious issue alone. Follow established organizational procedures and consult HR or another responsible internal resource when the concern may lead to formal action, involves sensitive personal information, or appears connected to discrimination, harassment, retaliation, safety, or an accommodation request. The appropriate resource can help ensure that the response is consistent and that important information is handled properly.
Support should also be practical rather than symbolic. If training is offered, identify what the employee must learn and how competence will be demonstrated. If priorities are changed, confirm what work will be paused. If a performance plan is needed, state the required improvements, available support, review dates, and possible next steps under the organization’s procedures.
How to Document Performance Concerns
Documentation should create a reliable record, not a case built from opinions. Write down the date, assignment or situation, observable conduct, impact, employee response, agreed expectation, and follow-up date. Use neutral language. “The report contained five incorrect entries” is more useful than “The employee was careless again.”
Keep the record focused on work-related facts and relevant conversations. Include positive developments when they occur, especially if the employee makes a meaningful improvement or completes an agreed action. Balanced documentation helps managers evaluate progress rather than relying on the most recent incident or the strongest emotional impression.
A simple record might include:
- Concern: Three customer responses exceeded the agreed response period.
- Impact: Customers contacted the service desk again for updates.
- Employee response: The employee reported difficulty prioritizing urgent requests.
- Expectation: Acknowledge customer requests within one business day and escalate unresolved issues.
- Support: Review the prioritization process and use the shared task queue.
- Follow-up: Review response records after two weeks.
Documentation does not replace judgment or conversation. It supports both by making the concern specific and allowing the manager and employee to assess whether the agreed change has occurred.
Closing Thoughts
Poor employee performance is best addressed through clarity rather than labels. Identify the observable problem, explain its effect, listen for relevant circumstances, and define the standard that must be met. Then provide practical support, document the agreement, and follow up when promised. This approach protects fairness while preserving accountability. A difficult conversation may not solve every performance issue immediately, but it gives both the manager and employee a clear basis for deciding what must change next.