01 / UNDERSTAND
What is the Single Ease Question?
The Single Ease Question is a brief rating of how easy or difficult a task felt immediately after an attempt. A commonly used version has seven response points from very difficult to very easy, with higher values meaning easier. SEQ captures perceived task ease, including after unsuccessful attempts.
It complements Task Success Rate and Time on Task. It should not replace direct observation when completion can be checked, nor be described as a whole product usability score like System Usability Scale (SUS).
Why use Single Ease Question (SEQ)?
People can experience the same completion differently. One may struggle and eventually succeed; another may confidently stop at an incorrect result. A post task ease rating helps expose those mismatches. It is useful to a designer when it leads back to a specific point of difficulty or misunderstanding rather than becoming another undifferentiated satisfaction average.
When to use it
USE IT WHEN
Participants have just attempted a clearly defined task.
The team wants a repeatable task level ease signal.
Observed performance and perceived difficulty may disagree.
When to choose another method
Use System Usability Scale (SUS) for a broader post study usability assessment.
Use Customer Effort Score (CES) for a defined service interaction or request.
Use Task Success Rate to measure whether the goal was reached.
What you’ll need
Choose the exact SEQ version, wording and direction and keep it consistent. Ask immediately after each task before a discussion changes the participant’s appraisal. Store the task, rating and observed outcome together. Plan a neutral follow up separately and record missing ratings without silently treating them as ordinary scores.
What an SEQ observation contains
Keep the elements that help answer your question and support a decision.
The attempt the person is rating.
Consistent wording and endpoints.
Immediately after the attempt.
The selected value on the stated seven point scale.
Completion, assistance and duration recorded separately.
A neutral account of what made the task easy or difficult.
02 / PUT IT INTO PRACTICE
How to use the Single Ease Question
Keep evidence and assumptions distinct. Revisit your work when new information changes your understanding.
01
Prepare the task
Use a realistic goal and define completion before testing.
Move a repair visit without losing the current booking.
02
Select the instrument
Use a documented version of the question and scale rather than an improvised rewrite.
Keep higher values meaning easier across tasks.
03
Ask after the attempt
Collect the rating before discussing errors or teaching the intended route.
Ask even when the person did not finish.
04
Record the pairing
Store rating and performance under the same attempt identifier.
A rating of six may accompany an incorrect final state.
05
Follow up neutrally
Ask what influenced the rating without suggesting the task should have felt difficult.
What made that feel easy or difficult?
06
Inspect mismatches
Read individual ratings with outcomes before summarising a task.
High ease with failure deserves different attention from low ease with success.
07
Review comparable tasks
Report count, distribution and a declared summary under consistent conditions.
Do not claim a product wide score from one appointment task.
Example: an easy feeling task with a wrong result
Fictional scenario: three illustrative attempts receive ratings of six, three and five out of seven. The first participant stops at an unconfirmed change request but believes the replacement is booked. The second completes correctly after considerable searching. The third completes correctly without help.
The paired cards show rating and outcome together. The high rating beside failure is highlighted, while the low rating beside success points to another design problem. These are invented observations, not a benchmark sample.
The first intervention concerns false confidence. Clarify the difference between a request and a confirmed appointment. The second concerns navigation effort. Averaging the three ratings would conceal the distinction that actually guides the design decision.
03 / BELOW THE SURFACE
Below the surface: ease can be the feeling of not noticing an error
A smooth interaction is not necessarily a correctly understood one.
ATTEMPT
What task and outcome does the rating belong to?
Keep the pairing intact.
CONFIDENCE
Could ease reflect an unnoticed error?
Compare belief and actual state.
CHANGE
What kind of improvement produced a higher rating?
Distinguish effort reduction from missing feedback.
If feedback is incomplete, people may rate a task as easy because they believe they reached the goal. A higher ease score after simplifying confirmation could therefore coexist with more incorrect outcomes.
Pair the rating with a nonleading comprehension check where the task creates a promise. Ask what the person thinks will happen next, then verify the system state independently. Treat high ease with failure as evidence to investigate, not as a reason to dismiss the failure.
This editorial interpretation adds no new composite score. It preserves distinct measures so the team can see whether an improvement reduced work, corrected a misunderstanding or merely removed a visible warning. The same summary rating can hide any of those changes.
Single Ease Question (SEQ) companion worksheet
The original companion records a task, instrument version, rating and paired performance observations. Page two reviews mismatches and the next test. It does not reproduce or replace the established SEQ instrument and does not combine its rating with other metrics into a new score.
Practical tips
Collect the rating before discussing performance.
Keep unsuccessful attempts in the record.
Inspect individual mismatches before reading the average.
Common mistakes
Changing wording and treating versions as directly comparable.
Using SEQ as a whole product score.
Assuming a high rating proves successful completion.
What you’ll get
A task ease assessment connected to observed performance. Use the mismatch, where one exists, to select a precise change and verify both perception and outcome in a comparable retest.