By the end of this topic, you should be able to...
explain and apply five usability objectives (learnability, efficiency, memorability, errors and satisfaction) in order to evaluate a product.
Guiding Question
How does understanding user needs directly impact the design of products and services?
The Origin and Authority of the Framework
These five usability objectives derive directly from the foundational work of usability engineer Jakob Nielsen, first formalised in his landmark text Usability Engineering (1993) and subsequently refined through decades of empirical research at the Nielsen Norman Group.
Nielsen defines usability not as a single property but as a multi-dimensional quality attribute — a product cannot be assessed as simply "usable" or "unusable" because usability is composed of distinct, measurable, and sometimes competing dimensions:
"Usability is a quality attribute that assesses how easy user interfaces are to use. The word 'usability' also refers to methods for improving ease-of-use during the design process."— Nielsen, Jakob. Usability Engineering. Morgan Kaufmann, 1993.
The IBO Design Technology Guide (First Assessment 2025) adopts Nielsen's five-component framework as the analytical vocabulary for product evaluation — these five objectives are the tools through which students move from subjective opinion ("this product is confusing") to rigorous, evidence-based critique ("this product scores poorly on learnability because the menu structure requires more than three levels of navigation to access core functions, with no progressive disclosure or visual hierarchy to guide a first-time user").
Nielsen himself situates usability within the broader concept of system acceptability, noting that usability is a component of utility within usefulness — a product that cannot be used is worthless regardless of how technically sophisticated it is.
Why Five Objectives — Not One?
The power of this framework lies in its recognition that usability objectives can conflict with each other — optimising for one may compromise another. This is not a flaw in the framework — it is its most important insight, because it means that product evaluation is never simply about measuring a single score, but about understanding the trade-offs a designer has made.
Conflict Example | Objective A | Objective B |
A feature-rich toolbar maximises power-user efficiency but overwhelms new users | High Efficiency (experts) | Low Learnability (novices) |
A confirmation dialogue before deletion reduces errors but slows down experienced users | Low Errors | Reduced Efficiency |
A simplified interface improves learnability but limits the actions experienced users can take | High Learnability | Reduced Efficiency |
Automatic form completion increases efficiency but reduces user control, which may decrease satisfaction | High Efficiency | Reduced Satisfaction |
Design Technology principle: When analysing a product using usability objectives, identifying these trade-off decisions demonstrates the deepest level of analytical thinking. A product that scores poorly on one objective has not necessarily been poorly designed — the designer may have made a deliberate trade-off. The critical question is: was that trade-off appropriate for the primary user and context?
Objective 1: Learnability
Definition
"How easy is it for users to accomplish basic tasks the first time they encounter the design?"— Nielsen, Jakob. "Usability 101: Introduction to Usability." Nielsen Norman Group, 4 Jan. 2012.
Learnability measures the gradient of the learning curve — how quickly a new user can move from zero knowledge to productive use of a product. A product with high learnability allows a first-time user to accomplish their primary goal with minimal instruction, error, or frustration.
What Learnability Is Not
Learnability is not about whether a product can eventually be learned — almost any product can be learned given sufficient time and instruction. Learnability specifically measures the speed and ease of initial acquisition — the first encounter, not the eventual mastery.
Factors That Affect Learnability
1: Consistency with established conventions
Users arrive at any product with pre-existing mental models — expectations about how things work based on prior experience. Products that violate established conventions impose additional learning costs:
2: Feedback and Signifiers
Norman distinguishes between affordances (the actual possibilities for action) and signifiers (the perceptible signals that communicate those possibilities). Learnability is enhanced when signifiers clearly communicate affordances — when the product tells the user what to do without requiring prior knowledge or instruction.
3: Progressive Disclosure
Presenting only the information and options needed for the current task rather than all possible features simultaneously reduces initial cognitive load and improves learnability. This is why well-designed onboarding sequences reveal complexity gradually rather than presenting the full interface immediately.
4: Error Visibility
Users learn a product partly through making and recovering from errors. A product with high learnability makes errors visible, understandable, and recoverable — the user can see that something went wrong, understand why, and correct it. This transforms errors into learning opportunities rather than frustration barriers.
How to Evaluate Learnability
Evaluation Method | What It Measures |
First-use task completion test | Can a new user complete a defined task without instruction or assistance? |
Time-to-first-success | How long does it take a new user to successfully complete the primary task? |
Error frequency on first use | How many errors does a new user make before completing the task? |
Think-aloud protocol | What does a new user say and think while attempting to use the product for the first time? |
Heuristic evaluation | Does the product follow Nielsen's usability heuristics related to learnability? |
Real-World Application
Product: A commercial espresso machine (domestic model) Learnability evaluation: The machine presents new users with six unlabelled buttons arranged in a horizontal row, each differentiated only by icon. The icons use non-standard representations — a circle-within-a-circle for single espresso, two circles for double — that do not align with any established visual convention. The water reservoir is accessible only after removing a panel that appears fixed, with no visible handle or signifier indicating it is removable. There is no onboarding sequence. First-use task completion testing with five participants revealed that none could successfully produce a single espresso within five minutes without consulting the manual. Verdict: LOW learnability. The design prioritises aesthetic minimalism over communicative clarity. The trade-off is appropriate for an experienced barista audience but inappropriate for a domestic consumer market.
Objective 2: Efficiency
Definition
"How quickly can users perform tasks, once they have learned the design?"— Nielsen, Jakob. "Usability 101." Nielsen Norman Group, 4 Jan. 2012.
Efficiency specifically addresses the performance of experienced, proficient users — it is the measure of how much productive work can be done per unit of time, once the learning phase has been completed. This is a crucial distinction: learnability addresses the novice; efficiency addresses the expert.
Why the Distinction Matters
A product designed for a user who will interact with it once or rarely should prioritise learnability. A product designed for a user who will interact with it daily, intensively should prioritise efficiency. Confusing these contexts leads to design failures:
Factors That Affect Efficiency
1: Pathway Depth
The number of steps, clicks, taps, or interactions required to complete a task determines efficiency directly. Each additional step is a time cost and a cognitive cost.
2: Shortcuts and Accelerators
Nielsen's heuristic principle of flexibility and efficiency of use identifies accelerators — keyboard shortcuts, gesture commands, custom hotkeys — as the primary mechanism for distinguishing novice and expert efficiency. A well-designed product offers two interaction pathways: a visible, discoverable path for novices and an efficient shortcut path for experts.
"Accelerators — unseen by the novice user — may often speed up the interaction for the expert user to such a degree that the system can cater to both inexperienced and experienced users."— Nielsen, Jakob. "10 Usability Heuristics for User Interface Design." Nielsen Norman Group, 24 Apr. 1994.
3: Cognitive Load and Decision Points
Every moment at which a user must make a decision — choose between options, recall information, interpret feedback — is an efficiency cost. Reducing unnecessary decision points is central to efficiency design. This is the principle behind progressive automation in software — a product that remembers the user's previous choices and offers them as defaults reduces the cognitive burden of repeated decisions.
4: Physical Ergonomics and Motor Efficiency
For physical products, efficiency is determined not only by cognitive pathway depth but by physical interaction quality:
Reach envelope — are frequently used controls within the primary reach zone?
Force requirements — does the control demand appropriate force without fatigue?
Feedback on actuation — does the control confirm that it has been activated?
Grip and surface design — does the form facilitate quick, accurate interaction?
How to Evaluate Efficiency
Evaluation Method | What It Measures |
Task time measurement | Average time for proficient users to complete defined tasks |
Keystroke-Level Modelling (KLM) | Predicted task time based on counting physical operations required |
Eye-tracking | Visual search time — how long does it take to locate target elements? |
Pathway analysis | Minimum number of steps to complete core tasks |
Comparative benchmarking | Task completion time vs. competitor products or prior versions |
Real-World Application — Evaluating a Product
Product: A professional kitchen knife Efficiency evaluation: The knife's handle geometry places the user's grip index finger directly at the bolster — the junction between blade and handle — allowing the grip to be established in a single, repeatable motion without visual guidance. The weight balance (54% blade, 46% handle, measured at the bolster) minimises wrist fatigue during extended use, reducing the recovery time between cutting strokes. The blade geometry (hollow ground with 15° edge angle) reduces drag through dense materials, decreasing the force and time required per stroke. Verdict: HIGH efficiency for proficient users. The design embodies efficiency at every physical interaction point. Note that the professional grip technique required to exploit these features must be learned — the design trades some learnability for significant efficiency gains. This trade-off is appropriate for professional kitchen use.
Objective 3: Memorability
Definition
"When users return to the design after a period of not using it, how easily can they re-establish proficiency?"— Nielsen, Jakob. "Usability 101." Nielsen Norman Group, 4 Jan. 2012.
Memorability addresses the durability of learned skill — how much of what was learned during initial use can be retained and recovered after a gap in use. It is the measure of how quickly an intermittent user (one who uses the product occasionally rather than daily) can return to productive use.
Factors That Affect Memorability
1: Metaphor and Mental Model Alignment
Products that map their interface onto familiar real-world structures are more memorable because users can draw on existing long-term memory frameworks rather than constructing entirely new ones. The desktop metaphor in computing (files, folders, trash/recycle bin) was successful precisely because it mapped onto the familiar spatial and categorical structures of physical office work — users could recover their mental model of the system by drawing on memories of physical office organisation.
2: Consistent Structure and Location
When interface elements maintain consistent positions across sessions, users develop spatial memory for their location — they remember where things are physically, not only what they are. Redesigns that relocate familiar elements force re-learning of spatial memory, explaining the intense user frustration experienced when major platform updates (Facebook's periodic redesigns, Google's occasional interface overhauls) move established elements.
3: Visual Distinctiveness and Uniqueness
Elements that are visually distinctive are more memorable than those that are visually similar. If five buttons in a row are identical in size, colour, and shape, users must rely on cognitive recall of labels to distinguish them. If one button is visually distinct — larger, differently coloured, differently positioned — the visual distinction supports spatial and visual memory.
4: Meaningful Labels and Icons
Recognition is always easier than recall — this is a fundamental principle of human memory (Tulving and Thomson, 1973). Interfaces that allow users to recognise the correct action from visible options outperform interfaces that require users to recall commands from memory. This is why graphical user interfaces (GUIs) displaced command-line interfaces for general use — selecting from visible options is cognitively cheaper than recalling typed commands from memory.
This principle — recognition over recall — is one of Nielsen's ten usability heuristics and is the primary design mechanism for improving memorability.
How to Evaluate Memorability
Evaluation Method | What It Measures |
Delayed recall test | After a gap of 1–4 weeks, how quickly can users return to proficiency? |
Re-use task completion rate | Can returning users complete core tasks without re-consulting instructions? |
Error rate on return visit | How many errors do returning users make in their first 5 minutes of re-engagement? |
Subjective confidence rating | Do returning users feel confident or uncertain about their ability to operate the product? |
Real-World Application
Product: A domestic sewing machine (mid-range, computerised) Memorability evaluation: The machine is used seasonally by an intermittent user — perhaps monthly for craft projects. Thread path is indicated by a printed colour-coded sequence of numbered arrows physically moulded into the machine body — this engages spatial and sequential memory and is reinforced by consistent visual coding across all models in the manufacturer's range. Stitch selection is via a physical dial with printed stitch diagrams directly adjacent to each setting — recognition from visual stimulus rather than recall of stitch numbers. The needle threading mechanism has a single labelled lever with a clear spatial relationship to the needle — the label persists, so users can re-orient after a gap in use without referring to the manual. Verdict: HIGH memorability. The design externalises critical sequential knowledge onto the machine body, reducing the memory burden on the intermittent user. The colour-coded threading guide and dial-based stitch selection both leverage recognition over recall, directly supporting re-use after periods of non-use.
Objective 4: Errors
Definition
"How many errors do users make, how severe are these errors, and how easily can they recover from the errors?"— Nielsen, Jakob. "Usability 101." Nielsen Norman Group, 4 Jan. 2012.
The errors objective has three distinct components, each requiring separate design attention.
The Cost of Errors — A Spectrum
Not all errors are equivalent. An error classification by consequence severity is essential for design prioritisation:
Severity Level | Consequence | Design Priority |
Catastrophic | Irreversible, life-threatening, or severely damaging consequence — data permanently destroyed, physical injury, financial loss | Prevent at all costs — physical guards, forced confirmation sequences, automatic protection |
Critical | Significant consequence requiring substantial recovery effort — major data loss, significant rework required, extended process interruption | Prevent by design — confirmation dialogs, auto-save, reversible defaults |
Moderate | Noticeable consequence with recovery possible — minor data loss, task restart required, brief interruption | Recover gracefully — clear error messages, undo function, auto-recovery |
Minor | Negligible consequence — small inconvenience, easily corrected | Minimise annoyance — clear feedback, single-step correction |
Error Prevention Design Strategies
Forcing Functions
Physical or digital constraints that make it impossible to perform an action incorrectly:
A car that cannot be shifted from Park into Drive without the brake pedal depressed
A plug that can only be inserted in one orientation
A software form that cannot be submitted without completing required fields
Constraints
Limiting the possible range of actions to those that are appropriate in context:
A date selector that does not allow impossible dates (February 31st)
A physical knob with hard stops at the minimum and maximum settings
A colour picker that only offers accessible colour combinations
Confirmation Dialogs
Requiring explicit user confirmation before irreversible, high-consequence actions:
"Are you sure you want to permanently delete this file?"
Note: Confirmation dialogs should be reserved for truly consequential actions — overuse causes confirmation fatigue (users click "Yes" without reading) and reduces efficiency without improving safety.
Affordance and Visibility of Safe Paths
Making the correct action visually prominent and incorrect or dangerous actions visually recessive — the good path is easy to find, the risky path requires deliberate navigation.
How to Evaluate Errors
Evaluation Method | What It Measures |
Usability testing error log | Count, type, and severity of errors during observed task completion |
Support ticket analysis | Systematic patterns in user errors reported to support channels |
Heuristic evaluation | Assessment against Nielsen's error-related heuristics |
Failure Mode and Effect Analysis (FMEA) | Systematic identification of all possible failure modes and their consequences |
Cognitive walkthrough | Step-by-step analysis of whether each action in a task is clear and error-resistant |
Real-World Application
Product: A domestic microwave oven Errors evaluation: Error frequency analysis: The numeric keypad requires users to enter time in a non-standard format (pressing '1', '3', '0' to set 1 minute 30 seconds) — a format inconsistent with the clock display format (HH:MM) — generating frequent input errors observed in user testing. Error severity analysis: Over-time errors are catastrophic in specific use cases (heating oil, certain materials) — the design provides no automatic high-temperature detection to interrupt operation. Error recoverability: A single dedicated 'Clear' button allows immediate cancellation of incorrectly entered values without navigating menus. The 'Add 30 Seconds' button is a significant error-prevention feature — it reduces the probability of input errors by allowing approximate time setting through additive, single-press operations. Verdict: MIXED errors performance. Excellent recoverability design (Clear button, Add 30 Seconds) partially mitigates poor error prevention in the time-entry interface. Critical safety gap in high-temperature detection represents an unaddressed catastrophic severity failure mode.
Objective 5: Satisfaction
Definition
"How pleasant is it to use the design?"— Nielsen, Jakob. "Usability 101." Nielsen Norman Group, 4 Jan. 2012.
Satisfaction is the most holistic of the five usability objectives — it encompasses the full subjective experience of using a product, including emotional responses, aesthetic pleasure, sense of control, trust, engagement, and felt competence. It is the dimension that captures what the other four objectives miss: a product can be learnable, efficient, memorable, and error-resistant and still be profoundly unpleasant to use.
Why Satisfaction Is a Usability Objective
There is a temptation in functional design disciplines to treat satisfaction as a luxury — a property relevant only after the "real" functional objectives are met. This is a significant design error for two reasons:
Satisfaction drives continued use A product that users find unsatisfying will be abandoned when an alternative appears, regardless of its functional performance. User satisfaction is directly correlated with product adoption, sustained use, and recommendation behaviour.
Emotional responses affect functional performance Donald Norman's research on affect and cognition demonstrates that positive emotional states improve user performance — specifically, broadening attention, increasing creative problem-solving, and reducing the perceived difficulty of tasks:
"Attractive things work better... When you wash and wax a car, it drives better, doesn't it? Or at least it feels like it does."— Norman, Donald A. Emotional Design: Why We Love (or Hate) Everyday Things. Basic Books, 2004, p. 17.
This is not merely subjective opinion — Norman draws on neurological research demonstrating that positive affect increases the availability of dopamine in the prefrontal cortex, which directly enhances cognitive flexibility and tolerance for ambiguity. A user who finds a product satisfying will persist longer through difficulties, explore more actively, and tolerate minor errors more generously than a user who finds the same product unpleasant.
The Three Levels of Emotional Design
Norman's Emotional Design (2004) provides the theoretical framework for understanding and designing for satisfaction at three distinct levels:
Visceral Level
Immediate, pre-conscious sensory response - appearance, sound, texture, smell, initial physical impression.
"This feels good in my hand" "This looks expensive/cheap"
Behavioural Level
Pleasure and effectiveness of use - the experience during operation
"This does what I expect" "I feel in control" "The feedback is satisfying"
Reflective Level
Conscious, narratigve self-image - meaning, identify, story, pride.
"I am the kind of person who uses this product" "This respresents quality/craft/values I identify with"
All three levels contribute to user satisfaction. A product that delivers strongly at the visceral level but fails at the behavioural level (beautiful but frustrating to use) will ultimately produce low satisfaction. A product that performs excellently at all three levels — physically pleasurable, behaviourally empowering, and reflectively meaningful — achieves the highest satisfaction scores.
Satisfaction and Trust
Satisfaction is closely related to user trust — the user's confidence that the product will behave as expected, that their data or safety is protected, and that the manufacturer stands behind the product. Trust is particularly critical in:
Medical and safety-critical devices
Financial products
Products that store personal data
Products used in high-stakes contexts (professional tools, emergency equipment)
A product that violates user trust — through unexpected behaviour, data loss, safety failure, or inconsistent performance — cannot recover satisfaction through aesthetic appeal or efficiency alone.
How to Evaluate Satisfaction
Evaluation Method | What It Measures |
System Usability Scale (SUS) | 10-item standardised questionnaire producing a 0–100 satisfaction score |
Post-task rating scales | Immediate satisfaction ratings after specific task completion |
Net Promoter Score (NPS) | Likelihood to recommend as proxy for overall satisfaction |
Semi-structured interview | Qualitative satisfaction data — the emotional language users use about the product |
Longitudinal engagement data | Return use frequency, session duration, abandonment rates |
Semantic differential scales | Rating product qualities on paired adjective scales (beautiful–ugly, trustworthy–untrustworthy) |
Real-World Application
Product: Apple AirPods (first generation, 2016) Satisfaction evaluation: Visceral level: The matte white stem, satisfying magnetic click of the charging case lid, and the distinct acoustic "click" of case opening created immediate positive sensory impressions widely documented in launch reviews. Behavioural level: The automatic ear-detection pause function (music stops when one earbud is removed) delivered a precise match between user expectation and product behaviour — the product appeared to understand the user's intent, generating a strong sense of felt intelligence. The Reflective level: The distinctiveness of the white stem design — visible and identifiable at distance — created a cultural signifier; early adopters reported that AirPods communicated a particular identity claim (technology-forward, premium, unconstrained by wires). The product generated Net Promoter Scores consistently above 70 in its first 18 months of release. Verdict: EXCEPTIONAL satisfaction performance at all three Norman levels. The satisfaction achievement was not incidental — it was the primary design brief, with functional specifications (audio quality, battery life, connectivity) serving the satisfaction design goal rather than leading it.
The Usability Matrix
When evaluating a real product for IB Design Technology, the five objectives should be applied as an integrated analytical framework, not as five separate analyses. The most sophisticated evaluation identifies how the five objectives interact and conflict in the specific product:
Template coming soon....
Common Errors in IB Assessment
Error | Why It Fails | Correction |
Defining objectives without applying them | Definition alone is knowledge recall (low marks); application is the required command term | Always apply each objective to a specific, named product with cited evidence |
Applying objectives without evidence | Unsupported opinion is not analysis | Cite specific observations, measurements, user data, or design features as evidence for each evaluation claim |
Treating all five objectives as equally relevant | In any real product, some objectives are more critical than others depending on context of use and user type | Identify which objectives are most critical for your specific product and context, and justify why |
Listing weaknesses without identifying design opportunities | The learning objective requires identifying opportunities for improvement | For each weakness identified, propose a specific, feasible design improvement |
Ignoring trade-offs between objectives | Failing to identify trade-offs suggests shallow analysis | Explicitly acknowledge where improving one objective creates tension with another |
Applying objectives in isolation from user context | Learnability for whom? Efficiency for which user type? | Always specify the user type and context of use when applying each objective |
The Five Objectives at a Glance
Sources
Nielsen, Jakob. Usability Engineering. Morgan Kaufmann, 1993.
Nielsen, Jakob. "10 Usability Heuristics for User Interface Design." Nielsen Norman Group, 24 Apr. 1994, www.nngroup.com/articles/ten-usability-heuristics.
Nielsen, Jakob. "Usability 101: Introduction to Usability." Nielsen Norman Group, 4 Jan. 2012, www.nngroup.com/articles/usability-101-introduction-to-usability.
Norman, Donald A. The Design of Everyday Things. Rev. ed., Basic Books, 2013.
Norman, Donald A. Emotional Design: Why We Love (or Hate) Everyday Things. Basic Books, 2004.
International Baccalaureate Organization. Design Technology Guide. International Baccalaureate Organization, 2023. First Assessment 2025.
Cooper, Alan, Robert Reimann, David Cronin, and Christopher Noessel. About Face: The Essentials of Interaction Design. 4th ed., Wiley, 2014.
Martin, Bella, and Bruce Hanington. Universal Methods of Design: 100 Ways to Research Complex Problems, Develop Innovative Ideas, and Design Effective Solutions. Rockport Publishers, 2012.
Tulving, Endel, and Donald M. Thomson. "Encoding Specificity and Retrieval Processes in Episodic Memory." Psychological Review, vol. 80, no. 5, 1973, pp. 352–373.
Linking Questions
To what extent does UCD rely on a strong foundation of ergonomics? (A1.1)
How important is a good understanding of user-centred research methods to ensure effective UCD? (A2.1)
To what extent can the UCD process be influenced by the quality of modelling and prototyping of potential design solutions? (B2.2)
To what extent should a UCD process focus on ensuring inclusive design? (C1.2)
What influence can product analysis and evaluation have on the effectiveness of UCD? (C3.1).