Loading content
The System Usability Scale (SUS) is a standardized ten-item questionnaire for rapidly assessing perceived usability of interactive systems. It yields a single numeric score to compare products and evaluate design changes in user research and product development. The method is lightweight, widely adopted, and supports quantitative comparisons across users and…
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Theoretical construct: explains a term, principle, or mental model.
Concrete cog in the system that works inside larger relationships.
A standardised ten-item questionnaire for quickly capturing perceived usability.
The System Usability Scale was developed in 1986 by John Brooke at Digital Equipment Corporation as a short, technology-independent usability measure. Its ten alternating statements produce a standardised comparison score.
After use, a person rates ten statements on a five-point scale. The answers are transformed and summed to produce a SUS score from 0 to 100; it is a comparative measure, not a direct percentage.
The approach provides shared language for the system context under consideration.
Relationships, processes or measures make the effects of decisions traceable.
The approach supports comparing products or iterations with a standardised score.
SUS enables quick comparative measurements of perceived usability after a user test or between design variants.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.