How do I test whether readers can follow written instructions without coaching them?
Quick answer
Give a reader the draft and one realistic task, then ask them to work through it as they normally would. Stay quiet while they read; note pauses, rereading, unexpected interpretations, and questions without explaining what the text means. If they get stuck, ask what they expected or what they would look for next. Record what happened separately from your interpretation, then use the notes to find passages worth revising—not to claim a formal result.
The question, the details, the next step.
I have a set of written instructions and want to know whether a reader can follow them. How do I try this without accidentally guiding them?
Treat it as an informal walkthrough: your aim is to notice how someone encounters the draft, not to teach it or score them. Choose a task that matches what the instructions are for, and give the reader the draft in the form they would normally use. For example, if it explains how to submit a community event notice, ask the reader to use it to prepare a notice—not simply to read it and say whether it seems clear.
Before starting, say something like: “I’m reviewing these instructions, not testing you. Please work through them as you normally would. I’ll try not to help, but you can tell me what you’re thinking.” Make clear they may pause or stop. Avoid explaining the intended meaning of a step.
What should I do while they work? If they stop, it feels rude to just watch.
Give them time to reread or think. Quiet observation can feel awkward, but jumping in with “You need to click the second option” changes what you are observing. Note the location in the draft and what you saw: a long pause, a reread, a question, or an action that did not match the instruction.
If they seem stuck, use a neutral prompt such as “What are you looking for?” or “What would you do next?” Avoid prompts that contain the answer, such as “Did you notice the note at the bottom?” If they ask you what a sentence means, you can say, “What does it mean to you as written?” If they still cannot proceed, offer to move on; record that the task paused rather than coaching them through it.
How do I take useful notes instead of writing down a vague judgment like ‘this section is confusing’?
Separate the observation from your interpretation. Capture the step or wording involved, what the reader did or said, and what question you want to investigate. Use the reader’s words where helpful, but do not turn a single person’s reaction into a general claim about all readers.
A short observation sheet could look like this:
- Task: Prepare a sample event notice using the draft.
- Draft location: “Choose a contact method.”
- What I observed: Reader reread the step, then asked whether a phone number was required.
- Reader’s words: “Do I have to include both?”
- Possible issue to review: The instruction does not say whether one method is enough.
- Follow-up: Check whether the next sentence or an example resolves this.
The possible issue is a hypothesis, not a finding. Keep it visibly separate from what you actually observed.
Should I ask questions afterward, and how do I use the notes without overclaiming?
Yes. After the task, ask open questions about specific moments: “What did you expect that step to tell you?” or “Was there anything you had to guess?” You can also ask which instruction they would change first and why. Avoid asking whether the draft was “easy” or leading them toward a particular criticism; general praise may not explain what happened during the task.
Review the notes for recurring trouble spots, but keep the scope honest. If one reader hesitated at a phrase, you can say that the reader hesitated in this walkthrough—not that readers generally fail there. Decide whether the passage can be made more explicit, then invite another reader to try the revised version if useful. This informal exercise helps identify questions to investigate; it does not establish a success rate or prove that the instructions work for every audience.
A practical checklist
Choose one realistic task that the written instructions are meant to support.
Explain that you are reviewing the draft, not evaluating the reader, and avoid teaching the steps.
Use neutral prompts only when needed; do not include the answer in the prompt.
Record the passage, observable behavior, and reader’s words separately from your interpretation.
Afterward, ask open questions about specific moments of hesitation or uncertainty.
Describe the notes as observations from this walkthrough, not formal test results or claims about all readers.
A few more useful answers
What if the reader asks me directly what a step means?
Ask what they understand it to mean as written. If they still cannot continue, offer to move on and note the point where they needed help rather than explaining the step.
How many readers do I need for an informal walkthrough?
There is no required number for this kind of editorial review. Be clear about how many people tried the draft and treat each session as a source of observations, not a representative measurement.
Can I ask readers to think aloud?
You can invite them to say what they are looking for or expecting, while noting that talking may change how they work. If they prefer to read quietly, observe pauses and ask about those moments afterward.