Decide whether your pilot is ready for more readers

Your pilot is ready for more readers when the evidence supports the specific task, audience, and level of support you plan to offer next. Review actual attempts, serious failures, unresolved questions, and your capacity to respond. Enthusiastic comments are useful feedback, but they cannot answer all of those questions.

Define “more readers” before reviewing the results. Inviting a small supervised group to try a revised exercise is different from offering an open, self-directed companion for your entire book. Evidence that supports the first step may leave the second largely unexamined.

The review sheet below is a proposed author decision aid. Its numbers and example findings are fictional, not Skillfully pilot results or recommended universal thresholds.

Keep invitations, starts, completed tasks, usable artifacts, and later application separate. Preserve unknowns. If someone did not reply, you do not know whether they tried the task, disliked it, became busy, or encountered an access problem.

A writer describes the gap between interest and visible participation:

“However, my friends have asked me to send them my beta and I don't think any of them have even opened the document.”

— u/alaricmoras, discussing beta readers and friends

The wording expresses the writer's uncertainty. It does not establish whether the friends opened the document or why they did not respond. Treat a similarly incomplete pilot record as missing evidence, rather than automatically converting silence into failure or approval.

For a fictional companion to a book about planning a short community workshop, imagine this record:

Invited: 8 readers
Known to have started the planning task: 5
Returned a workshop plan: 4
Plans meeting the stated exercise criteria: 3
Needed direct author help to finish: 2 of the 4 returned plans
Reported delivering the workshop: 1
No response about starting: 3

These invented figures describe different questions. Three acceptable plans do not show that three workshops succeeded. Four returned plans do not show that four readers could finish independently. The unknown experiences remain part of the decision record.

Name failures that would make the proposed next stage unsuitable even if most comments were positive. For the fictional workshop companion, examples include ignoring the reader's stated session length, inventing available equipment, or presenting an unconfirmed venue arrangement as settled.

Choose criteria relevant to your method and its consequences. A spelling issue and an instruction that contradicts the reader's constraints should not count as equivalent items in a single satisfaction score.

Retain the exact example, instruction version, and conditions for each serious failure. If you revise the guidance, check the failed case again and examine nearby cases where the revision could create another problem. A change made is not yet a change verified.

Use the skill-testing guide for instruction checks. Reader task evidence is an additional layer: the companion can follow its instructions and still leave the reader unable to use the result.

A strong demonstration of one step does not show whether the reader can complete the experience you plan to offer. Check the path from understanding the task to using or handing over the resulting artifact, within the pilot's stated scope.

In a discussion about sending manuscript chapters separately, a beta reader writes:

“As a beta reader we absolutely hate this method and can’t get a feel for your whole book and whether or not it flows in its entirety.”

— u/shukke, discussing chapter-by-chapter beta reading

That is the commenter's view about fiction manuscripts, not a universal rule against testing individual steps. The relevant question for a companion is whether your evidence covers the experience you are about to promise. An early step test can be valuable while leaving the full journey unresolved.

GOV.UK's beta-phase guidance pairs learning from limited use with support capacity and readiness for wider use. Authors do not need to adopt the government assessment process to apply the narrower principle: expansion requires an operational plan as well as encouraging feedback.

PILOT UNDER REVIEW
Task and intended reader:
Version used:
Period and recruitment method:
Support participants received:

PROPOSED NEXT STAGE
Who would be invited:
What they would be promised:
Self-directed or supported:
Maximum group size and why it is manageable:

EVIDENCE
Invited / started / completed / unknown:
Artifacts checked and criteria used:
Assistance required:
Reports of later application:
Reader contexts covered and missing:

FAILURES AND UNCERTAINTIES
Critical failures and evidence:
Fixes made and checks completed:
Open issues with owners:
What could change the decision:

OPERATIONS
Who responds to problems and how:
How readers report a difficulty:
How a faulty version can be paused or replaced:
What happens to existing participants after a change:

DECISION
Expand within stated limits / revise and repeat / stop this approach:
Reason:
Conditions that must be satisfied first:
Next review date and evidence to collect:

Set practical limits based on the work you can actually support. There is no universal number of readers that makes an author companion validated. A small pilot may expose a decisive problem, while a larger but poorly documented pilot may leave the main question unanswered.

For the fictional workshop pilot, suppose the returned plans are promising but direct author help was needed to clarify the audience. The evidence might support revising that question and running another bounded round. It would not yet support describing the experience as reliably self-directed.

If an unresolved failure changes important constraints, hold expansion until you understand and address it. If the method does not fit the problem readers actually bring, reconsider the task instead of extending the pilot indefinitely to collect more praise.

When evidence supports expansion, state its limits. You might invite readers preparing the same kind of short workshop, retain an explicit support channel, and schedule a review after the next round. Do not silently expand to new audiences or tasks that were absent from the evidence.

Include people who stopped early in follow-up where they are willing to participate. GOV.UK's satisfaction-measurement guidance explicitly includes feedback from people who leave a service before completing it. Their experience may identify a difficulty that a completion-only survey would miss.

A useful review note links the next step to evidence and names what remains unknown. “Readers loved it, so launch” is hard to examine. “The revised task has usable examples across these contexts; this failure was checked; these gaps remain; we can support this next group” gives the decision a basis another person can inspect.

Keep the pilot record even when you choose to stop. It can clarify which part of the book is worth turning into a companion and which promise needs a different form of help.

Visit Skillfully and choose Book onboarding to review a concrete author task. Bring your pilot sheet, one successful attempt, and one unresolved difficulty. Together they provide a more useful starting point than a collection of compliments alone.