Reconstruct one attempt before asking for an opinion
After a reader tries your method, ask about a specific occasion: what was happening, what they attempted, what they produced, and what happened next. Use the output as a reference if they are comfortable sharing it. Ask what remained difficult as carefully as you ask what helped.
A post-use interview can reveal how your book or companion fits into someone's work. It is not, by itself, proof that the method caused an improvement. Keep the reader's account, anything you can inspect, and your interpretation separate.
The script below is designed for a deeper conversation after an attempt. It complements brief feedback collected during use; it does not replace watching someone work when your question is about what they actually do.
Ask about the path from reading to doing
In a discussion about applying nonfiction, u/Ordinary-Screen679 wrote:
Most of the books I've applied weren't the ones I expected to apply.
The reader was asking what happened between finishing a book and making a change. This is a personal observation, not a finding about how often books work. It is a useful reminder to ask about the route to application rather than assuming enthusiasm predicts it. Read the original post.
Your reader may have returned to a chapter weeks later, used only one question, or combined the method with advice from someone else. Those details matter. If you ask only whether they liked the companion, you may never hear them.
GOV.UK's in-depth interview guidance recommends concrete stories and examples, open questions, and a discussion guide flexible enough to follow relevant details. The following script applies that approach to an author's method.
Prepare the conversation
Invite people with different experiences of the trial, including those who stopped, skipped steps, or chose not to use the output. A set of interviews with only satisfied completers cannot explain why others left.
Ask the participant to choose one recent attempt they remember. They may bring a safe excerpt, a blank version of their worksheet, or simply a description. Do not make sharing private work a condition of being heard.
Explain the purpose, approximate length, observers, recording arrangements, and how notes will be used. Make participation optional and keep compensation independent of their opinion. Permission to discuss a draft is not permission to publish it or turn their words into a testimonial.
Prepare enough time to follow the important episode without rushing through every question. Try the script once before the first research interview to catch unclear wording. This is a conversation guide, not a questionnaire that must be completed in order.
The post-use interview script
Start with this original introduction:
I'd like to understand one occasion when you tried the exercise, including anything you skipped or found unhelpful. I'm interested in what happened, not in a positive review. You can decline a question or stop whenever you want. Please leave out confidential details.
Then work through the following sequence. Ask follow-ups only when they help clarify the participant's own account.
| Stage | Opening question | Possible follow-up |
|---|---|---|
| Situation | What were you trying to do on that occasion? | What made it worth dealing with then? |
| Previous approach | How had you approached this kind of task before? | Was anything different this time? |
| Starting point | What led you to try this exercise? | Had you read or used any part of it before? |
| Attempt | Take me through what you did first and what happened next. | Where did you pause, skip, repeat, or change something? |
| Other help | What else did you use while working on it? | Did another person, tool, or resource contribute? |
| Artifact | What did you end up with, if anything? | Is there a safe part you would like to show or describe? |
| Use afterward | What happened to that output afterward? | Did you use it, revise it, set it aside, or do something else? |
| Consequence | What, if anything, was different after the attempt? | What makes you connect that difference to this exercise? |
| Limits | What did the exercise leave unresolved? | Where did it ask for something you could not supply? |
| Closing | What have I misunderstood or not asked about? | May I contact you to clarify a point, if needed? |
“If anything” is intentional. The wording should leave room for no artifact, no improvement, or a useful decision to stop.
If the participant says the exercise was excellent, ask which part they used. If they say it was useless, ask where the attempt ended. Neither answer requires you to agree or defend the method; both deserve a concrete follow-up.
Work through an example without inventing a success story
Imagine a fictional author, Farah, whose book helps volunteers write clearer handover notes. A reader tried a companion to prepare a handover for a community radio shift.
For demonstration, suppose the reader reports that the exercise helped them list unfinished work, but the next volunteer still called with questions. These are invented details for showing how the script works, not interview findings.
Farah should ask what the questions were before assuming the handover failed. Perhaps the note omitted a deadline. Perhaps a new problem arose after it was written. Perhaps the next volunteer never received the note.
The distinction changes the next design decision. An omitted deadline might justify a better prompt. A delivery problem might call for a clearer handoff step. A new situation might be outside the method's scope.
Her working record could look like this:
| Evidence type | Illustrative entry |
|---|---|
| Reader's account | The next volunteer asked when an unfinished task was due. |
| Artifact inspected, if shared | The note lists the task but contains no deadline or unknown-deadline marker. |
| Other influences | The reader also used an older shift checklist. |
| Interpretation | The exercise may not make time constraints visible enough. |
| Uncertainty | We do not know whether a clearer prompt would have changed this handover. |
| Next check | Try a revised time-constraint prompt on a new suitable handover task. |
Even with a shared artifact, Farah has not established that her method reduces calls or improves volunteer performance. She has identified a specific possible weakness worth testing.
Keep memory and measurement distinct
People may not remember the order of every action. Do not force precision they cannot supply. Mark an approximate sequence as approximate, and use a saved artifact or agreed session record to clarify it where available.
Nielsen Norman Group's interview guide distinguishes reported behavior from observed behavior and discusses memory and social-desirability limits. A reader's recollection is valuable evidence of their experience; it should not silently become a verified event log.
Likewise, a small qualitative interview set can reveal different views without establishing their prevalence. That limitation is explicit in the UK government's qualitative interview study guidance. Avoid turning three similar accounts into “most readers” unless you have a sampling and measurement design that supports the claim.
Finish with a decision you can defend
After each interview, write a short summary while the context is fresh: the attempted task, the output, what happened afterward, the evidence available, and the next question. Preserve a counterexample that challenges your preferred explanation.
Across interviews, group similar obstacles without losing their contexts. Two readers who did not use an output may have very different reasons. One found it unhelpful; another discovered they no longer needed to do the task.
When a pattern suggests a revision, turn it into a concrete change and a new check. The guide to measuring agent skill quality can help you define what the revised output should demonstrate.
If those interviews have clarified a reader task you want to support through a skill, visit Skillfully and choose Book onboarding. Bring the method and a safe example of what readers are trying to accomplish.