The meeting was going well until I asked the question.

We were forty minutes into a quarterly strategy session — a room full of senior leaders, the kind of meeting that moves slowly by design. Someone had walked through a workflow chart. A process with three approval gates before anyone could greenlight a decision that one person could reasonably make in four seconds. I watched the room nod at the slide. I waited for someone to say something. Nobody did.

So I asked: "Why does this need three sign-offs?"

The silence that followed had a particular texture. Not the silence of people thinking. The silence of people who had already decided the question wasn't welcome.

"That's just how we do it here."

I know now what I didn't fully understand then: the process question was right. The process was genuinely broken — we fixed it eight months later, and it mattered. But in the room that day, what I had done was spend capital I didn't have yet, on a fight I hadn't earned the right to start, in a way that made everyone uncomfortable rather than curious. I left that meeting having been right and having made things measurably harder for myself.

That tension — between accurate judgment and effective presence — is what this post is about.

---

The Seat You Earned and the Room You Walked Into

I've spent 25 years in senior technical leadership. In that time, I've worked alongside some of the most precise problem-solvers I've ever encountered. Leaders who could read a vendor contract in ten minutes and find the clause that would bite the organization in year three. Leaders whose pattern recognition moved so fast they had the answer before the meeting had finished framing the question. Leaders whose first instinct, in almost every situation, was accurate — and who still had a harder time in the room than their track record should have produced.

The pattern was consistent enough that I started paying close attention to it. The capability was real. The friction was real. And somewhere between those two things, organizations kept losing access to exactly what they'd hired for.

The gap isn't technical. It's navigational. You earned your seat through analytical rigor, pattern recognition, and results. And then you walked into a room that runs on different rules — rules that often feel arbitrary, unspoken, and mildly irrational — and discovered that the skills that got you in are not the same skills that keep you effective once you're there.

That's not a complaint. It's a design constraint. Understanding it as a design constraint rather than a character flaw is the first move.

---

The Message That Didn't Land

Here is something I had to learn the hard way, more than once.

"This won't work" and "I see a risk at point three that I think we need to address before we commit" contain identical information. They reach the same conclusion. The first puts the room on the defensive whilst making the messenger the focus. The second invites engagement. The difference isn't the analysis — the analysis is identical. The difference is the entry point.

I've watched technically brilliant leaders walk into a status review, front-load every conclusion, and spend the next forty minutes fighting to be heard in a room that had already stopped listening. The precision was genuine. The pattern recognition was accurate. The delivery cost them the audience before the argument had started.

Communication is bidirectional, and some of the work is yours. That's not a comfortable thing to hear. It isn't the whole picture either — I'll get to the parts that genuinely aren't your problem. But the bidirectional part comes first, because most writing on this topic skips it entirely, which does nobody any favors.

You don't have to perform warmth you don't feel. You don't have to soften your message until it's no longer accurate. But you do have to take responsibility for whether your message was received, not just whether it was correct. "I think what I said didn't come across the way I intended — let me try again" costs you nothing and builds more trust than being technically right and making someone feel blamed for it. I've said that sentence enough times that I could recite it at 3 a.m. It still works every time.

The other piece of this is relationship capital, and it doesn't replenish the way stamina does after a good night's sleep. Every leadership team has a finite economy of trust, and you are working within it whether you acknowledge it or not. Every illogical process, every ambiguous role boundary, every meeting that could have been a document registers as a system error that demands resolution. That instinct is exactly right in a crisis. In the routine friction of a leadership team, it will drain you if you let it run unchecked.

A practical filter I've come back to over the years: before raising a challenge, ask yourself whether this creates actual risk or whether it just offends your sense of how things should work. Both are valid experiences. Only one justifies spending capital you'll need for the architecture decision that actually matters next week. Being strategic about when and how you engage isn't capitulation. It's being effective. And being effective is the reason you're in the room.

---

What Doesn't Belong to You

Now the other side. Because some of what you experience in senior leadership is not yours to fix, and it's important to know the difference — so you don't spend years trying to change something about yourself when the system is what needs changing.

When you ask "why do we do it this way?" and the answer is "because we've always done it this way," you've found a process sustained by inertia rather than logic. The discomfort your question creates belongs to the process. It doesn't belong to you. That distinction matters enormously. Not every friction you generate is a signal that something is wrong with you.

The same is true for "culture fit." I've watched that phrase do two very different kinds of work over 25 years. Sometimes it's a legitimate read — the leader's style genuinely creates instability the organization can't absorb, and that's worth taking seriously. But I've also watched it deployed as a way to describe a leader whose pattern recognition is surfacing problems that the leadership team would prefer to leave unexamined. The diagnostic I offer to every leader who brings me this question is simple: look at outcomes. If the things you flag turn out to be real, if your track record demonstrates capability, if the friction you create points consistently at actual risks rather than perceived slights — then the fit issue may be about the organization's tolerance for accuracy, not your fitness for the role.

And on the question of how you communicate: effective communication and neurotypical-passing communication are not the same thing. You don't need to master small talk, enjoy unstructured networking events, or project executive presence as it's usually defined — which is mostly code for "behaves like the other executives." You need to communicate in ways that land. Written communication where your precision is a feature rather than a liability. One-on-ones where you can be direct without navigating an audience. Pre-reads that let the analysis speak before anyone has to process the delivery. Structured meetings where the agenda is a guide. These aren't accommodations. They're modes. Find the ones that work and build your operating rhythm around them.

The leaders who process differently and navigate senior leadership well have almost always found one or two allies who make this work. Not handlers — peers who can say "what they meant was" when delivery misfires, and who give you honest feedback when the friction you're creating is genuinely unproductive. The best of these relationships are reciprocal. You give them something too: usually the early warning on technical risks that nobody else in the room is flagging yet. That exchange has real value on both sides.

Find translators. Not handlers. The difference is everything.

---

The Feedback, Sorted

At some point in your senior leadership tenure, someone will tell you that you were "too direct" in a meeting. This feedback is almost never useless. But it almost always requires translation before it's actionable.

"You were too direct" might mean: you were right, your delivery cost you the audience, and adjusting your entry point next time would help. Take that feedback. It might mean: you were right, the room didn't want to hear it, and the problem isn't your delivery at all. That's organizational information, not personal feedback — file it accordingly. It might mean: you were wrong, and the directness made the error harder to recover from. That's the most useful version and the rarest to receive clearly.

Learning to hear the difference between those three takes practice and a trusted sounding board — someone close enough to the situation to give you the honest read, not someone who tells you what you want to hear.

There is also the energy conversation, which most people in this situation don't have explicitly enough. Senior leadership is socially expensive. The unstructured interactions, the political navigation, the constant switching between technical depth and social performance — for leaders who experience this switching cost at a higher rate, the accumulated drain is not imaginary and not weakness. It's resource consumption, and it has a ceiling.

Protecting your cognitive best for the problems that actually require it is not self-indulgence. It is resource management. The organization hired you for your best judgment, not your depleted remainder after three hours of performing approachability. Build recovery into your schedule. Know what restores you. Act accordingly.

---

The Room You Can Stay In

I come back often to that meeting with the three-sign-off approval process. The question I asked was right. The process was broken, and fixing it mattered. What I understand now that I didn't then is that I could have asked the same question differently — in a one-on-one with the process owner first, or in writing before the meeting, or even in the room but framed as genuine curiosity rather than a flaw I'd already diagnosed. Same outcome. Less friction. More speed.

That's the honest middle. It is not choosing between being effective and being yourself. It is learning, over time and through some real cost, which situations call for holding your ground and which call for adjusting your approach — and accepting that both of those are leadership.

Your pattern recognition is real. Your technical judgment is real. The things that make you uncomfortable in a meeting room often point at things that genuinely matter. The work is staying in the room long enough to do something about them. Sometimes that means adapting how you operate. Sometimes it means holding your ground and accepting the discomfort that causes.

Neither self-accommodation nor self-advocacy should be confused with weakness. Sometimes both are the right answer at the same time.

That's the job.

---

This is the second of three articles in the series. The first, "The Friction Framework," is written for organizations and managers working alongside neurodiverse technical leaders. The third, "When Structure Fails," addresses what happens when the structural preconditions for both break down.

References

• NeuroBridge. (2026). Neurodiversity in the Workplace: Manager Confidence and Training Report. NeuroBridge.