I conducted a survey via my mailing list asking about people’s experiences with beta readers. I received a rush of responses – 50 in the first two hours alone. Thank you all so much for your input! Clearly, many writers think it’s valuable to get manuscript feedback, but also sometimes struggle with the process.
Beta readers are the superheroes who give us feedback on our draft manuscripts. People use the term in various ways, which is absolutely fine, but when I use it, I’m referring to a volunteer rather than a paid professional. I call a paid professional an editor, proofreader or writing coach.
I’ve seen feedback, when it’s appropriate and used intelligently, transform not just books but writers, which is why I’ve written a whole book on the topic: Beta Reader Superhero Writer’s Handbook. (This informal, self-selected survey formed part of my research for the book.)
I’m the Number 1 fan of beta readers, but I’ve also encountered problems in the process myself, and spoken to lots of others about their frustrations. This survey was about diving deeper into the pros and cons to figure out how to make it work better.
The biggest problems
My first survey question was: What is the biggest problem you face with beta readers? I deliberately started with an open-ended question which allowed people to tell me whatever came first to their minds, without any prompting from me, and without them knowing what others might be saying.
Out of 146 responses, there was a surprising (or not-surprising??) number of common themes.
- 46 people said that their biggest problem was finding the right beta readers – people who were right for the genre, had the necessary skill, could understand the beta reader role and knew what was expected of them.
- 44 people said they had trouble getting beta readers to return their feedback fast enough, if at all.
- 24 people said beta readers were too nice and had trouble giving useful criticism.
- 12 people said they received feedback that had too little detail to be any use.
- And 7 respondents said people insisted on correcting typos when it was not what they wanted from a beta reader.
I’ve got some possible solutions, but first let’s look at the rest of the results.
I asked what writers most wanted to receive from their beta readers. These graphs show the responses.
- Fix typos and grammar – most writers saw this as only slightly important or not at all important. If that surprises you, check out this article on why correcting detail is not often the best task for a beta reader.
- Tell me if my book doesn’t make sense – the vast majority of writers saw that as very important.
- Show me possible solutions to the problems in my book – this was more evenly spread, from slightly important up to very important. These answers might vary according to the confidence of the writer and the insight of the beta reader.
- Tell me what they liked about it – this one tilts towards important to very important. I think this element often gets overlooked in detailed critical feedback, and yet those authentic positive statements give the writer courage to persevere with the enormity of the rewrite.
- Alert me to wrong information etc – the majority saw this as very important.
- Big picture feedback, eg too many characters or events in the wrong order (fiction & memoir), or for non-fiction such things as poor structure, weak arguments etc – the writers in my survey overwhelmingly saw this type of feedback as very important.
I asked the respondents whether they’d had any bad experiences with beta readers. Many of them expanded here on what they’d said in Question 1.
Many of the bad experiences they reported related to getting exceptionally negative feedback from a beta reader, without any sense that the book was redeemable. Some found this crushing. Conversely, some were disappointed that they’d received only positive feedback, but it had been too brief and shallow to be any use. Others told of people fixating on small details and missing the main point, while some referred to arrogance from their beta readers. There were also multiple reports of beta readers being too slow or never submitting any feedback.
Thankfully, the question about whether people had good experiences with beta readers also received plenty of responses. These are some of the things that were mentioned:
- Beta readers revealed both strong points and weaknesses, discovering inconsistencies such as names or character details that accidentally changed. They spotted things that weren’t plausible or didn’t make sense, moments that might cause confusion for a reader, and times when the manuscript became boring. They noticed phrases or words that were used too often, helped reduce wordiness, and caught ‘obvious’ problems that the writer hadn’t noticed. Some contributed specialist skills or technical knowledge.
- Writers reported beta readers who brought a professional attitude and creativity to the task, who mentioned what they liked about characters, and explained parts of the story that resonated. Their feedback helped writers strengthen the ending.
- Writers reported beta readers who were kind, honest, encouraging and generous, who asked intelligent questions and sparked wonderful conversations, while presenting criticism in a respectful way. Some particularly appreciated the opportunity to ask more questions of a beta reader later.
- Some writers mentioned beta readers who gave helpful, concrete suggestions on such issues as readability and how to improve the clarity of the author’s voice – without trying to turn it into someone else’s voice.
- Beta readers helped writers see their manuscript possibilities, resulting in a better book.
- Writers mentioned feedback processes that generated better results after they started giving more detailed briefings to their beta readers (I was particularly thrilled about this – see my suggestions below).
Beta reading for others
The next question asked whether people had done beta reading for other writers. The good news is that most had found the experience rewarding, but there were a few glitches along the way.
- Many said they felt honoured to be asked, enjoyed being first to read it, and loved helping others. Many enjoyed offering big-picture feedback, and said it worked best if the writer and beta reader were a good fit, and they liked the book and the genre.
- Some preferred not to read manuscripts that were poorly written or still a rough first draft. Some wouldn’t read for random writers, but only for people they knew.
- Some declined beta reading because they were time-poor, or the timeframe was too tight. Others were very selective about beta reading opportunities, because of the heavy time commitment. Some felt embarrassed that they were ‘slow’ beta readers.
- Some beta readers reported finding the task draining, stressful and harder than they expected. Some felt overwhelmed or even scared.
- Some found it a challenge to be helpful without being hurtful, hard to be honest without being discouraging, and feared they probably gave too much detail.
- Some were disappointed that the writer didn’t seem to benefit from their input or know how to use it. Some felt frustrated when the author didn’t adopt their suggestions, but others were relaxed about whether or not their suggestions were used.
- Some didn’t enjoy the process because their author was offended, and some felt their author just wanted flattery. Others were annoyed when they received no thanks for their feedback.
- On the plus side, some said the writer’s appreciation made their task worthwhile. They enjoyed seeing a writer wrestling with how to make a book work, and were particularly satisfied to watch a writer they’d helped go on to great things.
There were other benefits, too. Some learned a lot about writing from reading other people’s drafts with a discerning eye. They learned from the way different writers worked, and became more aware of their own mistakes and possibilities.
My methods are shaped by my work as a developmental editor over a couple of decades and years of trial and error getting useful beta feedback for my own manuscripts and helping my editing clients get beta feedback for theirs. I try something, observe what worked and didn’t work, and then I test it again.
Let’s look at some brief suggestions for how to solve the main problems listed above, which boil down to three main issues:
- Finding the right beta readers.
- Getting the right type of feedback.
- Getting feedback fast enough.
1. Finding the right beta readers
I recommend that at least some of your beta readers do not come from random requests. See these resources:
- How to find a beta reader
- What makes a good beta reader
- Chapters 3 and 4 of the Beta Reader Superhero Writer’s Handbook, including how to find specialist beta readers.
2. Getting the right type of feedback
Choosing the right people is obviously important, but managing our communications with the beta reading team also has a powerful impact on the quality of feedback we receive. Try these resources on approaching and briefing a beta reader:
- The initial invitation
- Practical details
- A sample briefing document
- Chapters 6 to 8 of the Beta Reader Superhero Writer’s Handbook.
Managing our response to feedback can also make a huge difference:
- Chapter 9 of the Beta Reader Superhero Writer’s Handbook covers how to get the most out of feedback. The right techniques can sometimes turn what seems to be ‘poor feedback’ into surprisingly useful information.
3. Getting feedback fast enough
Sometimes we’ve chosen people who are too busy or not motivated, BUT sometimes we simply need to communicate effectively about when we want it, and why we want it at that time. Gentle, polite reminders can also make a big difference.
We also need to manage our own expectations. Most of our beta readers have busy lives, and it might take them several of their precious relaxation-days even to read the manuscript (fitting it in around other responsibilities) – let alone think carefully and creatively about their feedback.
Whenever possible, I allow 3 to 6 weeks for my beta readers, and a similar length of time for me to process the feedback, before any publishing deadlines. It’s not always possible – sometimes timelines are tight.
But it’s when I’m doing other things over a period of time that my rewriting strategy gets a chance to mellow and mature in the back cupboard of my brain. So as the years pass and I see more evidence of the cost of rushing the process, I’m fighting more and more for that longer timeframe for both me and my beta readers.
What are your experiences with beta readers? What has worked for you? Scroll down and join the conversation below.