The standard definition confines usability to specified users, specified goals, and a specified context of use

What it is

ISO 9241-11 defines usability as "the extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency, and satisfaction in a specified context of use." The three "specified" are not rhetoric—they turn usability from an adjective into a normative term with a scope, and they are what contracts, procurement, and conformance testing cite.

Why it happens

The triple specification is the entry point for operationalization: without "specified users" there is no recruitable sample or capability baseline; without "specified goals," no tasks or success criteria; without "specified context," no control of environmental variables. The definition's job is to collapse argument into testable propositions—"under conditions X, effectiveness, efficiency, and satisfaction reach degree Y." Quoting it outside the specification exceeds the standard's own scope; that is the boundary between the term and everyday "easy to use."

Studying it

Conformance-style evaluation designs follow the definition: state the user group, goal tasks, and context settings, then collect and judge the three-component metrics. Studying the definition's evolution means comparing version texts: the 1998 wording and the 2018 revision moved from "product used by users" toward interactive systems and outcomes, reflecting a shift from product-centered to use-centered. Methodologically, evaluation reports citing the standard must disclose the triple specification, or they violate the standard's own traceability.

Where it stops holding

The definition is a normative instrument, not a theory: it fixes the measurement frame but does not explain why usability arises, and it leaves component weights and methods to users—two "conforming" measurements with different setups remain incomparable. It also sets no thresholds; how effective counts as usable is decided by business and regulation, not the text.

Applying it

• In contracts and acceptance documents, spell out all three specifications when citing the definition, so "meets usability requirements" becomes a decidable clause.
• Build evaluation templates on the definition's structure: user-group description, goals and tasks, context setting, three-component metrics.
• Annotate legacy documents citing older versions of the definition to prevent mixed calibers across versions.

Related

• Same group: B5.08.2 Context of use includes device, physical environment, and social environment—not just the interface · B5.08.3 The definition treats usability as a relational property of product and context, not an inherent property of the product · B5.08.4 Newer standards place usability inside a broader quality-in-use concept alongside accessibility, not containing it
• Nearby: B5.01 Usability Definition · Q2 Usability Testing
• Search terms: iso 9241-11 · usability standard · specified context of use