Executive Function at Work: Design the Job So Brains Can Do It

When people “miss easy things”, it’s rarely motivation. It’s executive function load: initiation, prioritisation, working memory, and switching being over-taxed by the way work is designed. Neuro-inclusive teams don’t wait for willpower; they change the conditions so the brain can get started, stay on track, and finish.

Executive function, briefly

Executive functions are the brain’s control processes—starting tasks, holding steps in mind, sequencing, resisting distraction, shifting gears, and checking results. They are separable but linked (Miyake et al., 2000; Diamond, 2013). They fluctuate with sleep, stress, medication, environment, task meaning, and sensory load. ADHD foregrounds EF variability; dyslexia and autism often interact with working memory, processing speed, and switching demands. The upshot: the same competent person can look brilliant at 10:00 and stuck at 14:00—because the context changed.

The hidden EF taxes in modern knowledge work

Unsignalled priorities, vague asks, constant context-switching, and meeting-heavy days quietly burn EF. So do visually noisy offices, notifications, and materials that bury the “what/when” inside paragraphs. Many “performance issues” are actually design issues: the job is asking the brain to improvise structure all day.

Design for initiation: remove the friction of the first step

Starting is a design problem, not a character test. Replace “Can you take a look?” with a 90-second brief that names the goal, deliverable, audience, due date, and what counts as “good”. Provide a worked example when possible. For sticky tasks, co-create a first slice due today (a title, a stub outline, a data pull). Offer body-doubling (quiet co-working) and camera-optional focus slots. These moves offload planning and lower the “activation energy” to begin.

Design for prioritisation: make trade-offs explicit

Brains can’t rank ghosts. Publish a visible queue (kanban or list) where items carry size, due date, and importance. Limit work-in-progress; batch hand-offs into predictable windows. When everything is urgent, nothing is. Leaders should write—briefly—why something is top of the stack and what can slip. Externalising priorities protects EF and reduces masking (“pretending I know what matters”).

Design for working memory: externalise, don’t test it

Working memory holds the steps while you act (Baddeley, 2003). Treat it as a scarce resource. Put acceptance criteria next to the task; keep one idea per paragraph; make numbers live beside the nouns they modify. In meetings, show the agenda on-screen, capture decisions and owners in real time, and end with a clear next step. Afterwards, send a short written recap. You are not “writing things down for slow people”; you are engineering reliability.

Design for switching: fewer jumps, cleaner edges

Switching costs attention (Miyake et al., 2000). Reduce rapid toggles by protecting deep-work windows and clustering similar tasks. End meetings five minutes early to create decompression buffers; the next task starts faster when the last one has a clean landing. Group notifications; turn off pop-ups during focus. For role designs with forced interrupts (support, incident response), rotate the “interrupt owner” so others can have uninterrupted blocks.

Design for checking and finishing: make quality visible

“Attention to detail” is not a personality; it’s a process. Standardise short checklists for recurring artefacts (client email, board slide, data pull), and use text-to-speech or peer reads for critical items. Separate composition from surface edit; ask for ideas first, polish later. Define “done” in the brief so teams stop chasing moving targets.

EF-friendly meeting culture

Signal, structure, silence. Signal by stating the decision due and materials needed, sent in good time. Structure by time-boxing segments and allowing multiple participation modes (voice, chat, shared doc). Silence by ending early and sending the recap promptly. This reduces working-memory load and minimises performative “fast talk”, which disproportionately penalises neurodivergent colleagues.

Remote and hybrid: scaffolds, not surveillance

Remote work can improve controllability and crush EF with ambiguity. Publish daily priorities, keep a live board, and make “how to ask for help” explicit (e.g., tag + expected response time). Encourage quiet co-working and asynchronous updates. Judge the change in the work, not presence on video.

Policies that back the practice (UK)

Under the Equality Act 2010, employers must make reasonable adjustments to remove substantial disadvantage. Everyday EF supports—clear briefs, agenda-in-advance, camera-optional meetings, protected focus time—are proportionate, low cost, and do not require diagnosis to begin (ACAS guidance). Reserve Occupational Health for bespoke or materially costly changes; don’t gatekeep the basics.

What to measure (keep it light)

Watch cycle time on typical tasks, error/rework rates, and decision clarity after meetings. Add two pulse questions monthly: “Was the next step clear?” and “Could you control your environment enough to focus?” If they trend up, EF load is coming down.

Manager scripts that change behaviour

“Here’s the outcome, the deadline, and what ‘good’ looks like. Let’s agree the first slice now.” “You can contribute by voice, chat, or a note—I’ll bring written points into the room.” “Protect two 50-minute focus blocks today; message me after the first slice ships.”

The payoff

When teams stop testing executive function and start supporting it, pace goes up and panic goes down. You’ll see faster starts, steadier throughput, fewer last-minute saves, and more honest signal about what’s actually stuck. That isn’t indulgence; it’s professional operations for real human brains.

References (APA-7)

• Baddeley, A. (2003). Working memory: Looking back and looking forward. Nature Reviews Neuroscience, 4(10), 829–839. https://doi.org/10.1038/nrn1201

• Diamond, A. (2013). Executive functions. Annual Review of Psychology, 64, 135–168. https://doi.org/10.1146/annurev-psych-113011-143750

• Miyake, A., Friedman, N. P., Emerson, M. J., Witzki, A. H., Howerter, A., & Wager, T. D. (2000). The unity and diversity of executive functions and their contributions to complex “frontal lobe” tasks: A latent variable analysis. Cognitive Psychology, 41(1), 49–100. https://doi.org/10.1006/cogp.1999.0734

• ACAS. (n.d.). Reasonable adjustments at work; Neurodiversity in the workplace. https://www.acas.org.uk

• Equality Act 2010, c. 15 (UK).