How usability is scored, and why most entries lose points in the first minute
Usability is the heaviest-weighted question in any UX review: can people finish what they came to do? What editors measure, the first-minute failures that cost the most, and the evidence that moves the number.
Of the seven criteria, usability is the one everybody thinks they understand and the one entries most often misjudge. It isn't a measure of how clean a product looks or how modern it feels. It's one question, asked coldly: can a person complete what they came to do — efficiently, confidently, and without error?
What an editor is actually measuring
- Completion5Did the task finish at all, without help, without a reset?
- Errors4How many wrong turns, and could each be recovered without starting again?
- Effort4Steps, fields, decisions — how much the product asked of the person.
- Confidence3Did they know it had worked, or did they have to check?
- Recovery3When it went wrong, how quickly were they back on track?
Note what isn't on that list: aesthetics, novelty, how impressive the transitions are. Those are scored elsewhere. This criterion is stubbornly about whether the thing works for a person who has other plans today.
The first minute, where entries are won and lost
Editors open the product cold. The first sixty seconds set the tone for every score that follows, and there are four failures that recur:
- No obvious next action. A screen with six equally weighted options is a screen with no design. One primary action, obviously primary.
- A gate before any value. Sign-up walls, email verification, a mandatory tour, a sales call. Every step before the first useful moment is paid for in patience.
- A demo that isn't the product. Fake data that behaves differently from real data teaches the wrong thing and then breaks its own lesson.
- A first screen that assumes yesterday. Onboarding that starts mid-conversation, as if the user had already read the marketing site.
Efficiency is not the same as minimalism
Teams often read "efficient" as "fewer elements," and hide functionality behind progressive disclosure until the product becomes a guessing game. Efficiency is measured in the user's effort, not in the interface's element count.
Looks simple, costs more
- One field at a time across six screens
- Everything behind a hamburger
- Icons without labels, to keep it clean
- A wizard for a task experts do daily
Looks busier, costs less
- One form, sensibly grouped, on one screen
- The five most-used destinations visible
- Icons with labels, always
- A wizard for the first time, a form after that
Confidence: the half of usability nobody measures
A task that completes but leaves the person unsure it completed has failed at something. It generates a check, a screenshot, a support message, a second submission. The fixes are small and consistently under-done: state what happened in specific words, show the changed thing rather than describing it, and make the record findable afterwards.
The question isn't whether they finished. It's whether they knew they'd finished — and whether they'd be willing to do it again tomorrow without checking.
Evidence that moves the number
Usability is the criterion where data is most available and most often absent from entries. What persuades, in order:
| Compared on | Strong | Weak |
|---|---|---|
| Completion | 71% → 89%, unmoderated, n=600, one task | "Users find it much easier" |
| Time on task | 11 minutes → 4, measured, same task | "Faster than before" |
| Errors | Form errors per submission, before and after | "Fewer mistakes" |
| Support | Tickets in one category, quarter over quarter | "Support load decreased" |
| Qualitative | Five sessions, what changed as a result | A quote from a happy customer |
Small samples are fine. Five moderated sessions honestly reported beat a thousand-person survey about satisfaction — and a team that says "we watched five people and three of them missed the button, so we moved it" has demonstrated the discipline better than any number.
The cheapest test before you enter
Find someone who has never used the product. Give them the main task, say nothing, and watch. Don't explain, don't rescue them, don't answer questions — just write down every moment they hesitate.
Twenty minutes of that will tell you more about your usability score than any internal review, because it is exactly what an editor will do. The difference is that your colleague forgives you and the editor writes it down.
Enter a project and find out where it lands — seven criteria, and a written verdict either way.
Forms: where usability is most often decided
Most products' hardest usability moment is a form, and most forms are longer than they need to be because every team that wanted a field got one.
| Compared on | Raises the score | Lowers it |
|---|---|---|
| Length | Only what's needed now; the rest later | Everything the business might want one day |
| Labels | Above the field, always visible | Placeholder text as a label |
| Validation | On blur, with a specific message at the field | On every keystroke, or only after submit |
| Errors | Keeps the input, moves focus to the problem | Clears the form |
| Optionality | Marks optional fields, not required ones | Asterisks everywhere |
| Autofill | Correct autocomplete attributes | Blocked, "for security" |
The difference between hard and complicated
Some products are genuinely complex — tax software, clinical systems, logistics planning. Complexity is not a usability failure, and editors don't score a product down for being about something difficult. What is scored is whether the interface adds difficulty of its own on top of the domain's.
The test isn't whether a novice can use it. It's whether someone who understands the job can do the job — without the interface being one of the things they have to understand.
Questions we get asked
Is usability weighted more heavily than the other criteria?
All seven carry equal weight today. Usability tends to dominate anyway, because a product that fails here usually drags interaction, learnability and IA down with it.
How many people do we need to test with?
Fewer than you think. Five moderated sessions, honestly reported, tell us more than a thousand-response satisfaction survey.
Our product is for experts. Does that change scoring?
It changes the expectations, not the standard. Density and shortcuts are appropriate; ambiguity and dead ends aren't.
What's the single most common usability failure in entries?
No obvious next action on the first screen — six equally weighted options where there should be one primary path.
Assessed work that scores highest on usability
Chosen by score from the work the editors have assessed, not by hand.
- usability
- scoring
- criteria
Written by
The UXE editors
The team that selects the work, uses it, scores the seven criteria and writes every verdict on this site.
Keep reading
Judging & criteria6 min read
What a winning award entry looks like from our side
The difference between entries that score well and entries that don't is rarely the product. It's the evidence. What editors open first, what makes them raise a score, and the five mistakes that cost the most points.
The UXE editors
Craft & practice5 min read
Information architecture that scores: labels, depth and the way back
Information architecture is one of the seven UXE criteria. What editors test — labels people would use themselves, depth that matches the task, search that works, and a way back from anywhere.
The UXE editors
Craft & practice5 min read
Learnability: onboarding that teaches instead of touring
Learnability is one of the seven UXE criteria: how quickly a first-time user becomes a confident one. Why product tours rarely work, what does, and how to measure time-to-first-value honestly.
The UXE editors