User Experience

Definition

User experience (UX) is the holistic perception, ease, and outcome a person has while interacting with a product, service, or interface — measured across discovery, first use, repeat use, and the moment they decide whether to return.

User experience encompasses everything a person notices, feels, and remembers about using a product. It is not the same as the visual interface, the brand, or the technology underneath — those are inputs into UX, but the experience itself is the integrated outcome. A site can have beautiful UI and still deliver bad UX if pages load slowly, copy is unclear, or the path to the goal has unnecessary friction.

The modern usage of "user experience" was popularised by Don Norman at Apple in the early 1990s. Norman wanted a term that captured every aspect of a person's interaction with a system — industrial design, graphics, interface, physical interaction, manuals, support — not just the screen. That broad definition still holds today: UX is the whole journey, including pricing pages, onboarding emails, error messages, and the cancellation flow.

Origin

Coined by Don Norman in the early 1990s while at Apple, where he held the title "User Experience Architect" — believed to be the first person to use the term in a job title. Norman's 1988 book The Design of Everyday Things laid the conceptual groundwork.

How it works

Research the people who will use the product — their goals, contexts, and current workarounds.
Map their end-to-end journey, including the emotional highs and lows at each step.
Identify the moments of highest friction or drop-off — those are the highest-leverage targets.
Design and prototype solutions that remove friction without adding complexity.
Test with real users; ship; measure behaviour against the goals defined in step one.
Iterate. UX is never "done" — it improves continuously against changing user needs.

When to use it

Use when

Building any product where the user has alternatives — competitors, doing it manually, or doing nothing.
Redesigning a flow with high abandonment, support volume, or low conversion.
Onboarding a new audience whose mental model differs from the existing user base.
Before a major feature launch, when the cost of getting it wrong is high.

Skip when

When there is no defined success metric. UX work without a target collapses into taste debates.
On internal tools used twice a year — invest only what the usage frequency justifies.
As a substitute for fixing a broken business model. UX cannot rescue a product no one wants.

Key metrics

Task success rate — did the user complete the job they came to do?
Time on task — how long did it take, and is that improving?
Error rate — how often did they recover from a wrong action?
System Usability Scale (SUS) score — a standardised 0–100 perceived-usability rating.
Net Promoter Score (NPS) — a directional read on whether users would recommend the product.
Conversion rate on the primary flow — the business outcome the UX is engineered for.

Examples

The user experience on the new checkout page reduced cart abandonment by 38%.
Good user experience is invisible — bad user experience is the only thing the user remembers.
We rebuilt the onboarding flow and lifted day-7 retention from 18% to 31%.

In practice at Makreate

Every product Makreate ships — websites, apps, brand systems — is engineered around measurable UX outcomes, not aesthetics alone. A recent SaaS engagement started with a 22-minute onboarding flow that lost 70% of trials before activation. We mapped the journey, killed three optional steps, replaced a long form with progressive disclosure, and shipped in two weeks. Activation jumped from 30% to 62% — same product, same audience, better experience. That outcome is the UX, not the redesigned screens.

UX Design →

Common mistakes

Confusing UX with UI. UI is the surface; UX is the whole journey, including copy, performance, support, and pricing.
Designing for stakeholders instead of users. The exec who pays for the project rarely uses the product daily.
Treating UX as a final-stage polish. The most expensive UX problems are baked in at the architecture stage.
Optimising for time on site as a UX metric. For most products, less time on task is the win.
Asking users what they want. People are excellent at describing problems, poor at designing solutions.

Frequently asked

Is UX the same as UI?

No. UI is the visual and interactive surface — buttons, type, colours, layouts. UX is the whole journey, including UI, but also copy, performance, pricing, support, and the emotional outcome. A clean UI cannot rescue a confused experience.

How do you measure UX?

With a mix of quantitative (task success rate, time on task, conversion) and qualitative (interviews, observed sessions, SUS score, NPS) signals. The right mix depends on the question — analytics tell you what; observation tells you why.

Who owns UX in a company?

Officially, a UX team if one exists — but in practice everyone whose decisions touch the user. Engineers shipping a slow page, marketers writing confusing ad copy, support agents replying late — all of them shape UX.

How long does good UX take?

A focused redesign of a single flow can ship in 2–6 weeks. A full product UX overhaul is a 3–9 month engagement. UX is iterative, not one-shot — the product gets better continuously, not in a single launch.