User experience

User experience, usually shortened to UX, describes what it is like for someone to interact with a product, service or organisation. On a website, it includes how people find information, understand an offer, complete tasks and deal with what happens afterwards.

A good-looking interface is part of that experience, but the wider journey also matters. A visitor can enjoy the visual design and still struggle to establish whether a service is suitable or whether an enquiry has reached anyone.

What does UX design involve?

UX design investigates the needs of the people using a service and shapes the journey around those needs. It can involve research, information structure, content, interaction design, prototypes and evaluation.

The work starts with a task or problem. A hotel guest may need to compare rooms. An industrial buyer may need to establish technical suitability. A business owner may need to understand the scope of a website project.

Those tasks provide a basis for decisions. Instead of asking whether a page feels modern in the abstract, the team can examine whether it supports the decisions people actually need to make.

UX versus UI

User interface, or UI, concerns the points of interaction: controls, page layouts, menus, forms and the way information is presented. UX includes those details within the broader experience.

An attractive booking form may have a polished interface. If the service offers no suitable appointments and gives no alternative route, the overall experience can still be poor.

The distinction helps teams diagnose problems. Some require a clearer control or visual hierarchy. Others require different information, a revised process or better coordination beyond the website.

Why research matters

People inside a business often know its terminology, structure and offer extremely well. That knowledge can make it difficult to notice what a new visitor does not understand.

Research introduces evidence from outside that internal perspective. Conversations with customers, observed tasks, support questions and sales feedback can reveal the language people use and the points at which they hesitate.

The method should fit the uncertainty. A broad questionnaire may collect opinions, while watching a person attempt a specific task can reveal a practical obstacle they would not have described beforehand.

Information architecture and content

Information architecture concerns how content is organised and connected. Menus, categories and labels help people form a model of the website and choose a route.

A structure based entirely on internal departments may make little sense to a prospective customer. Organising around services, needs or tasks can provide a clearer starting point, depending on the audience.

Content then needs to answer the questions along that route. Design cannot supply a missing specification or clarify a process the business itself has not defined. Strong UX work brings those gaps into the brief.

What is usability?

Usability concerns how effectively people can use an interface to achieve a goal. It includes practical questions about understanding, effort and errors.

Can someone find the relevant product, compare options and complete the enquiry? Do they recognise what is clickable? Can they recover when they enter information incorrectly?

Usability is an important part of UX, but the overall experience also includes whether the service meets a meaningful need. A process can be straightforward and still deliver an outcome that disappoints the customer.

UX across different devices

The same person may use a website in several contexts. They might research on a laptop, revisit details on a phone and forward a page to a colleague. The journey should remain coherent.

Responsive web design helps adapt presentation to available space. The UX question is whether the person can still achieve the task, including when touch input, a smaller screen or an on-screen keyboard changes the conditions.

Test the actual process rather than only checking screenshots. A menu that looks neat can still be difficult to operate, and a form can fit the screen while making error correction unnecessarily hard.

UX and accessibility

Accessibility concerns whether people with disabilities can use the content and functionality. It should be part of the design process from the beginning.

Clear structure, meaningful labels and predictable behaviour can support many users. Accessibility also involves specific needs that cannot be reduced to general convenience.

Include appropriate evaluation and, where possible, the experiences of people using different access methods. An automated scan can help identify some issues, but it cannot explain every aspect of a person's experience.

How do you measure UX?

Choose evidence connected with the task. Useful measures can include successful completion, errors, time spent resolving a problem and the need for support. Customer feedback helps explain the experience behind those measures.

Business outcomes such as qualified enquiries can add context, but a single conversion rate does not describe the entire experience. A restrictive process might filter submissions while frustrating suitable customers.

Combine observation and measurement. A dashboard can reveal where a journey changes; research can help explain why and guide an appropriate improvement.

What should a UX review deliver?

A useful review identifies specific problems, the people affected and the evidence supporting each finding. Recommendations should explain how a change would improve the task.

Prioritise work by impact and confidence. A broken essential journey usually deserves attention before an aesthetic preference with little supporting evidence.

For the broader definition, see Nielsen Norman Group's introduction to user experience. Explore Linford websites for the relationship between research, content, design and implementation.