Make it easy to understand and complete
Simple checks that show where people get stuck, and how to fix those spots before people give up.
In short
Making a design easy to understand and complete means checking where people get stuck and fixing those spots, using simple checks like Nielsen's ten heuristics.
4 min readFree
What you will learn
Good design helps people understand what to do next, then do it. This lesson shows you how to find the spots where people get stuck, and how to check a screen before you ship it.
A screen can look nice and still fail. A person may not see the right button, or may quit halfway through a form. The words below will help you talk about these problems.
Key words
- Interface
- The part of a product people see and touch, such as screens, buttons, menus and forms.
- Task
- A goal a person tries to reach, such as paying a bill or changing a password.
- Usability
- How easily people can finish a task with an interface.
- Heuristic
- A broad rule of thumb. It points you at likely problems but does not prove them.
- Completion rate
- The share of people who finish a task successfully.
What does usability mean?
<cite index="20-1">In plain terms, usability asks whether people can finish a job with a design, and how easily they get it done.</cite> Usability is not a property of the screen alone. The same design can work well for one person and badly for another, depending on the job and the place they use it.
<cite index="22-4">Nielsen Norman Group names five parts of usability.</cite> The best focus depends on the product.
Learnability
How fast a new person can finish basic jobs. A tax website used once a year needs this most.
Efficiency
How quickly experienced people work once they know the design. A tool used all day needs this most.
Memorability
How easily someone gets back up to speed after a long break.
Errors
How many mistakes people make, how serious they are, and how easily people recover.
Satisfaction
How pleasant the design feels to use.
Rules of thumb to check screens
<cite index="10-4">Jakob Nielsen's list of 10 usability heuristics was published in 1994 and is still widely used.</cite> <cite index="10-5">Nielsen called them heuristics, not rules, because they are broad principles of interaction design rather than exact specifications.</cite> Four of them are a good place to start.
Keep people informed
<cite index="9-18">When something happens, the system should show what was done and respond within a reasonable time.</cite>
Speak the user's language
<cite index="7-5">Use words and ideas people already know, not internal project names.</cite>
Show it, don't make people remember it
<cite index="10-10">If people must recall where something is or what it was called, the design leans too hard on memory.</cite>
Give people a way out
<cite index="10-7">Users should always feel in control of where they are and how to get somewhere else.</cite> An undo or back button helps here.
Help people finish a task
The best way to find what is hard is to watch people. <cite index="20-2">Watch representative users do realistic tasks, early and repeatedly, and fix what you see.</cite>
- 1
Pick one important task
Choose a job people really need to do, such as signing up or booking a ticket.
- 2
Watch someone try it
Stay quiet. Notice where they pause, click the wrong thing or give up.
- 3
Write down each stuck point
Note the screen, what the person expected, and what happened instead.
- 4
Fix the worst problem and test again
Change one thing, then test with new people to see if the task is easier.
Watching people is not the only way to check a design. Teams can also use the rules above as a checklist, as described in the section below.
How can you check a screen without users?
<cite index="3-2">A heuristic evaluation is a quick inspection, and it needs no lab and no test users.</cite> You walk through each screen and ask whether it breaks any of the rules. It is a good first pass before you test with people.
Tip
Do not block every risky action to stop mistakes. A screen that stops people from doing anything is also hard to use. Prevent the likely errors, and still let people act.
How do you measure how often people finish?
A simple way to measure how often people finish a task is the completion rate. Divide the tasks finished by the tasks tried, then multiply by 100.
In words: completion rate equals tasks completed divided by tasks attempted, times 100. Here is a short Python check with five attempts.
results = ["done", "done", "gave up", "done", "done"]
done = results.count("done")
print(f"Completed {done} of {len(results)} tasks")
print(f"Completion rate: {done / len(results) * 100:.0f}%")Output
Completed 4 of 5 tasks Completion rate: 80%
Check your understanding
Quick check
A form gives no message after you press Submit, so you cannot tell if it worked. Which rule is broken?
Sources
- Usability 101: Introduction to Usability (Nielsen Norman Group)
- Nielsen Norman Group articles index
- Nielsen's 10 Usability Heuristics (Human Standards)
- Nielsen's Heuristics (The Decision Lab)
- Usability Heuristics for Designers: Nielsen's 10 Principles (Design Thinker Labs)
- 10 Usability Heuristics for User Interface Design (SDH)
- 10 Usability Heuristics: S-Tier Behavioral Designer's Guide (Yu-kai Chou)
- Classification and taxonomy of mobile application usability issues (arXiv)
Last updated on 17 November 2026
Related lessons
Learn with me
Every lesson is free. I add new ones as I learn. Have a question, or want help with your own work? Book a short call.