Handle contradictory feedback from readers of your method

When readers give opposite feedback about your method, first check whether they attempted the same task, with the same instructions, under comparable conditions. Then separate what happened from what each reader wants you to change.

“Explain more” and “make it shorter” may describe different levels of experience. They may also point to the same problem: readers cannot find the instruction they need. A vote between those two suggestions would miss the distinction.

Keep the book's intended outcome in view, but do not use “not my target reader” to dismiss an inconvenient report. A person outside your core audience can still identify a factual error, an unclear instruction, or an accessibility problem.

The matrix below is a proposed author decision tool. The worked reports are fictional, not collected reader feedback or results from a Skillfully companion.

A writer describes the familiar dilemma:

“I’ve received some conflicting feedback about the same thing between beta readers. Some like this particular thing and others don’t.”

— u/JBark1990, discussing beta-reader feedback

The thread later identifies a fiction-formatting preference. A practical method needs additional scrutiny: disagreement about presentation is different from a report that someone could not complete the promised task.

Suppose your book teaches volunteer coordinators to prepare a short orientation checklist. Three fictional reports arrive about its AI companion:

The first two reports may support optional explanations with a direct route for experienced readers. The third concerns missing operational information. It should not disappear into an average preference for shorter or longer text.

For each report, preserve the instruction version, the attempted task, the relevant context, and the place where the difficulty occurred. Ask the reader to point to what they saw rather than making them defend their opinion.

A useful follow-up is:

Which part prevented you from doing what you intended? What did you expect to be able to do at that point?

For the fictional novice, the answer might identify one undefined term. For the experienced coordinator, it might reveal that the companion repeats all definitions before every new checklist. Those problems can coexist without either reader being wrong.

GOV.UK's guidance on user needs recommends grounding needs in research evidence and describing the problem rather than a preferred solution. Applied here, “understand who is responsible” is a need; “add three paragraphs” is one proposed way to address it.

Record each report separately before grouping it with others:

Reader's relevant experience and situation:
Task and instruction version:
What happened:
Evidence available:
Requested change:

Possible category:
- Missing or incorrect information
- Difficulty completing the intended task
- Different context or prerequisite
- Presentation preference
- Not enough evidence yet

Author decision:
Reason and remaining uncertainty:
Next check:

These are working categories, not permanent labels for people. A request that initially looks like a preference can reveal a genuine barrier once you inspect the task. Equally, a strongly worded criticism may offer little information about what happened.

Do not assign credibility through confidence, status, or agreement with your own taste. A specific, reproducible omission deserves attention even if only one person reports it. Several vague approvals do not cancel it out.

In the fictional example, keep the responsibility check in every route. Offer the definition and an example when needed, and provide a concise route for someone who can already complete the task. Those are proposed presentation changes around a shared requirement.

The author should then check both paths. Can a novice identify the responsible person? Can an experienced coordinator complete the checklist without repeated explanations? Does either path omit unresolved questions?

Do not declare the conflict resolved just because both readers like the revised wording. Their ability to complete the relevant task is a separate check.

A writer moving from academic nonfiction into fiction describes a similar surface disagreement:

“I occasionally run across contradictory feedback, especially on the issue of when something does or does not need to be explained.”

— u/4EverWriting, discussing contradictory feedback

That report concerns a novel, where explanation also serves artistic choices. It is not evidence for how a procedural companion should behave. It does show why “more explanation” is too broad a change request to implement without understanding the particular reader experience.

Some disagreements cannot be solved with optional detail. One reader may want your method to prioritize speed while another wants it to explore every alternative. If the method has a deliberate tradeoff, explain it and its intended conditions.

For example, the volunteer checklist might cover preparing an initial orientation, while a reader requests a complete organizational training system. That request may be valuable, but it changes the scope. Record it as a different need rather than expanding the companion until its original task becomes difficult to finish.

Sometimes the right decision is to revise the method itself. If the checklist repeatedly leaves readers unable to identify responsibility, better presentation may not be sufficient. Investigate the missing decision rather than repeatedly repackaging the same instruction.

Finish the review with a short decision note: what evidence you considered, what you changed, what you retained, and what a new attempt needs to show. Include unresolved disagreement instead of implying consensus.

For the fictional case, the note might propose optional definitions, retain the responsibility requirement, and add an explicit unresolved-question check. None is a demonstrated improvement until examined through further use.

Use the skill-testing guide to check that the proposed routes preserve your rules. Follow that with appropriate reader review of the actual task. Instruction compliance and reader usefulness answer different questions.

To work through conflicting feedback on your own book companion, visit Skillfully and choose Book onboarding. Bring two contrasting reports and the exact instruction they concern. The disagreement can become a focused design question once its context is visible.