The Invisible Waste: Cognitive Load in Processes

For decades, process improvement teams have been trained to look for the obvious stuff.

Waiting time. Defects. Excess movement. Downtime. Inventory sitting around doing nothing.

You can see it, measure it, map it.

But in 2026, across a lot of NSW and QLD organisations, there’s another type of waste starting to show up in conversations. And it’s a bit harder to put your finger on.

Cognitive overload.

It’s the mental effort people burn just trying to get work done in systems that aren’t exactly helping them.

You don’t see it on a process map. It doesn’t show up neatly in a KPI dashboard. But you feel it in the way work actually flows. Or doesn’t.

You see it in people hesitating before making decisions they used to make quickly. In the constant “just checking” messages. In the errors that creep in when attention is split too many ways. In the quiet frustration when someone says, “it’s easier if I just do it this way instead.”

Most of the time, this kind of complexity doesn’t arrive in one big redesign failure. It builds slowly.

A new system gets added. Then another. A temporary workaround becomes permanent. A compliance step gets introduced. A second approval path gets layered in “just in case.”

Individually, none of it feels unreasonable. In fact, each change usually makes sense on its own.

But over time, people end up carrying the system in their head just to navigate it.

I was looking at a utilities operation in NSW recently where this showed up pretty clearly. On paper, everything looked fine — systems were modern, staffing was steady, processes were documented.

But frontline coordinators were juggling multiple platforms, chasing updates across different channels, and constantly reprioritising work based on shifting information. Nothing was broken in isolation. It was just mentally heavy to run.

When the team stepped back and simplified how information flowed — fewer channels, clearer priorities, less duplication — performance improved almost immediately. Not because people changed. Because the system stopped asking them to constantly translate it.

That’s the part that’s changing how people think about improvement.

Cognitive load is no longer just a “wellbeing” conversation. It’s operational. Because when people are mentally overloaded, everything slows down. Decisions get softer. Errors increase. Workarounds multiply.

And interestingly, most of this doesn’t come from bad intent. It comes from well-intended complexity that was never cleaned up.

The organisations starting to get on top of it are doing something quite simple, but uncomfortable. They’re asking not just “does this process work?” but “how hard is this to think through every day?”

Because sometimes the biggest inefficiency in a process isn’t the steps themselves.

It’s the mental effort required just to hold it all together.