The CX leader's blind spot: you are designing for stated preferences, not actual behaviour

Your customer journey map looks perfect. Clean touchpoints, logical progression, pain points identified and solved. You have validated it with focus groups. The C-suite loves it. There is just one problem: it bears little resemblance to how your customers actually behave.

I see this everywhere. CX teams mapping the rational, sequential journey that customers should take. Meanwhile, your actual customers are bouncing between channels, abandoning processes halfway through, and making decisions in ways that would horrify your strategy deck.

The root issue is that you are designing for stated preferences, not actual behaviour. And the gap between what people say they do and what they actually do is enormous.

Why stated preferences lie

When you ask customers how they want to interact with your brand, they give you the socially acceptable answer. They tell you they want simple, efficient, logical experiences. They claim they read terms and conditions. They insist they compare shop rationally.

None of this is true.

At Disney, we learned this the hard way. Guests told us they wanted shorter queue times above everything else. So we invested millions in virtual queuing systems. Usage was terrible. Why? Because guests actually wanted certainty and control more than speed. They would rather wait 30 minutes in a physical queue they could see than 20 minutes wondering if the app was working.

The stated preference was speed. The actual behaviour revealed a need for predictability.

How actual behaviour works

Real customer behaviour is messy, emotional, and context-dependent. People start processes on mobile and finish on desktop. They abandon shopping carts not because of price but because they got distracted. They choose the second-best option because the best option required one extra click.

Your customers are not optimising machines. They are humans with limited attention, competing priorities, and decision fatigue. They satisfice rather than maximise. They go with good enough rather than perfect.

This matters because every CX improvement you make based on stated preferences will miss the mark. You will solve the wrong problems and wonder why adoption is low.

Three ways to design for actual behaviour

1. Observe before you ask

Start with behavioural data, not survey data. Look at where people actually drop off in your processes. Track the real paths they take through your website or app. Watch session recordings to see where they hesitate, backtrack, or struggle.

One insurance client discovered that 40% of customers were calling the contact centre immediately after starting an online claim. The survey data said the process was "easy to use." The behavioural data revealed a trust gap. Customers wanted human confirmation they were doing it right.

Action step: Pick one key customer process. Pull the analytics for the last 30 days. Map the actual customer paths, not your intended journey. Where do the biggest gaps appear?

2. Test behaviour, not opinions

When you want to improve something, do not ask customers what they think. Give them a prototype and watch what they do. A/B test real interactions, not concept cards.

We ran a test for a bank that wanted to increase mobile app logins. Focus groups said they wanted biometric authentication because it was "more secure." The behavioural test showed biometric users logged in 23% less often than PIN users. The extra friction outweighed the perceived security benefit.

Action step: Take your next proposed CX improvement. Before rolling it out, create a simple test with 200 real customers. Measure behaviour, not satisfaction scores.

3. Design for the context, not the feature

Most CX design fails because it ignores context. Your customer might love your new streamlined checkout when they are sitting at their desk with perfect wifi. But if they are trying to complete it while walking to a meeting with 20% battery and patchy signal, your elegant design becomes unusable.

Context drives behaviour more than features do. Design for the worst-case scenario, not the best-case demo.

Action step: Map one critical customer journey. For each step, list the three most likely contexts where this happens (device, location, time pressure, emotional state). How does your current design perform in those contexts?

The uncomfortable truth

Designing for actual behaviour means accepting that your customers are not always rational, consistent, or efficient. That feels uncomfortable when you are trying to create clean, logical experiences.

But this is where the opportunity lies. While your competitors are optimising for the customer that exists in surveys, you can design for the customer that exists in reality.

People do not buy what makes sense. They buy what feels right in the moment.

We've been helping big brands for over 28 years. Book a call and see how we can help you too!