From Complexity to Clarity: Using Behavioural Design to Simplify Operations

How Complexity Creeps into Operational Systems 

Most operational systems weren't designed; they evolved.

A new approval step added after something went wrong. An extra notification bolted on to stop the calls coming in. A new team created to manage the backlog that somehow became permanent. Built one sticky plaster at a time, until the system is held together with good intentions and nobody quite remembers why they do what they do.

The instinct is understandable. Something breaks; you fix it. Something slows down; you add resource. A customer complains; you add a step. But over time this creates a patchwork operating model, and the problems it was meant to solve have a habit of quietly getting worse.

Complexity isn't something that happens to organisations. It's something they build, incrementally, unintentionally and almost always with the best of intentions. And until it's treated as the root cause of underperformance rather than a symptom of growth, every fix will create the next problem.

Case Study Example

When a Logical Fix Makes Performance Worse    

We were introduced to a client who was drowning in inbound calls. Customers chasing updates, asking where things were, wanting to know when they'd hear back. The team were stretched, and the business needed a quick fix.

The solution they landed on seemed perfectly logical. If customers are calling for information, give them information. So, they built a new process sending automated updates at key milestones, keeping customers in the loop. Tick. Problem solved.

But the result was the opposite of what was intended. Call volumes increased. Service levels dropped. Overtime rose. The organisation had added cost and complexity to solve a problem that had now intensified.

The issue wasn’t execution—it was design. The updates acted as a salience trigger, reminding customers they were waiting. And when people are reminded they are waiting, the natural response is to act. In this case, that meant picking up the phone.

A solution designed for rational behaviour was deployed in a human system.

Designing Operational Improvement for People, Not Just Processes  

The real issue was never a lack of information. It was uncertainty. Customers were calling because waiting felt uncomfortable, not because they lacked updates.

Without a behavioural lens, the diagnosis focused on what customers were doing rather than why they were doing it. And without that understanding, the intervention simply reinforced the problem.

Most operational challenges are viewed through two lenses:

• Structure – how the process is designed
• Information – how data flows through it

Both matter. But they don’t explain behaviour.

Adding a third lens — behaviour — changes how you diagnose and solve problems. 

One of the most well-established frameworks in behavioural science (1) makes this explicit: Capability and Opportunity are never enough without Motivation. In our example what was missing was the motivation to stop calling, because the anxiety driving the behaviour had never been addressed. And until behaviour sits alongside structure and information, organisations will keep solving the wrong problems with the right intentions.

The Behavioural Patterns Behind Operational Complexity 

Behavioural science has spent decades mapping the consistent, reliable patterns that shape human behaviour. Far from being obstacles to simplification, these patterns are your greatest asset. Understand them and you don't just know where the complexity is coming from, you know exactly how to design your way out of it.

Several principles are particularly relevant in operational design:

• Status quo bias means people tend to stick with default options, regardless of alternatives
• Reactance means overly rigid processes drive workarounds, reintroducing complexity
• Availability bias means decisions are shaped by the information most visible at the time
• Cognitive load means every additional step or decision reduces effectiveness and performance

These are not flaws in people; they are predictable features of how people operate.  In the earlier example, two behavioural effects were at play:

• Salience – updates brought waiting back to the forefront of the customer’s mind
• Locus of control – customers, lacking control, sought action to regain it

The updates did not reassure. They activated.

Removing Friction is More Effective Than Adding Incentives  

Behavioural scientists believe that removing friction is more powerful and more cost effective than adding incentives. This is why we obsess over sludge, the accumulated friction that builds up in systems over time and quietly works against the behaviour you're trying to enable. The approval nobody questions. The zombie process added years ago that everyone has forgotten the reason for. In behavioural terms each one of these doesn't just add a step it alters the choice architecture of your business, making the right outcome harder to achieve than it should be.

It's also no coincidence that Easy comes first in another well-known behavioural science framework (2). Before any other lever is pulled, the desired behaviour needs to be the path of least resistance. Get that right and you don't just have a simpler operation. You have one that's ready to scale.

Simplify First to Scale Effectively   

The organisations that will win in the next decade won't necessarily be the ones that move fastest or invest most heavily in technology. They'll be the ones that have the discipline to simplify operations first. To strip out the complexity that is slowing their people down, design for how humans actually behave, and build operations that are genuinely ready to scale.

Because the most powerful thing you can do for your operation isn't to add. It's to subtract. Simplicity is the ultimate nudge. And it changes everything.

1. The COM-B model (ref)

2. EAST framework (ref), developed by the Behavioural Insights Team