What it is
An inspection method where evaluators simulate a first-time user completing a task step by step, asking at each action whether a novice would know what to do and get useful feedback.
When to use it
During Prototype, especially for learnability of tasks aimed at new or infrequent users.
Why (value)
Focuses specifically on whether people can learn an interface by exploration, catching learnability gaps early.
How to run it
- Define the user profile and the task.
- List the correct action sequence.
- At each step ask the walkthrough questions about visibility, understanding, and feedback.
- Record where a novice would stall.
- Prioritize fixes to the sticking points.
Inputs and outputs
- Inputs: A task, the correct action path, evaluators.
- Outputs: Learnability problems located at specific steps.
Time and effort
Low. A focused session per task.
Evidence and limitations
Produces expert-review evidence about learnability, not direct-user data; evaluators approximate the novice and can miss or misjudge real behavior. See Evidence and limitations.
Tips and pitfalls
- Stay honest about what a true novice knows.
- Walk one task at a time.
- Confirm key findings with real users.
Variations
Streamlined cognitive walkthrough and group walkthroughs.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
- 18F Methods (US government, public domain).
Explore related methods
- Heuristic evaluation — Have evaluators inspect an interface against usability principles to catch problems fast.
- Expert review — Have an experienced UX practitioner assess a design and report likely problems and fixes.
- Task analysis — Break a goal into the concrete steps, sub-tasks, and decisions people perform to accomplish it.
