Interface Usability Measure (IUM)
Also known as: IUM, Usability Assessment, System Usability Scale
Interface Usability Measure (IUM), exemplified by the System Usability Scale (SUS) developed by John Brooke in 1986 and extended by Lewis and others, is a rapid, single-scale or multi-item assessment of perceived interface usability. IUM captures how easy, intuitive, and satisfying users find an interactive system, ranging from 10-item SUS questionnaires to custom domain-specific usability measures. IUM is widely used in software development, web design, and human-factors research to quantify user perception of system ease-of-use and guide iterative interface improvement.
Read the full method
Sign in with a free account to read this section.
Method map
The neighbourhood of related methods — select a node to explore.
When to use it
Use IUM (especially SUS) to rapidly assess user-perceived usability during iterative software design, web development, and interface evaluation. Ideal for: (1) Comparing design alternatives (test 5 designs with 5–10 users each, compare SUS scores to identify best option); (2) Tracking usability across development releases (measure SUS with each release, graphing trend over time); (3) Benchmarking against competitors (compare your app's SUS to industry-standard or competitor products); (4) Identifying design friction points (ask follow-up questions about low-scoring items: 'You rated the system as complex—what was confusing?'). Less suitable if you need detailed diagnostic breakdown of specific usability issues (use think-aloud protocols, eye-tracking, or task-based error analysis); IUM gives you a score but not detailed 'why.' Also less suitable for novice users unfamiliar with computers or digital interfaces; SUS assumes basic digital literacy.
Strengths & limitations
- Ultra-brief and practical: SUS is 10 items, 2–3 minute completion; no instrumentation required; feasible to administer dozens of times per project.
- Robust and well-validated: SUS has been used in thousands of studies and products; extensive published norms, benchmarks, and psychometric evidence available.
- Sensitive to design changes: SUS consistently detects usability improvements post-redesign; effect sizes are typically 5–15 SUS points for meaningful improvements.
- Applicable across domains: Used successfully for desktop software, web, mobile apps, embedded systems, medical devices, consumer electronics; generalizable across contexts.
- Low respondent burden: 10-item questionnaire is quick, minimizing fatigue and respondent drop-out in rapid iteration cycles.
- Actionable feedback: SUS provides a single, interpretable score that stakeholders understand; a SUS=72 is better than a score of 65.
- Subjective and not task-performance-based: High SUS does not guarantee users can actually accomplish their goals efficiently; a system may feel easy but be slow. Pair SUS with task-completion metrics (time, error rate).
- Overlaps with satisfaction and overall quality: SUS items touch on ease-of-use, complexity, and willingness to use again, conflating usability with overall satisfaction. A system can be complex but satisfying (e.g., Photoshop); SUS might not capture this distinction cleanly.
- Ceiling effect in excellent products: For best-in-class software, SUS scores cluster near 85–95; floor space for further discrimination is limited. Sensitive alternatives exist for high-end usability assessment.
- Cultural and language sensitivity: SUS is English-developed; translations require careful adaptation to ensure 'easy to use' and 'unnecessarily complex' carry equivalent meaning across languages.
- Limited diagnostic detail: A low SUS score (40) tells you usability is poor; it doesn't tell you whether the problem is navigation, information architecture, visual design, or learning curve. Use open-ended follow-up or qualitative methods.
- Requires sufficient exposure: SUS assumes users have interacted with the system enough to form judgments; first-impression ratings (1–2 minutes) are unreliable.
Frequently asked
Can I modify SUS items for my specific product or domain?
Modifying SUS reduces comparability to published norms and literature. If you must customize, keep the original 10 items intact and add domain-specific items as supplements (e.g., for medical software: 'Patient data entry was secure and private'). Score the original SUS unmodified, then analyze custom items separately. If your domain requires fundamentally different items (e.g., IoT device usability), consider building a custom scale validated for your context, rather than calling it 'SUS.'
What is the difference between SUS and the Single Ease Question (SEQ)?
SUS is 10 items, ~3 minutes; SEQ is 1 item ('How easy was this task?', 0–100 scale), <1 minute. SEQ correlates ~0.80 with SUS; they rank designs similarly but SEQ is less precise. Use SEQ for rapid feedback in fast-paced iteration (test 10 designs, pick top 3 via SEQ, then deep-dive with SUS). Use SUS for publication, benchmarking, or when precision is critical.
How many users do I need to administer SUS?
For design comparison (Design A vs. B), n=5–10 per design is often sufficient to detect meaningful differences (SUS differences >10 points). For publication or regulatory submission, n≥30 provides stable estimates. For longitudinal tracking (SUS measured monthly), continuous data collection with rolling averages (e.g., last 20 ratings) is practical. Sample size depends on expected effect size and statistical power desired; conduct a priori power analysis if doing formal hypothesis testing.
Can I use SUS for non-software (e.g., physical products, appliances)?
SUS is designed for interactive software but has been adapted for physical products and devices (e.g., 'This device is easy to use,' adjusted for context). However, the adaptation is non-standard; document changes explicitly. For physical product usability, dedicated instruments (System Usability Scale for Physical Products) may be more appropriate. When in doubt, use standard SUS for software, custom measures for non-software.
What if my SUS score is very high (85+)? Does that mean I don't need further usability work?
A high SUS indicates good perceived usability; it's a positive signal. However, perceived usability (SUS) and actual performance (task success, efficiency) may diverge. A system can have high SUS but still have issues: low efficiency (slow), poor task discoverability, or usability problems affecting experienced users more than novices. Pair SUS with task-based metrics (completion rate, error rate, task time) to get a fuller picture. Aim for both high SUS (70+) and high task-performance metrics (>95% completion, <2% errors).
Sources
- Brooke, J. (1986). System Usability Scale (SUS): A quick and dirty usability scale. In B. Weerdmeester & M. Evaluating the Usability of Human-Computer Interfaces (pp. 5-7). IOS Press. link ↗
- Lewis, J. R. (1995). IBM Computer Usability Satisfaction Questionnaires: Psychometric evaluation and recommendations. International Journal of Human-Computer Interaction, 7(1), 57–78. DOI: 10.1080/10447319509526110 ↗
How to cite this page
ScholarGate. (2026, June 3). Interface Usability Measure (IUM). ScholarGate. https://scholargate.app/en/human-factors/interface-usability-measure
Which method?
Set this method beside its closest kin and read them side by side — the library lays the books on the table; the choice is yours.
- Cognitive Load ScaleHuman Factors↔ compare
- NASA Task Load IndexHuman Factors↔ compare
- Operator Performance Assessment ScaleHuman Factors↔ compare
- User Experience QuestionnaireHuman Factors↔ compare