Here's an uncomfortable thought to start with: you have been designed. All of us have.
From the earliest age, our behaviour is shaped by other people. A parent's look that stops you misbehaving. Learning to wait at a crossing. By the time you're an adult, you are the product of decades of behaviour being deliberately, patiently designed by others - and mostly you didn't notice it happening.
Designers are simply doing this on purpose. An advert nudges you toward a product. A shop layout walks you past the thing you weren't going to buy. And digital products are no different: every element on a screen is placed to encourage a behaviour. This is behavioural design - applying behavioural science to the design of a product or service. It's powerful, it's everywhere, and it's worth being honest that it can be used well or badly.
To influence behaviour, you have to understand it
Plato reckoned human behaviour flows from three sources: desire, emotion and knowledge. Not bad for someone working without a research budget. We've refined it since, and the model I find most useful in practice is B.J. Fogg's: for a behaviour to happen, you need three things at once - motivation, ability and a trigger.
Miss any one of the three and nothing happens. And the reason so many digital experiences underperform is that teams obsess over one of the three and ignore the others entirely.
Think about a food delivery service. The customer is hungry - motivation, sorted. The app works and the restaurants are open - ability, sorted. But if nothing prompts them at the moment the hunger arrives, the behaviour doesn't occur. They order a takeaway from someone else, or they eat toast. The trigger was the missing piece, and no amount of interface polish would have fixed it.
Most digital experiences don't fail because they're badly designed. They fail because they turn up at the wrong moment.
Where to actually start
Wanting to adopt behavioural design and actually doing it are two different problems. The entry point I'd always recommend is the customer journey map.
Mapping the journey - properly, end to end - gives you a visualisation of the whole experience over time, not just the screens. It surfaces the touchpoints and, crucially, the emotions attached to them. For a food delivery service, that journey starts long before the app opens: it starts with the first pang of hunger, and ends with the smell of dinner arriving at the door.
Once you've got that map, you can interrogate each moment through the three lenses. Where's the motivation here, and how strong is it? Do we actually have the ability to serve this person right now? And are we triggering at the right moment, or are we shouting into the void at 3pm on a Tuesday when nobody's hungry?
That last question is where the interesting work lives. If you know your customers are most likely to be hungry between five and eight on a Friday after payday, then the design problem isn't the checkout flow. It's the notification.
The bit I'd push back on
Behavioural design gets a slightly evangelical treatment in some quarters, so let me add the caveat. Understanding how to trigger a behaviour is not the same as having earned the right to. The techniques work whether or not the outcome is good for the person on the other end - which is precisely why they need to be handled with some care.
The test I'd apply is simple. If you explained to your customer exactly what you'd designed and why, would they be pleased, or would they feel slightly conned? Behavioural design that survives that question tends to build loyalty. Behavioural design that doesn't builds churn, with a short and pleasant delay before it does.
It doesn't work alone
Behavioural design isn't a replacement for the rest of the toolkit. It sits alongside user research and data. Research tells you what people say they want; data tells you what they actually did; behavioural design helps you understand why, and what would change it. Marry the three and you can anticipate behaviour rather than react to it.
So a question worth taking to your next design review. When your customers don't do the thing you want them to do - do you know whether they lacked the motivation, the ability, or the trigger? Most teams assume it's ability, and redesign the interface. It's usually the trigger.
If you'd like a hand working that out, book a short discovery call with the team at Distinction. No pitch, just a practical conversation about where your journey breaks down.
