Usability: a field guide

01 · The premise

“Usability is a quality attribute that assesses how easy user interfaces are to use — and the methods for improving that ease during design.”

Jakob Nielsen — Usability 101, Nielsen Norman Group

Digital.gov puts it plainly: measure how easily someone can finish what they came to do, usually through usability testing — success rates and satisfaction under established research methods. Utility asks whether the features exist. Usability asks whether people can use them without fighting the interface. Usefulness needs both.

If users cannot find it, they cannot buy it, claim it or finish it either.

02 · The five qualities

Ease is not one number.

NN/g breaks usability into five components. Score them separately and you stop arguing about vibes.

Q·01

Learnability

How easy is it to finish basic tasks the first time someone meets the design?

Q·02

Efficiency

Once they know it, how quickly can they perform those tasks?

Q·03

Memorability

After a break, how quickly can they re-establish proficiency?

Q·04

Errors

How many, how severe, and how easily can people recover?

Q·05

Satisfaction

How pleasant is it to use — not decorative, just not punishing?

+ Utility

Does it do the job?

Usability without the right features is still useless. Usefulness = usability + utility.

03 · The process

It's a loop, not a launch gate.

Test early, cheap and often. Paper prototypes first; polish last. Waiting for a finished build is how structural problems become permanent.

01 Plan

01 / 05

Agree research questions, recruit real or likely users, design believable tasks and write a discussion guide. GOV.UK: plan for 30–60 minute sessions, no more than six a day, with breathing room between them.

Select a phase — or keep scrolling. Iteration is the point.

04 · The unit of work

One honest task at a time.

NN/g's three ingredients: representative users, representative tasks, and quiet observation. Click the blanks to cycle scenarios.

Watch try so that .

Focus groups listen to opinions. Usability tests watch behaviour. Listening alone is misleading — watch what people actually do.

05 · The craft

Write tasks that do not cheat.

GOV.UK: good tasks set a clear goal, feel believable, are hard enough to surface friction — and never hint at the path.

As written · leading briefv1

Please click the blue Apply button ¹in the top-right corner, ²then complete the three-step wizard ³to submit your claim successfully.⁴

After the passv2

“You need to start a claim for Self Employment Income Support. Use this prototype as you would at home.”

Leading → neutral. Same goal, zero spoilers — now the hesitation you see is real.

Stay quiet. Let them talk.

06 · The toolkit

Six rules that keep tests honest.

Drawn from Digital.gov practice, NN/g discount methods and the GOV.UK Service Manual.

R·01

Test five, then revise

Five users usually surface the major issues. Run many small rounds; fix between them. Iteration beats one giant study.

NN/g — discount usability

R·02

You are not the user

Recruit outside your team. Colleagues know too much and forgive too easily. Real users bring real stakes.

R·03

Reassure before the first task

Tell them you are testing the service, not them. Nervous participants hide the problems you need to see.

GOV.UK — moderated sessions

R·04

Stay quiet

Mostly watch and listen. Interrupt only to recover a stuck participant or dig into something unexpected — with open questions.

R·05

Include assistive technology

Prefer participants on their own devices. Screen readers and magnification set-ups are hard to fake in a lab.

GOV.UK · Digital.gov — inclusive research

R·06

Start before the build is finished

Paper and prototypes first. Structural problems found after engineering are the expensive kind.

07 · The proof

Session readiness is measurable.

Tick what you already have. The gauge is a planning score — not a vanity metric — based on GOV.UK session prep.

target zone · readiness 75–100

0Session readiness

tick the planning steps you already have

0done
8checks
0ratio
0%ready

Research questions agreedWhat must you learn before you can change the design?
Representative users recruitedActual or likely users — not colleagues from your floor.
Tasks that do not give away the answerClear goals, believable context, no leading hints.
Discussion guide writtenIntro script, tasks, follow-ups, planning checklist.
Observers and a note-taker bookedWatch together; decide later. Do not design in the room.
Venue and access sortedAccessible space, remote option, assistive tech welcome.
Consent and recording coveredInformed consent, secure storage of personal data.
Same-day debrief plannedCapture findings while the session is still warm.

Pair this with a research plan and participant agreements — Digital.gov publishes samples for both. Store personal data securely after each day of sessions.

08 · The evidence

And the numbers agree.

5users

is usually enough to find the most important usability problems in a round.

Nielsen Norman Group — discount usability testing

10%of a design budget on usability roughly doubles website quality metrics on average.NN/g — Usability 101

30–60minper moderated session; plan no more than six one-hour sessions a day with gaps between.GOV.UK Service Manual

UX ⊃ UUsability sits inside user experience — mechanics that make goals achievable, measured by success and satisfaction.Digital.gov — Usability topic

Opinion theatreUsability discipline

Settles debates in the highest-paid opinionSettles debates by watching real tasks fail or finish

Runs one huge study after launchRuns many small tests from paper onwards

Asks ‘do you like it?’ in a focus groupAsks people to complete a goal, then observes

Writes tasks that point at the buttonWrites goals that leave the path for the user to find

Skips people who use assistive techTests with their devices and set-ups included