Performance Issue or Neurodivergence? Stop Treating It as Either/Or
- Jul 27
- 3 min read
A senior leader messages you: "This person keeps missing deadlines, seems disorganised in meetings, and struggles to follow instructions. Is this their neurodivergence, or is it a performance issue? Can I start the PIP process?"
It's one of the most common questions we hear from managers, and it's usually the wrong question. Not because it isn't worth asking, but because it's framed as an either/or when the real answer sits somewhere else entirely.
The problem with jumping to a conclusion
Managers tend to land on one of two conclusions, fast. Either the employee isn't capable and needs a performance conversation, or the employee is neurodivergent and that explains everything. Both skip the step that actually matters: working out what's causing the pattern before deciding what to do about it.
Land on the first too quickly, and genuine neurodivergent traits get read through the wrong lens, treated as a discipline problem when they were never about capability at all. Land on the second too quickly, and real performance issues get waved through as "just how someone's brain works," which helps no one, least of all the employee, who never gets the clear feedback they need to actually improve.
The insight: look at the environment before you look at the person
The question isn't "Is this person capable?" It's "Have we created the conditions for their capability to be seen?"
A missed deadline caused by unclear written instructions is a communication design issue. A missed deadline caused by someone consistently not doing the work, regardless of how it's communicated, is a performance issue. Same symptom, completely different cause, and the difference only shows up when you interrogate the system around the person, not the person themselves.
A simple framework for managers
Before raising a performance concern, work through these five questions.
1. Is the pattern consistent, or does it change with context? If someone struggles with verbal instructions but excels with written ones, that's a processing preference, not a capability gap. If the struggle shows up everywhere regardless of format, that's worth exploring further as a performance conversation.
2. Has the expectation actually been communicated clearly? Vague instructions ("just make it look professional") disadvantage anyone who thinks literally or needs explicit detail. Before flagging non-delivery, check whether the brief itself was ever clear enough to deliver against.
3. Would a low-cost adjustment change the outcome? If providing a written follow-up after meetings, a quiet space for focused work, or an agenda in advance would likely resolve the issue, you're looking at an environment gap, not a performance gap.
4. Are you assessing the output, or how the work looked while it happened? Fidgeting, avoiding eye contact, or working in a non-linear order aren't performance indicators. If the actual output meets the standard, the process by which someone got there isn't the problem.
5. Would this same pattern be a non-issue in a different role or team structure? If the answer is yes, there may be less of a performance problem than a mismatch between the environment and how the person works best.
If you've worked through all five and the issue persists regardless of clarity, adjustment, or context, that's a genuine performance conversation, and it deserves to be treated as one, honestly and directly. Avoiding it isn't kindness. It's a disservice to the employee.
Put it into action
Use this as a five-minute check before any informal or formal performance conversation involving a neurodivergent employee. Document what you find. If most of your answers point to environment, address the environment first and revisit performance separately, later, with a cleaner read on what's actually happening.
This isn't about lowering the bar. It's about making sure everyone can clearly see it before you judge whether they've reached it.
The ND Professional. Better workplaces start with better questions.
.png)



Comments