The System Isn't Broken for Them. It Was Never Built for Them: A Leader's Guide to Supporting Neurodiverse Team Members

You've got a team member who is brilliant at solving problems nobody else sees. They build systems in their head before anyone else finishes reading the brief. But they struggle in your Monday morning standup. They go quiet in brainstorming sessions. Their desk is a hurricane, or their Slack messages arrive at 2 a.m. in walls of text.

And you, the leader, have done everything you were told to do. You offered flexibility. You said your door is always open. You gave them extra time on deadlines when they asked.

Here's the part nobody wants to hear: none of those things are leadership. Those are concessions. Concessions don't build an environment where neurodiverse adults thrive. They build an environment where neurodiverse adults survive, spending enormous energy pretending your system works for them.

Leading neurodiverse team members, specifically adults with ADHD, autism, or both, demands something most leadership training never teaches. It demands that you look at your team's operating system and ask a question you've never been forced to ask: who was this designed for?

The answer, for the vast majority of workplaces, is neurotypical brains. Your meeting formats, your communication norms, your performance evaluation criteria, your definition of "professional behavior": all of it was built on a single cognitive template. And when someone doesn't fit the template, we call it an accommodation problem. We treat it as an exception to be managed.

It's not an exception. Conservative estimates put the neurodiverse population at 15 to 20 percent of adults. One in five. If your team has ten people, two of them are operating in a system not built for their brains. Most of them haven't told you.

The Accommodation Trap

The standard corporate playbook for neurodiversity goes something like this: someone discloses a diagnosis (or HR flags a performance issue), the company consults legal, and a set of "reasonable accommodations" gets documented. Extra time on tasks. Noise-canceling headphones. A quieter workspace. Permission to work from home on certain days.

These aren't bad things. But they share a fatal flaw: each assumes the workplace is fine and the person is the problem. The accommodations exist to help an individual cope with a system designed for someone else. The system itself never changes.

Think about it this way. If you built a staircase and then bolted a wheelchair ramp onto its side, you haven't designed an accessible building. You've added a patch. The building still tells wheelchair users: this place wasn't built with you in mind, but we're letting you in anyway.

Accommodations for neurodiverse employees work the same way. They signal tolerance, not belonging. The person receiving them knows the difference.

The cost of this approach is invisible to most leaders because it doesn't show up in performance metrics. It shows up in masking: the exhausting process by which neurodiverse adults suppress their natural cognitive patterns to appear neurotypical. Masking burns energy. It degrades focus. It creates anxiety. It explains why so many highly capable neurodiverse professionals appear to "burn out" or "disengage" after months or years of strong performance.

They didn't burn out from the work. They burned out from pretending.

Actionable takeaway: Audit your current list of accommodations. For each item, ask: Does this change the environment, or does it require the individual to work around it? If the answer is the latter, you've identified a design flaw in your system, not a need in your employee.

Stop Designing for the Default Brain

Every process your team follows was built on assumptions about how people think. Your meeting format assumes everyone processes information verbally at the same speed. Your email culture assumes everyone reads and responds to text with the same priority hierarchy. Your open-plan office assumes everyone works best with ambient social stimulation. Your performance reviews assume everyone demonstrates competence the same way.

None of these assumptions is true. They're defaults. And defaults are invisible until someone fails to meet them.

A team member with ADHD might produce their best work in intense, uninterrupted sprints followed by recovery periods where, to a neurotypical observer, they appear idle. A team member on the autism spectrum might need explicit, written context for tasks others pick up from a casual hallway conversation. Neither pattern is a deficiency. Both are legitimate cognitive approaches producing excellent results when the system makes room for them.

Let me bring this down to something concrete. Picture yourself running Toby's Taco Truck, a one-person operation where every hire matters. Your best cook, the person who builds tacos with precision and speed, keeping customers coming back, processes information through reading, not listening. You've always run your prep checklist verbally at the start of each shift. "We need extra pico today. We're low on carnitas. Don't forget to rotate the cheese." Your cook nods along, starts working, and misses two of the three items.

You have two choices. You label this a performance issue and start documenting. Or you print the prep checklist on a whiteboard, update it every morning, and let your cook read it, process it, and check items off. The second option takes four minutes. It costs you nothing. And it doesn't "accommodate" your cook. It redesigns a process existing as verbal-only because you never questioned why.

Here's the part most leaders miss: the whiteboard doesn't help only your neurodiverse cook. It helps everyone. Written checklists reduce errors across the board. Structured communication improves clarity for all team members. When you design for cognitive diversity, you raise the floor for the entire team.

THE SYSTEM ISN'T BROKEN FOR THEM. IT WAS NEVER BUILT FOR THEM.

Actionable takeaway: Pick one recurring process on your team: a meeting, a handoff, a review cycle. Write down the cognitive assumptions baked into it. Then redesign it with at least two different processing styles in mind: visual, written, asynchronous, whatever fits. Test the new version for two weeks.

ADHD at Work: What Leaders Get Wrong

ADHD in adults doesn't look like most people expect. It's not a child bouncing off walls. It's a senior analyst who produces exceptional strategic work but misses three deadlines in a row because time doesn't feel linear to her brain. It's a project manager who's running brilliant client calls but has ignored the shared tracker for two weeks because the format overwhelms his working memory.

The core challenge of ADHD is not a deficit of attention. It's a difference in how attention gets regulated. People with ADHD don't choose where to focus the way neurotypical people do. Their brains are interest-driven rather than importance-driven. When a task is novel, urgent, or personally meaningful, they lock in with a level of focus (hyperfocus) most neurotypical workers will never match. When a task is routine, abstract, or low-stimulation, their brain deprioritizes it regardless of its actual importance.

This means the standard productivity advice leaders offer, "break it into smaller tasks," "set reminders," or "write a to-do list," often misses the target. People with ADHD don't struggle because they lack systems. They struggle because systems designed for neurotypical executive function don't align with how their brains sequence and prioritize tasks.

What works instead:

Body doubling. Working alongside another person (even virtually or silently) provides enough external stimulation to keep the ADHD brain on task. This isn't a crutch. It's a legitimate neurological strategy. If you have a team member who does better working in the same room as others, or who keeps their camera on during Zoom coworking sessions, this is why.

Externalizing executive function. Instead of asking the person to remember priorities internally, make priorities visible externally. Physical kanban boards, shared dashboards with color-coded status indicators, and recurring 10-minute check-ins serving as external working memory all reduce the load on a cognitive system already running at capacity.

Deadline compression. This sounds counterintuitive, but shorter deadlines with smaller deliverables often work better than long runways. ADHD brains activate urgency networks. A two-week deadline feels abstract on day one and panic-inducing on day thirteen. A series of three-day sprints keeps the urgency signal active without the crash.

Actionable takeaway: If you lead someone with ADHD (disclosed or suspected), replace one long-cycle project assignment this week with a shorter sprint format. Give them a three-day deliverable instead of a two-week one. Watch what happens to both output quality and energy level.

Autism at Work: What Leaders Get Wrong

Autism in adults, particularly in professional settings, is deeply misunderstood. The stereotypes (poor social skills, rigid behavior, lack of empathy) describe a narrow and outdated picture. Many autistic adults in your organization are high-performing, socially competent professionals who have spent decades learning to mask their natural communication and sensory patterns.

The core difference isn't social ability. It's social processing. Neurotypical brains handle social cues automatically, below the level of conscious awareness. Autistic brains process the same cues manually, through learned rules and pattern recognition. An autistic team member might deliver a structured client presentation with confidence, only to feel exhausted afterward because every social interaction required active cognitive effort.

The other dimension most leaders overlook is sensory processing. Fluorescent lighting, background chatter, the hum of HVAC systems, cologne from three desks away: for many autistic adults, these aren't minor annoyances. They're genuine cognitive loads competing for the same mental bandwidth as the work itself. An autistic team member in an open-plan office isn't being "difficult" when they need headphones or a quieter space. They're managing a sensory environment that your brain filters automatically, but theirs does not.

What works instead:

Say what you mean. Indirect communication creates confusion and wastes energy. "It would be great if someone looked into the data issue" means nothing specific to a person who processes language at face value. "Alex, please review the Q3 data set for errors by Thursday at 2 p.m. and send me a summary" is clear, complete, and respectful. Clarity is not condescension. It's a courtesy benefiting every team member.

Provide context in writing. Many autistic professionals thrive when they receive task context, expectations, and feedback in written form. This isn't because they "don't listen." Written communication gives them time to process without the social load of real-time conversation. Send the agenda before the meeting. Follow up verbal decisions with a written summary. Put feedback in an email before (or instead of) a face-to-face conversation.

Respect routines and transitions. Autistic adults often rely on routine to manage cognitive load. Surprise schedule changes, last-minute meeting invites, and unstructured "brainstorming" sessions are cognitively expensive. Provide as much advance notice as possible for changes. Give explicit agendas for meetings. Structured doesn't mean rigid. It means predictable, and predictable means efficient.

Actionable takeaway: Review your team's last five meeting invitations. How many included an agenda? How many were sent with less than 24 hours' notice? Start a policy: no meeting without a written agenda sent at least one business day in advance. This one change reduces cognitive load for autistic team members and improves meeting quality for everyone.

The Disclosure Problem (and Why It's Your Problem)

One of the most common things leaders say when this topic comes up: "I'd love to support my neurodiverse team members, but nobody has told me they need accommodations."

This misses the point entirely. Most neurodiverse adults don't disclose at work. Research consistently shows that the majority of employees with ADHD or autism choose not to share their diagnosis with their manager or HR. The reasons are straightforward: fear of stigma, fear of being seen as less capable, fear of being sidelined for promotions, and a well-founded belief, built from years of experience, that the disclosure changes how people perceive you.

Waiting for disclosure before making changes is a passive leadership strategy. It puts the burden of vulnerability on the person with the least power in the relationship. And it guarantees you'll never help the team members who need it most, because those are the ones who've learned to hide.

Consider what disclosure looks like from their side. They walk into your office, tell you something deeply personal about their neurology, and then hope you don't treat them differently. Hope you don't lower your expectations. Hope you don't start explaining things more slowly or checking in with a worried tone. Hope their next promotion review isn't colored by the word "disorder" sitting in the back of your mind. For most neurodiverse professionals, the math doesn't add up. The risk of being seen differently outweighs the slim chance of getting meaningful support.

The better approach: design for neurodiversity by default. Make your team's processes, communication norms, and work environment flexible enough to accommodate different cognitive styles without requiring anyone to raise their hand to explain why they're different. When you build a system where written agendas, explicit instructions, flexible work patterns, and multiple communication channels are standard, you remove the need for disclosure. You make inclusion the default, not the exception.

Actionable takeaway: Stop waiting for someone to ask. Pick three process changes from this article and implement them for your entire team this week. Not as accommodations for a specific person. As upgrades to how your team operates.

Leading Neurodiverse Adults Starts with Your Own Assumptions

The hardest part of this work isn't learning strategies. It's examining what you believe about competence, professionalism, and "normal" workplace behavior.

Is maintaining eye contact during a conversation a sign of respect, or a neurotypical social norm you've mistaken for a universal truth? Is "attention to detail" defined by the end product, or by whether the process looks organized along the way? Is "team player" defined by the quality of collaboration, or by showing up to every optional social event?

Every one of these questions exposes a bias. Not a moral failure. A design assumption. And leaders who want to build teams where neurodiverse adults contribute at their full capacity need to rethink those assumptions one at a time.

This isn't about lowering standards. It's about separating the standard (the outcome you need) from the path (the process someone takes to get there). When you care more about the path than the destination, you're not managing performance. You're enforcing conformity.

Leadership has always been about getting the best from the people in front of you. All of them. Including the ones whose brains don't match the template you were trained on.

Start with one process. One meeting. One conversation. Redesign it for the team you have, not the team the system assumes.

Your neurodiverse team members aren't asking you to fix them. They're waiting to see if you'll fix the environment.

Actionable takeaway: Write down your team's three unwritten rules about "professionalism." For each one, ask: Does this describe an outcome or a behavior? If it describes a behavior ("responds to messages within an hour," "speaks up in meetings," "keeps a clean desk"), rewrite it as an outcome. Then share the updated expectations with your team.

LEAD . IMPROVE . GROW