A while back I wrote about why change and agility practitioners need to know more about trauma-informed practice. That piece still stands. But in the conversations I’m having with leaders right now, cognitive exhaustion in the workplace is a frame that’s landing more easily — and pointing to the same territory.
Cognitive exhaustion.
It’s the word leaders reach for when they describe what they’re seeing in their teams: people who used to be sharp now slow to respond, decisions that should be straightforward getting stuck, capable people defaulting to “just tell me what to do.” Not burnout exactly. Not disengagement. Something more like a workforce running on depleted batteries.
And unlike trauma, which can feel clinical or confronting to name, cognitive exhaustion is a frame leaders will admit to. Often because they’re feeling it themselves.
What’s driving it?
The load sources are different from the ones I named in the trauma piece. Pandemic, climate, social injustice — those are still there. But layered on top now is something more specific to organisational life:
- Perpetual restructuring and reorg
- AI tool churn — new platforms monthly, learning curves that never flatten
- Hybrid coordination cost — the cognitive tax of figuring out where, when, and how to work with whom
- Notification volume across Teams, Slack, email, project tools
- Concurrent change initiatives that no one has mapped or sequenced
- Ambient uncertainty about roles, futures, and what “good” looks like
Each one is manageable. Together, they deplete the working memory and attention people need to do their actual jobs — let alone absorb change.
Why this matters for change leaders
A cognitively exhausted workforce shows up looking a lot like a trauma-affected one. Reduced capacity to take in new information. Narrower tolerance for ambiguity. Retreat to default behaviours. Lower appetite for exploration. Slower embedding of new ways of working.
In other words: a very difficult workforce to land change with.
The good news is that many of the practices I pointed to in the trauma-informed piece work even harder in a cognitive exhaustion frame. Because cognitive exhaustion is, at its core, a load problem — and good agile change practice is fundamentally about externalising load, reducing concurrent demands, and making work visible.
Agile change practices that protect cognitive capacity
- Lean Coffee
In the trauma piece I described Lean Coffee as creating voice and choice. For exhausted teams, the relief is also cognitive. You don’t have to hold an agenda in your head, anticipate what’s coming, or strategise about what to raise. The structure carries the load. People show up, write a post-it, and the format does the rest.
- Visual communication
This one matters more for cognitive exhaustion than for almost anything else. When working memory is depleted, text-heavy comms genuinely cannot be processed — people will read your three-paragraph update and retain almost none of it. The brain’s preference for visual information (60,000 times faster than text) isn’t a nice-to-have when capacity is low. It’s the difference between your message landing and not.
Visual roadmaps. Infographics. One-pagers with icons. Photos of the team. These aren’t decorative — they’re a workload intervention.
- Kanban boards
The trauma frame on Kanban is safety and transparency. The cognitive exhaustion frame is externalising state. Depleted brains can’t reliably hold “what’s in flight, what’s blocked, what’s next, what’s done.” The board holds it for them.
And WIP limits — the unsung hero of Kanban — aren’t just flow optimisation. They are a direct intervention on cognitive load. Capping work in progress protects the team’s capacity to think.
- Work Out Loud
For exhausted workforces, WOL reduces the cognitive cost of finding out. People don’t have to chase, ask, interpret silence, or fill the gaps with anxiety. The information comes to them. Showcases, narrated work, public updates — these all reduce the energy people spend just trying to figure out what’s going on.
- (The new one) Make change load visible
This is the practice I didn’t include in the trauma piece, but it belongs here.
Most organisations have no shared picture of how much change a given team or function is absorbing at any one time. Strategy, technology, regulatory, people, process — initiatives stack up on the same teams, often without anyone noticing until something breaks.
A simple change heatmap — initiatives down the side, teams across the top, intensity shaded in — is itself a cognitive exhaustion intervention. Not because it changes the work, but because it changes what leaders see. And once they see it, the conversation shifts from “how do we drive more change through” to “what do we sequence, stop, or slow down.”
This is where “stop starting, start finishing” earns its keep.
A note for leaders
Trauma-informed practice asks leaders to adapt to conditions largely outside their control. Cognitive exhaustion is different. A meaningful share of it is directly produced by leadership decisions — about pace, concurrency, comms volume, tool adoption, and how much change is in flight at once.
Which means leaders aren’t just responding to cognitive exhaustion. They’re often generating it.
The practice ask, then, is twofold: adapt how you lead change so it lands in depleted conditions, and take responsibility for the load you’re adding to the system.
Both matter. Neither is optional anymore.
If you’d like to go deeper, the Agile Change Playbook covers these practices in more detail, and the Certificate of Agile Change Management builds them into a full capability program.
Frequently Asked Questions
What is cognitive exhaustion at work?
Cognitive exhaustion at work is a state of depleted mental capacity caused by sustained cognitive load — too much information, too many decisions, too many concurrent demands, and too little recovery. It shows up as reduced working memory, narrowed attention, decision fatigue, slower processing of new information, and a retreat to default behaviours. Unlike burnout, which is primarily about emotional and physical depletion, cognitive exhaustion is specifically about depleted thinking capacity. People experiencing it are often still motivated and engaged — they simply don’t have the mental resources to absorb more.
How is cognitive exhaustion different from burnout?
Burnout is a broader syndrome involving emotional exhaustion, cynicism or detachment, and reduced sense of accomplishment, typically developed over months or years of chronic workplace stress. Cognitive exhaustion is narrower and more immediate — it refers specifically to depleted mental processing capacity. A person can be cognitively exhausted without being burnt out, and vice versa. In practice, cognitive exhaustion often precedes burnout. It’s the earlier signal, and it’s more responsive to intervention because the causes — load, concurrency, comms volume — are often directly addressable by leadership.
How is cognitive exhaustion different from change fatigue?
Change fatigue describes the reduced willingness and capacity to engage with change after too much of it, too quickly. Cognitive exhaustion is the underlying mechanism that produces much of what we call change fatigue. When working memory and attention are depleted, people genuinely cannot absorb new change — it’s not resistance, it’s capacity. Treating change fatigue as an attitude problem misses this. Treating it as a cognitive load problem points to better interventions.
What causes cognitive exhaustion in the workplace?
The most common drivers in current workplaces are perpetual restructuring, AI tool churn (new platforms with steep learning curves arriving monthly), the coordination cost of hybrid work, high notification volume across multiple channels, concurrent change initiatives that aren’t sequenced or mapped, and ambient uncertainty about roles and futures. Each is manageable in isolation. Stacked together, they deplete the cognitive resources people need to do their jobs and absorb change.
What are the signs of a cognitively exhausted workforce?
Common signs include capable people becoming slow to respond, simple decisions getting stuck, increased requests for explicit direction (“just tell me what to do”), reduced willingness to explore new ideas, narrower tolerance for ambiguity, lower retention of information from meetings and comms, and a noticeable drop in proactive behaviour. Engagement scores may still look reasonable — cognitive exhaustion is often invisible in standard pulse surveys because people are trying, they just don’t have capacity.
Can agile change practices help a cognitively exhausted workforce?
Yes. Agile change practices are well-suited to cognitive exhaustion because they’re fundamentally about externalising cognitive load, reducing concurrent work, and making information visible. Five practices that directly protect cognitive capacity are Lean Coffee (structure carries the agenda load), visual communication (faster processing than text), Kanban boards (externalising work state and capping work in progress), Work Out Loud (reducing the cost of finding out), and making change load visible through tools like a change heatmap.
What can leaders do about cognitive exhaustion?
Leaders can do two things. First, adapt how they lead change so it lands in depleted conditions — using more visual communication, reducing comms volume, capping concurrent initiatives, and making work visible. Second, and more importantly, take responsibility for the cognitive load they’re generating. A meaningful share of workplace cognitive exhaustion is directly produced by leadership decisions about pace, concurrency, tool adoption, and how much change is in flight at once. Recognising this shifts the conversation from “how do we drive more change through” to “what do we sequence, stop, or slow down.”
