Start with an uncomfortable thought: 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 are an adult, you are the product of decades of behaviour being deliberately, patiently influenced by others, and mostly you did not notice it happening.

Designers do this on purpose. An advert nudges you towards a product. A shop layout walks you past the thing you were not going to buy. Digital products are no different: every element on a screen makes some behaviours easier and others less likely. This is behavioural design, applying an understanding of human behaviour to the design of a product or service. It is powerful, it is everywhere, and it can be used well or badly.

For service firms, that distinction matters. The behaviour you want might be completing an onboarding task, uploading a document, booking an appointment or reviewing advice. Those actions often sit inside relationships built on trust. A prompt that feels helpful in a food delivery app can feel intrusive when the subject is a pension, a legal dispute or a medical record.

Name the behaviour before you design for it

Teams often begin with a broad ambition such as "increase engagement" or "improve adoption". Neither describes something a person can actually do. A useful target behaviour is specific enough to observe: a client reviews the pre-meeting questionnaire by Thursday; a relationship manager records the next action before closing the account; a prospect compares two service options before asking for a proposal.

That precision changes the conversation. It reveals whose behaviour matters, when it needs to happen and what conditions have to be present. It also makes it harder to hide a weak proposition behind a more persuasive interface. If the desired action has little value for the customer, improving the prompt is the wrong job.

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. A more practical model for design work is B.J. Fogg's. In the current version of the Fogg Behavior Model, behaviour happens when motivation, ability and a prompt come together at the same moment.

Earlier explanations of the model used the word "trigger". Fogg now uses "prompt", which is a useful correction. A prompt can be a message, a visual cue, a request from another person or something in the environment. It does not have to be a marketing notification.

Miss any one of the three elements and the behaviour does not happen. Many digital experiences underperform because teams obsess over one and ignore the others.

Think about a food delivery service. The customer is hungry, so motivation is present. The app works and the restaurants are open, so the customer has the ability to order. Yet if nothing brings the service to mind when the hunger arrives, they may order from someone else or eat toast. The prompt was missing, and no amount of interface polish would have fixed that.

Many digital experiences fail because they turn up at the wrong moment.

In professional services, the diagnosis is rarely quite so tidy. A client who has not uploaded an identity document may lack motivation because the reason for the request is unclear. They may lack ability because the file format is rejected on mobile. They may simply have forgotten. Sending three more reminders treats every cause as a prompt problem and risks making the relationship worse.

Where to start

Wanting to adopt behavioural design and actually doing it are two different problems. A useful entry point is the customer journey map.

Mapping the journey properly, from the customer's first need through to the outcome, gives you a view of the experience over time rather than a diagram of screens. It surfaces touchpoints and 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.

For a service firm, include the human and operational parts too. The journey may pass from a referral to a website, then to a partner, a form, an operations team and a client portal. A customer experiences one relationship even when the firm sees five systems and three departmental owners.

Once you have that map, examine each important behaviour through the three lenses:

  • How strong is the person's motivation at this point, and what might compete with it?
  • Can they perform the action with the time, knowledge, confidence, access and tools they actually have?
  • What will prompt the action at an appropriate moment?

The third question often contains the interesting work. If customers usually decide what to eat between five and eight on a Friday after payday, the design problem may be timing rather than checkout. In a legal or financial journey, the best prompt might come from a trusted adviser during a scheduled conversation. Context decides whether a prompt is welcome.

Test the diagnosis with evidence

The model is a way to form better questions, rather than proof of why somebody behaved as they did. Use research and data to test the diagnosis.

Interview customers who completed the task and those who stopped. Watch people attempt it where that is practical and appropriate. Look at operational records, support calls, device failures and the time between steps. Ask customer-facing colleagues where they intervene manually. A drop-off chart tells you where people left; it rarely tells you whether they were confused, unconvinced, unable to continue or distracted by something more urgent.

Small changes can then be tested against a clear hypothesis. You might explain why a document is needed before asking for it, allow a mobile photograph instead of a scan, or move the request into a conversation already taking place. Measure completion alongside complaints, support demand and downstream quality. A higher conversion rate can conceal a worse outcome if people act without understanding what they agreed to.

The part I would push back on

Behavioural design gets a slightly evangelical treatment in some quarters, so it needs a caveat. Understanding how to prompt a behaviour is different from having earned the right to influence it. The same techniques work whether the outcome is good for the person on the other end, which is precisely why they need care.

The test I would apply is simple. If you explained to your customer exactly what you had designed and why, would they be pleased, or would they feel slightly conned? Behavioural design that survives that question can build loyalty. Behavioural design that fails it can produce a short-term uplift followed by mistrust, complaints or churn.

There are further questions for regulated and high-trust services. Can a person decline without being punished through friction? Is urgency real? Are defaults easy to understand and reverse? Does the design help someone make a considered choice, or exploit fatigue and anxiety? Treat those as design questions from the beginning, alongside commercial measures.

It does not work alone

Behavioural design is one part of the toolkit. It sits alongside user research, service design, analytics and operational knowledge. Research can reveal what people say and how they make sense of a situation. Behavioural data shows what occurred. Frontline colleagues see the workarounds and exceptions. Behavioural models help a team develop plausible explanations and interventions to test.

So take one question to your next design review. When customers do not take the action you expected, do you know whether motivation, ability or the prompt was missing? Teams commonly assume the interface is at fault and redesign it. Sometimes that is right. Sometimes the real problem is timing, trust, an unclear benefit or a process that asks too much.

Test the assumed barrier before changing the interface. A small observation study can prevent the team from optimising the prompt when timing, trust or the underlying service is the real constraint.

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.