Tip: Choose Save as PDF in the print dialog to download. Use A4 paper size.
Shade in the A or B circle for each question.
Draw a line connecting each item on the left to its match on the right.
| Left column | Right column | |
|---|---|---|
| 1observing | ALook for: pauses, wrong clicks, frowns | |
| 2Notes: 10:02 Mia pressed Back 3 times | BObserve = what they DO, Ask = what they SAY | |
| 3When observing, look for places where the user pauses, looks confused or makes a mistake | CWatching a user do a task to see where they get stuck, without helping or interrupting | |
| 4Observing shows what users really do, while asking only tells you what they say they do | DThis note is an opinion, not something you saw. Notes should record actions, like 'Mia could not find the Save button'. | |
| 5Observer: "Click the blue button, Sam!" | EThe observer helped the user. When observing you must not help or interrupt, or you will not see where they get stuck. | |
| 6Notes: Mia is bad at computers | FRecording what you saw, with a time and the exact action the user did |
Complete each line of code by filling in the missing parts.
Shade in the letter of the line that contains an error.
observing — Watching a user do a task to see where they get stuck, without helping or interrupting. You write down what you see instead of just asking them what they think.OBSERVE the user doing the taskIF user gets stuck THEN WRITE a noteWhile observing, do not help or interruptLook for where the user gets stuckObserving: see what users do, not just say