Designing Workshops for Neurodiverse Teams

Designing neurodiverse workshops is mostly a matter of writing down the things you would otherwise improvise. The prompts, the timings, the order of activities, what you are actually asking for - if those exist only in your head and arrive verbally on the day, you are running a session that rewards fast verbal processing and quietly taxes everyone else.

That is the honest version of the problem. Very few standard workshop conventions were designed at all; they were inherited. Go round the room and everyone says one thing. Shout out ideas. Ten minutes, discuss. Each of those is a specific cognitive demand - rapid verbal recall under social observation, unstructured turn-taking, unbounded time estimation - and each one has people in your group for whom it is dramatically harder than it looks from the front.

This guide covers what to change before the day, how to design contributions so there are always two ways in, how to manage sensory and cognitive load, what to do differently in the room, and how to offer adjustments without asking anyone to disclose a diagnosis to get them.

What neurodivergence actually changes about a workshop

Neurodivergence is a broad label - it covers autistic people, people with ADHD, dyslexic and dyspraxic people, people with anxiety disorders and plenty of others. There is no single adjustment that serves all of them, and some needs genuinely conflict: one person wants the room quiet and predictable, another needs movement and a change of pace every fifteen minutes.

What they have in common is that standard workshop design assumes a narrow default. It assumes you can hold a four-part instruction in working memory while also watching a slide and reading the room. It assumes you can generate a considered answer in the eight seconds between being asked and it being your turn. It assumes ambiguity is comfortable and that 'have a think and we'll come back to you' is a neutral instruction rather than an anxious ten minutes.

The practical consequence is that you should stop designing for a hypothetical average participant and start designing for range. A session built with slack in it - written instructions, more than one way to answer, predictable transitions - is not a compromised session. It is a better-run session that happens to also be accessible, and the people who did not need the adjustments will not notice they were made.

Send the material early - this is the highest-value change

If you only do one thing from this article, send the agenda and the actual questions at least 48 hours ahead. Not a topic list. The questions, worded exactly as you will ask them, plus what you expect people to produce.

Preparation time converts a live processing demand into an offline one. Someone who would have said nothing in a fast-moving discussion arrives with three points written down. Someone who needs to know what is coming can stop spending attention on prediction and spend it on the work instead. And you get better raw material, because people have had a day to think rather than ninety seconds.

Replace the conventions that do the most damage

Some standard moves are worth keeping and some are worth retiring outright. The table below is the short version of what to swap. In each case, the replacement is not slower or softer - most of them are faster, because parallel contribution beats serial contribution once you have more than about eight people in the room.

Give every contribution two routes in

The rule that carries most of the weight: for anything you want from the group, there should be a typed route and a spoken route, and neither should be presented as the lesser option. If the only way to be counted is to speak in front of twenty people, you will systematically lose the input of people who process slowly, people who are anxious about interrupting, and people who are perfectly capable of speaking but need thirty seconds you are not giving them.

Digital response tools do this work naturally, which is one of the few places where the technology genuinely matters. Running a poll, a word cloud or an open-text question in Session Flo means everyone answers simultaneously and privately, so no one is waiting for a turn or competing for the floor. The output arrives as a single screen you can talk about, which also gives you a way to credit a quiet person's point without putting them on the spot to defend it.

Treat sensory and cognitive load as a design variable

Working memory is finite and it is shared across everything happening in the room. Cognitive load research is unambiguous that anything competing for attention while people are trying to think - a busy slide, background music, an animated transition, a group talking at the next table - takes capacity away from the task you actually care about.

For some people the cost is mild. For others, particularly autistic participants and people with sensory processing differences, an over-stimulating room is the entire experience of the day, and by hour three the only goal left is getting through it. Nearly all of it is avoidable at no cost to anyone else.

Timing, breaks and the shape of the day

Long unbroken blocks are a design failure for everybody, and a disproportionate one for people with ADHD or chronic fatigue. Sustained attention is limited for the whole room, and the standard three-hour morning with one coffee break at the ninety-minute mark ignores that entirely.

The numbers below are a starting shape rather than a rule. Adjust them for your group, but adjust from something explicit - the failure mode is running to whatever the calendar invite happened to say.

Write the instructions down, every time

A spoken instruction with more than two parts will be lost by a meaningful share of the room, and the people who lost it will usually not ask. They will watch what everyone else does and copy it, which costs them the first two minutes of every activity and produces work that is a step behind.

The fix is trivial: every activity brief appears on screen, stays on screen for the whole activity, and is also pasted into the chat or handout. Three lines maximum - what to do, how long, what to produce. If your brief cannot fit in three lines, the activity is too complicated and would have gone wrong anyway.

Offer adjustments without requiring disclosure

Asking 'does anyone have any accessibility needs I should know about?' in front of a group is well-intentioned and close to useless. Answering it means disclosing something personal to colleagues, in public, at speed. Most people will say nothing and then have a worse day.

Build the adjustment into the default instead. If the agenda always goes out early, nobody has to request it. If every prompt has a typed route, nobody has to explain why they would rather not speak. If breaks are scheduled and the quiet room is announced, using them is not a request for special treatment.

Then add one private channel and mention it once, in writing: 'If there is anything about the format that would make this harder for you, reply to this email and I will change it - you do not need to tell me why.' That last clause is doing most of the work. It removes the price of asking.

Facilitating on the day - the small moves

None of these require you to know anything about who is in the room, which is the point. They are just better facilitation, and they happen to remove most of the barriers that make a standard workshop harder than it needs to be.

Where inclusive design and workshop energy conflict

There is a genuine tension worth naming. High-energy facilitation - fast rounds, competitive quizzes, rapid-fire brainstorms, loud music between activities - creates momentum, and some people love it. It is also the exact profile of session that is hardest for people who need predictability and low sensory load.

The answer is not to strip all energy out. It is to make the intense parts opt-in and bounded. A quiz with team scoring is fine if the teams are assigned rather than self-selected, the questions are visible in advance, and nobody is required to answer aloud. A fast ideation round is fine if it is four minutes and preceded by silent writing. What does not work is a whole day pitched at one energy level with no route through it for anyone who needs a different one.

Similarly, do not over-correct into a session so structured that there is no room to think out loud. Some neurodivergent people do their best work in fast, associative discussion. Range is the goal, and range means the day contains both quiet structured blocks and looser conversational ones, clearly labelled so people know which one they are in.

A pre-session checklist you can actually run

Work down it once while you are building the agenda, not on the morning. Most of the items cost minutes at design time and are impossible to retrofit at nine o'clock on the day.

The last item is the one people skip. A same-day written recap means that anyone who spent part of the session managing their own load - which is most people by hour four, neurodivergent or not - can recover what they missed privately. It is the difference between a session that was inclusive while it ran and one that stays inclusive afterwards.