User experience, or UX, is everything a person goes through when they deal with a company and its products, not just the screens they tap. These user experience basics start with the definition the field itself uses, then cover the building blocks, the classic rules of thumb, and the testing habit that holds it all together.
User experience means the full experience a person has with a company, its services and its products. That is the definition behind the Nielsen Norman Group’s definition of user experience: user experience encompasses all aspects of the end user’s interaction with the company, its services, and its products. Every step counts, from the first advert a person sees to the day they call support and ask for help.
Why does one plain definition matter so much? Because teams keep shrinking UX down to the look of an app, and then wonder why customers still leave angry. User experience basics begin with the wider view: a product can have perfect screens and still deliver a poor experience when the price hides fees, the parcel arrives late, or the help page answers nothing. This guide lays out the foundation in order: the meaning, the origin, UX vs UI, the seven qualities, the ten heuristics, and how the work gets done.
| UX at a glance | |
|---|---|
| Definition | All aspects of the end user’s interaction with the company, its services and its products (Nielsen Norman Group) |
| Term coined by | Don Norman, at Apple in 1993, as the first User Experience Architect |
| Seven facets | Useful, usable, desirable, findable, accessible, credible and valuable (Peter Morville’s honeycomb) |
| Classic checklist | Jakob Nielsen’s 10 usability heuristics, first developed in 1990 and refined in 1994 |
| Testing rule of thumb | About 5 similar users per round find most problems in a qualitative study (Nielsen and Landauer) |
What user experience actually means
Start the user experience basics with the first requirement NN/g sets: an exemplary user experience meets the exact needs of the customer, without fuss or bother. Next comes simplicity and elegance, which produce products that are a joy to own and a joy to use. Notice what the definition leaves out. It never mentions colors, fonts or button shapes. Those belong to one part of the work, and the definition sits above all of them.
NN/g makes the point with a website that carries movie reviews. Imagine the site has a perfect interface for finding a film: fast search, clean pages, clear ratings. If the database behind it only holds movies from the major studios, a reader hunting for a small independent release still walks away with a poor experience. The screen did its job. The service behind the screen did not, and the experience is the whole thing, not the screen.
That is also why NN/g says a high quality experience needs a seamless merging of several disciplines at once, including engineering, marketing, graphical and industrial design, and interface design. A checkout flow can be beautifully drawn and still fail at the payment step. A support team can be kind and still fail because the product confuses people daily. User experience basics treat all of it as one product: the relationship between the person and the company.
Where the term came from
The words are younger than the work. Don Norman, a cognitive scientist who studies how people think and act, joined Apple in 1993 as an Apple Fellow. He asked for the title User Experience Architect, the first time the phrase appeared in a job title, and led a small User Experience Office there.
Norman explains the coinage in his own words: “I invented the term because I thought human interface and usability were too narrow. I wanted to cover all aspects of the person’s experience with the system, including industrial design, graphics, the interface, the physical interaction and the manual.” He wanted one term for the whole relationship, not a handful of smaller terms for the parts.
In 1998 Norman co-founded the Nielsen Norman Group with Jakob Nielsen, the usability researcher behind the heuristics later in this guide. The firm’s research still anchors most of what beginners learn as user experience basics today, which is why this guide keeps returning to its pages.
UX vs UI, and where usability fits
The most common beginner confusion mixes up three words: UX, UI and usability. The user interface, UI for short, is the part of a product a person sees and touches: screens, buttons, menus, icons and forms. NN/g calls the UI an extremely important part of the design. It is still only a part.
Usability is a different word again. NN/g treats usability as a quality attribute of the user interface, covering whether the system is easy to learn, efficient to use and pleasant. A product can score well on usability and still miss on experience, like the movie site above, whose interface worked while its catalog failed the reader.
Think of it as layers. The UI sits inside usability, and usability sits inside the total experience, alongside content, speed, trust, delivery and support. When a team says it is doing UX by redrawing screens, it is working on the smallest of the three layers.
| User interface (UI) | User experience (UX) | |
|---|---|---|
| What it is | The screens and controls a person uses | The whole interaction with the company and its products |
| It covers | Buttons, menus, forms, icons, layouts | Research, structure, content, delivery, support, trust |
| Judged by | Does the screen look right and respond well | Does the person reach the goal without fuss, and feel good about it |
| Example | One clear checkout button | Finding the product, trusting the price, paying, receiving it, returning it if needed |
The seven building blocks: Morville’s honeycomb
One diagram has taught beginners the shape of this field for two decades. Peter Morville, an information architect, developed the user experience honeycomb to help his clients move beyond usability alone. His model names seven facets, or qualities, that a good experience balances: useful, usable, desirable, findable, accessible and credible, with valuable at the center, because an experience must deliver value to the people who use it and to the sponsors who fund it. For user experience basics, this is the map to memorize.
- Useful. The product does a real job. Morville urges practitioners to ask whether their products are truly useful, and to define solutions that are more useful, not just prettier.
- Usable. People can learn it and use it with ease. Morville calls ease of use vital, then adds the warning that usability is necessary but not sufficient.
- Desirable. Image, identity, brand and emotion pull people toward a product. Pure efficiency is not the whole quest.
- Findable. Sites and objects must be designed so users can find what they need, through navigation and search alike.
- Accessible. Just as buildings have elevators and ramps, websites should work for people with disabilities. Morville calls it good business and the ethical thing to do.
- Credible. Whether users trust and believe what a product tells them decides whether they stay.
- Valuable. The center of the honeycomb. For profit sites must contribute to the bottom line and improve customer satisfaction; nonprofits must advance the mission.
The honeycomb also teaches priorities. Morville’s point is that each project strikes its own unique balance between the facets, and teams should make those tradeoffs explicitly rather than by accident. A hospital site may put accessible and credible first. A game studio pushes desirable to the front. Problems start when a team copies another product’s balance wholesale, or never chooses one at all.
Nielsen’s 10 usability heuristics
If the honeycomb says what an experience needs, the heuristics say how to check an interface. Jakob Nielsen developed the 10 heuristics for heuristic evaluation with Rolf Molich in 1990, then refined them in 1994 through a factor analysis of 249 usability problems. NN/g calls them heuristics because they are broad rules of thumb, not specific usability guidelines, and the set has remained relevant and unchanged since 1994. The full list lives on NN/g’s 10 usability heuristics page; here it is in plain words.
| # | Heuristic | What it means in plain words |
|---|---|---|
| 1 | Visibility of system status | Keep users informed about what is going on, with clear feedback in reasonable time. |
| 2 | Match between the system and the real world | Speak the users’ language, follow real world conventions, and show information in a natural, logical order. |
| 3 | User control and freedom | People act by mistake. Give them a clearly marked exit, undo and cancel, without a long process. |
| 4 | Consistency and standards | The same words and actions should mean the same thing. Follow platform and industry conventions. |
| 5 | Error prevention | The best designs stop problems before they happen: remove risky conditions or ask for confirmation first. |
| 6 | Recognition rather than recall | Make options visible so users recognize them, instead of forcing them to remember information. |
| 7 | Flexibility and efficiency of use | Add shortcuts for expert users without hurting beginners, and let people tailor frequent actions. |
| 8 | Aesthetic and minimalist design | Cut information that is irrelevant or rarely needed. Every extra detail competes with what matters. |
| 9 | Help users recognize, diagnose and recover from errors | Error messages in plain language, no codes, that name the problem and suggest a solution. |
| 10 | Help and documentation | Best when the system needs no extra explanation. When help exists, keep it searchable, task focused and concise. |
Beginners use the list as a review tool. Walk through a design screen by screen, note every place a rule breaks, and fix the worst breaks first. The check costs nothing but attention, and it catches the classic faults: silent failures, mystery icons, dead ends and error codes that help nobody. No set of user experience basics is complete without it.
How UX work actually happens
UX is not a single talent or a single step. It is a loop that teams repeat: research, design, test, fix, and test again. Research comes first. Designers interview and observe real users to learn their goals, habits and pain points, instead of guessing from a meeting room. What they learn turns into sketches, flows and early drafts of the product. That is where our guide to rapid prototyping fits: teams test the idea before they build the real thing, and structural methods such as feature sliced design keep the growing interface organized once building starts.
Then comes the step that defines the field: usability testing. In a typical session, a facilitator asks a participant to perform realistic tasks, such as finding a product or resetting a password, while the participant works through them and thinks aloud. The facilitator observes behavior and listens for feedback, without defending or explaining the design. The goals are plain: identify problems in the design, uncover opportunities to improve, and learn how the target users actually behave. NN/g puts it bluntly: even the best designers cannot design a good enough experience without iterative design driven by observations of real users. The only way to get UX design right is to test it. That sentence is the working heart of user experience basics.
How many people do you need to watch? Fewer than most teams fear. In research with Tom Landauer, Nielsen showed that a single test user reveals about a third of a design’s usability problems on average, and that testing with 5 users in one round uncovers about 85 percent of them. His advice follows from the math: spread the budget across many small tests. After the first round finds most problems, the team fixes them, then tests again to check the fixes worked and to reach the deeper structural issues the surface problems were hiding. Three studies with 5 users each improve a product far more than one monster study with 15.
Hold the finding with its conditions, though, because five is not magic. The formula holds for comparable users who use the product in fairly similar ways, in qualitative studies that hunt for problems. A product aimed at two distinct groups, such as children and parents, needs a small round with people from each group, around 3 to 4 users per group. And when a team wants numbers it can benchmark, like task success rates, NN/g points to about 20 users instead. Testing also only pays when the team acts on it: fixes get planned, shipped and retested, the adaptive habit our guide to adaptive software development describes at project level. Watching users sits beside, never instead of, the wider craft of software testing basics, which checks that the product works at all. UX testing checks that people can work it.
Mistakes beginners make
Four mistakes show up in almost every beginner project. The first is designing for yourself. You are not your user, and your insider knowledge of the product hides its confusing parts from you. The second is asking people what they want and building exactly that. NN/g warns that true user experience goes far beyond giving customers what they say they want. People describe solutions; observation reveals needs, and needs are what design must serve.
The third mistake is testing once, at the end, when changes cost the most. The loop above exists to spread small, cheap tests across the whole project. The fourth is treating UX as decoration, a coat of paint applied to a finished product. By then the structure, the content and the prices, the things that decide the experience, are already fixed. User experience basics exist to move these questions to the start, where they are still cheap to change.
Conclusion
User experience basics rest on one wide definition: everything a person goes through with a company, its services and its products. Norman coined the term at Apple to cover that whole relationship, not just the interface. Morville’s honeycomb names the seven qualities a good experience balances, Nielsen’s heuristics give you a checklist to review any screen, and small repeated rounds of testing with real users tell you the truth about your design. Learn those four pieces, and you hold the foundation the rest of UX builds on.
Frequently asked questions
What is user experience in simple words?
User experience is everything a person feels and goes through when they deal with a company and its products: finding them, buying, setting up, using them day to day, and getting help when something breaks. The Nielsen Norman Group defines it as all aspects of the end user’s interaction with the company, its services, and its products.
What is the difference between UX and UI?
The user interface is the part you see and touch: screens, buttons, menus and forms. User experience is the whole journey around that interface, including research, content, delivery, support and trust. UI is one part of UX, not a synonym for it.
How many users do you need for a usability test?
For a qualitative test that hunts for problems, about five users per round reveal roughly 85 percent of the issues, as long as the users are similar to each other and do similar tasks. Fix what they expose, then run another small round. Studies that measure numbers, such as task times, need more people, around 20.
Written by
Ahmad Jajja
Ahmad covers AI, chips and the companies behind them. For this guide he went back to the sources beginners skip: NN/g’s own definition, heuristics and testing research, checked line by line.
Reviewed by
Danish Mustafa
Danish reviews laptops, phones and home tech over weeks of real use, and fact-checks the numbers in our coverage. Here he verified every heuristic name, date and percentage against the Nielsen Norman Group pages.