Marcus Andrey Study
Ler em português Library

Framework · Measurement · 2 min read

SEQ

The Single Ease Question: one 7-point question asked right after each task ("How difficult or easy was the task?"), so you can compare tasks cheaply in any test.

QQuestion

One question, same wording every time.

"Overall, how difficult or easy was the task to complete?"
7Scale

Seven points, from 1 Very difficult to 7 Very easy.

Higher is better
TTiming

Ask right after each task, while the memory is fresh.

Not at the end of the session
WWhy

On low scores, ask what made it hard.

"What made it difficult?"
The Single Ease Question is one 7-point question asked after each task, with a follow-up on low scores.

Use it when

  • You run any usability test and want a cheap, standard number per task.
  • You need to find which of several tasks feels hardest to users.
  • You are setting up a UX benchmarking baseline and want a perceived-ease measure next to success and time.

How to use it

  1. Use the standard wording and scale. Ask "Overall, how difficult or easy was the task to complete?" on a 7-point scale labelled 1 = Very difficult and 7 = Very easy. Don't change the wording between rounds. Output: one fixed question in your test script.
  2. Ask it right after each task. Ask before the next task starts, while the experience is fresh, in moderated or unmoderated tests. Output: one score per participant per task.
  3. Ask why on low scores. When someone answers low, ask "What made it difficult?" and note the answer. Output: reasons attached to low scores.
  4. Report the mean per task. Calculate the average score per task and compare tasks with each other and with your last round. MeasuringU's published data puts the average SEQ across many tasks at about 5.5, which you can use as a rough reference. Output: a per-task SEQ table.
  5. Read it with task success. A task can feel easy and still fail. Always show SEQ next to success and time. Output: SEQ in the same table as Task success and time on task.

Worked example

A benchmark test of three tasks on an internal operations platform, 8 participants (fictional data).

Task Success SEQ (mean, 1–7) Common reason for low scores
Create a booking 8 / 8 6.3 —
Correct a customs code 5 / 8 3.9 "I couldn't find where to edit the code."
Export a monthly report 7 / 8 5.1 "Too many filters before export."

The customs task is clearly the hardest, and the "why" answers point to a findability problem, not a form problem.

Watch out for

  • Changing the wording or scale. A 5-point version or new wording breaks comparison with past rounds and with published data.
  • Asking only at the end. Asked after the session, people mix up tasks. Ask after each task.
  • SEQ as a product score. Averaging SEQ across all tasks hides the hard ones. Report per task.
  • Skipping the follow-up. A low number without a reason doesn't tell you what to fix.

Template

Copy this into your test script after each task.

Task [n]: ________________________

Overall, how difficult or easy was the task to complete?

Very difficult  1   2   3   4   5   6   7  Very easy

If 1-4: What made it difficult?
->
Source
MeasuringU (Jeff Sauro; Sauro & Dumas, 2009)

"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