← Latest papers
💻 computer science

Neurodiversity in Agile Teams: Obstacles and Inclusion Barriers

This study reveals that while agile practices offer potential for neurodiverse inclusion, their effectiveness is currently hindered by rigid organizational structures, stereotypes, and a lack of tailored support, necessitating a shift from individual adaptation to flexible, standardized accommodations.

Original authors: Lars Struck, Christian Veenaas, Robert Wiedekind, Joshua Riechmann, Maria Rauschenberger, Philipp Diebold, Simone Dogu, Michael Neumann

Published 2026-06-01
📖 5 min read🧠 Deep dive

Original authors: Lars Struck, Christian Veenaas, Robert Wiedekind, Joshua Riechmann, Maria Rauschenberger, Philipp Diebold, Simone Dogu, Michael Neumann

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine a software development team as a high-speed train (fitting, since the study was done at a German railway company). The train runs on a strict schedule, follows a set track, and everyone is expected to move in perfect unison. This is the world of Agile software development: fast, collaborative, and constantly moving.

Now, imagine some passengers on this train have brains that work like different types of engines. Some engines are built for deep, long-distance focus; others are built for spotting tiny details in the scenery; others might need a different kind of fuel or a quieter cabin to run smoothly. These are neurodivergent employees (people with autism, ADHD, dyslexia, etc.).

This paper asks: How well does this "train" accommodate these different engines, and what stops them from running at full speed?

Here is the breakdown of their findings, using simple analogies:

1. The Current Situation: A Patchwork Quilt

The researchers looked at what people are saying online (on Reddit and LinkedIn) and talked to 11 experts inside a company. They found that there is no single "rulebook" for how to include neurodivergent people in these teams.

Instead, the current state is like a patchwork quilt. Some teams are doing great things, like:

  • The "Asynchronous" Lifeline: Instead of forcing everyone to speak up in a loud, fast meeting (which can be overwhelming), some teams let people write their updates in a chat first. This is like letting a passenger write a note to the conductor instead of shouting over the noise of the train.
  • The "Tool" Advantage: Automated tests and clear checklists help everyone stay on track, but they are especially helpful for those who need extra structure to focus.
  • The "Strength" Match: When a team assigns a task based on what a person is naturally good at (like spotting patterns or organizing data) rather than forcing them into a generic role, it's like putting a high-speed engine on the right track.

However, the paper warns that if you apply Agile rules too rigidly—like forcing everyone to stand up and speak at the same time every morning—it can actually break the engine rather than help it.

2. The Nine Roadblocks (Barriers)

The study identified nine specific "speed bumps" that stop neurodivergent employees from thriving. Here are the main ones, translated into everyday terms:

  • The "One-Size-Fits-All" Uniform: The biggest barrier is when the company says, "Everyone must wear the same uniform and march to the same drum." If a team insists that everyone must speak up in meetings or work in an open office, it ignores that some people need quiet or written communication to do their best work.
  • The "Old Guard" Mindset: Some older managers or colleagues still think of ADHD as just "hyperactive kids running around." They don't realize that in adults, it might look like deep focus or a different way of thinking. This leads to skepticism: "Oh, you have ADHD? Well, I'm a bit distracted too, so we're all the same." This dismisses the real differences.
  • The "Unwritten Rules" Trap: Agile teams often rely on "team vibes" and unspoken norms. If you don't know the secret handshake or the hidden rule, you get left behind. Neurodivergent employees often need the rules written down clearly, not just hinted at.
  • The "Speed vs. Depth" Clash: Agile often values "fast and good enough." But some neurodivergent workers are like deep-dive divers; they take longer to get to the bottom of a problem, but they find treasures others miss. If the team penalizes them for being "slow" instead of valuing their thoroughness, they get punished for their strength.
  • The "Uncertainty" Freeze: Sometimes, regular team members want to help but are afraid of saying the wrong thing. They freeze up because they don't know how to interact. It's like being afraid to pet a dog because you don't know if it bites.
  • The "Crisis" Squeeze: When the company is under financial pressure or stress, the first things to get cut are usually the "extra" supports for inclusion. It's like stopping the train's air conditioning during a heatwave to save fuel; the system survives, but the passengers suffer.

3. The Solution: Flexible Tracks, Not New Trains

The paper doesn't suggest building a whole new type of train (a new software framework). Instead, it suggests adjusting the tracks the current train runs on.

  • Make the rules configurable: Just as you can adjust the seat in a car, teams should be able to adjust how they work. Can we have a meeting without talking? Can we submit feedback in writing?
  • Stop the "Fix-It" mentality: Don't try to "fix" the neurodivergent employee to make them fit the team. Instead, fix the environment so the team can fit the employee.
  • Clear Communication: Be explicit. If you want a written update, say "Please send a written update." Don't assume everyone knows to do it.

The Bottom Line

The paper concludes that Agile methods (the train) are actually great for neurodivergent people if they aren't run too rigidly. The problem isn't the people; it's the inflexible organizational structures and the lack of awareness.

To get the most out of these teams, companies need to stop treating "neurodiversity" as a checklist item and start treating it as a design feature. They need to build flexibility into their daily routines, allowing different "engines" to run on the same track without crashing.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →