Tech leader having a focused one-on-one conversation with an engineer in a quiet, structured workspace

A manager recently told me about a developer on their team. "Brilliant," they said. "One of our strongest engineers. But quiet in meetings, struggles with deadlines sometimes, and the team doesn't quite know how to work with them."

She wasn't frustrated. She was confused. Because the signals didn't match.

What she was experiencing is becoming more common in tech teams: working with people who think and operate differently. In other words, leading a neurodiverse workforce.

1. The Shift Happening in Our Teams

Neurodiversity refers to the natural variation in how people think and process information. It includes conditions like ADHD, autism, and dyslexia, but also people without a formal diagnosis who still experience the workplace differently.

And this matters, because diagnosis is not always present, or disclosed. But as leaders, we manage people, not labels.

2. When the Signals Are Misleading

In engineering teams, we're used to reading certain behaviors as indicators of performance: speaking up, communicating proactively, managing time consistently. But what happens when someone produces great work and at the same time doesn't fit those signals?

You may see more direct communication, difficulty with prioritization, sensitivity to noise, or a strong need for structure. These are often interpreted as gaps. But many times, they are simply differences.

What you observeCommon interpretationWhat it may actually mean
Quiet in meetingsDisengaged or unpreparedProcessing differently; benefits from async input
Misses informal check-insAvoidant or uninterestedUnstructured social situations are genuinely harder
Direct, blunt communicationUnprofessional or abrasivePreference for precision over social convention
Intense focus on a single taskNarrow or inflexibleDeep work preference; context-switching has a real cost
Struggles with shifting datesPoor time managementNeeds structured, explicit prioritization
Sensitivity to environmentDifficult or demandingSensory sensitivity, not attitude

This table is not a diagnostic tool. It is a reminder to pause before drawing conclusions. The wrong interpretation leads to the wrong intervention.

3. The Environment Is Often the Problem

Modern workplaces, especially in tech, can create unnecessary friction: constant interruptions, unclear expectations, shifting priorities, and heavy reliance on implicit communication. For some people, that's manageable. For others, it's simply overwhelming.

Add to this the fact that neurodiverse individuals are significantly more likely to experience anxiety and other psychiatric issues, and what looks like inconsistency can actually be someone navigating a system that wasn't designed with them in mind.

When the signals are misleading

4. What Better Leadership Looks Like

Supporting neurodiversity is not about special treatment. It's about better management.

Focusing on clarity becomes essential. Being explicit about expectations, priorities, and outcomes removes guesswork. Flexibility becomes a performance tool. Not everyone works best in the same way, and rigid structures can limit output without anyone realizing it.

And perhaps most importantly, leaders need to shift from judgment to curiosity. Instead of asking "What's wrong?", ask "What does this person need to do their best work?" That question produces a different kind of conversation and a different kind of outcome.

Organizations that have embraced this approach, like Dell and IBM, are already seeing the impact on innovation and performance. Not as a side effect. As a direct result.

5. The Manager's Role and Its Limits

As a manager, your role is to create the conditions for success, not to diagnose people.

That means listening, being informed, and guiding people toward professional support when needed. It also means continuing to build your own skills. Most of us were never taught how to support someone dealing with anxiety, time management challenges, or recurring setbacks. But we can learn.

Mid-market engineering teams operate with lean management structures, which makes this even more relevant. There's rarely a dedicated DEI function to lean on. The manager is the system.

6. When Your Team Meets the Outside World

Even if you build an inclusive environment internally, your team doesn't work in isolation. Clients and stakeholders may not share the same understanding of neurodiversity. What is normal inside your team can be misinterpreted outside of it. Direct communication could be seen as rudeness. Quiet participation as disengagement.

Part of your role as a leader is managing that interface. That might mean setting expectations with clients, providing context when needed, or coaching your team through those interactions when useful. But without asking them to fundamentally change who they are.

Because inclusion doesn't stop at the team boundary.

7. When Neurodivergence Impacts Performance

Here's the nuance. Many performance issues are actually mismatches between the person and the environment. When you improve clarity, structure, and flexibility, performance often improves. But not always.

Supporting neurodiversity does not mean lowering expectations. It means making them clear, fair, and achievable. If favorable conditions are in place and performance is still not where it needs to be, that needs to be addressed, just as it would for anyone else. With empathy, but also with accountability.

The distributed engineering teams I've worked with closest to this challenge are the ones that got this balance right: they invested in the environment first, and only then evaluated the person.

When neurodivergence impacts performance

FAQ

How do I know if someone on my team is neurodivergent?

In most cases, you won't. Diagnosis is rarely disclosed, and it's not your role to ask. Focus on behavior and environment, not on labels. If someone discloses a diagnosis or requests formal accommodations, involve HR and build a plan from there.

Does supporting a neurodiverse workforce mean accepting lower standards?

No. It means making standards explicit, fair, and consistently communicated. Ambiguity is not a neutral default, it's a design choice that disadvantages some people more than others. Clear expectations benefit everyone.

What is one thing I can do differently starting tomorrow?

Write things down more. Define what done means for every task. Send a written summary after every key conversation. These small changes reduce the ambient ambiguity that creates friction for neurodivergent team members, and they cost nothing.

Are there legal obligations I should be aware of as a manager?

In the United States, many neurodevelopmental conditions qualify as disabilities under the Americans with Disabilities Act. If a team member formally requests accommodations, the company has obligations. Don't handle accommodation requests alone. Involve HR and, when needed, legal counsel.

A Final Thought

Neurodiversity is not an edge case anymore. It's part of the reality of modern teams.

And the leaders who learn to work with it, rather than against it, will not only build more inclusive teams. They will build better ones.

If this resonates with how you're thinking about your engineering organization, I'd be glad to talk.

References and Further Reading