Anthony Shephard-Williams explores how UX research must go beyond evaluating individual messages or features, and instead test the full moment in a real customer journey. The blog highlights why timing, context, and user intent are critical to understanding whether experiences truly work.
I was recently browsing plants on the mobile site of a very well-known DIY and garden retailer. I won’t name them, because this isn’t really about one brand. It’s about a common digital moment: being told that the “better experience” is somewhere other than the journey you’re already in.
I was shopping for three x 4ft outdoor plants, not something I have ever done in my life, nor something I will likely ever do again. The mobile website experience was rough to say the least (navigating and searching wasn’t very intuitive), then came the prompt: for a “better experience”, I should download the app.
And there’s the interesting bit. Was that good UX? Or was it just a tactic to drive app downloads? Probably both.
From the retailer’s point of view, the app makes complete sense. It creates a logged-in customer. It supports loyalty, offers, notifications, personalisation and repeat behaviour. It gives the brand more control over the customer relationship. All useful. All measurable. All commercially attractive.
But from my point of view, in that moment, I wasn’t trying to build a deeper relationship with a garden retailer. I was trying to buy some plants.
That is the gap brands need to understand. The business objective might be to increase app downloads. The customer objective might be to find the plants they want, order them, and get on with their day. When those two objectives clash, what the business sees as a smart nudge can feel to the customer like an annoying interruption.
And there’s another slightly awkward question. If the app is the “better experience”, what does that say about the mobile website I’m currently using?
This is where research makes the difference
We see versions of this all the time in UX and customer experience research. A message, feature or process can make complete sense internally. It can be logical, commercially sensible and technically well-designed. But when a real person encounters it in a real journey, it can land very differently.
We’re currently working with a client on a digital customer experience project where the challenge is not simply whether people can get through the journey. It’s whether they understand what is happening, whether the language gives them confidence, and whether the experience reassures them at the moments that matter.
That is often where the most valuable insight sits. Not just whether people can technically complete the task, but whether the experience supports them properly while they do it.
The better questions are often things like:
- Do customers trust what is happening?
- Do they understand the language being used?
- Does the journey behave how they expect?
- Where do they hesitate, second-guess or lose confidence?
In research sessions, these moments are often really obvious. It is the pause before someone clicks. The “I think this means…” before they commit. The moment they complete the journey, but still don’t quite trust what happened.
The next phase of that work is to trial the experience further with an exclusive group of customers, before moving into a more in-depth customer trial. That staged approach matters because it gives the team a chance to learn in a controlled way, refine the experience, spot where people hesitate, and build confidence before opening it up more widely.
Good research does not just tell you whether something works on paper. It tells you whether it works in real life, with real people, in real situations, when they are not thinking like stakeholders, product owners or UX specialists.
They are just trying to get something done.
Don’t just test the thing. Test the moment.
The plant example is small, but it points to something bigger. A prompt to download an app can be useful. If I’m tracking an order, managing loyalty rewards, scanning a product in-store or doing something I’ll repeat regularly, the app might genuinely be better.
But if I’m halfway through buying plants, the timing matters. The benefit also needs to be specific. There is a big difference between a vague promise and a useful reason:
- “Download the app for a better experience” is broad and easy to ignore.
- “Download the app to check live local stock” gives me a reason.
- “Download the app to complete this order and keep your basket” tells me what I gain.
Without that clarity, it can feel like the business is asking the customer to do extra work in service of its own KPI.
And sometimes that extra work creates problems elsewhere.
In my case, I DID download the app. I did order the plants. So, from one perspective, the nudge worked. The retailer got what it wanted: another app download and a completed purchase.
But I’ll probably delete the app, because I don’t really want a DIY and garden retailer (that I typically shop at once every 5 years or so) taking up space on my phone. I was just trying to buy plants.
Worse, I had started the journey through an Avios app because I was trying to collect points. That should have tracked me through to the retailer’s website. But because I was encouraged to switch into the retailer’s app, I’m now not convinced the journey tracked properly. Which means I will have to contact Avios to chase the points.
So the retailer got the app download. But the customer got admin.
That is the bit brands need to be careful about. What looks like success on a dashboard might still feel like a slightly broken experience to the customer. An app download might count as a conversion internally, but if it adds uncertainty, creates an extra job, or disrupts another part of the journey, the customer experience is not quite as successful as the metric suggests.
So, was the app prompt poor UX or a smart tactic?
It depends.
If it helps me do the thing I came to do, it is useful. If it gets in the way, it becomes an unnecessary step. And if it solves a problem for the business while creating extra hassle for the customer, it probably needs more research.
Evaluating digital experiences requires more than measuring clicks or message comprehension. UX research that tests moments in context captures user intent, hesitation, trust, and emotional response. By combining qualitative observation with quantitative metrics, brands can optimise journeys, reduce friction, and ensure users achieve their goals effectively while maintaining confidence and satisfaction.
Understanding the full moment is important. Knowing what users experience, when, and how they interpret it is critical to designing successful digital experiences. At Mustard, we help organisations embed UX insight into real customer journeys, ensuring experiences are trusted, engaging, and rewarding. If you’re looking to optimise your mobile or web UX in 2026, get in touch.