Readers Speak. Authors Listen.
“Words mean more than what is set down on paper. It takes the human voice to infuse them with shades of deeper meaning.”
During the Beta Reader process, authors, your job ISN'T to fight for your life in the comment section, nor is it your job to defend WHY you wrote what you wrote or your choice of words or reasoning. Your job is to LISTEN.
That's right. Read and listen to the feedback given. Will you agree with all the feedback you've received? No, and that's okay. Learn how to say thank you for reading and discern which Beta reader feedback to apply to your manuscript.
Remember, the point of the Beta Reader process is to see how the average reader interprets what you've written. If you are finding that the readers are misunderstanding, overlooking, or not comprehending what you're trying to write, it could be because what's in YOUR head isn't translating correctly to the reader. This means you'll need to develop whatever area or areas in your manuscript to make sure the reader is seeing the world as you meant them to see it.
That being said, Beta Readers, be honest. Again, ghosting isn't a solution because you don't want to tell the truth. Your job is to honestly let the author know how you're feeling as you're reading the manuscript. If you want to DNF, say that and state the reason why. If parts of the story are too slow, too confusing, etc., say that. Especially if the author didn't give you set questions. Beta Readers should give positive feedback as well as constructive feedback. Do not be afraid to give both. If an author is offended because you didn't stroke their egos and praise their piece, the problem isn't with you. It's them.
I SAID WHAT I SAID!
To wrap up, Beta Readers and Authors are partners, not enemies. The goal is to make sure the story is at its best.
Sometimes the truth can be hard. Trust me, a few Beta Readers once told me that my book was boring AF and they would have DNF'd a long time ago. That is hard to hear. But I said thank you for your time, I appreciate your feedback, and looked over my manuscript to see how I could improve it.
Sometimes it's appropriate for the author to ask follow-up questions to clarify the Beta Reader's feedback.
Let's give examples:
Example One:
Beta Reader: This part is unclear to me. Why would the MC choose to go here when on page 22 she said she was going there?
Author Response: Well, she's going there and not here because I need her to do this and not that, and I put on page 25 this one brief sentence when she changed her mind. You didn't read it?
WRONG RESPONSE!
Again, an author's job during the Beta Reader process is to LISTEN, not defend or double down on your choices. If multiple readers are having the same issues, then the problem is in the writing, not the Betas (most of the time).
Example 2:
Beta Reader: I don't like this.
Author Response: Hey, if you don't mind, can you please clarify what you do not like about this section or part? I need it for editing. Thank you.
Beta Response: Oh sure, the scene made me feel <insert emotion>, but nothing is wrong with the scene.
Author Response: Thank you for clarifying.
These are just examples.
In summary:
While in the Beta Reader process, an author's job is to listen.
The Beta Reader's job is to respond to the story itself and/or the questions the author has given. Make sure your feedback is constructive and give examples as to why you dislike or like a certain part in the text.
When Authors and Beta Readers work together, the manuscript will turn out fire. We are partners working toward similar goals. Remember that!
