Neurodiversity in project management: Enabling neuro-inclusion improves project delivery and metrics

Project delivery is often based on a single ‘right’ way of thinking - one largely designed for neurotypical minds. When we choose to widen the design process to include neurodivergence excellence, project delivery improves.

In July last year, The Association for Project Management (APM) published its report Promoting Neurodiversity: Unveiling Barriers and Enablers in the Project Management Profession. The research captures neurodivergent strengths which are considered in-demand in projects - systems thinking, pattern spotting, calm in a crisis – as well as common barriers such as sensory overload, memory challenges and unstructured social events. It also touches on a sensitive point on disclosure: it is often safer to disclose your neurodiversity when you’re a senior professional, while far riskier when you’re early in your career. For me, though, the most useful part is that small, practical enablers make project work better and improve delivery outcomes.

I have Attention Deficit Hyperactivity Disorder (ADHD) diagnosis. On good days, I can navigate the messy risk landscape and spot patterns quickly. On bad days, a long, unstructured meeting or a noisy office drains me, and I need more time to relax and recharge. I believe that the following simple changes in how we run our projects and teams can provide benefits to our project delivery metrics. We see that decision speed increases, less rework is needed, stakeholder trust improves, while stress levels across the project teams are much lower.

Providing space to think

Much of the project time is still focused on thinking on the spot and deciding right away. This may work for business-as-usual projects but it is a poor choice for complex delivery. The respondents in the neurodiversity report echo this by stating, “Share the agenda first. Give people time to think about the agenda before.”

When I’m chairing a meeting, I send a brief email with the next decision points we need to discuss, along with the agenda, at least a day ahead. If there are minutes from prior meetings, I include them as attachments in my email. As a habit, for more complex projects, I tend to send these at the start of the week to allow people time to prepare. Project members can also provide written comments beforehand. For sessions over an hour, I add a five‑minute pause halfway or at a suitable point in the agenda. This is a simple and inclusive choice I make.

The impact is immediate. Decision‑making speeds up because the thinking has already happened. Actions become clearer, reducing the need to revisit the same item repeatedly. Stakeholders report feeling included rather than taken by surprise. Short, structured pauses also cool down the temperature in tense sessions. The metric story is straightforward: faster decisions, fewer follow‑ups, delighted sponsors.

Write it down, keep it clear, log decisions in one place

Ambiguity is a key source of project risks. This can be cut by using plain English as much as possible and maintaining a single decision log. The format should be simple: who decided what, when and why, and the impact on scope, budget or risk. Include a summary table on the front page, provide details as an appendix. For accessibility, use alt text on images and graphs, and when recording remember to turn on captions.

The effect is instant. Rework drops because people are working from the same understanding. Onboarding requires less time. New project members don’t need to read and get lost in long chat threads. Governance feels calmer. Reasoning from big calls is easy to retrieve and show at later stages. We still require a good conversation – but we no longer depend solely on our memory to carry these outcomes.

If you try one thing this month

Pick one meeting that always overruns. Send a brief pre-read and the decision you intend to make. Offer a slot for written input beforehand. During the meeting, pause briefly halfway. Close with a clear who/what/when, then add the decision to a shared log. Notice what changes, speed improves on agreement, clarity of actions is captured and follow-ups are reduced. Check what has helped. Ask for feedback, discuss and agree further changes. Maintain an open loop and provide space for people to request further adjustments.

A note on disclosure and choice

As the research shows, disclosure often feels safe for established and senior project professionals and risky for early career project professionals. That rings true. I disclose when it helps the team work better with me. I don’t expect others to. You shouldn’t need to share a diagnosis to ask for an agenda in advance or to contribute in writing. Neuro-inclusive design should be the norm.

If you take one thing away from this year’s Neurodiversity Celebration Week, let it be this: Neuro‑inclusive enablers are catalysts for improved delivery. They provide clear inputs, bolster space for thinking, focus on work based on the strengths of the project team and reduce friction for every individual on the project. They are small, practical shifts any team can make. The payoff is better decisions, less rework and healthier teams.