ND-Friendly Ops: What It Actually Means to Design for Neurodivergent Workers
ND-friendly operations is not about accommodations. It is about redesigning the system so that the system absorbs the load — not the individual.
What “ND-friendly” actually means in an operational context
“ND-friendly” is not a checklist item or a diversity statement.
In an operational context, it means designing systems, workflows, and tools such that the system absorbs structural complexity — rather than silently offloading it onto individual workers to manage through extra effort, memory, or social navigation.
Most workplaces do the opposite: they build processes for an assumed-default cognitive style, then ask workers who do not fit that default to quietly compensate.
ND-friendly ops is the attempt to close that gap at the system level.
What ND-friendly ops is not
-
It is not a list of individual accommodations (noise-cancelling headphones, flexible hours).
Those matter, but they address symptoms, not the underlying design problem. -
It is not only for diagnosed neurodivergent workers.
Systems that absorb load instead of people tend to be better for everyone — especially in high-complexity, high-turnover operational environments. -
It is not “making things easier” in the sense of removing challenge.
It is making sure the hardest parts of a role are the parts that matter — not the invisible overhead of navigating a system that was never built for how your brain works.
The core design shift
The shift from a conventional ops design to an ND-friendly one can be summarised as:
| Conventional assumption | ND-friendly redesign |
|---|---|
| Workers adapt to the system | The system is designed around cognitive reality |
| Edge cases are the worker’s problem | Edge cases are documented and absorbed by process |
| Consistency comes from training people | Consistency comes from reducing ambiguity in rules |
| Exhaustion is a personal management issue | Exhaustion is a signal of design friction |
What this looks like in practice
A few patterns that appear repeatedly in ND-friendly operational design:
1. Externalise working memory
Reduce the number of things a worker has to hold in their head at once.
This means decision trees, visible checklists, and handover protocols that live
in the system — not in undocumented “how we do it here” knowledge.
2. Reduce rule ambiguity
When rules have too many exceptions, or when formal rules differ from informal
practice, workers have to perform constant rule-translation.
ND-friendly design maps the gap and closes it — or at minimum, makes the gap
visible and named.
3. Align tools with tasks
When dashboards show proxies instead of what workers actually need to make a
decision, they add cognitive friction at every use.
ND-friendly tooling asks: what does this person actually need to see to do their
job safely and accurately?
4. Make escalation paths explicit
Ambiguous escalation — “use your judgement”, “check with your manager” — places
a social navigation burden on workers who may find informal hierarchies
particularly costly.
Named, documented escalation paths reduce this load substantially.
How this connects to my research
My work on cognitive friction in operations treats ND-friendly design as an operational principle, not a welfare measure.
The argument is: when systems are designed to absorb load instead of individuals, the organisation gets more stable outcomes and less hidden attrition — independent of whether any given worker has a formal diagnosis.
Paper B in my current research programme develops a measurement instrument for this, focusing on how system-level friction accumulates and distributes across workers with different cognitive ecologies.
A working definition
ND-friendly ops: an operational design orientation in which system complexity is absorbed by the system itself — through process clarity, tool alignment, and explicit protocols — rather than distributed as invisible cognitive labour onto individual workers.
This note is part of my long-term programme on neurodivergent-friendly
operations.
More notes → /notes