Poor Performance: How to Spot It Early and Address It Before It Damages the Team


serious workplace conversation desk

Why Managers Wait Too Long

Most managers don’t ignore poor performance because they don’t care. They wait because they’re not sure what to say, they’re worried about damaging the relationship, or they hope the problem will sort itself out. It almost never does.

The longer you wait, the harder the conversation becomes. The employee has had more time to entrench the habit. Other team members have noticed and started wondering why nothing is being done. And by the time you finally say something, the stakes feel so high that both sides go into the conversation on edge.

Addressing performance issues early—when they’re still small—is one of the most important habits you can build as a manager. It keeps small problems from becoming formal disciplinary issues, and it gives the employee the best possible chance to course-correct.

Get Clear on What You’re Actually Seeing

Before you say anything to the employee, get specific about what the problem actually is. Vague concerns lead to vague conversations, and vague conversations don’t change behavior.

Ask yourself:

  • What exactly is happening that shouldn’t be, or what isn’t happening that should be?
  • How often is it occurring, and when did it start?
  • What is the impact on the team, the work, or the customer?
  • Do I have concrete examples I can refer to?

There’s a big difference between “she seems disengaged” and “she’s missed three deadlines in the past month and didn’t flag any of them in advance.” The second version gives you something to talk about. The first version gives you an impression—and impressions are easy to dismiss.

Write down two or three specific examples before you have the conversation. Not to build a legal case, but to keep yourself grounded when you’re in the room.

Consider Whether There’s a Root Cause You Don’t Know About

Performance problems don’t always come from attitude or effort. Sometimes there are underlying causes that aren’t obvious from the outside.

The employee might not fully understand what’s expected of them. The role may have shifted without clear communication. They might be dealing with a personal situation that’s affecting their focus. They could be struggling with a skill gap they’re embarrassed to admit. They might be getting conflicting direction from multiple sources.

None of this means you avoid the conversation. But it does mean you go in with curiosity, not just conclusions. The goal of the first conversation is often to understand what’s going on as much as it is to deliver feedback.

Have the Conversation Early and in Private

The right time to address a performance issue is as soon as you’ve confirmed it’s a pattern and not a one-off. One bad day is context. Three missed deadlines is a pattern.

Always have this conversation in private. Not in the hallway, not in a team meeting, not via email. Find a time when you won’t be interrupted and when the employee has enough mental space to actually hear what you’re saying—Monday morning right before a major deadline is not the time.

Keep the tone matter-of-fact. You’re not delivering punishment. You’re having a professional conversation about work that needs to improve. The calmer and clearer you are, the better the employee will receive it.

How to Structure the Conversation

You don’t need a script, but having a clear structure helps. Here’s a framework that works well for most early-stage performance conversations:

1. State what you’ve observed

Start with the facts. Be direct and specific. Avoid softening the message so much that it gets lost. “I’ve noticed that the last three reports came in after the deadline, and I didn’t hear about the delays in advance” is clear and professional.

2. Explain the impact

Help the employee understand why it matters. “When reports are late without warning, it creates a ripple effect—I can’t review them before the client call, and the team has to scramble to fill the gap.” Impact makes the feedback real. It shifts the conversation from personal to professional.

3. Ask for their perspective

This is the part many managers skip, and it’s often where the most useful information comes out. “I wanted to hear from you—is there something getting in the way?” Give them space to respond without jumping in too quickly. You might learn something that changes how you approach the solution.

4. Be clear about what needs to change

Don’t leave the conversation open-ended. State clearly what you need to see going forward. “Going forward, I need reports submitted by Thursday at noon. If there’s a risk you won’t hit that, I need to know at least two days in advance so we can work around it.” Specific, observable, achievable.

5. Agree on next steps and a check-in

Close the conversation with a clear follow-up plan. “Let’s check in again in two weeks to see how things are going.” This signals that the conversation wasn’t a one-time warning—it’s the beginning of a process you’re both part of.

What Not to Do

Even managers with good intentions can handle these conversations in ways that backfire. Here are the most common mistakes to avoid:

Don’t cushion the message out of existence

The “feedback sandwich”—positive, negative, positive—is so widely taught that most employees have learned to tune out the middle part. If there’s a real performance issue, make sure it lands. You can be kind and direct at the same time. They’re not opposites.

Don’t make it personal

Focus on behaviors and outcomes, not character. “You’ve been missing deadlines” is a behavior. “You’re not reliable” is a character judgment. One opens a conversation. The other puts someone on the defensive.

Don’t compare them to other employees

“Everyone else manages to get this right” is not feedback. It’s humiliation. Keep the conversation about the individual’s performance and what you need from them specifically.

Don’t make promises you can’t keep

Avoid vague reassurances like “this won’t affect your review” if you don’t know that to be true. If the performance doesn’t improve and it does affect their review, you’ve broken trust on top of everything else.

Don’t wait for a formal process to fix an informal problem

A Performance Improvement Plan (PIP) is a formal tool for serious, documented issues. Most early performance problems don’t need a PIP—they need a clear, direct conversation and a follow-up. Jumping straight to formal processes for minor issues often damages the relationship more than it helps.

Document What You Discussed

You don’t need to send a formal memo after every performance conversation, but you should write a brief note for yourself. Date, what was discussed, what was agreed, and what the next check-in looks like. Keep it in a place you can retrieve it.

If the problem continues and escalates, this record matters. It shows that you addressed it early, that the employee was informed, and that you gave them an opportunity to improve. Without documentation, it’s your word against theirs—and that becomes a problem quickly.

For more serious or recurring issues, consider sending a brief follow-up email to the employee after the conversation: “Just wanted to summarize what we discussed today so we’re on the same page.” Keep it factual and neutral. This creates a written record without feeling punitive.

Follow Through on the Check-In

One of the most common reasons performance conversations fail is that managers have the conversation and then disappear. The employee doesn’t know if things are improving, whether the manager is still paying attention, or what happens next.

Follow through on the check-in you promised. Even if things are going well, say so. “I’ve noticed the last two reports came in on time—that’s exactly what I was looking for. Keep it up.” Positive reinforcement after a performance conversation is not weakness. It’s what actually makes the behavior stick.

If things aren’t improving after your check-in, have a second conversation. Be more explicit about the consequences. This is when you start to move from an informal discussion to a more structured improvement plan. But you need that first conversation to have happened—and been documented—before you can credibly take the next step.

When to Involve HR

For most early-stage performance issues, you don’t need HR involved in the initial conversation. Handle it directly with your employee first.

Bring HR in when:

  • The issue is serious enough that formal documentation is needed from the start
  • You’ve had multiple conversations and nothing has changed
  • The situation involves potential policy violations, discrimination concerns, or legal risk
  • You’re unsure how to proceed and want guidance before you act

HR is a resource, not a last resort. If you’re genuinely uncertain, a quick consultation before the conversation—not after it goes sideways—is always a better move.

The Bigger Picture

Addressing poor performance is not about being tough or being the bad guy. It’s about taking your responsibility as a manager seriously. Your team members deserve honest feedback. The ones who are performing well deserve to work alongside people who are held to the same standard. And the person who’s struggling deserves the chance to fix things before the situation becomes irreversible.

Most people, when given clear and respectful feedback early, will respond positively. They often didn’t realize how their behavior was landing, or they needed permission to ask for help. The conversation you’ve been dreading is frequently the one they needed someone to have with them.

Act early, be specific, stay calm, and follow through. That’s the whole job.

Frequently Asked Questions

Why do managers avoid addressing poor performance right away?

Most managers delay addressing poor performance because they’re unsure what to say, worried about damaging relationships, or hope the problem will resolve itself. This hesitation actually makes the situation worse, as the employee has more time to entrench bad habits and other team members begin questioning why no action is being taken. The longer you wait, the more difficult and high-stakes the eventual conversation becomes.

How do I document employee performance issues before talking to them?

Get specific about what’s actually happening by asking yourself what behaviors are occurring that shouldn’t be, how often they happen, and what impact they have on the team or work. Write down two or three concrete examples before the conversation—not to build a legal case, but to keep yourself grounded during the discussion. Focus on observable behaviors rather than vague impressions like ‘seems disengaged.’

What should I consider before assuming an employee has a bad attitude?

Performance problems don’t always stem from poor attitude or lack of effort—there may be underlying causes you’re not aware of. The employee might not understand expectations, could be dealing with personal issues affecting their focus, or may have skill gaps they’re embarrassed to admit. They might also be receiving conflicting direction from multiple sources or working in a role that has shifted without clear communication.

How early should I address performance problems with my team?

Address performance issues as soon as you notice them, while they’re still small problems rather than formal disciplinary matters. Early intervention prevents small issues from becoming entrenched habits and gives employees the best chance to course-correct. Waiting only makes the conversation more difficult and allows the behavior to negatively impact other team members.

What’s the difference between vague concerns and actionable performance feedback?

Vague concerns are based on impressions and feelings, like ‘she seems disengaged,’ while actionable feedback focuses on specific, observable behaviors with concrete examples. For instance, ‘she’s missed three deadlines in the past month and didn’t flag any of them in advance’ gives you something concrete to discuss. Vague concerns lead to ineffective conversations that don’t change behavior, while specific examples create clear expectations for improvement.

Ty Sutherland

Ty Sutherland is an operations and technology leader with 20+ years of experience. He is Director of IT Operations at SaskTel, founder of Ops Harmony (fractional COO and EOS Integrator), and former COO at WTFast. He writes Management Skills Daily to share practical management frameworks that work in the real world.

Recent Posts