Build a reader advisory group without turning it into a fan club

A reader advisory group should help you understand how people use your method, where they struggle, and what assumptions need checking. Give it a defined task and a limited commitment. Ask for concrete accounts before inviting general opinions about your work.

Loyal readers can make useful advisers. Their enthusiasm becomes a problem when admiration substitutes for evidence, or when participants believe criticism might cost them access to the author. Make the group's purpose and the author's responsibilities explicit from the start.

For an author AI companion, a useful question might be: “Can readers apply the chapter's selection criteria to choose a manageable local-history project?” That is more actionable than asking whether they love the companion or what features they want next.

The charter and session below are an original proposed design. The local-history examples are fictional; no advisory group has been recruited or studied for this article.

Write a short invitation that describes the work, the expected time, and what will happen to the findings. Avoid presenting membership as a reward for supporting the book. A reader who reports that the method was unhelpful should still have fulfilled their role.

A writer asking about friends' feedback puts the concern plainly:

“So, what can I do to help my friends give me honest feedback on my writing?”

— u/MoonInAries17, discussing feedback from family and friends

The post concerns writing critique, not a product advisory panel. It identifies a relationship question worth addressing directly: what does the author do to make criticism welcome?

Your invitation could say:

We are examining whether this companion helps with one task from the book. Reporting confusion, disagreement, or a reason you stopped is useful. Participation does not require a positive review, recommendation, purchase, or public endorsement. You can decline any activity or leave the group.

That is proposed invitation language, not a statement about an existing Skillfully program. Set any compensation in advance and tie it to the agreed participation, not the tone of the feedback.

Adapt this charter to one research period:

Purpose: Understand how readers attempt [specific task].
Question for this period: [One uncertainty about the method].
Term: [Start, end, and optional renewal].
Commitment: [Preparation, sessions, and follow-up time].
Participation: Voluntary; activities may be declined.
Compensation: [Amount or benefit, unrelated to positive feedback].

Members provide:
- Accounts of actual attempts, including unfinished attempts.
- Relevant context and examples they are comfortable sharing.
- Questions and disagreements without needing to propose a fix.

Author provides:
- Clear tasks, scope, and materials.
- A way to give feedback privately.
- A record of decisions and unresolved questions.
- An explanation when advice is not adopted.

Use of material: [Who can access notes and for how long].
Recording: [Separate choice and handling arrangements].
Publication: No quotes or case studies without separate agreement.
Exit contact: [Named person and contact route].

The charter is an operating agreement to discuss with participants, not a substitute for any obligations that apply to your situation. Be specific enough that people know what they are joining. “Occasional feedback” is not useful if it later becomes a weekly call plus extensive reading.

Give the group an end date even if you hope to continue. At that point, review whether the same people still fit the questions and whether they want to renew. Familiarity with previous versions can be useful for examining changes, while also making those readers less informative about a first encounter.

For the fictional local-history companion, useful perspectives might include someone starting a first project, someone who tried the chapter but stalled, and someone with experience completing a small project. These are task-relevant differences; follower count and praise for the book do not replace them.

Do not assume this mix represents your whole audience. Write down who is missing, including people unable to join at the proposed time or use the chosen meeting format. Offer other ways to participate when practical.

GOV.UK's participant-recruitment guidance notes that recruitment methods, scheduling, location, and activities can affect who takes part. It recommends varying research and recruitment approaches to limit that risk. An author's standing group should likewise remain one source of evidence rather than the only place the author listens.

A friend can still be a strong contributor. Another author describes one such relationship:

“I do have one retired friend who is highly interested in humorous fantasy and is among my best beta readers.”

— u/MayhemAuthor, discussing manuscript feedback

The commenter goes on to describe help with confusion and inconsistencies. This is a personal account about fiction, not proof that friends are always good or bad research participants. The useful distinction is what the person contributes and under what conditions.

Before a meeting, ask each participant to attempt the same bounded task, or a clearly documented variant. For the fictional companion, the task is to narrow one project idea using three criteria from the book: available sources, a manageable scope, and a reason the question matters to the reader.

Ask participants to bring the idea they started with, the criterion they found hardest to apply, and the decision they reached. An unfinished attempt is a valid submission. They should not feel required to produce an impressive artifact for the author.

Collect this privately before people hear each other's responses. Otherwise, the first confident explanation may become the language everyone uses to describe their own experience. Individual notes also give quieter participants a contribution that does not depend on winning speaking time.

Avoid asking for sensitive material just to make the discussion concrete. A project about a neighborhood building can be described without sharing private family records or identifying living people. Use a supplied fictional case when a participant prefers it, and record that difference in the task.

Here is a proposed 45-minute agenda. The timing is an author planning choice, not a research requirement.

The author should avoid defending the chapter while someone describes a difficulty. Ask what they understood and what they did. Explanations can come later, after the report is clear enough to examine.

GOV.UK's small-group research guidance identifies dominant speakers and discomfort speaking openly as group risks. It also advises individual sessions when bringing people together adds no useful value. An advisory group does not require every research activity to happen in a group meeting.

Ask questions that give disagreement a concrete place to land:

• Which instruction did you work around or ignore, and why?
• What would make this task unsuitable for someone in your situation?
• Which conclusion in our summary does your experience not support?
• Where did you need information the companion did not provide?
• What should we investigate before inviting more readers?

Do not require each person to manufacture a criticism. Positive evidence matters too, when it identifies what worked in an actual attempt. “The source-availability question helped me drop an idea that needed records I cannot access” is more informative than a general compliment.

For the fictional task, suppose one person can narrow a building-history project, while another cannot interpret what counts as an available source. The author should preserve both accounts. The group does not need to vote on whether the instruction is “clear.” It needs to reveal where the instruction depends on prior knowledge.

After the session, share a concise account that participants can correct. Separate what they reported from your interpretation and your proposed action.

For the fictional example, the record might say:

Reported: One participant could apply the source criterion;
another could not distinguish an accessible record from a lead.

Interpretation: The instruction may assume prior research experience.

Proposed action: Add one example showing that distinction.

Next check: Ask new readers to apply the revised criterion.

Unresolved: Whether this issue appears in other project types.

This is an illustrative note, not actual feedback data. Its structure keeps a proposed fix from becoming a claimed improvement before further evidence exists.

Explain why some requests are deferred or declined. A reader may suggest a complete archive-search service when your companion only helps choose a project. Thank them, record the need, and state the current boundary without implying that every suggestion belongs on a roadmap.

At the end of the term, compare the questions you started with to what you learned. Check who participated, whose perspective is absent, and whether the group is now mostly commenting from memory of earlier versions.

Continue when there is a clear next question and members want to help. Rotate or supplement participation when the next task needs different experience. Pause when you cannot act on the findings or maintain the promised commitment.

If you are preparing an author companion, the skill-writing guide can help structure the instructions the group will examine. The group itself should evaluate concrete reader tasks rather than a general demonstration.

Visit Skillfully and choose Book onboarding to scope that first task. Bring your proposed charter and one uncertainty about how readers apply the book. That gives the conversation a specific research purpose from the start.