Efficiency
Concept
One axis of usability: how fast and with how few actions an already-familiar user can finish the same task.
Why it exists
"Easy to use" was read for a long time as easy for someone on their first day. Add guidance, break steps into smaller ones, insert a confirmation, and the first-day experience improves.
The trouble started after the first day. Theo heard it from an operations lead who uses Pagedeck daily: duplicating a document and renaming it took six clicks, and they did it ten times a day. That's sixty clicks a day and 1,200 a month. Steps that had been split apart for newcomers became a cost that daily users couldn't skip. Nobody had decided to charge them that; the decision had only ever been made for the first day.
Efficiency is the axis that looks at that cost. Instead of asking whether something is easy, it asks whether it's fast once someone knows it.
How it works
You measure the time and the number of actions a familiar user needs to complete one task. The unit drops all the way to seconds and clicks. Duplicating and renaming going from six clicks to two is an improvement on this axis, and nothing else needs to change for that to count.
What it applies to is repetition. Cutting one click from a screen opened ten times a day is worth a lot; the same cut on a screen opened once a month changes almost nothing. What binds there is memorability — whether someone returning after a long gap has to learn the thing again.
The usual way to raise it is to open a separate path that only experienced users take: keyboard shortcuts, multi-select for acting on many items at once, sensible defaults, recently used items pushed to the top. Removing a confirmation and adding undo belongs here too. It meets error prevention at that point, and when undo works reliably, dropping the confirmation stays safe.
This axis collides with learnability regularly. A wizard that splits a task into steps for beginners is twelve unskippable clicks for an expert. So teams decide in advance which one takes priority and build a separate route for the one they gave up. Before recruiting any users, the flexibility and efficiency item in the Nielsen heuristics serves as the checklist for this axis, since experts can usually spot a missing shortcut without watching anyone work.
How it sounds at work
"This takes six clicks. Someone doing it ten times a day is doing sixty."
Multiplying by frequency to show what the improvement is worth.
"Leave the wizard alone and open a separate shortcut path for experienced users."
Splitting the route where the two axes collide.
"Let's drop this confirmation and add undo. People are clicking through it without reading."
The confirmation isn't protecting anyone and is only adding actions.
Theo counted the clicks and worked with Noa to add a path that duplicates straight from the list. The wizard stayed as it was, and six clicks became two.
Easily confused with
| Term | When it's measured | How it differs |
|---|---|---|
| Learnability | Within the first 30 minutes after signup | Looks at whether a first-time user gets through without help. Efficiency measures someone who already learned it, so a design that raises one often cuts into the other |
Where to go next
- Usability
see the set this axis is one piece of
- Learnability
compare it with the axis it collides with most
Last updated 2026-09-16