UX Design Principles: 10 Ways to Improve Usability
UX design principles start with Jakob Nielsen's ten usability heuristics, first published in April 1994 and still the reference set today. Several of them overlap with testable WCAG requirements, including error identification and labels at Level A. Seed Light designs against both sets.
Most advice about UX design principles is either a list of ten things with no source, or a lecture about empathy.
The actual set is older, shorter and more useful than either. It was published in 1994 and it still describes why your enquiry form annoys people.
This guide covers the ten heuristics and where they came from, which ones overlap with accessibility requirements, and how to apply them without recruiting a single test participant.
Key Takeaways
- The canonical set is Nielsen's ten heuristics. First published on 24 April 1994, still maintained by Nielsen Norman Group.
- They describe people, not technology. Which is why they have outlived every platform written since.
- Several overlap with WCAG. Error Identification and Labels or Instructions both sit at Level A.
- Heuristics are judgement, criteria are tests. You evaluate one and you pass or fail the other.
- No research budget required. The point of a heuristic is that one person can apply it alone.
Where the Principles of UX Design Come From
Jakob Nielsen published ten general principles for interaction design in April 1994. Nielsen Norman Group still maintains them, and the current page is the canonical wording.
They are called heuristics deliberately. They are rules of thumb for evaluating an interface rather than specific usability guidelines, which means they apply to a booking form and a bank app equally.
That generality is why they date so well. Nothing in the list mentions a mouse, a browser or a screen size. The ux design principles that survived three decades did so by describing the person rather than the device.
It also explains why they keep being rediscovered under new names. Most modern design systems are a house style sitting on top of the same ten ideas.
Nielsen wrote them for software nobody runs any more. They still read as current.
A house style tells you what a button looks like. A heuristic tells you whether the button is doing its job. That is the difference between a brand rule and the ux design principles underneath it.
That is a real difference when you inherit somebody else's site. The style guide is usually missing, and the pages still have to be judged somehow.
These ux best practices give you that judgement without needing the original designer in the room. You can open any page and ask the same ten questions of it.
The Ten, in Plain Words
- Visibility of system status. Tell people what is happening. A form that submits silently fails here.
- Match between the system and the real world. Use the words customers use rather than your internal terms.
- User control and freedom. An obvious way out of anything, including a half finished form.
- Consistency and standards. The same thing in the same place on every page.
- Error prevention. Stop the mistake happening rather than explaining it afterwards.
- Recognition rather than recall. Show the options instead of asking people to remember them.
- Flexibility and efficiency of use. Shortcuts for people who already know what they want.
- Aesthetic and minimalist design. Every extra element competes with the one that matters.
- Help users recognise, diagnose and recover from errors. Say what went wrong, in words, next to the thing.
- Help and documentation. Available when needed, not required to get started.
Read as a set, the ten principles of ux design are mostly about reducing uncertainty. Four of them are explicitly about telling somebody where they are and what just happened.
Where They Meet Accessibility Requirements
Three of the heuristics restate something WCAG makes testable, which is worth knowing because the testable version is the one an auditor checks.
Error Identification at Level A requires that when an input error is automatically detected, the item in error is identified and the error described to the user in text. That is heuristic nine, written as a pass or fail.
Labels or Instructions at Level A requires labels or instructions when content requires user input. That covers heuristics five and six, and it is the criterion a placeholder-only form fails.
Consistent Help, added in WCAG 2.2 at Level A, requires repeated help mechanisms to occur in the same order relative to other page content. That is heuristics four and ten together.
So a site built against these ux design principles tends to pass several accessibility criteria without anybody aiming at them. The reverse also holds, which is the more useful direction for a small business: fixing the testable criteria drags the judgement calls along behind them.
How to Apply Them Without a Research Budget
Four steps. A heuristic evaluation is something one person does alone, which is the whole reason the method exists and the reason it suits a business with no research team.
1. Walk your own enquiry path
Start at a service page and go through to the confirmation, as a stranger would. Write down every moment you were unsure what was happening.
Those moments are almost always visibility of system status, and they are the cheapest thing on the list to fix. A spinner, a sentence and a confirmation page cover most of them.
Do it on a phone as well. Half the uncertainty on a small screen comes from something being below the fold rather than missing.
Write it down as you go. Nobody remembers the third hesitation by the end of the walk.
2. Read your own error messages
Submit the form wrong on purpose. Leave the email blank, type a nonsense phone number, skip a required field.
Do the same with your phone number field. Most forms are strictest there for no reason.
WCAG asks that the item in error is identified and described in text. A red border alone does neither, and a message at the top of the page that does not name the field does only half.
3. Check your words against your customers'
Match between the system and the real world is the heuristic small businesses break most, usually by using industry terms on buttons.
Request a consultation is internal language. Book a visit is what the customer said on the phone. The second one is shorter, clearer and already in their vocabulary.
Your enquiry emails are the cheapest source of this. People tell you what they call the thing in the first line, and matching it costs nothing but a text edit.
4. Count what each page asks of memory
Recognition rather than recall means showing the choices rather than expecting somebody to hold them in their head.
Any step that requires remembering something from two pages earlier is a candidate for rework. Price lists and service names are the usual offenders, because they live on one page and are referenced from three.
Ideas That Work Right Now
Four things you can do today. None needs a designer.
- Name the button after the job. Read it aloud. If you would not say it, change it.
- Add a confirmation sentence. Say what happens next and when.
- Move error text beside the field. Not the top of the page.
- Delete one element per page. Usually the one nobody can explain.
These are the ux best practices that need no sign-off. Each is a text or layout change.
UX Design Rules Worth Applying First
Not every principle costs the same to act on. These are the ux design rules that return the most for the least work on an ordinary business site.
| Principle | What to fix first | Cost |
|---|---|---|
| Visibility of system status | Form confirmation and loading states | Low |
| Error recovery | Message text next to the field | Low |
| Match the real world | Button and menu wording | None |
| Consistency | Header and footer across pages | Low |
None of these is a redesign. All of them are the sort of thing a site accumulates and nobody revisits, usually because each one was correct the day it shipped.
Common Mistakes With UI UX Design Principles
- Treating them as a style guide. They are evaluation criteria, not a visual direction, and no heuristic names a colour.
- Quoting an effect size. Nielsen Norman Group publishes no figure for how many problems the heuristics catch, so neither should anybody else.
- Confusing them with WCAG. One is judgement and the other is testable, and only one of them can be failed formally.
- Skipping the walkthrough. The method is designed to be done without participants, so there is no excuse for not doing it.
- Fixing aesthetics first. Aesthetic and minimalist design is one of ten, and it is not the one your enquiries are failing on.
- Applying them once. Every new page and every new form reintroduces the same faults.
The last one is the expensive mistake. A site passes its own review at launch and then drifts, one well-meant addition at a time. Putting the ux design principles into whoever reviews new pages is what stops that, and it is a habit rather than a project.
FAQs
What are the ten usability heuristics?
Visibility of system status, match between the system and the real world, user control and freedom, consistency and standards, error prevention, recognition rather than recall, flexibility and efficiency of use, aesthetic and minimalist design, helping users recognise and recover from errors, and help and documentation.
Who wrote the usability heuristics and when?
Jakob Nielsen, first published on 24 April 1994, and still maintained by Nielsen Norman Group. The age is a feature rather than a problem. They describe how people deal with interfaces rather than any particular technology, which is why they have outlasted every platform they were written for.
Are UX principles the same as accessibility rules?
They overlap but they are not the same. Heuristics are judgement, while WCAG criteria are testable requirements. Error Identification and Labels or Instructions both sit at Level A and both restate what two of the heuristics ask for, so meeting one often satisfies the other.
Which principle matters most for a small business site?
Visibility of system status, usually. Most complaints about small business sites come down to somebody not knowing whether something worked: whether the form sent, whether the order was received, or whether the page is still loading or simply broken. A confirmation sentence fixes more than a redesign does.
Do I need to test with users to apply these?
No, though testing finds more. The heuristics exist so a designer can evaluate an interface without recruiting anybody. That is what makes them practical for a small business. Walk through your own enquiry flow against the ten and faults appear quickly.
Conclusion
These ux design principles are thirty years old, freely published, and still describe why most enquiry forms lose people.
Walk your own path, read your own error messages, and fix the wording before the aesthetics. The ten questions cost nothing to ask and the answers are usually obvious. Applied honestly, these ui ux design principles find more than a redesign would, and they find it this afternoon.
If you would rather have that done as part of a build, see how we approach web design.
