The “Say” Layer Is for the Supporter, Not the Person Being Supported
Why Think / Say / Do scripts the colleague, manager or leader receiving a disclosure — never the person making it.
A quiet design mistake shows up across a great deal of inclusion training: the scripts are written for the wrong person.
It is common to see workshop material that hands the neurodivergent employee a script — how to disclose a need, how to explain a difference, how to request an adjustment without sounding difficult. The intention is usually good. The effect is that the burden of translation stays exactly where it has always sat: with the person who holds the least structural power in the interaction, and the most to lose if the conversation goes badly.
Think, Say, Do — and who each layer belongs to
The Think / Say / Do method runs through every tier of the CARE, ENGAGE and ENABLE ladder.
Think is the internal cognitive shift — noticing an assumption before it hardens into a reaction.
Do is the observable action, built wherever possible around universal design, so that an adjustment does not require singling anyone out.
Say is the layer most often assigned to the wrong party. In this framework, Say is social scripting for the supporter — the colleague, the manager, the leader — not for the person being supported. It answers a different question than most training asks: not how should a neurodivergent employee explain themselves, but what does a manager actually say, out loud, in the moment a need surfaces.
The person disclosing a need has usually spent years working out how to ask. The person receiving that disclosure has usually had no equivalent practice at all — and it shows.
Why this matters for managers specifically
This is precisely the gap ENGAGE exists to close. A manager who has never rehearsed a response defaults to silence, over-formality, or an anxious over-correction — none of which count as inclusive conduct, however well-intentioned.
Giving the supporter a workable script, tested against realistic scenarios rather than invented ones, is what turns a good policy into something that actually gets said out loud on a Tuesday afternoon.
Universal design as the default “Do”
The corollary is that Do should rarely require a visible adjustment aimed at one person.
Written follow-ups after verbal briefings, predictable meeting structures, and unambiguous task instructions tend to help considerably more of the workforce than the one colleague who happened to ask for them first — which is also why they are easier for a manager to introduce without drawing attention to any individual.