Neurodivergent Participants Are Not a Special Case: Design the Session So Nobody Has to Ask

Most facilitators have received the message: “Could I get the slides in advance? I process better that way.” It tends to come after the first session, or after a frustrating hour, and it usually comes from someone who has learned to ask for things politely and in small amounts. For every person who writes that message, others sit through the same hour without asking.

The cost is not only to them. A session designed for one speed of processing, one mode of response and one way of showing attention loses everyone who works differently, whether or not they ever say so. I do not need to know who is neurodivergent to see the design problem. I only need to notice how many participants must disclose something before the room works for them.

That is why I do not treat neurodivergent participants as a special case. The special case is the session built on a narrow set of assumptions. Neurodiversity in training is better handled in the design than in the exception list.

Federal guidance on workplace accommodations is a useful check on how much you are asking of people. The EEOC’s enforcement guidance on reasonable accommodation and undue hardship under the ADA says a request can be made orally, does not require special words, and can come from a representative on the person’s behalf. It also describes an interactive process between employer and employee, and says an employer may ask for documentation only when the need for the accommodation is not obvious.

I read that as a reminder of how low the bar is for the person asking, and how high the bar should be for the organization to make asking unnecessary. It does not tell a facilitator what a participant has or needs, and I do not guess. Whether a request is covered by the law is a question for an attorney. The design question is separate and simpler: what can I change so fewer requests are needed?

The easiest change is to offer the written version first. Post the discussion question in the chat before asking it aloud. Share the instructions for an activity in text as well as speech. Ask people to write for a minute before anyone speaks.

Written-first helps participants who need time to process, who think better in text, who are working in a second language, or who simply did not hear the first sentence because a dog barked. Nobody needs to explain why. The room gets slower in a good way, and the answers get better because people had time to form them.

Spoken options stay available. The point is sequence: written, then spoken, so the person who needs the extra minute is never the last to know what was asked.

A short agenda sent two or three days before the session removes a whole category of stress. People know how long it will run, what they will be asked to do, and whether they will be asked to speak. Participants who plan their energy around a meeting can decide how to spend it.

Include the questions you will ask, any prep you want them to do, and what will not be asked of them. Say plainly that cameras are optional and that chat is a full way to take part. That is the content that makes ADHD friendly meetings possible, and it costs ten minutes to write.

If your session has surprises, such as a cold call or a live role-play, say so in advance, and give people a way to pass. Surprise is not a teaching technique. It is a risk to the person who needs predictability.

Build in short stretches of silent individual work before group discussion. Two minutes of silent writing before a breakout does more for a mixed group than a long warm-up does. I now treat silence as a design element, not a failure of the facilitator.

A quiet-time default also changes the problem I describe in what to do when nobody talks. Often nobody talks because nobody had a minute to think. Giving the minute upfront makes the discussion easier to start and more varied once it does.

Camera on is not a measure of attention and I do not use it as one. Camera off is not disengagement makes the case. Some people listen better while moving, doodling or looking away from a face. Others find a screen full of faces tiring. If cameras are optional and chat is a full channel, people can arrange the conditions they need without a conversation.

I treat chat as a first-class response. I read it aloud, credit it and build on it. If chat only counts when it is read, people learn to wait and not to type. That is the difference between an option that exists and an option that works.

Defaults for neurodivergent participants overlap with the baseline for everyone: captions, readable slides, a clear structure and enough time. The full list lives in accessibility in live sessions. Treat the two as one design job, not two.

Inclusive virtual training design is not a separate track. It is the ordinary design, done with the actual range of people in mind. When someone does ask for something outside the defaults, say yes, work out the details together and thank them. Their request is information about the design, not an inconvenience.

Pick one session and make three changes. Send the agenda two days early. Post each question in chat before saying it. Add two minutes of silent writing before the first discussion. Then notice what happens to the quality of the contributions, not only the quantity.

You do not need to know who in the room is neurodivergent, and you should not ask. You need to design as if some of them are, because some of them are. The accommodations for live online sessions that people ask for most often cost very little when they are built in from the start, and a lot when they are added later.

Want a session designed so nobody has to ask?

Bring a session you run today. In a free consult we mark where participants must disclose something to take part, and rebuild those moments as defaults.