Context-aware design

Context is broader than device. It includes lighting, motion, urgency, location, cognitive load, and physical state: a customer who is running through an airport, tired, or stressed. Each of these changes what a person can process and what they need first. Airline apps are the canonical failure. They show the same home screen whether the flight is in three days or thirty minutes, whether the customer is on the sofa or past security. The journey stage changes everything about what matters. The interface changes nothing.

Why it matters to the business

Context-blind design is effort, and effort destroys loyalty. CEB research published in Harvard Business Review found that 96% of customers who go through high-effort experiences become more disloyal, against 9% after low-effort ones. Hunting through a generic menu for a boarding pass while a gate closes is a high-effort experience delivered at the worst possible moment.

PwC's study of 15,000 consumers across 12 countries found nearly 80% of US consumers rank speed, convenience, knowledgeable help, and friendly service as what matters most, and 32% will leave a brand they love after one bad experience. Bad experiences cluster at high-stress moments, which is precisely where context-blind products fail hardest.

How to use it

• Map the states of your key journey, not just the steps: three days before, one day before, at the venue, mid-task, after a failure.
• Define the single thing the customer needs first in each state, and put it on top.
• Use signals you already hold, such as time-to-event, location permission, and recent activity, to switch the default view.
• Test in real conditions: walking, one-handed, in glare, under time pressure, on a weak connection.
• Move everything else behind progressive disclosure so the urgent state stays clean.

Where teams get it wrong

Teams equate context with responsive layout. The screen resizes correctly, so the box is ticked. But a perfectly rendered generic home screen is still the wrong screen for a customer standing at the gate. Others bolt on personalization gimmicks, greeting the customer by name, while the thing that customer actually needs in this moment remains three taps deep.

Ask your team

• What does our product show a customer thirty minutes before their moment of highest stress, and is it the thing they need first?
• When did we last test our product in real conditions rather than at a desk?
• Which contextual signals do we already collect, and do any of them change what the customer sees?

The journey stage changes everything about what matters. The interface changes nothing.