top of page

What High-Performing Organizations Get Right About Neurodivergence

  • Writer: Gillian Forth
    Gillian Forth
  • Feb 24
  • 2 min read
Seven people in an office with brick walls, sharing a laugh around a desk. A woman stands holding papers. Plants and charts in the background.

I have worked with many large organizations, including banks, consulting firms, insurance companies, and branches of the government, and most of them want to hire and retain disabled talent but they also mainly invest in surface level awareness and one-off training. There's a flash in the pan of energy and enthusiasm, with a slight movement of the needle, but it's nowhere near sufficient to make real, lasting change.


Here is the uncomfortable truth: most organizations say they support neurodivergent employees, but very few have actually built the internal muscle to do it well.


It is one thing to approve an accommodation request. It is another thing entirely to have HR teams and leaders who are competent and confident navigating neurodiversity in real time, in messy human situations, under pressure.


Right now, many workplaces are stuck in performative inclusion. Policies exist. Statements are polished. But when a neurodivergent employee discloses, asks for support, or simply works differently, leaders often freeze, overcorrect, or quietly hope HR will handle it.


Building true neuro-inclusive workplaces requires investing in internal capability at three levels:


First, foundational competence. HR and leaders need a working understanding of neurodivergence that goes beyond stereotypes and diagnostic labels. This includes executive functioning differences, sensory needs, communication styles, and the reality that accommodations are often simple but highly individualized.


Second, practical confidence. Knowing the policy is not the same as knowing what to say in the moment. Leaders need scripts, decision frameworks, and real world practice navigating disclosure conversations, performance discussions, and evolving accommodation needs. Confidence is built through application, not PDFs.


Third, systems fluency. Accommodations do not live in a vacuum. They intersect with performance management, team dynamics, workload design, and psychological safety. Organizations that treat accommodations as one off exceptions create friction for everyone involved. Organizations that embed flexibility into their systems reduce the need for constant case by case firefighting.


If your organization believes “we handle accommodations when they come up,” you are likely underestimating the hidden load on neurodivergent employees and frontline managers. Most people are quietly compensating long before they formally ask for support.


Neurodivergent employees need support that is timely, individualized, and stigma aware

• Managers need clarity, guardrails, and permission to respond humanely without legal panic

• HR needs scalable processes that are compliant and actually usable

• Organizations need retention, performance, and reduced burnout costs


When you build competence and confidence internally, accommodations stop being viewed as special treatment and start being understood as good work design.


Some leaders worry that expanding accommodation literacy will open the floodgates or create inconsistency. The evidence we see in practice suggests the opposite. When expectations are clear and flexibility is normalized, teams experience less ambiguity, not more.


Organizations that invest now in neuro-inclusive capability are building a competitive advantage in retention, engagement, and innovation. Those that rely on reactive, case by case responses will continue to bleed talent and wonder why their inclusion efforts are not landing.


If your managers are still asking HR, “What am I allowed to do here?” that is your signal. The work is not just policy it's building human competence at scale.


Where does your organization feel most confident right now and where are people still quietly guessing when it comes to supporting neurodivergent employees?

 
 
 

Comments


bottom of page