A VP of engineering at a professional services firm had a habit her leadership team found increasingly uncomfortable. Every time a project was declared "on track" in a status meeting, she would ask one question: "On track to what, exactly?" She was not hostile. She did not grandstand. She just wanted a specific answer — a deliverable, a number, a date — rather than a general reassurance. The room would go quiet. People would flip through slides. The answer was almost never actually there.
Within eight months, she was in a structured feedback process that described her as "creating a culture of anxiety" and "demonstrating difficulty with collaborative leadership." The project she had been questioning shipped six weeks late, with scope that had been quietly reduced by roughly 30 percent. The reduction was never formally announced. It just happened.
She had been the only person in the room reading the actual signal. The organization called that a personality problem.
What Friction Actually Means in a Human System
Research published in HBR this month identified a pattern worth naming directly. When a leader creates friction — meaning they slow things down, surface discomfort, or challenge prevailing narratives — organizations default to a single diagnostic: the leader needs to change. The friction gets categorized as a communication gap, a culture mismatch, a behavioral issue. What rarely gets asked is whether the friction is telling the organization something it needs to hear.
Friction in complex systems is not inherently a problem. It is often information. A car's brakes create friction. A surgeon who stops a procedure to verify the patient's chart matches what's on the table creates friction. In both cases, the friction is the mechanism working correctly — the system slowing down before it gets something catastrophically wrong. What changes the valence of friction is whether the organization has the capacity to ask: what is this showing us? Most organizations do not have that capacity. They have the capacity to ask: who is causing this, and what can we do about them?
The leader who kept asking "why does this keep failing?" gets managed out. The leader who runs smooth retrospectives where nothing of consequence is ever said gets promoted. Then everyone wonders why nothing changes.
The Four Sources of Friction — and the One That Goes Unexamined
The HBR analysis identifies four actual sources of friction when a leader is labeled "the problem": capability (they genuinely lack a skill), perception (they are being misread), identity (their values do not fit the culture), or system (the organization itself is the source of the problem they keep surfacing). Of those four, only the first tends to get examined with any real rigor — and even that assessment is usually shaped by who does the assessing and what they find convenient to conclude.
The systemic source goes essentially untouched. Because examining it requires the organization to ask whether the leader asking hard questions is simply the only person in the room doing it, and whether the organization has mistaken that rarity for a defect. That is a more uncomfortable question than "does this person need coaching on executive presence." So it usually does not get asked.
This matters in a specific way. Systemic friction — where a leader keeps surfacing the same unresolved problem from different angles — is the clearest diagnostic signal available to senior leadership. It is the equivalent of an engine warning light that keeps returning after a mechanic clears the code. The code can be cleared again. The underlying condition is not waiting.
What Gets Lost When the Friction Generator Leaves
When organizations manage out the leader who creates productive friction, they do not solve the problem. They solve the discomfort. Those are different outcomes with very different trajectories.
The executive team returns to smooth status meetings where every project is on track until it suddenly is not. Retrospectives run cleanly. The metrics hold. And then, sometime in the next two or three quarters, something fails in a way that feels sudden but should not have been surprising to anyone who had been paying attention, and everyone agrees that the warning signs simply were not visible.
They were visible. They were being raised by someone in a leadership role who kept asking about delivery on commitments, kept questioning whether the numbers matched what people were experiencing, kept making the room uncomfortable in exactly the ways the room needed to be made uncomfortable. That person is gone now. And the first thing an organization does after removing its pressure gauge is point to the absence of bad readings as evidence that everything is fine.
The senior leaders worth knowing — the ones who have been through enough organizational cycles to recognize the pattern — can usually name two or three people in their careers who were branded as problems, managed out, and turned out to have been right about the precise thing the organization most needed to fix. The telling detail is that most of them can name those people immediately, without hesitation, as if they have thought about it before.
The Question That Comes Before the Feedback Conversation
None of this means every leader labeled difficult is right, or that friction is always diagnostic. Some people genuinely lack the skills they think they have. Some create chaos rather than clarity. The question is not whether a given leader is blameless — it is whether the organization has asked the right question before deciding whose behavior needs to change.
The right question is not "how is this person showing up?" The right question is "what are they consistently surfacing that we have not wanted to look at?" If the answer is nothing — if the friction genuinely has no recurring subject matter, no pattern, no specific concern underneath it — then the conversation about style and fit is probably warranted. But if there is a recurring subject matter, a pattern, a specific concern that keeps coming back in different forms, the organization owes it to itself to examine that before it examines the person raising it.
If you have someone in your orbit right now who keeps asking the question the room does not want to answer — the interesting conversation is probably not about their communication style.
Chapter 8 of Agile Sucks! (When You Do It Wrong) traces what happened to Iomega after it grew from $140M to $1.7B in three years under a mission that was clear, specific, and broadly understood. When that mission changed to "maximize shareholder value," the organization dismantled the very conditions that had produced the growth. The leaders who had built something real became, in effect, incompatible with a system that no longer needed them to build anything real. That is the pattern. The friction they had been willing to create was no longer useful to the organization. It was more comfortable to remove them than to ask what they were still trying to say.
Read Agile Sucks! (When You Do It Wrong) →