A sabotaging employee can undermine projects, damage working relationships, and leave colleagues unsure about whom to trust. However, apparent sabotage is not always deliberate: poor communication, competing priorities, lack of skill, or unresolved conflict can produce similar results. The responsible response is to protect the work while investigating the behavior fairly. That means focusing on observable actions, documenting patterns, addressing concerns directly, and involving the right internal support when necessary. The following process helps managers respond firmly without making unsupported accusations or allowing harmful conduct to continue.
How to Deal With Sabotaging Employee Conduct and Protect the Team
#1. Define the Conduct You Are Concerned About
Begin by separating facts from interpretation. “She is trying to ruin the project” is a conclusion about motive, while “she withheld the revised figures until after the client presentation” is an observable event. Your first task is to identify the specific actions, dates, communications, and consequences that led you to suspect sabotage.
Look for conduct such as deliberately withholding essential information, altering work without authorization, misleading colleagues about decisions, missing agreed deadlines without explanation, or encouraging others to disregard a reasonable process. One mistake or disagreement does not establish a pattern. Consider whether the behavior could also reflect unclear instructions, inadequate training, excessive workload, or a legitimate concern expressed poorly.
Write a neutral description of each incident. Include who was involved, what was expected, what occurred, and how the work was affected. Avoid labels such as “toxic,” “disloyal,” or “troublemaker,” because they can distort your judgment and make later discussions less productive.
#2. Protect Critical Work Without Creating a Public Conflict
While you investigate, take sensible steps to reduce the risk of further disruption. This is not the same as punishing the employee or announcing that you distrust them. It means making important work more visible and less dependent on one person’s unverified updates.
For example, use shared project files, confirm decisions in writing, establish clear ownership, and create reasonable review points for work that affects customers, safety, finances, or deadlines. A second reviewer may be appropriate for a high-impact deliverable, but present that review as a normal quality-control measure rather than a public accusation.
Avoid removing responsibilities impulsively unless there is an immediate and serious risk. Sudden exclusion can intensify conflict, damage morale, and create the appearance of retaliation. Explain any temporary process changes in terms of business continuity and apply them consistently to comparable work.
If you supervise the team, reassure colleagues that concerns are being handled without inviting them to speculate. Do not ask employees to collect gossip or take sides. Your goal is to stabilize the work while preserving a fair process for everyone involved.
#3. Document a Pattern Using Neutral Evidence
Good documentation helps you distinguish a recurring problem from an isolated incident. Keep records of relevant emails, missed commitments, changed files, meeting decisions, and project effects. Note the original expectation and any explanation the employee provided. Documentation should help another reasonable manager understand what happened without requiring access to your private assumptions.
Focus on business impact rather than emotional reaction. For instance, record that a required approval was not shared, which caused a two-day delay and forced another employee to redo the submission. Do not write that the employee “wanted the team to fail” unless there is direct evidence supporting that claim.
Also document your own management actions. Record when you clarified expectations, offered support, asked for an explanation, or adjusted a process. This prevents the record from becoming one-sided and shows whether the employee had a meaningful opportunity to correct the issue.
Store information appropriately and limit access to people with a legitimate need to know. Documentation is not a private dossier. It should be accurate, proportionate, and connected to resolving the workplace problem.
#4. Check for Alternative Explanations Before Confronting the Employee
Before concluding that sabotage is deliberate, test other plausible explanations. Perhaps two departments received conflicting instructions. Maybe the employee did not have access to the latest file, misunderstood who owned a task, or believed a deadline had changed. A strong performer may also challenge a decision because they see a genuine operational risk.
Speak with relevant people separately and ask factual questions. Compare the employee’s account with project records, previous instructions, and the accounts of others. Be careful not to treat every disagreement as evidence of bad faith. Employees are allowed to question decisions, raise concerns, and make mistakes.
You should also examine whether your management contributed to the confusion. Were expectations written down? Did priorities change without being communicated? Did the employee receive the resources and authority required to complete the assignment? Fairness does not mean excusing harmful conduct, but it does mean correcting conditions that could have caused it.
This review is especially important when the alleged behavior involves interpersonal conflict. A colleague’s negative description may be accurate, incomplete, or shaped by a separate disagreement. Gather enough information to address conduct rather than simply adopting one person’s interpretation.
#5. Hold a Private, Direct Conversation
Once you have a reasonable factual basis, speak with the employee privately. Describe the behavior, explain its effect, and invite their response. Do not begin by calling them a saboteur or demanding that they admit an intention you cannot prove. A direct conversation should create accountability while leaving room for relevant information.
Prepare two or three specific examples rather than presenting a long list of complaints. Explain the expectation that was not met and ask what happened. Listen for practical explanations, but do not allow explanations to replace accountability if the conduct was still inappropriate.
You might say:
I want to discuss the client figures that were not added to the shared file before yesterday’s presentation. The team understood that you had the final figures, and the missing information caused us to present an incomplete update. Can you help me understand what happened?
Going forward, information needed for a shared deadline must be uploaded by the agreed time, or you need to tell me promptly if that will not happen. What support or clarification do you need to meet that expectation?
Keep your tone calm and specific. If the employee becomes defensive, return to the facts. If they raise a legitimate process problem, acknowledge it and address it without losing sight of the behavior that must change.
#6. Set Clear Expectations and Follow Up Consistently
A conversation has limited value unless it produces a clear next step. Explain what the employee must do differently, how success will be observed, and when you will review progress. Expectations should be practical and measurable: share status updates by a stated time, use the approved file, obtain authorization before changing a deliverable, or raise objections through the agreed channel.
Summarize the discussion in writing. A follow-up message might state what was discussed, the agreed expectations, the support available, and the date of the next review. Keep the language factual and professional. If the issue is serious or recurring, follow your organization’s performance-management or conduct procedures rather than inventing an informal system.
Apply the same standards to comparable employees. Consistency matters both for fairness and for credibility with the team. Do not monitor one employee obsessively while ignoring similar conduct from others, and do not impose new requirements only because a particular person has become difficult to manage.
At the follow-up, assess actual behavior. Recognize meaningful improvement, address partial compliance, and escalate through established channels when the conduct continues. A boundary without follow-through teaches the team that the stated expectation is optional.
#7. Escalate Proportionately and Rebuild Team Reliability
If the behavior continues, becomes more serious, or involves deception, retaliation, harassment, confidential information, safety, or significant financial or customer risk, involve HR or the appropriate internal authority. Bring your factual documentation, the expectations communicated, the employee’s responses, and the impact on the work. Ask for guidance on the applicable process rather than demanding a predetermined punishment.
Escalation should be proportionate. Not every difficult interaction requires a formal complaint, but repeated interference with work should not be dismissed as a personality conflict. If you are not the employee’s manager, report the concern through your supervisor or established reporting channel and avoid conducting your own investigation beyond what is appropriate for your role.
The team may need practical reassurance after the issue is addressed. Without disclosing confidential details, reinforce shared processes, decision ownership, communication standards, and routes for raising concerns. Do not ask colleagues to forgive, isolate, or monitor the employee.
Finally, review whether the team’s systems made the problem easier to create. Better visibility, clearer handoffs, access controls, and documented decisions can reduce dependence on individual goodwill. Accountability addresses the person’s conduct; reliable systems protect the team going forward.
How to Tell Sabotage From Legitimate Disagreement
Employees do not have to agree with every management decision. A person who challenges a plan, points out a risk, asks for evidence, or recommends an alternative is not necessarily sabotaging the team. Constructive disagreement usually addresses the work and can be brought into an open discussion, even when the tone needs improvement.
Sabotage concerns become more credible when there is a repeated pattern of actions that obstructs legitimate work without a reasonable explanation. Examples might include withholding information after being told clearly to share it, privately encouraging others to disregard an agreed decision, misrepresenting instructions, or changing important work without authorization. Even then, focus on the conduct and impact rather than claiming certainty about intent.
Ask yourself several questions before escalating:
- Was the expectation clear and reasonable?
- Did the employee have the authority, information, and resources needed?
- Was the action a mistake, a disagreement, or a deliberate departure from an agreed process?
- Has the conduct happened more than once?
- Did the employee raise a legitimate concern through an appropriate channel?
- Can the issue be corrected through clarification and follow-up?
This distinction protects both sides. It prevents managers from suppressing valid criticism, while ensuring that “speaking up” is not used to excuse conduct that knowingly disrupts colleagues or projects.
What to Say When the Employee Denies the Behavior
A denial does not automatically prove innocence, and it does not automatically prove guilt. Stay with the evidence and give the employee a fair opportunity to explain. If the employee says they never received the instruction, check the communication record. If they say the delay resulted from another department, verify the handoff rather than arguing from assumption.
You can respond without turning the meeting into a contest:
I understand that you did not intend to create a problem. My concern is the result and the process we agreed to use. The figures were not available when the presentation began, and no delay was reported beforehand. Let’s identify what happened and agree on how this will be handled next time.
If the employee raises a concern about your direction, separate that concern from the failure to follow the process. You can investigate whether the direction was reasonable while still requiring the employee to communicate obstacles promptly. If the evidence remains unclear, avoid making a formal accusation based only on suspicion. Increase clarity and follow-up, then evaluate future conduct against the stated expectations.
When the denial includes a credible allegation about another employee, do not dismiss it simply because the person is already under scrutiny. Record the concern and route it appropriately. Fair management requires investigating relevant information even when it complicates the original conclusion.
Protecting the Team Without Damaging Confidentiality
Teams often notice conflict before managers do, but they should not be recruited into an investigation. Sharing private details can create gossip, damage reputations, and make it harder to resolve the underlying issue. Employees generally need to know how work will be handled, not every detail of another person’s performance discussion.
Give the team process-based guidance. You might clarify who approves changes, where final documents belong, how missed deadlines should be reported, and whom employees should contact when a decision is disputed. These instructions help everyone and avoid singling out one person publicly.
If colleagues ask whether action has been taken, respond briefly and consistently:
I’m aware of the concern and am handling it through the appropriate process. I can’t discuss another employee’s private situation, but please continue to document work clearly and bring any specific issue to me promptly.
Also watch for secondary harm. Team members may begin withholding information from one another, excluding the employee from necessary discussions, or making sarcastic comments. Address those behaviors as well. Protecting the team does not mean permitting collective punishment or informal retaliation.
Closing Thoughts
Dealing with a sabotaging employee requires more than confronting difficult behavior. It requires disciplined observation, fair investigation, clear expectations, and reliable follow-through. Protect important work while you establish the facts, distinguish disagreement from deliberate obstruction, and address conduct privately and specifically. If the pattern continues or the risk is serious, use your organization’s established support and escalation processes. The immediate goal is to stop avoidable disruption; the broader goal is to build a workplace where concerns can be raised openly and responsibilities cannot be quietly undermined.