Explain like I'm five · SW Eng

What is a Usability Test?

Usability testing, told as a story about handing over a book with no instructions and quietly watching where a reader gets stuck.

zero typos!but I can't find the table of contentszero typos, and the reader is still lost

Zero typos, and the reader is still lost.No typos and easy to use are two different things.

surely this reads fine, right?the team has never watched a real reader flip through itthe team's guess and what readers really do often differ

The editorial team just assumes it'll be easy to use.The team has never actually watched a reader flip through it.

a usability test = handing a reader the book with no instructions, and watching where they get stucknot grading the reader — checking whether the book itself is easy to use

A usability test hands over the book with no instructions and simply watches where the reader gets stuck.It's not grading the reader — it's checking whether the book itself is easy to use.

Learnabilitya first-time reader figures out the book right away
Efficiencyreaders find the page they want quickly
Memorabilityreturning readers don't get lost
Satisfactionreaders feel good after using the book
OBSERVATION LOGtime taken — minutes to find the contentswhere the reader stalledhow many times the reader asked for helpsatisfaction — how they feel afterwardthe proofreader quietly watches and notes each reader, one at a time

The proofreader quietly watches and logs each reader, one at a time.The log records time taken, where they stalled, help requests, and satisfaction.

proofing — any typos?usability — is it easy to use?usability testing checks ease of use, not right or wrong — a different job from proofing

Usability testing isn't about catching typos.Usability testing checks ease of use, not right or wrong.

In one breath

Usability testing means handing the book over as-is and quietly watching where the reader gets stuck, with no instructions given.

Usability testing gives real users tasks and observes them using a product, assessing learnability, efficiency, memorability, errors, and satisfaction. Broader usability evaluation also includes heuristic evaluation, where experts review a product against a checklist. Unlike QC, which catches typos and functional bugs, it's a user-centered evaluation of whether something is easy to use — not whether it's correct.

When grown-ups say it

Usability Test
A test that hands something over with no instructions and watches. It checks whether the product itself is easy to use.
Learnability
How quickly someone figures out how to use it the first time. Ideally it works without a manual.
Efficiency
How fast someone finds what they want. Measured by time taken.
Memorability
How little someone struggles coming back later. How to use it comes back quickly even after a long gap.
Satisfaction
How someone feels after using it. Usually gathered with a survey or interview.
Errors
How often mistakes happen, and how serious they are. Often tracked as a fifth attribute alongside the rest.
QC / Proofing
Catching typos and functional mistakes. It checks correctness — a different job from usability, which checks ease of use.
Software Quality Certification
Usability is one line item on a bigger checklist. → the official mark on the cover
Next story
The Blueprint That Shapes the Whole Book Ahead of Time →
Want another term as a picture book? Request →