Look for an attempted task and an unresolved difficulty
Book reviews can help you discover where readers need more support, but the useful material is usually more specific than the rating. Look for what someone wanted to do, what they tried, where the book helped or fell short, and what remains unclear about their situation.
Keep those observations separate from your proposed solution. A reader asking for examples has not asked for an AI companion. A reader who disliked a book has not agreed to buy another product from its author.
Use reviews to choose a question worth investigating with readers. Then test whether a guided exercise addresses it. This guide provides a coding worksheet for that discovery work; it is not a process for collecting endorsements or increasing review counts.
Start with a narrow research question
Imagine a fictional author, Cedric, whose book helps neighborhood groups plan local history projects. He is considering a companion for turning a broad topic into a manageable research question.
He could search reviews for anything negative and produce a long list of features. Instead, he asks: where do readers struggle when narrowing the topic of a small project?
That question gives him a reason to include a review that discusses scope and exclude a comment about damaged packaging. It also keeps him from treating every criticism of a history book as a problem his method can solve.
Start with your own book and a small set of genuinely adjacent titles. Write down why each belongs: similar reader, task, or promise. A research manual for professional historians and a memoir for general readers may share a subject while serving very different purposes. Mixing their reviews without that distinction makes the resulting themes hard to interpret.
Record how you selected the material
Before coding, write a short collection note: which titles and editions you considered, where you looked, which languages you included, and how you selected reviews. Record the date you collected them and the review date when available.
If you choose a manageable batch, describe it as that. “Twenty recent reviews available on this page” is a transparent collection rule. “What readers think” implies a much broader view.
Include praise, mixed responses, and criticism. A positive review may describe the exact situation in which a method helped. A low rating may concern delivery, an audiobook narrator, or a mismatch with the book's advertised level. Neither rating alone identifies an application problem.
Preserve a direct source link and enough context to revisit each interpretation. Note disclosed free copies, review swaps, affiliations, or other incentives. Do not assume a missing disclosure proves there was none. Exclude material you cannot attribute or verify from quoted evidence, and do not treat an automated review summary as a reader's own account.
For public writing, use short necessary excerpts with attribution. Your research worksheet is not a reason to republish entire reviews or collect unrelated personal information.
Give each useful passage a descriptive label
Coding means attaching a label to a passage so you can compare related material. The UK government's guide to qualitative analysis includes user reviews among possible sources and explains that interpreting themes requires more than counting repeated words. It also notes that reviewers' questions and context are less under a researcher's control than in an interview.
For an initial author review, use simple labels close to the passage:
| Starting label | Include when the passage describes | Do not infer automatically |
|---|---|---|
| Cannot start | Difficulty choosing an initial action or input | The reader needs a chatbot. |
| Example does not fit | Trouble connecting an example to their circumstances | The whole method is invalid. |
| Missing decision rule | Uncertainty about choosing among options | More information will solve it. |
| Hard to locate | Difficulty finding a previously encountered step | A shorter book is necessarily better. |
| Prerequisite missing | A term or skill the reader needed but lacked | The reader did not pay attention. |
| Useful application | A described occasion when something helped | Everyone will get the same result. |
| Audience mismatch | Expectations or prior knowledge differ from the book's scope | The author should serve every audience. |
| Unclear | Insufficient detail to assign a useful interpretation | You should fill the gap with a guess. |
These are proposed starting labels, not a validated classification system. Add or revise labels when the actual material requires it. A passage may receive more than one label, and some reviews may contain no useful application evidence.
Read the full context before proposing a feature
In a discussion about nonfiction filler, u/davecopperfield wrote:
I sometimes take notes when I read a book and it really feels like looking for pieces of gold in the sand.
The post criticizes content the reader finds irrelevant, while acknowledging that stories and background can be useful. It also allows that the writer may have been choosing the wrong books. That context matters: the sentence describes frustration locating value, not a request to automate learning or evidence that all nonfiction is padded. Read the original post.
In a separate discussion about reading several books on the same topic, u/Cutivia wrote:
I try to change the angle, rather than just change the author.
They describe seeking a history, biography, academic treatment, opposing argument, or another discipline. Their response suggests a different possible explanation for repetition: the reader may want a new perspective rather than faster access to the same material. Read the original comment.
These are individual reading accounts, not reviews of Cedric's fictional book and not a representative sample. They show why similar surface language can lead to different research questions.
Use an evidence, interpretation, uncertainty worksheet
Create one row per relevant passage, with a source ID connecting it to your collection note. Do not merge several reviewers into a composite quotation.
The following entries are invented to demonstrate the worksheet for Cedric's project. They are not real reviews, findings, or customer statements.
| Illustrative review wording | Descriptive code | Possible interpretation | What remains unknown | Next research question |
|---|---|---|---|---|
| “I chose the history of the whole town and never got past collecting links.” | Cannot start; scope too broad | Reader may need help narrowing a topic | Whether the book already explains narrowing; whether the reader tried that section | How did you decide the first question to investigate? |
| “The archive examples were interesting, but I only have access to family papers.” | Example does not fit | Available materials may shape a different project | Whether family materials are sufficient for their intended claim | What could you examine without requesting more access? |
| “I returned to the question checklist when our project started expanding.” | Useful application; scope review | A repeatable check may help during a project | What changed after using it | Which question led you to keep or remove work? |
| “I wanted local stories, not a guide to doing research.” | Audience mismatch | Reader expected narrative rather than instruction | Whether the cover or description created that expectation | Would clearer positioning have prevented the mismatch? |
The first row suggests a candidate exercise: move from a large subject to one answerable question. The fourth may suggest a change to the book description instead. It would be a mistake to put both into a backlog titled “AI features readers need.”
Keep the uncertainty column even when the interpretation feels obvious. It is the part of the worksheet that tells you what to ask next.
Separate the reader's account from your conclusion
GOV.UK's research analysis guidance separates observations, findings, and actions. That is a useful discipline when reading reviews too: preserve what someone said before deciding what it means and what you should do.
Ask another person to inspect a few rows, if available. Give them the original passages as well as your labels. Ask where your interpretation goes beyond the evidence, whether a different code fits, and what you have ignored because it challenges your preferred product idea.
Look especially for counterexamples. If some readers find the question checklist useful and others cannot start, the problem may involve finding or understanding the checklist rather than needing an entirely new method. If experienced readers find a section repetitive while beginners praise it, an optional path may be worth investigating. Neither pattern automatically dictates a solution.
Count carefully if counts help you organize the work. Four passages from one reviewer are four passages, not four independent people. A review copied onto several sites is not several independent accounts. A percentage within a convenience sample describes that sample; it does not establish the share of all readers facing the problem.
Choose one companion hypothesis
Cedric can now write a bounded proposal:
For readers who have a local-history topic and a limited set of available materials, a short guided exercise may help them produce one research question they can begin investigating.
That is a hypothesis. It is more useful than “readers want an AI historian” because it names the situation, input, and output without claiming demand or success.
His next step is to ask suitable readers about a recent attempt to narrow a project, then try the exercise on a safe example. The companion should not claim that accessible evidence is complete or that a plausible account is historically established. Its output can include gaps and a question that cannot yet be answered.
Write down what would change your mind. If readers can already narrow projects easily but struggle to access records, this exercise may address the wrong bottleneck. If they want an engaging narrative rather than a research process, they may not be the intended audience. Choosing not to build is a legitimate research result.
Preserve the trail from review to test
The final research note should contain the collection rule, source links, coded passages, competing interpretations, and the one task you will investigate next. Keep evidence from your own book separate from adjacent-title evidence so you know whose readers you are describing.
When the task is concrete, use how to write an agent skill to turn the proposed exercise into instructions and output checks. Reviews have helped you choose the question; an actual trial must still establish whether your answer helps.
If that work points to a companion grounded in your method, visit Skillfully and choose Book onboarding. Bring the task and evidence, including the uncertainty that the first version needs to resolve.