Planning Teams for Neurodivergent Strengths in the Annual Cycle
September and October often decide more than next year’s budget. They decide who gets asked to carry the hardest work, which teams get built around real capability, and which people spend another year being measured against a narrow idea of the “well-rounded” employee. And many employees have no idea how important this cycle is. They just feel the outcome. Who gets the new project, without fully understanding the why. And sometimes it feels like you will never be assigned to that desired project, because your flaws are just too pronounced. Even if your strengths are also exceptional. Somehow that spike in talent as high as Mount Everest doesn't seem to be as important as that dip in another skill, that seems to be as deep as the Mariana Trench.
And guess what? The people who feel this are often the neurodivergent employees because we often have what psychologists and workplace inclusion specialists call spiky profiles(1). A person may show exceptional strength in pattern recognition, systems thinking, memory, visual reasoning, quality control, writing, crisis response, or original problem solving, while finding other tasks genuinely draining or difficult. The gap can be large.
Annual planning is the right time to treat that gap as design information, not as a performance flaw. This will not only lead to better planning outcomes, but also more engaged employees. And it will be fairer, because talent and weakness will be given the same weight when it comes to making decisions on who gets assigned where.
Annual planning should include people design, not just headcount
Most planning cycles ask familiar questions.
What projects are on the roadmap? What budget do they need? Which roles are open? Which teams are at capacity?
Those questions are useful, but incomplete. A project does not succeed because a spreadsheet says six people are assigned to it. It succeeds because the right mix of thinking styles can move through uncertainty, detail, execution, communication, and change without burning people out.
Neurodiversity, a term introduced by sociologist Judy Singer in the late 1990s, frames neurological differences such as autism, ADHD, dyslexia, dyspraxia, Tourette syndrome and others as part of natural human variation. That does not mean every challenge disappears. It means the workplace should stop treating one style of attention, communication, learning, and energy management as the default human setting.
For managers, the practical shift is simple to state and harder to practise:
Plan teams around complementary contribution, not interchangeable contribution.
The old model asks everyone to be mostly average at everything. And when looking at skills distribution in neurotypical people, this is fair. Most people hover for most skills around the average, with limited variation. Neurodivergent folks however, may have pronounced strengths and really struggle in other areas. Their distribution pattern of skills shows unusually high peaks and pronounced lows. The aforementioned Spiky Profile.
Each person attends every meeting, tracks every stakeholder, writes every update, handles ambiguity, manages detail, switches context, and delivers specialist work. Each person is supposed to be doing it all to an average standard. That model is inefficient for many people. For some neurodivergent employees, it is actively disabling.
The better model asks:
Where does this person produce unusually strong work?
Where do they lose energy, accuracy, or confidence?
What pairing or structure would let their strengths show up more often?
In the teams, who does what and why?
What friction can the manager remove before delivery pressure rises?
These questions belong in annual planning because by the time a project is already slipping, correcting this becomes exponentially harder. The manager is left with escalation, overtime, and vague encouragement. October is a better time to design the work than March is to rescue it.
Spot extreme talents by looking for repeatable evidence
Extreme strengths rarely announce themselves in the language of job descriptions. They show up in patterns.
A neurodivergent employee may not say, “I have exceptional systems thinking.” They may be the person who notices the hidden dependency that would break the roadmap. Someone with ADHD may not describe themselves as strong in urgency or divergent thinking. They may be the person who finds three possible routes around a blocked delivery path before others have named the problem. An autistic colleague may not promote their accuracy. They may be the one who finds the edge case in a process that everyone else skimmed past.
The task is not to diagnose people. Managers shouldn't infer conditions or play doctor. The task is to observe work with precision—and stop letting substantial difficulties overshadow exceptional strengths. Take my own profile: give my ability to network and connect the room the exact same weight you give my time blindness. Don't write off my output just because my timeline slipped.
A useful evidence base includes:
Work samples that show unusually high quality, speed, originality, or consistency
Repeated feedback from peers about where the person adds rare value
Situations where the person enters a state of deep focus or high engagement
Problems the person solves that others avoid or miss
Tasks the person keeps returning to because they match their way of thinking
Performance reviews often flatten this evidence. They reward average competence across a generic list of categories and differentiate people mostly by picking apart their weaknesses. Annual planning needs a completely different lens: ask what the person is capable of delivering when conditions are actually designed for them to succeed.
A simple manager note might look like this:
Observed strength | Evidence | Conditions that helped |
Finds defects in complex material | Caught recurring data errors before release | Quiet review time and clear acceptance criteria |
Connects ideas across teams | Proposed a workaround when two projects clashed | Early access to context and freedom to sketch options |
Learns technical detail quickly | Built working knowledge of a new tool within days | Self-paced learning and written documentation |
Spots user confusion | Rewrote instructions that reduced support questions | Concrete examples and time to test language |
This is not special treatment. It is basic resource planning.
Research and practice in occupational psychology have long recognised that job fit affects performance and wellbeing. The same principle applies here. If a person’s cognitive strengths are central to the project design, they are more likely to contribute at a high level. If their biggest barriers sit in the centre of the role, the team pays for that mismatch.
Name real struggles without making them the person’s identity
A strengths-based approach becomes dishonest if it erases or minimizes the impact of struggles.
Some people are brilliant at analysis and find rapid context switching painful. Some produce outstanding creative work but leave people disappointed because they are inconsistent or even sloppy in routine admin tasks. Some communicate well in writing and freeze in live discussion. Some can focus for hours on complex detail but struggle to start when a task is vague. Some are highly sensitive to noise, interruption, conflict, lighting, or unclear expectations.
These are not character defects. They are work design facts.
The manager’s role is to make those facts discussable without creating shame. That requires careful language.
Instead of asking, “Why can’t you manage stakeholder updates?”, ask, “Which parts of the update cycle create the most friction?” And an honest answer might be that the employee doesn't see the value of these stakeholder updates because they themselves view updates like those as superfluous. That's a difference in style, not a moral failing. And a difference in style can be bridged.
Instead of demanding, “You need to be more flexible,” ask, “What kind of change notice helps you adjust without losing the thread?” Accept that for some people, change will always take a real physical toll. Once you stop trying to make change feel pleasant, you can focus on managing the fallout—like building in planned downtime so they can recharge and reset.
Instead of writing, “Poor listener,” specify, “Live verbal updates are hard to process. Written summaries are more accessible.” And then determine, if live verbal updates are necessary. If they are, is there a mitigation strategy that you can put into place? ideas are, more breaks to process information, or live transcription so that the employee can both read and listen to what others are saying.
Good planning separates three things that often get mixed together:
Work issue | Better question | Possible support |
The person misses details after meetings | How is information captured and confirmed? | Written decisions, clear owners, meeting notes |
The person avoids ambiguous tasks | What definition of done is missing? | Examples, acceptance criteria, first-step agreement |
The person struggles with interruption | What focus time does the work require? | Protected work blocks, fewer ad hoc requests |
The person reacts strongly to sudden change | How much notice can the team give? | Early warning, change log, priority reset |
The point is not to remove all challenge. Growth still matters. But growth works best when people are not spending most of their energy hiding predictable struggle.
Pair complementary profiles with intent
Project teams often get assigned by availability. Someone has capacity, so they are added. Someone knows the system, so they inherit more work. Someone is reliable, so they become the backstop for everything.
That is how teams become overloaded with hidden labour.
A better annual planning habit is to pair people based on complementary profiles. This works especially well when one person’s extreme strength sits beside another person’s natural ease.
Examples include:
Strong profile | Common friction | Complementary partner |
Deep technical specialist | May struggle to translate detail for non-specialists | Communicator who can shape updates and questions |
Big-picture idea generator | May struggle to finish or sequence tasks | Delivery-focused planner who enjoys closure |
Detail and quality expert | May get stuck in perfection or edge cases | Prioritiser who can decide what is good enough |
Fast crisis responder | May neglect documentation after the fix | Process-minded colleague who captures learning (or an AI who supports the employee) |
Written thinker | May find live workshops draining | Facilitator who can gather input before and after |
The pairing should not create a parent-child dynamic. One person is not there to “handle” the other. Both people bring value. Both receive support. Ideally both get to do the work they thoroughly enjoy and can receive recognition for.
Managers can protect that balance with three clear agreements.
Define the shared outcome.
The pair should know what they own together, not just what each individual is meant to do.
Name the handoff points.
If one person explores options and another shapes the delivery plan, agree when exploration stops and planning starts.
Make invisible work visible.
Translation, sequencing, documenting, reminding, and calming confusion are real project contributions. They should show up in workload and recognition.
This is where many teams fail. The person with strong organisation skills quietly carries the friction created by everyone else. The person with rare specialist insight gets praised for brilliance but never learns how their work affects delivery. Both patterns breed resentment.
A manager can prevent this by treating the pairing as a design choice, not a favour.
Build structures that remove friction before the work begins
Neurodivergent strengths often appear or disappear depending on the environment. A person who seems distracted in a noisy, interruption-heavy setting may produce excellent work with protected focus time. Someone who seems resistant in a vague project may move quickly once the goal, owner, and next step are clear.
Facilitating structures don't need to be complex; they just need to be consistent. And remember: structure isn't just tools or software—it’s process. It’s how work turns into time and tasks. Standard capacity planning only counts hours on a calendar. That completely misses the real tax on energy—context switching, sensory load, emotional labor, and ambiguous directives that drain neurodivergent workers long before the actual work begins. A person may have six free hours on paper and no useful focus left. Another may do their best work early in the day and lose accuracy after repeated meetings. Someone else may manage delivery well if they do not also have to chase every response.
During annual planning, ask where the project creates high cognitive load. Then decide who is best placed to carry each part and explore whether new technologies can also play a part in easing the load.
Make the manager’s role more like road maintenance
A project roadmap suggests a clean line from start to finish. Real work has potholes, fog, blocked paths, and bad signage. Managers cannot remove every obstacle, but they can maintain the road.
That means checking the conditions that allow strengths to keep showing up and mapping out the potential roadblocks before they occur.
Useful manager routines include:
A monthly review of whether each person is spending enough time in their strength zone
A check on whether support tasks are fairly shared
A review of meetings, handoffs, and decision points causing repeated friction
A planned reset when priorities change
A private conversation about what is working and what is draining
The best question is often direct: “What is making this harder than it needs to be?”
Then listen for system problems, not just personal problems.
If three people misunderstand the same handoff, the handoff is unclear. If the same person keeps failing at a task that sits far from their strengths, the assignment may be poor. If a neurodivergent employee keeps asking for written instructions, the answer is not to praise resilience. The answer is to provide written instructions.
Support should also be reviewed. A structure that helped in January may not fit a different project in June. A pairing that worked during discovery may need to change during delivery. Good managers adjust the scaffolding as the work changes.
Plan the team before the pressure arrives
Annual planning is a rare chance to make thoughtful choices before deadlines narrow everyone’s options.
The strongest teams are not made of all-rounders who perform every task in the same way. They are made of people whose strengths are understood, whose struggles are named without shame, and whose work is shaped so that difference becomes useful.
For neurodivergent employees, this can mean the difference between being seen as inconsistent and being recognised as exceptional under the right conditions. For managers, it means fewer preventable breakdowns, better use of talent, and a roadmap that reflects how people actually work.
The next planning cycle should include one extra resource question: What conditions will let each person do the best work they are capable of doing?
Answer that early, and the project starts on firmer ground.
References
Baron-Cohen, S. (2002). The Extreme Male Brain Theory of Autism. PubMed Central.
Comments