I left a role in part because one cross-functional relationship kept overstimulating me and I did not have a framework to understand my own reaction pattern. My ADHD diagnosis did not magically fix leadership, but it gave me language for what was happening and a path to own it before it kept damaging relationships.
Before diagnosis, I would get intensely irritated in certain cross-functional dynamics, not with my direct team as much as in partner relationships where interaction style and pacing repeatedly overloaded me.
I remember one relationship clearly. She moved from one topic to the next to the next to the next like Red Bull was her default operating system. I am not saying she was wrong. I am saying my nervous system was getting lit up every time we interacted, and that overstimulation created friction I did not manage well. Eventually it contributed to me leaving that role. That part is uncomfortable to admit, but it is true.
It matters because leadership stories usually hide this part. We talk about frameworks after we figure things out. We skip the cost of not understanding ourselves early enough.
Then comes the lie everyone repeats ... "The grass is greener on the other side." No ... the grass is not greener. There is just more sh*t.
I changed roles and found new versions of the same trigger pattern. Different person. Different team. Same internal reaction. That was the turning point. The question stopped being "why are they like this?" and became "how do I lead well when this is how I react?" That shift matters more than any title change.
Leadership got better the moment I stopped outsourcing my reaction to other people's personalities.
Diagnosis as a Framework You Still Own
Diagnosis gave me a framework for response patterns.
- what overstimulation feels like in real time
- what kind of interactions spike reactivity
- where I lose signal and start operating from friction
Framework is useful. Excuse is useless. Owning it meant designing operating habits that protect relational quality under pressure, not because I wanted to be "nicer," but because cross-functional leadership breaks fast when your reactions run the meeting. I needed to stop treating overload as a personality conflict and start treating it as an operating condition I had to manage.
What Changed in Practice
I started treating self-regulation like any other leadership system ... pre-work before high-friction conversations, clear agenda boundaries, decision framing in writing, breathing room between context-heavy meetings, and intentional pauses before replying when I felt escalation energy rise. Nothing glamorous. Very effective.
The core move was simple. Separate stimulus from response. When I could feel overload, I stopped trying to win the moment and started trying to preserve the relationship plus the outcome. That single shift reduced avoidable cross-team conflict more than any communication framework deck I have ever seen.
One practical example ... I stopped trying to resolve high-friction ambiguity live in fast back-and-forth meetings. I moved key decisions into clearer written framing first, then used meetings to resolve deltas. That reduced context switching and lowered reactive conflict loops.
Another one ... when I could feel overload rising, I stopped arguing content and started clarifying sequence.
Turns out "winning the point" and "leading the room" are not the same sport.
- what decision are we making right now
- what belongs later
- who owns the next step
That small sequencing habit preserved more relationships than trying to "win" in the moment ever did.
Why This Is a Team Topic, Not a Personal Diary
If this only changed my mood, it would be personal wellness. It changed how I lead across multiple teams and personalities, and that is operational.
Leadership at scale is not just strategy quality. It is nervous-system quality under stress. If your reactions are unmanaged, your team eventually pays for it in slower decisions, avoidant communication, and trust erosion. When leaders regulate well, teams handle ambiguity better because the emotional temperature stays workable even when constraints are ugly. The inverse is also true. When leaders are dysregulated, ambiguity feels personal, collaboration gets sharp, and people start optimizing for self-protection instead of joint problem-solving.
Cognitive Variance Is an Advantage When Designed For
There is a second-order effect here. Once you stop pretending everyone processes information the same way, team design gets better for everyone.
- clearer written context
- cleaner meeting handoffs
- better decision logs
- fewer assumptions hidden in verbal backchannels
People without ADHD benefit from those systems too. Inclusive design is not charity. It is better engineering management.
This is why I treat cognitive variance like any other design constraint ... not a side conversation, not a soft topic, and definitely not something you solve by hoping people "communicate better."
The Operating Boundaries That Helped Most
The biggest improvements came from boundaries that looked small.
- fewer context-switch meetings stacked back-to-back
- explicit decision owners in cross-functional threads
- written pre-reads for high-stakes discussions
- explicit "not now" parking lot for tangents
Those boundaries reduced overstimulation load for me and reduced confusion load for everyone else. That is the hidden upside. What started as self-regulation work became team clarity infrastructure. Once those patterns were in place, they made it easier for other people with different cognitive profiles to do better work too.
Triggers still show up. Leadership is what you do in the room after they do.
The Leadership Protocol I Use Now
When I feel overstimulation rising in a cross-functional thread, I run a short protocol.
- Name the decision we are actually making.
- Split urgent from important.
- Move the rest into written follow-up.
- Confirm ownership before exiting the conversation.
That protocol sounds almost too simple, and that is why it works. It protects signal when your brain wants speed. It protects relationships when your body wants escape. It protects execution when the room wants noise.
What Ownership Looks Like on a Bad Day
The real test of this work is not when I am regulated and rested.
The real test is a bad day ... poor sleep, stacked meetings, and a thread that starts moving too fast.
On those days, old patterns still try to run:
- interrupt to regain control
- escalate tone to force clarity
- rush to closure just to end the overload
Ownership means noticing those instincts early and choosing a better move before they become team damage.
For me, that usually looks like saying one sentence out loud ... "I am losing signal. Let me slow this down so we make the right call." That line has saved more relationships than any clever framing. It does not make me weaker as a leader. It makes the room safer for honest decision-making.
It also gives other people permission to do the same. Once one leader models regulation out loud, teams stop pretending cognitive strain does not exist. Meetings get better because people can name overload without collapsing into drama.
Funny how fast a meeting improves when everyone stops role-playing as a perfectly calm robot.
That is the part I did not understand early enough. Self-regulation is not only personal discipline. It is cultural design. People mirror what leadership normalizes:
- if you normalize reactivity, teams normalize defensiveness
- if you normalize pause and clarity, teams normalize better judgment
No one gets this perfect. I still miss it sometimes. The difference now is recovery speed. I can name it faster, repair faster, and reduce collateral damage faster. That is what ownership gives you. Not perfection. Better reliability in how you show up when conditions are not ideal.
One final piece that helped was making repair explicit when I missed. A quick follow-up ... "I was reactive in that conversation, and I want to reset how we finish this decision." That sentence used to feel risky. In practice, it increased trust. People do not need leaders who never misfire. They need leaders who can own impact without defensiveness and get the room back on track fast.
If you want one hard indicator that this is working, watch cycle time on cross-functional decisions. When reactivity drops, decision loops shorten because people stop bracing for emotional whiplash and start collaborating on the actual trade-offs.
You feel this in meetings immediately ... less posturing, faster clarity, and fewer unresolved threads leaking into the next week.
This Week
Run one self-regulation retrofit in your leadership workflow.
- Identify one interaction pattern that repeatedly derails your signal.
- Add one structural guardrail before that interaction.
- Debrief afterward in writing ... what triggered, what worked, what to keep.
Do it for 2 weeks and watch how much friction was never about "difficult people" in the first place.
If you lead multiple teams, this becomes even more critical. You are crossing personalities, work styles, and pressure profiles every day. People mirror your emotional operating system faster than they mirror your strategy decks. If your default pattern is reactivity under overload, teams learn reactivity. If your default pattern is pause-clarify-decide, teams learn stability.
If this lands, read Your Team Doesn't Need a Buddy. It Needs a Coach. for the coaching side of relational leadership under pressure.
You do not become a better leader by finding cleaner environments. You become a better leader by building better responses inside the real ones. That is the work, and it is daily work, not a one-time insight. And yes, some days I still miss it. Owning it does not mean perfect regulation. It means faster recovery and less collateral damage when you miss. That difference is everything in leadership. Teams do not need flawless leaders. They need leaders who can notice patterns, own impact, and adjust behavior fast enough to keep trust intact.
One email a week from The Builder's Leader. The frameworks, the blind spots, and the conversations most leaders avoid. Subscribe for free.