A director at a mid-size company spent eighteen months flagging the same operational risk in every planning meeting. She had the data. She had the timeline. She had made the case in writing more than once. The feedback in her annual review was that she needed to work on "influencing without alienating." Eight weeks later she left. The risk she had been pointing at showed up in Q3 earnings.
This is not a story about a difficult personality. It is a story about a diagnostic failure. The organization had a tool for handling friction, and it applied that tool, and the tool did not address the problem. The friction stopped. The underlying risk did not.
The Default Diagnosis
Research published in Harvard Business Review in May 2026 examined what happens when effective leaders create organizational friction. The finding was straightforward: organizations default to a single explanation. The leader needs to change. The research identified four distinct causes that actually operate in these situations: capability gaps, perception mismatches, identity conflicts, and system pressures. The system cause was the one organizations checked last, if at all.
The system cause is the interesting one, because it is the one that inverts the usual logic. When a system is dysfunctional and operating as designed, the leader who refuses to accommodate that dysfunction will generate friction. Not because they have a temperament problem. Because they have an accurate read of something the system is built not to surface. The organization experiences that accuracy as resistance, which is a reasonable description of what it feels like, and an unreliable guide to what it actually is.
The friction is not the problem. The friction is a signal about the system the leader refuses to accommodate.
Why Systems Brand Their Critics
Organizations are not, in most cases, consciously protecting dysfunction. What they are doing is optimizing for coherence. A leader who keeps raising the same issue disrupts planning cycles, slows decisions, and creates tension in rooms that are trying to move forward. From the outside, that pattern looks like a style problem. The framing that naturally follows is that the leader needs to learn to make their point more effectively, or to pick their battles, or to build more relationships before pushing harder.
What that framing misses is the question of whether the issue they keep raising is real. Operational competence and interpersonal friction can coexist. The two do not cancel each other out. A leader can be genuinely difficult to work with and simultaneously be correct about something important. An organization that treats the friction as evidence of the latter being wrong about the former has confused two separate data points.
This matters because the label tends to travel. Once a leader has been identified as someone who creates friction, the signal embedded in that friction stops being examined on its merits. The label does the work of the diagnosis. Everything the leader raises subsequently gets filtered through it.
The Cost of the Wrong Diagnosis
The immediate cost is talent. High performers who have accurate reads and are told to soften them will often conclude that the organization is not one where accuracy is valued. They leave. The dysfunction they were pointing at remains.
The secondary cost is harder to track. The person who replaces them, or who takes on the same responsibilities, learns quickly what kind of friction is acceptable. They accommodate the dysfunction, which produces smoother meetings and cleaner performance reviews. That accommodation looks like effectiveness. It gets rewarded. The organizational norm firms up around it.
By the time the underlying problem becomes visible, usually in a missed number or a failed initiative or a surprise departure higher up the chain, the connection to the original friction has been lost. The person who kept raising it is gone. The institutional memory of what they kept raising has faded. What remains is the organization's confidence that it handled the situation correctly, because the friction stopped.
What to Ask Before the Label Sticks
The practical question is not whether a leader is creating friction. Friction is a symptom, and symptoms require a diagnosis, not a suppression. The more useful questions are about the direction and accuracy of that friction over time.
Has what this leader flagged previously turned out to be real? Not necessarily in the timeline they predicted, and not always in the precise form they described, but broadly real? If the answer is yes, that is informative in a way that "they are hard to work with" is not. Accuracy does not make friction comfortable. It does make it worth examining before you conclude that the leader is the problem.
The other useful question is what the friction is pointing at. Not how the leader is raising it, which is a style question and a legitimate one, but what they are raising. If the answer is a systemic issue that the organization has a structural interest in not surfacing, the style conversation is probably a deflection, even if it is an unconscious one.
None of this means every difficult leader is a misunderstood prophet. Capability gaps, perception problems, and identity conflicts are real causes and they require real responses. The problem is the default, the reflexive move toward "the leader needs to change" that skips the diagnostic step entirely. Effective leaders get branded as problems when the organization's diagnostic process is too fast. Slowing that process down enough to ask what the friction is actually about is one of the more valuable things a senior leader can do.
In Agile Sucks! (When You Do It Wrong), Zac Parker and James Wright document a pattern they call "Successful Failure" — roughly 70% of Agile organizations report clean metrics and produce no real business outcomes. Inside those organizations, the leaders who kept saying the numbers were telling the wrong story were rarely recognized for their accuracy. They were sidelined for being resistant. The book examines what gets built when transformation looks fine on paper and the people pointing at the seams are treated as the problem.
Read Agile Sucks! (When You Do It Wrong) →