Marcus Andrey Study
Ler em português Library

Framework · Measurement · 2 min read

UMUX-Lite

A 2-item usability questionnaire (usefulness and ease) that correlates with SUS and is light enough for frequent in-app surveys.

1Usefulness

"This system's capabilities meet my requirements."

1 Strongly disagree to 7 Strongly agree
2Ease

"This system is easy to use."

1 Strongly disagree to 7 Strongly agree
%Score

Rescale to 0–100, then optionally convert to a SUS-like score.

Compare with SUS average of 68

UMUX-Lite = (item 1 + item 2 − 2) × 100 ÷ 12 · SUS-like = 0.65 × UMUX-Lite + 22.9

UMUX-Lite asks two 7-point questions, usefulness and ease, and rescales them to a 0–100 score close to SUS.

Use it when

  • You want a frequent pulse check on an app, for example after each release, and a 10-item SUS is too long.
  • You want a usability score inside the app itself, shown to users at a natural pause.
  • You need a Happiness metric for a HEART framework table across several apps.

How to use it

  1. Use the two standard items. Item 1: "This system's capabilities meet my requirements." Item 2: "This system is easy to use." Replace "this system" with the app name if you like. Use a 7-point scale from 1 = Strongly disagree to 7 = Strongly agree. Output: a two-question survey.
  2. Choose when to ask. Show it in the app after people have done real work, not on first login. Keep the timing the same every round. Output: a trigger rule, such as "after the 5th completed booking".
  3. Score each response. UMUX-Lite = (item 1 + item 2 − 2) × 100 ÷ 12. This gives 0–100. Then average across respondents. Output: one UMUX-Lite score per app.
  4. Convert to a SUS-like score if you need comparison. Lewis, Utesch and Maher published a regression: SUS-like score = 0.65 × UMUX-Lite + 22.9. Use it to compare with SUS data such as the average of about 68. Check MeasuringU for current guidance, then use the same method every round. Output: a score you can set next to SUS results.
  5. Add one open question. Ask "What is the one thing we should improve?" so the score has a reason. Output: comments grouped by theme.

Worked example

An internal operations platform runs UMUX-Lite in its booking tool after each quarterly release (fictional data).

Item 1 (capabilities) Item 2 (ease) UMUX-Lite SUS-like
One response 6 5 (6 + 5 − 2) × 100 ÷ 12 = 75 0.65 × 75 + 22.9 ≈ 71.7

The app average over 140 responses is the number the team tracks from release to release, next to the open comments.

Watch out for

  • Changing the wording or scale. Any change breaks the link to SUS and to published data.
  • Mixing raw and converted scores. Decide whether you report the raw UMUX-Lite or the SUS-like score, label it, and don't switch.
  • Asking too often. Showing the survey to the same people every week causes fatigue and bias. Limit how often each user sees it.
  • Expecting a diagnosis. Two items show the trend, not the cause. Follow up with research on low scores.

Template

Copy this into your in-app survey tool.

[App name]'s capabilities meet my requirements.
Strongly disagree  1   2   3   4   5   6   7  Strongly agree

[App name] is easy to use.
Strongly disagree  1   2   3   4   5   6   7  Strongly agree

What is the one thing we should improve? (optional)
->

UMUX-Lite = (item 1 + item 2 - 2) x 100 / 12
SUS-like  = 0.65 x UMUX-Lite + 22.9
Source
Lewis, Utesch & Maher (2013)
Related
SUS · SEQ

"See on Amazon" links are affiliate links. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close