# Walk through the task as a first-time user

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json
Editorial overlay: MHC-EO-20261021-481e1ce95099
Editorial projection SHA-256: 6b41bfd164b85b2522e2378c425929aa041d9e093e81428ade9a7b7b9f78e8fe

---

## Walk through the task as a first-time user

ID: MHC-D-RESEARCH-1090 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/walk-through-the-task-as-a-first-time-user

Knowing where the button is can hide how hard it is to find.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- You need to inspect a new flow before arranging user sessions.

### Avoid when

- An expert imagining a newcomer is still an expert. Test important assumptions with representative users.

### Explanation

Write the task and the actions required. At each action, inspect what a newcomer would need to know and what the interface actually reveals. Record possible failures as hypotheses, not as user research results.

### Steps

1. Ask whether the user would form this immediate goal and notice the available action.
2. Ask whether the label connects the action to the goal and the result makes progress clear.
3. Record the missing cue and a change or user test that could examine it.

### Example

A training app offers Start baseline, but nothing explains that this creates a recording. The walkthrough flags the unexplained term.

### Check

Can each predicted difficulty be traced to a particular step and missing piece of information?

### Limits

- An expert imagining a newcomer is still an expert. Test important assumptions with representative users.

### Evidence and sources

- supports: A cognitive walkthrough inspects whether a new user would form the relevant goal, notice an action, connect it to the goal and recognise progress. — RS-9494823B724BD182. Inspectors predict difficulties; a walkthrough does not observe users succeeding. (Four questions for each action.)
- RS-9494823B724BD182: Evaluate Interface Learnability with Cognitive Walkthroughs — https://www.nngroup.com/articles/cognitive-walkthroughs/

### Vedokrok editorial review

Can a new user see the next move?

A cognitive walkthrough can expose where a first-time user loses the connection between a goal, the right action and visible progress. It is much weaker as a substitute for observing real users.

#### Turn a vague review into a task-level inspection

Teams know what their own interface means. A new user does not. A cognitive walkthrough makes that gap inspectable by following one concrete task and asking what a newcomer would need at each step: would they form the immediate goal, notice the available action, connect the label to the goal and recognise progress after acting? This structure can turn “the navigation is confusing” into a reviewable hypothesis. For example, a first-time user who wants a CSV report may see only a control called Share and receive no clear export confirmation. The finding now points to two specific risks: the action may not be associated with the goal, and the result may not confirm progress.

#### Use the method early, but name the instrument

The original method was designed around learnability in walk-up-and-use interfaces. Modern practice applies the same task-based logic to prototypes and product flows, where it can reveal missing cues before a broader study is practical. The reviewer remains part of the measuring instrument. Reviewers choose the task, assume what the user already knows and judge what that user is likely to notice or understand. Those judgments are useful design hypotheses, not observations of representative users. Record the assumed user knowledge, the exact step and the missing cue so a later change or user session can test the prediction.

#### Do not turn one method comparison into a universal ranking

A real-world comparison of heuristic evaluation, guidelines, cognitive walkthroughs and usability testing found different strengths and costs across the four approaches. In that study, the walkthrough helped define user goals and assumptions but was tedious and missed some general or recurring problems. A later methodological review warned that design choices in influential method-comparison experiments weakened simple claims about which usability-evaluation method is generally superior. The practical conclusion is not that walkthroughs fail. It is that the method answers a narrower question about first-use learnability, while other methods may be better for observed behaviour, broad interface coverage or recurring problems.

#### Start with the primary route, then expand by consequence

The main successful route is an efficient first pass: can a plausible newcomer move from the starting state to the intended result without insider knowledge? If that route already breaks, the team has a concrete place to improve. A clean happy path says little about error recovery, alternate routes, accessibility needs, interruptions or behaviour under real conditions. Add those cases when they are common or consequential. Sensitive, safety-critical or hard-to-reverse flows need stronger usability or professional review; confidence from an internal walkthrough is not enough.

#### Keep walkthrough findings in their proper evidence class

A cognitive walkthrough is an inspection, not a user test. It differs from heuristic evaluation because it follows a specific task step by step and concentrates on first-use learnability, while heuristic evaluation checks a broader interface against general usability principles. The methods can complement each other, but neither makes the other redundant. Treat every walkthrough result as a reviewer-generated hypothesis. When a decision depends on what representative users actually notice, misunderstand, avoid or recover from, direct observation provides the stronger evidence.

**Editorial takeaway:** Use a cognitive walkthrough to locate a first-time user's action-and-feedback breaks before broad testing. Tie every finding to one task step, an assumed piece of user knowledge and a missing cue. Then treat the result as a hypothesis about learnability, not as observed user evidence or proof that the whole interface works.

#### Editorial evidence

- supports: The original cognitive-walkthrough paper presents a theoretically structured, question-based evaluation of individual interface actions for walk-up-and-use systems. — UI-PAPER-1990-COGNITIVE-WALKTHROUGH. This supports a task-level inspection of goals, actions and visible progress. It does not turn reviewer predictions into observed user behaviour. (Method description and walkthrough form)
- contextualizes: A real-world study compared heuristic evaluation, software guidelines, cognitive walkthroughs and usability testing on one pre-release interface and reported different advantages and disadvantages for the methods. — UI-PAPER-1991-REAL-WORLD-COMPARISON. The walkthrough helped define user goals and assumptions in this study, but it was also described as tedious and missed some general and recurring problems. One product evaluation does not establish a universal method ranking. (Abstract; Table 6 and Discussion)
- limits: Work applying cognitive walkthroughs to more complex interfaces reported practical issues and recommendations for using the method beyond simple walk-up-and-use systems. — UI-PAPER-1992-COMPLEX-WALKTHROUGHS. This supports preserving task selection, evaluator assumptions and interpretation as part of the method rather than treating a walkthrough as an automatic usability score. (Case study and recommendations)
- challenges: A methodological review of experiments comparing usability-evaluation methods argued that experimental-design choices can substantially weaken the conclusions drawn from those comparisons. — UI-REVIEW-1998-DAMAGED-MERCHANDISE. This challenges broad superiority claims across usability methods. It does not show that cognitive walkthroughs have no value for their narrower learnability question. (Abstract and review conclusions)
- contextualizes: Current practitioner guidance defines a cognitive walkthrough as a task-based inspection of learnability performed by reviewers rather than users and recommends combining it with other evaluation methods. — UI-GUIDE-2022-NNG-WALKTHROUGH. This is practical method guidance, not comparative efficacy evidence. Its distinction between reviewer inspection and user testing supports the editorial boundary used here. (Defining Cognitive Walkthroughs; When Should a Cognitive Walkthrough Be Conducted?)
- UI-PAPER-1990-COGNITIVE-WALKTHROUGH: Testing a walkthrough methodology for theory-based design of walk-up-and-use interfaces — https://doi.org/10.1145/97243.97279 — Clayton Lewis, Peter G. Polson, Cathleen Wharton, John Rieman
- UI-PAPER-1991-REAL-WORLD-COMPARISON: User interface evaluation in the real world: a comparison of four techniques — https://doi.org/10.1145/108844.108862 — Robin Jeffries, James R. Miller, Cathleen Wharton, Kathy Uyeda
- UI-PAPER-1992-COMPLEX-WALKTHROUGHS: Applying cognitive walkthroughs to more complex user interfaces — https://doi.org/10.1145/142750.142864 — Cathleen Wharton, John Rieman, Clayton Lewis, Peter Polson
- UI-REVIEW-1998-DAMAGED-MERCHANDISE: Damaged Merchandise? A Review of Experiments That Compare Usability Evaluation Methods — https://doi.org/10.1207/s15327051hci1303_2 — Wayne D. Gray, Marilyn C. Salzman
- UI-GUIDE-2022-NNG-WALKTHROUGH: Evaluate Interface Learnability with Cognitive Walkthroughs — https://www.nngroup.com/articles/cognitive-walkthroughs/ — Kim Flaherty

Editorial version: 2.0.0 · evidence checked 2026-09-27 · Agent editorial review; not human or expert certification.

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/give-the-user-a-goal-and-keep-your-instructions-out-of-the-result
