Performance conversations can become awkward when the message is vague, overly softened, or delivered without a clear next step. Yet avoiding the discussion usually leaves the employee uncertain and the manager frustrated. The most useful conversations focus on observable work, explain the impact, invite the employee’s perspective, and establish what should happen next. The following performance conversation examples show how to address common situations with clarity and respect, whether you are recognizing strong work, correcting a problem, or discussing improvement over time.
Performance Conversations Examples You Can Adapt at Work
#1. Recognizing Strong Performance
A good performance conversation is not limited to correcting problems. When someone performs well, describe specifically what they did and why it mattered. General praise such as “Great job” may feel positive, but it gives the employee little information they can use to repeat the behavior. Connect the recognition to a result, a skill, or a contribution to the team.
I want to recognize how you handled the client implementation last week. You identified the scheduling risk early, explained it clearly to the client, and coordinated with the technical team before it affected the deadline.
That preparation helped us maintain the client’s confidence and avoid a last-minute escalation. Please continue using that same approach on projects with several dependencies.
You can also ask the employee what helped them succeed. Their answer may reveal a useful process that can be shared with colleagues. Recognition becomes more meaningful when it is timely, specific, and connected to work the employee can intentionally repeat.
#2. Addressing Missed Deadlines
When an employee misses a deadline, begin with the agreed expectation and the observable result. Avoid assuming laziness, carelessness, or poor commitment. A missed deadline may involve unclear priorities, an unrealistic estimate, competing work, or a failure to communicate a risk. The conversation should identify what happened and establish a better process for the future.
The report was due Friday afternoon, and I received it Monday morning. I also did not receive an update that the deadline was at risk.
Please walk me through what affected the timeline. After we understand that, I’d like us to agree on how you will flag delays earlier and what revised deadline is realistic.
If the explanation is reasonable, discuss workload or planning changes rather than treating the issue as a character flaw. If the employee could have communicated sooner, state that expectation directly. A practical follow-up might include an interim check-in, an earlier draft, or a requirement to raise risks as soon as they become apparent.
#3. Discussing Work That Does Not Meet Expectations
Some performance issues involve work that is completed but falls below the required standard. Be precise about the gap. Identify the expected quality, describe what was delivered, and explain the effect on customers, colleagues, cost, timing, or future work. Do not rely on labels such as “sloppy” or “not good enough” without examples.
The three customer summaries submitted this week contained missing account details and several figures that did not match the source records. The summaries had to be returned for correction, which delayed the team’s response to those customers.
The expectation is that each summary is checked against the source record before submission. What part of that review process is creating difficulty, and what would help you complete it accurately?
A useful improvement plan might include a checklist, a temporary review by a colleague, or a short training session. Set a date to review progress. The purpose is not simply to point out errors; it is to make the required standard clear and give the employee a fair opportunity to meet it.
#4. Responding to Repeated Mistakes
A repeated mistake requires a different conversation from a single error. Start by explaining that the pattern has continued and provide two or three specific examples. Then distinguish between the mistake itself and the process surrounding it. The employee may need clearer instructions, a different checking method, additional practice, or stronger accountability.
We discussed the incorrect inventory entries on March 4, and you agreed to verify each entry against the delivery record. Similar errors appeared again on March 12 and March 19.
I want to understand what is preventing the new checking process from working. Going forward, I need every entry verified before it is submitted, and we will review a sample together each Friday for the next month.
Do not promise indefinite coaching without a review point. Explain what improvement will look like and when you will assess it. If the problem continues despite clear expectations and reasonable support, follow the organization’s established performance-management process rather than improvising a response.
#5. Addressing Communication and Collaboration Problems
Performance includes how work is carried out with others, especially when communication affects decisions or deadlines. Focus on conduct that can be observed rather than describing the employee as difficult, negative, or uncooperative. Explain the impact and invite the employee’s account before agreeing on a change.
During the last two project meetings, you interrupted colleagues before they finished explaining their updates. In one meeting, the discussion moved on before the risks were fully described, and the team had to revisit them later.
I need you to allow colleagues to finish, then raise your question or disagreement. If you believe a discussion is missing an important issue, make that concern clearly after the speaker has finished.
The conversation should not demand agreement on every issue. Employees can challenge proposals and express strong views. The standard is respectful participation that allows the team to exchange information and make decisions. If the behavior has affected a particular colleague, address the conduct without requiring the employee to guess which personality traits are being criticized.
#6. Discussing Low Engagement or Limited Initiative
“Low engagement” can mean several different things, so avoid presenting it as a diagnosis. Describe the work behavior you have observed: limited participation, uncompleted follow-up, reluctance to take ownership, or failure to raise concerns. Then ask what is contributing to the pattern. The employee may have unclear priorities, insufficient authority, competing responsibilities, or a problem that has not been discussed.
Over the past month, you have attended the planning meetings but have not contributed updates, taken ownership of the assigned follow-up tasks, or raised questions when deadlines changed.
I want to understand what is getting in the way. The expectation for this role is that you take responsibility for your assigned actions and raise concerns early. What support or clarification would help you do that consistently?
Do not treat quietness alone as poor performance. Some employees contribute more effectively in writing or in smaller discussions. Address the actual work requirements, such as completing commitments, sharing necessary information, and taking responsibility for agreed tasks. Define initiative in terms of actions rather than personality.
#7. Giving Feedback After a Difficult Customer Interaction
A difficult customer interaction should be reviewed fairly. Do not automatically assume that the employee was at fault simply because the customer complained. Examine the employee’s actions, the circumstances, and whether the response followed the expected service standard. The conversation should recognize legitimate pressure while still addressing conduct that needs to change.
I reviewed the call with the customer. Their request was unusually demanding, but your response became increasingly abrupt, and you ended the call before confirming the next step.
I understand that the situation was frustrating. In future calls, acknowledge the concern, explain what you can do, and confirm the follow-up before ending the conversation. Let’s discuss how you can signal for support when a call begins to escalate.
If the employee followed a reasonable process and the complaint reflects an unreasonable demand, say so. Performance feedback should not reward customers for every complaint or place employees in impossible situations. The goal is to identify controllable behavior and provide a practical method for handling similar interactions.
#8. Discussing Performance During a Probationary or New-Hire Period
Early performance conversations should prevent surprises. A new employee may still be learning systems, terminology, relationships, and the organization’s preferred methods. At the same time, a manager should not postpone important feedback until the end of a probationary period. Explain what is going well, identify the most important gap, and state what progress should look like.
You have learned the scheduling system quickly and have built good relationships with the operations team. The main issue is that several handover notes have not included the information the next shift needs.
For the next two weeks, please use the handover checklist for every shift and bring any unclear items to me before you finish. We will review a few examples together next Friday.
Limit the discussion to priorities the employee can reasonably act on. New hires often receive too much feedback at once, which makes it difficult to know what matters most. A short, regular review can clarify expectations and allow both sides to identify misunderstandings before they become an established pattern.
#9. Discussing Readiness for Greater Responsibility
When an employee wants a promotion or expanded responsibilities, the conversation should be honest without becoming dismissive. Do not promise advancement merely to encourage the employee, and do not reject the request with vague comments such as “You are not ready.” Explain the capabilities the next role requires and compare them with demonstrated performance.
You have asked about leading larger client projects. You have shown strong technical judgment, but the next level also requires coordinating competing priorities, delegating work, and communicating risks to senior stakeholders.
Over the next quarter, I would like you to lead the smaller implementation project, prepare the weekly risk update, and delegate two workstreams. We can review those experiences and discuss your readiness using specific examples.
This approach turns a general career conversation into an observable development plan. Be clear about what you can and cannot guarantee. Readiness is not always the only factor in advancement; available roles, organizational needs, and timing may also matter. The employee deserves an accurate picture rather than encouragement that creates false expectations.
#10. Setting Expectations After an Improvement Conversation
A performance conversation should end with a clear understanding of what happens next. If the employee leaves unsure about the expected change, the discussion may produce temporary agreement but little improvement. Summarize the issue, the required behavior, the support available, and the date for review. Ask the employee to explain the plan in their own words if necessary.
To summarize, the priority is submitting accurate weekly reports by 3 p.m. Thursday, checking the figures against the source data, and telling me by Wednesday if you expect a delay. I will provide the reporting checklist today, and we will review your next three reports together.
Before we finish, can you summarize the steps you will take and let me know whether anything remains unclear?
Document the agreed actions afterward in a neutral, factual message. Include the date, expectations, support, and review point. Documentation is not meant to turn every conversation into a threat; it helps both people remember what was discussed and provides a fair basis for follow-up.
How to Use These Performance Conversation Examples
Use the examples as frameworks, not scripts that must be repeated word for word. Before the meeting, write down the specific behavior or result you need to discuss, the relevant date or example, the effect on the work, and the outcome you want. This preparation helps you avoid broad claims and keeps the conversation focused.
A useful structure is:
- Observation: What happened?
- Impact: Why did it matter?
- Perspective: What does the employee see differently or need to explain?
- Expectation: What should happen next time?
- Support: What resources, clarification, or coaching are appropriate?
- Follow-up: When will you review progress?
Keep the tone direct and respectful. Do not bury the central message under excessive reassurance, but do not treat a performance gap as proof of bad intent. Ask questions, listen to the answer, and separate information that changes the plan from explanations that avoid responsibility.
For serious, recurring, or potentially disciplinary issues, follow your organization’s established procedures and involve HR or the appropriate internal resource when required. Managers should not make promises about job status, compensation, or formal consequences unless they have the authority and information to do so.
Adapting the Wording to the Employee’s Response
The first response may not tell you everything you need to know. An employee may be surprised, disagree with the example, become upset, or immediately accept responsibility. Your next step should depend on the substance of the response rather than on whether the conversation feels comfortable.
If the employee disagrees, return to the observable facts and ask what information is missing. You can say:
I hear that you experienced the situation differently. Let’s look at the specific example together and identify which part of the account you believe is inaccurate.
If the employee becomes upset, allow a reasonable pause without abandoning the discussion. Acknowledge the reaction while keeping the purpose clear:
I can see that this feedback is difficult to hear. We can take a short break, and I also want to make sure we leave with a clear understanding of the expectation and the support available.
If the employee accepts the feedback, do not assume the problem is solved. Confirm the actions, timing, and follow-up. Agreement during a meeting matters less than observable improvement afterward.
The manager also has a responsibility to listen for information that changes the situation. A workload conflict, unclear instruction, missing access, or inconsistent direction may require the manager to correct the working conditions rather than simply demand better performance.
Closing Thoughts
The strongest performance conversations are specific enough to be fair and practical enough to guide change. Describe what you observed, explain its effect, invite the employee’s perspective, and agree on a measurable next step. Recognition should be as concrete as correction, and difficult feedback should address conduct rather than personality. Before your next conversation, prepare one clear example, one reasonable expectation, and one follow-up date. That preparation can turn an uncomfortable discussion into a useful professional exchange.