Single Ease Question (SEQ): Instant Task Difficulty Scores
The Single Ease Question is a 7-point post-task thermometer for perceived difficulty. Ask it immediately after a task attempt in usability tests. It correlates around r=.5 with completion and time, yet 14% of users rate failed tasks as easy.
WHY IT EXISTS: Usability testing generates behavioral data like task times and completion rates, but these do not capture the user's subjective experience. A task might be completed quickly yet feel confusing, or take a long time yet feel straightforward. Researchers needed a lightweight instrument to quantify perceived difficulty without the burden of complex questionnaires that disrupt testing flow.
THE MENTAL MODEL: Think of the SEQ as a thermometer you take immediately after physical activity. Just as heart rate captures exertion in the moment, the SEQ captures the user's perceived exertion immediately after a task. The memory is fresh, the rating is quick, and the result gives you a temperature check on task difficulty before the user forgets the friction they just felt.
HOW IT WORKS: Immediately after a user attempts a task, ask "Overall, how difficult or easy was the task to complete?" Provide a 7-point scale from 1 to 7, typically labeling only the endpoints as very difficult and very easy. The question can be delivered verbally, on paper, or in any survey software. While some practitioners label every point or remove numbers, research shows these variations matter far less than the recency of the task experience itself. Users are keenly aware of the nuances of their struggle or success and can express it reliably in a single number.
WHEN TO USE IT: Use the SEQ in moderated or unmoderated usability tests when you need a standardized difficulty metric across tasks, products, or iterations. It works across all technologies including mobile apps, websites, desktop software, and even paper prototypes. Because the historical average across thousands of tasks hovers around 5.5, you can compare your task average against this benchmark or your own longitudinal database. When a user rates a task below 5, follow up by asking why to capture immediate diagnostic context while the struggle is still salient.
WHEN NOT TO USE IT: Do not use the SEQ as a standalone replacement for behavioral metrics. It correlates around r equals 0.5 with task time and completion, meaning it overlaps with but does not replace them. Do not rely solely on top box scores because users calibrate rating scales differently; some users cluster at 6 and 7 while others use the full range. Also avoid treating the SEQ as a mechanical instrument like a thermometer; around 14 percent of users will rate a failed task as extremely easy, so expect noise in subjective data.
ONE CANONICAL EXAMPLE: A team testing a checkout flow administers the SEQ after each step. The payment step averages 3.2 while the confirmation step averages 6.1. The team digs into the low payment score and discovers users find the credit card form confusing. After redesigning the form labels, the average rises to 5.8 and completion improves, showing how the SEQ pinpoints friction and validates fixes across iterations.
Read the original → measuringu.com
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.