Why Service Design Fails Without Behavioural Insight

Most service maps show how a service is supposed to work. The trouble is in the part nobody drew.

Service design fails without behavioural insight because it designs for the process on paper, not for what customers and staff actually do. People skip steps, find shortcuts and build their own workarounds. If you don't see those, you end up improving a map that nobody follows.

The gap in traditional service design

A typical project starts with a journey map: steps, decision points, pain points. That's useful. But it's usually built from workshops and documents, which means it shows the service as the organisation believes it runs.

Real behaviour is messier. And the mess is where the experience breaks.

Why behavioural research matters

Behavioural research looks at what people do, not just what they say they do. In service design, that means:

• Seeing where customers go around the official process, and why.
• Seeing the workarounds staff use to keep things running.
• Finding the moments where one small failure causes several more further down the line.

You can't get this from a survey. You have to go and watch.

Heidelberg Materials: the process nobody was using

Heidelberg Materials (formerly Hanson) had a well-documented delivery process. It just wasn't the one anyone was using.

We sat in the call centres, walked the plants, and rode along with sales teams and delivery trucks across New South Wales, Victoria and Queensland.

Customers who couldn't get an answer had built their own way in. Some called their sales rep direct. Some turned up at a plant and demanded service on the spot. None of it showed up on a single process map, and all of it was where the experience was breaking.

You can't fix that by improving the map.

The changes that worked came from what we saw: adjusting how bookings were scheduled against real capacity, changing how updates reached customers, and building a way for customer feedback to reach the executive team.

How we combine the pieces

We look at three things side by side:

• How the service is meant to work. Systems, processes and policies.
• How it actually works. What customers and staff really do, seen first hand.
• What to change. Prototypes that close the gap, tested with the people who'll use them.

The gap between the first two is where the design work is.

Fixing touchpoints is not enough

A new screen, script or email can improve one moment. But if the behaviour causing the problem stays the same, the problem moves somewhere else. Lasting change comes from designing for how people really behave.

For a practical guide to improving a whole service, read how to improve your service design end-to-end.

Related: Experience design and the Heidelberg case study.