Read a sample: 1. When Leadership Meets Emotional Sabotage
The meeting has barely begun when a project lead presents a recommendation her team has spent the week preparing. A colleague interrupts before she reaches the decision point.
“That’s not what we agreed,” he says. He offers a different account of the previous discussion, and the room turns toward him. The project lead tries to clarify, but the meeting moves on. Later, she tells her manager this has happened before: decisions are challenged in public, relevant information appears late, and responsibility becomes unclear when the work falls behind.
The manager faces several questions at once. Was the colleague correcting a genuine misunderstanding? Was the recommendation incomplete? Has the project lead been excluded from information she needed? Is there a recurring problem with how decisions are recorded? The manager cannot answer those questions from one account or one meeting. But neither should the uncertainty be an excuse to do nothing.
This is where leadership meets what this book calls emotional sabotage: a pattern of workplace behavior that disrupts another person’s ability to contribute, make decisions, maintain credibility, or carry out responsibilities. The behavior may be experienced as deliberate, and sometimes an investigation may establish a violation of policy. At the outset, however, the label is not a finding about anyone’s motives. It is a practical description of a problem that deserves careful attention.
The work is not to identify a villain. It is to understand what is happening, reduce avoidable harm, and use the authority and processes available to you responsibly.
Workplaces contain pressure, imperfect communication, competing priorities, and people with different styles. A tense exchange does not automatically amount to sabotage. Nor does the presence of hurt feelings settle what occurred. Feelings matter because they can reveal impact and point toward concerns that need attention, but a leader must still examine conduct and context.
The distinction is especially important when language becomes clinical or absolute. Calling a colleague “a narcissist,” “toxic,” or “a manipulator” may express frustration, but it does not tell a manager what happened or what needs to change. It can also make a fair response harder by turning a discussion of actions into an argument about character.
Compare these two descriptions:
> “Jordan is trying to destroy Priya’s reputation.”
> “In the project review and again in the client planning meeting, Jordan interrupted Priya while she was explaining the recommendation and said the team had not agreed to it. Priya says the interruptions prevented her from presenting the decision record. We need to review the records and hear Jordan’s account.”
The second description is more useful even though it is less certain. It identifies conduct, settings, a reported impact, and a next step. It leaves room for the possibility that Jordan had relevant information or understood the decision differently. It also leaves room for the possibility that a meaningful pattern is emerging.
This book uses terms such as undermining, blame shifting, and manipulation as shorthand for observable workplace concerns. They are not diagnoses, and they should not be treated as proof of intent. A person can contribute to a damaging pattern without understanding its effect. A person can also offer an innocent explanation that does not fully account for the evidence. Your responsibility is to take the concern seriously enough to examine it, without deciding the outcome in advance.
Healthy teams disagree. Colleagues question proposals, challenge assumptions, make mistakes, and occasionally speak sharply. A manager who treats every interruption or disagreement as misconduct can suppress the very candor a team needs.
Imagine that a colleague interrupts a presentation because the proposed course of action depends on an outdated requirement. The interruption may be awkward, and the team may still need a better way to raise concerns. But the challenge itself could protect the work. Similarly, a person who disputes an account of a missed deadline may be correcting an inaccurate assignment of responsibility rather than shifting blame.
A concerning pattern is more than disagreement. It may involve repeated actions that make it harder for someone to perform, participate, or be treated fairly. Consider questions such as:
- Does the conduct recur across meetings, decisions, or projects?
- Is the same person repeatedly left without information, contradicted without a chance to respond, or assigned responsibility that was not agreed?
- What happens after the concern is raised? Is there clarification and adjustment, or does the problem continue?
- Are accounts, records, and observed behavior consistent, or are there important gaps?
- What effect is the situation having on decisions, workload, participation, or trust?
Frequency alone is not the whole test. Repeated minor interruptions may call for a reset of meeting practices, while a single serious incident may require prompt attention under organizational policy. Conversely, similar behavior can have different meanings in different settings. A manager should not wait for a pattern to form before responding to a credible threat, suspected retaliation, or another serious concern.
Nor must every concern be classified conclusively before action is possible. You may not yet know why information was withheld, for example, but you can clarify who needs it and establish a shared process for distributing it. Practical steps can protect the work while a fuller assessment continues.
Emotional sabotage is a strong phrase, but its effects are not always dramatic. A capable employee may stop offering ideas in meetings because previous contributions were repeatedly dismissed. A team member may spend hours reconstructing…