How to handle difficult employees starts with one shift: address specific, repeated behavior early, not a label. Back every conversation with evidence. Follow a fair, consistent process instead of reacting to frustration.

A manager’s job is not to diagnose someone’s personality. It is to clarify what the role requires, hear the employee’s side, offer real support, and document what actually happened. “Difficult employee” describes a search term, not a diagnosis. The behavior behind it might be missed deadlines, resistance to feedback, or a pattern of blame-shifting that affects the team. Treating it as a management problem, not a character flaw, keeps the response fair and defensible.

Dealing with a difficult coworker rather than a direct report? Read our guide to dealing with difficult coworkers.

What This Guide Covers

• Performance management for direct reports you supervise.
• Repeated behavior that affects work quality, colleagues, customers, or team outcomes.
• Coaching, fair documentation, improvement plans, HR partnership, and respectful exit decisions.

What This Guide Does Not Cover

• One-off misunderstandings between peers with no reporting relationship.
• A personal dislike for an employee, absent an actual performance or conduct problem.
• Medical, legal, discrimination, safety, or protected-leave situations, which need immediate HR or specialist involvement.

Recognize the Difference Between a Difficult Moment and a Management Issue

Learning how to handle difficult employees starts with telling a bad day apart from an actual pattern. A single rough meeting or a missed deadline during a hard week is not a management issue. It becomes one when the behavior repeats, or when a performance gap is clear and consistent over a defined period.

Common Patterns That Require a Manager’s Attention

• Work consistently falls below the agreed standard.
• The employee misses commitments or deadlines without flagging problems early.
• Teamwork or communication breaks down repeatedly, not just once.
• Feedback gets rejected without any real engagement with it.
• The employee avoids accountability or shifts blame onto others.
• The employee resists a necessary change without raising workable concerns.

Check Whether the Problem Is Actually a Management or System Issue

Before the first conversation, confirm the basics are actually in place:

• Expectations, priorities, workload, and success measures are clear and were communicated.
• The employee has the training, tools, and authority the role requires.

This check is not an excuse for repeated poor behavior. It exists so the manager acts on accurate information instead of assumptions.

Gather Facts Before You Start the Conversation

Fair feedback and useful documentation both start with the same discipline: write down what happened, not what you assume it means.

Separate Observable Behavior From Subjective Labels

Weak: “You are negative and difficult.”

Strong: “In the last three project meetings, you interrupted colleagues before they finished and rejected agreed actions without offering an alternative.”

Specific language gives the employee something concrete to respond to. A label just invites defensiveness.

Identify the Expected Standard and the Impact

State the standard the behavior fell short of: a policy, a role requirement, a deadline, or a team agreement. Then name the actual impact, on a customer, a colleague, a delivery date, or the quality of the work. Skip exaggeration like “everyone is unhappy.” Vague claims collapse under a follow-up question, and they are unfair to the employee if you cannot back them up.

Know When to Involve HR Before the First Meeting

Loop in HR before you say anything to the employee if the situation involves:

• Harassment, threats, or violence.
• Discrimination or retaliation.
• A medical concern, accommodation request, or protected leave.
• Union matters or a serious policy breach.

HR involvement at this stage protects the employee and the organization. This guide is not legal advice. For any of the situations above, follow your internal policy and get qualified local counsel involved.

Have the First Performance Conversation Early

Difficult conversations get harder the longer a manager waits. Hold the meeting privately, prepared, and direct, while the behavior is still recent.

Use a Clear Conversation Structure

A five-part structure keeps the conversation direct without becoming personal, building on the situation-behavior-impact model described by the Center for Creative Leadership:

• Situation: name when and where the issue happened.
• Behavior: describe only what you observed.
• Impact: explain the consequence.
• Expectation: state what needs to change.
• Question: ask for the employee’s perspective and any context you are missing.

Listen Without Losing Clarity

Ask questions that invite a real answer:

• “What is your perspective on what happened?”
• “What is making this expectation difficult to meet?”
• “What support or clarification would help you meet it?”

Listening is not the same as accepting an excuse or lowering the standard. It is how you find out whether the fix is coaching, a resource gap, or a direct accountability conversation.

End With an Agreed Next Step

Close every conversation with three things: what needs to change, what support you will provide, and a specific check-in date with a clear description of what improvement looks like. Managers who give feedback effectively treat this step as part of the conversation, not an afterthought tacked on at the end.

Document Performance Concerns Fairly and Consistently

Documentation is not a punishment, and it is not a retrospective attempt to build a case. It is a factual record of expectations, support, feedback, and progress that both sides can point back to.

What Managers Should Document

• Date, time, and relevant context.
• The observable behavior or work output.
• The expected standard and its impact on the business or team.
• The employee’s response or explanation.
• Support offered, agreed actions, and the next review date.
• Evidence of improvement, no change, or a new concern.

What Managers Should Not Document

• Personality labels or guesses about motivation.
• Irrelevant private or medical details.
• Rumors or secondhand claims you have not verified.
• Conclusions that belong to HR, legal counsel, or a formal investigation.

Keep Documentation Aligned With Company Policy

Follow your organization’s HR and data-handling process for storing these records. Inconsistent documentation across managers or employees undermines fairness and makes later decisions harder to defend.

Coach for Improvement Before Escalating

Give the employee a genuine, structured chance to improve where the situation allows for one. Ordinary coaching and a formal improvement plan are not the same thing, and skipping straight to the second reads as punitive.

Create a Practical Improvement Plan

Effective plans share a small set of features, whether or not they use a formal performance improvement plan. SHRM’s guide to performance improvement plans recommends a minimum of 30 days, with 60 to 90 days more typical for a genuine improvement window. Build the plan around:

• The specific behavior or outcome that needs to change.
• A measurable standard, not a vague impression.
• The support, training, or resources available.
• A defined timeline with regular check-ins.
• What happens if progress falls short, in line with your organization’s policy.

Give Feedback Throughout the Process

Reinforce real progress as it happens, not only at the final review. Correct new issues promptly instead of saving them up. Keep every note specific and tied to the agreed standard, not to how the conversation felt.

Avoid Turning a PIP Into a Surprise

A formal improvement plan should follow earlier, clear feedback, unless the issue is serious enough to require immediate escalation. Build the plan with HR or under your organization’s established process. An employee who is blindsided by a PIP has a legitimate complaint about the process, whatever the underlying performance issue turns out to be.

When to Escalate to HR or Senior Leadership

Escalation is not failure. It is the right step when the situation needs authority, expertise, or policy knowledge beyond what one manager holds alone.

Signs Informal Coaching Is Not Enough

• The pattern continues after clear feedback and reasonable support.
• The issue affects safety, customers, team function, or compliance.
• The employee refuses to engage with the process at all.
• A formal warning, PIP, investigation, reassignment, or termination looks likely.

Partner With HR Before Formal Action

Before you take a formal step, review the evidence, the policy requirements, and how similar situations were handled for other employees. Make sure the employee understands the issue, what needs to change, and the process ahead. Avoid implying an outcome before HR has weighed in.

Handle an Exit Process Respectfully

If the relationship ends, keep the process dignified and confidential, and communicate through the channels your organization has defined. The exact steps vary by employer policy and jurisdiction, so treat this as a decision to make with HR and qualified local counsel, not a script to follow alone.

Common Mistakes Managers Make With Difficult Employees

• Waiting Until Frustration Takes Over

Delayed feedback turns a manageable pattern into a formal problem. A timely, proportionate conversation early is easier for everyone than a heated one after months of silence.

• Making the Discussion About Personality

“Unmotivated,” “toxic,” and “bad attitude” are weak starting points that describe the manager’s exhaustion more than the employee’s behavior. Replace the label with behavior, impact, and expectation every time.

• Being Inconsistent Across Employees

Similar issues need similar standards and similar documentation. Inconsistency is one of the most common HR-sensitive complaints, and one of the hardest to defend after the fact.

• Giving Feedback but Failing to Follow Through

A missed check-in, a vague plan, or a consequence that never arrives damages trust with the employee, and it signals to the rest of the team that the standard is optional.

• Treating Peer Conflict as a Disciplinary Issue by Default

Not every interpersonal problem is a performance issue. If the situation is really a clash between colleagues with no reporting relationship, our guide to dealing with difficult coworkers covers the right approach for that instead.

Manager Scripts for Common Situations

An Employee Repeatedly Misses Deadlines

“You’ve missed the last three delivery dates for this workstream, and each one pushed the release back for the rest of the team. I want to understand what’s getting in the way before we set the next date. What’s been blocking you?” Assume a blocker, not a lack of commitment, until the conversation rules it out.

• An Employee Reacts Defensively to Feedback

“I hear this feels unfair, and I want to understand your side. The behavior I need to change is [specific example], and the expectation going forward is [specific standard].” If the conversation gets heated, pause it and reschedule for later the same day rather than pushing through.

• An Employee’s Behavior Is Affecting the Team

“In the last two sprint reviews, you cut off two teammates before they finished their update, and the team has stopped raising blockers there. That’s the specific impact I need to see change.” Stay on the observed pattern, not on what colleagues have said about the person.

• An Employee Refuses Accountability

“I hear that the timeline was tight. The deliverable was still three days late and wasn’t flagged in advance, and that’s what I need to address. What can you do differently next time, starting with today’s task?” Redirect blame-based answers toward ownership and a next action. If the pattern repeats after two or three redirected conversations, document it and involve HR.

How First-Time Managers Can Prevent Problems Earlier

Proactive management prevents more problems than any conversation held after the fact, and this matters most in a manager’s first year. Our first-time manager guidance covers the fundamentals in more depth.

Set Expectations From the Beginning

Clarify priorities, quality standards, who decides what, communication norms, and how often you will check in. Research from the Program on Negotiation at Harvard Law School points to a simple mechanism: people make better, less overconfident decisions when they know in advance they will be held accountable. 

Ambiguity at the start turns an ordinary performance gap into a dispute over what was agreed.

Make Feedback Routine

Regular feedback and recognition make corrective feedback feel normal instead of alarming. An employee who only hears from their manager when something is wrong will read every conversation as a warning shot.

Build a Record of Support as Well as Concerns

Document training provided, check-ins held, real progress, and any accommodations made, through the right channel. A record that only shows problems looks selective, even when it isn’t.

Be Specific, Fair, and Timely

Knowing how to handle difficult employees well comes down to a short, repeatable sequence: gather the facts, address the behavior early, listen without lowering the standard, document consistently, coach with a real plan, and escalate when the pattern doesn’t change. None of that requires guessing at someone’s character.

If a direct report’s behavior is costing your team time, trust, or output, talk to PathWise about your team’s situation to work through the specific pattern you’re dealing with and what a fair next step looks like.