Poor performance is rarely solved by one difficult conversation. Managers need to establish what is happening, distinguish capability from conduct, provide a fair opportunity to improve, and follow through consistently. A checklist helps prevent rushed conclusions and keeps the process focused on observable work rather than personality judgments. The steps below are designed for everyday management situations, whether an employee is missing deadlines, producing unreliable work, struggling with a role requirement, or failing to meet an agreed workplace standard.
Managing Poor Performance Checklist: Practical Steps for Managers
#1. Define the Performance Concern Clearly
Start by identifying the specific performance problem. “Not committed” or “has a bad attitude” is too vague to guide a fair conversation. Describe what the employee did or failed to do, when it happened, what standard applied, and what effect it had on the work.
For example, the concern might be that three client reports were submitted after the agreed deadline, or that required quality checks were missing from several work orders. Separate observable facts from interpretations about the employee’s motives or character. A clear definition gives both of you something concrete to discuss and makes improvement easier to measure.
#2. Check the Expected Standard
Before addressing an employee’s performance, confirm that the expected standard was actually communicated. Review the job description, team procedures, previous instructions, project agreements, training materials, or relevant performance objectives. Consider whether a reasonable employee in the same role would understand what success requires.
Managers sometimes assume that a deadline, process, or quality expectation is obvious when it has never been stated clearly. If the standard is unclear, correct that management failure first. You can still discuss the impact of the work, but be careful not to present an unstated expectation as though it were an established rule.
#3. Gather Specific Evidence
Collect enough reliable information to understand the pattern without turning the process into an investigation of every minor error. Keep records of dates, missed commitments, work samples, customer concerns, relevant instructions, and previous discussions. Focus on information directly connected to the performance issue.
Evidence should help answer practical questions: How often has the problem occurred? What was expected? Was the employee given the necessary information or resources? Were similar situations handled consistently for other employees? Avoid relying on rumors or a single frustrated colleague’s general impression. A fair discussion depends on accurate, proportionate information.
#4. Consider Context Before Drawing Conclusions
Poor performance can result from different circumstances, and the appropriate response depends partly on what is causing it. The employee may lack training, face an unclear workload, misunderstand priorities, encounter a process obstacle, or be dealing with a personal matter that affects availability. You do not need to diagnose the problem, but you should ask enough questions to understand it.
Review staffing levels, changes in responsibilities, competing deadlines, system problems, and prior guidance. This does not mean excusing missed expectations automatically. It means deciding whether the solution involves instruction, support, workload adjustment, accountability, or a combination of these.
#5. Arrange a Private, Focused Conversation
Discuss performance concerns privately and at a time that allows enough space for a serious conversation. Do not raise the issue in front of colleagues, during a rushed hallway exchange, or through a vague message that leaves the employee guessing. Prepare the main facts and the outcome you need from the discussion.
A useful opening is direct without being hostile:
I want to discuss the last two project updates. They were submitted after the agreed deadlines, and both needed substantial corrections before they could be shared with the client. I’d like to understand what affected the work and agree on what needs to change.
Give the employee an opportunity to respond. Listen for relevant information, ask clarifying questions, and avoid interrupting simply because the explanation is uncomfortable.
#6. Describe the Impact of the Performance
Employees need to understand why the issue matters, not merely that a manager noticed it. Explain the practical effect on customers, colleagues, deadlines, costs, safety, service quality, or the team’s ability to plan. Keep the explanation connected to the work rather than using shame or exaggerated criticism.
For example, late inventory updates may cause purchasing decisions to be based on inaccurate information. Incomplete case notes may require another employee to repeat work or delay a customer response. Describing the impact makes the standard meaningful and helps the employee see what must improve. Use measured language: explain the actual consequence rather than claiming that one mistake proves a general lack of care.
#7. Ask What Support or Clarification Is Needed
After explaining the concern, ask what would help the employee meet the expected standard. The answer may reveal a training gap, unclear instructions, competing priorities, limited access to information, or a need to practice a task with supervision. Support should be specific rather than a general promise to “help more.”
You might offer a demonstration, a written process guide, a temporary review of early work, clearer priority-setting, or access to an experienced colleague. At the same time, distinguish a genuine support need from a request that simply avoids reasonable responsibility. Support removes preventable obstacles; it does not eliminate the expectation that the employee must perform the role.
#8. Agree on Measurable Improvement Expectations
Turn the conversation into clear expectations that both parties can understand. Identify what the employee must do, the required quality or timing, when the change begins, and how progress will be assessed. “Do better” is not a performance plan. “Submit the weekly report by noon each Friday with all required fields completed and no unresolved calculation errors” is much more useful.
Keep the expectations proportionate to the issue and realistic for the role. If several problems exist, prioritize the most important ones rather than presenting an overwhelming list. Ask the employee to explain the agreed expectations back in their own words if there is any risk of misunderstanding.
#9. Set a Review Date and Follow-Up Method
Agree on when you will review progress and how you will monitor it. A review date creates accountability for both manager and employee. The frequency should reflect the seriousness and urgency of the concern: a short weekly check may be appropriate for a critical project, while a broader monthly review may suit a less urgent issue.
Explain what evidence will be considered at the review. This could include completed work, error rates, response times, attendance at required training, customer outcomes, or feedback from a defined work process. Do not create constant surveillance that is unrelated to the concern. Monitor enough to assess improvement fairly and consistently.
#10. Document the Conversation and Agreement
After the meeting, make a concise written record of the concern, the employee’s response, the support offered, the expectations agreed, and the review date. Share an appropriate summary with the employee so both parties have the same understanding. Documentation is not only for possible formal action; it also prevents confusion and helps managers follow through.
Use neutral language. Record “the report was submitted two days after the agreed deadline” rather than “the employee was careless.” If the employee disputes the account, note the disagreement accurately and preserve relevant supporting information. Follow your organization’s established procedures for performance records and involve HR or another responsible internal resource where required.
#11. Follow Through Consistently
A performance conversation loses credibility when the manager never checks progress. Attend the review meeting, examine the agreed evidence, and tell the employee what has improved and what still falls short. If the employee meets the expectation, acknowledge it and decide whether the monitoring can reduce or end.
If improvement is partial, explain precisely what remains unresolved and revise the next step if appropriate. If there is no meaningful improvement, do not repeatedly restart the same informal conversation without direction. Follow the organization’s performance-management process, which may include a formal improvement plan or other proportionate action. Consistency matters more than dramatic language.
#12. Escalate When the Situation Requires It
Some performance concerns should not be handled solely through ordinary coaching. Seek guidance from HR or the appropriate internal authority when the issue is serious, recurring, disputed, connected to a protected concern, or potentially subject to formal disciplinary procedures. Also seek advice when you are unsure whether the problem involves capability, conduct, health, safety, or a workplace adjustment.
Escalation does not mean abandoning the employee or assuming the worst. It means making sure the next step is fair, consistent, and aligned with organizational procedures. Continue treating the employee respectfully, protect confidentiality, and avoid discussing the matter casually with colleagues who do not need the information.
#13. Distinguish Improvement From Permanent Labels
Assess the employee’s work against the agreed standard rather than allowing one difficult period to become a permanent judgment about the person. Someone may improve after receiving clearer direction or training. Another employee may perform well in most areas but continue to miss a critical requirement. Your response should reflect the evidence and the current situation.
Avoid labels such as “unreliable,” “unmotivated,” or “difficult” in everyday management conversations. Describe the behavior and its effect instead. This keeps feedback more accurate and gives the employee a fair opportunity to respond. It also helps you recognize genuine improvement rather than continuing to interpret every later event through an old assumption.
#14. Close the Process Deliberately
When the employee has met the agreed expectations, say so clearly. Explain what has improved, identify any standards that must continue, and confirm whether regular performance discussions will now return to the normal schedule. A clear conclusion reassures the employee that the issue has been addressed rather than left hanging indefinitely.
If the concern remains unresolved, explain the next formal or practical step and why it is being taken. Do not make promises about outcomes you cannot control. The goal is a process that is understandable from beginning to end: the employee knows what was expected, what support was available, how progress was assessed, and what happens next.
A Practical Conversation Framework
A manager can organize the discussion around five questions:
- What happened? Describe the observable performance issue.
- What was expected? Refer to the relevant standard or agreement.
- What was the impact? Explain the practical consequence.
- What affected the result? Invite the employee’s perspective and identify obstacles.
- What happens next? Agree on support, expectations, timing, and review.
This structure helps prevent two common extremes. A manager may soften the conversation so much that the employee does not understand the concern, or become so accusatory that the employee focuses only on defending themselves. A fact-based sequence allows the manager to be firm without being personal.
The tone should be calm and serious. You do not need to fill every silence, win an argument, or force an immediate admission of fault. If the employee becomes upset, acknowledge the reaction while returning to the work issue. If new information substantially changes the situation, pause and verify the facts rather than rushing to a conclusion.
What to Include in a Performance Follow-Up Note
A short follow-up note should normally cover:
- The date and purpose of the discussion.
- The specific performance concern.
- The standard or expectation involved.
- Relevant information provided by the employee.
- Any agreed support, training, or clarification.
- The required improvement and how it will be measured.
- The review date and participants.
- Any next step if the standard is not met.
The note should be factual and proportionate. It does not need to reproduce every sentence spoken in the meeting. Avoid sarcastic descriptions, emotional commentary, or conclusions about the employee’s motives. If your organization has a required form or procedure, use it rather than creating an informal system that may conflict with established practice.
When sharing the summary, invite the employee to identify factual inaccuracies. Agreement is not always necessary, but both parties should understand what was recorded. Keep the document in the appropriate workplace system and limit access to people with a legitimate role in the process.
When Coaching Is Not Enough
Coaching is appropriate when the employee can reasonably improve through clearer expectations, practice, feedback, or support. It is not a substitute for accountability when the employee understands the requirement and repeatedly chooses not to meet it. The distinction should be based on evidence, not on whether the manager personally likes the employee or finds them easy to work with.
A serious issue may also require a different response from the beginning, particularly where safety, integrity, confidentiality, harassment, or deliberate misconduct is involved. In such circumstances, follow the relevant organizational procedure and seek guidance promptly. Do not promise that the matter will remain informal, and do not investigate beyond your authority.
Managers should also avoid treating every difficulty as a performance failure. A temporary problem, a poorly designed process, or an unreasonable workload may require an operational solution. Good judgment means addressing the real source of the problem while still protecting legitimate workplace standards.
Closing Thoughts
Managing poor performance requires more than pointing out mistakes. The manager’s responsibility is to make the standard clear, examine the facts fairly, listen for relevant context, provide reasonable support, and hold the employee accountable for agreed improvement. Use this checklist to prepare before the conversation, document what follows, and review progress consistently. When the process is specific and respectful, employees are more likely to understand what must change—and managers are better positioned to respond fairly when it does not.