This is a three-part series about what happens when the way you think is simultaneously the reason you are good at your job and the reason your organization finds you difficult. It is written from the inside — by someone who has led technology organizations for twenty-five years and learned they were neurodiverse in adulthood, after most of those years had already happened.
This is not an awareness series. It is not about accommodation checklists or sensitivity training. It is about the specific structural dynamics that emerge when a leader whose cognitive wiring prioritizes systems, patterns, and consistency operates inside organizations that prioritize social fluency, ambiguity tolerance, and consensus.
The friction that results is real. Some of it is genuinely the leader's to own. Some of it is organizational infrastructure that was never built because no one who needed it was senior enough to demand it. This series draws the line between those two things with as much precision as the subject allows.
Organizations that hire technical leaders for their ability to see systems clearly and communicate directly will, in most cases, penalize exactly those behaviors once the leader is inside the organization. The penalty is rarely explicit. It operates through social feedback: the leader is "too blunt," "lacks emotional intelligence," "doesn't read the room," or "creates friction."
For neurodiverse technical leaders, this dynamic is not a surprise. It is the defining tension of their professional lives. What is less commonly understood is that the same dynamic affects organizations that have no neurodiverse leaders — because the organizational structures that accommodate cognitive diversity are the same structures that make any technical leadership effective.
When an organization cannot distinguish between a leader who is difficult because they are wrong and a leader who is difficult because they are seeing something the culture has agreed not to see, it will manage out both. The loss is not abstract. It is the loss of the most accurate analytical capability the organization had.
This series examines that loss — what causes it, what it costs, and what building the missing infrastructure actually looks like.
Neurodiverse technical leaders — diagnosed or not — who recognize the pattern of being simultaneously valued for their technical judgment and penalized for the way they deliver it. This series provides structural language for experiences that are usually processed as personal failure.
CEOs and executive teams who have watched a technically brilliant leader generate friction they could not explain or resolve. The series offers a framework for evaluating whether the friction is a signal about the leader or a signal about organizational infrastructure.
People leaders and HR professionals who mediate between technical leaders and organizational culture. The series provides analytical tools for distinguishing accommodation needs from performance issues — a distinction most organizations currently make badly.
A framework — the Friction Framework — for distinguishing between friction that signals a problem and friction that signals a capability the organization has not learned to use. The distinction is not academic. It determines whether the organization's response should be correction, accommodation, or structural change.
An understanding of what "navigating the room" actually requires when your processing style differs from the cultural default — and why individual adaptation has limits that organizational design does not.
A clear-eyed assessment of what happens when structure fails: not the acute failure of a crisis, but the chronic failure of an organization that depends on individual adaptation to compensate for missing infrastructure, and what it costs when the person doing the adapting leaves.
The series is designed to be read in sequence. Part 1 establishes the analytical framework. Part 2 applies it to the lived experience of leading while thinking differently. Part 3 examines what happens to organizations that never build the structural support their best technical leaders need.
If you are an executive rather than a technical leader, start with Part 3. The organizational cost described there is the most directly actionable from your position.
Not all friction is a culture problem. Some of it is the most accurate signal your organization is generating — and the leaders producing it are often the first ones managed out.
You got the seat. Now what? Practical guidance for neurodiverse technical leaders navigating senior leadership — the parts that are genuinely yours to own, and the parts where the system is what's broken.
Individual adaptation cannot compensate for missing organizational infrastructure. When structure fails, the leaders who surface its absence are the first to go — and the problems they pointed at stay.
This series is not a claim that neurodiversity is a superpower, a disability that requires only accommodation, or a personality type that organizations should learn to tolerate. It is a specific examination of how cognitive diversity interacts with organizational structure in technical leadership roles — and what both leaders and organizations can do about it.
It is also not a generalization from one person's experience to all neurodiverse leaders. Neurodiversity is a spectrum. Leadership is contextual. The patterns described here are consistent enough to be useful, but they are not universal, and individual variation matters.