Value Metric
UX-Lite
UX-Lite is a short, two-item standardized questionnaire measuring perceived usefulness and ease of use.
What is UX-Lite?
UX-Lite is a compact, standardized questionnaire that captures the two dimensions most predictive of adoption: perceived usefulness and perceived ease of use. With just two items, it is fast enough to embed in-product yet validated enough to benchmark, converting responses to a 0–100 score.
It draws on the classic Technology Acceptance Model idea that usefulness and ease of use together drive whether people adopt a product — and packages it into a survey light enough for continuous measurement.
How to calculate it
UX-Lite = Standardized average of the usefulness and ease-of-use items, scaled 0–100
- Usefulness item
- Agreement that the product is useful
- Ease-of-use item
- Agreement that the product is easy to use
Worked example
Average the two item responses and convert to the 0–100 scale using the published scoring; higher scores indicate a stronger perceived experience.
What good looks like
- Standardized 0–100Benchmarkable
Like SUS, UX-Lite is standardized so scores can be compared to norms and tracked over releases.
Source: MeasuringU (Jeff Sauro)
Why it matters
UX-Lite’s brevity is its power: two questions are short enough to ask often and in-context, giving a continuous pulse on perceived usefulness and ease without survey fatigue. Splitting the two dimensions is also diagnostic — a product can be easy but not useful, or useful but hard, and the fix differs.
How to improve UX-Lite
Diagnose usefulness vs. ease separately
Use the two sub-scores to tell whether to invest in value (usefulness) or in reducing friction (ease).
Fix ease problems with usability testing
When ease lags, run task-based usability sessions to find and remove the specific friction.
Frequently asked questions
How is UX-Lite different from SUS?
SUS uses 10 items to measure perceived usability. UX-Lite uses just two items to capture perceived usefulness and ease of use, making it faster to deploy and better suited to frequent, in-product measurement — at the cost of the detail a longer instrument provides.
Why measure usefulness and ease of use separately?
Because they fail independently. A product can be easy to use but not useful (people understand it but do not need it) or useful but hard (valuable but frustrating). Separating the two tells you whether to improve value or reduce friction.