i think the funniest part of my immortal is when ebony goes to the hogsmeade my chemcial romance show and describes gerard way as having an "ethnic voice" but theyre literally just from new jersey
How To Have a Good Beta Reading Experience (or: what I've learned from 3 years of beta reading)
So lately I've been having a lot of discussions about beta reading with my discord groups so I thought I would write it out here and also share some resources I've used over the years.
This is mostly by and for writers, however readers can learn from this post as well!
DISCLAIMER: I'm by no means a writing expert, but I have been either beta reading others' books, or having my own stories beta read consistently since 2020.
THIS IS ALL PERSONAL EXPERIENCE/OPINION. Others may agree or disagree ❤️
Here are the main points I'm going to talk about in this post, and I'll do it under the cut to save your dash space:
Understanding Alpha vs. Beta Readers
Choosing Readers
Being Clear About Feedback
Swapping / Compensation
The Importance of Writing Community/Groups
Websites/Resources for Finding Beta Readers
1. Understanding Alphas vs. Betas
So this is extremely important and for me, this may be the difference between me finishing your book or not. Many times, especially from new writers who had never had anyone read their work before, had extremely rough drafts that were barely coherent and were NOT beta ready, but asked me to beta read. I am not a person who can look past extensive grammar errors, nor am I the kind of person who will sit and fix all your grammar line-by-line for you.
Alpha Readers - for first/second drafts
Beta Readers - for polished drafts
It is ok for alpha reads to be unpolished and have grammar issues, and it's even ok if they have plot issues, continuity errors, etc. Because alpha readers are there for that purpose: to be the first eyes on your story and help you find and fix those issues.
The issue I have had over and over, though, is people asking for a beta reader when what they really needed was an alpha. I went in expecting a polished draft and got someone's Draft 0. In some cases, I got 100k drafts where the writer obviously had no idea how to format dialogue grammar and every single dialogue was wrong. Obviously this made me slow and in many cases, unable to finish.
Alpha readers will go in expecting it to be unpolished, and will be prepared to look past grammar/stylistic errors in order to focus on the big picture issues (plot holes, character consistency, pacing/engagement issues, etc). A Beta may be too frustrated by an unpolished draft to finish it or provide the feedback you're looking for. If you have been experiencing a lot of betas backing out and not finishing your work, you might consider this as a possible reason why.
I would also recommend, if you have never had anyone read your work before, even if you have had multiple drafts, it might be safest to ask for alphas rather than betas.
A quick way to see if your work is beta ready (again, personal experience): Pick up a published book from the shelf in your genre. Does your book read similarly? Does your formatting & grammar look the same?
Bonus: read it out loud! If reading the published book out loud is significantly easier than reading yours out loud, you're probably in the alpha stage.
TL;DR: Understand your draft and which level of reader your draft is ready for. Know the difference between polished and unpolished, and be upfront about it.
2. Choosing Alphas/Betas
You may not like it but: Just because someone is your friend, real life or online, does not mean they will make a good reader for you.
#1 MOST IMPORTANT: GET READERS WHO LIKE & REGULARLY READ YOUR GENRE!
I cannot stress this enough. As someone who writes vampire content, I cannot begin to express to you the amount of useless comments I got from readers who had clearly never read a vampire book in their life.
You need someone who is familiar with your genre and you likes your synopsis/blurb.
Caveat: that said, I did find a few great betas who had never read vampire content before and gave awesome feedback. However, these readers knew and admitted they knew nothing about the paranormal genre, and because of that did not make any comments on worldbuilding, instead sticking to plot and character development only. Some readers can't make this separation.
Another thing I would recommend, especially if you are swapping or the beta reader is also a writer/on writeblr, I would recommend reading their writing before having them beta read. If you read their excerpts and see that it's really unpolished or a style that's vastly different than yours, that might change whether you want them to read for you.
In my most recent beta round, I used a google form to do a quick survey to see who was interested in beta reading. This worked really well for me and I would recommend it! You can also use this to make all potential readers agree to not share/distribute/plagiarize your work, so you have it in writing just in case someone were to try something.
This was also a great way to see which genres they usually read and how many times they have beta read in the past!
TL;DR: Get readers who LIKE your genre. Read their writing and see how they write. Use an online signup form to narrow down.
3. Be Clear About The Type of Feedback You Want
This is perhaps the second most important thing when you get readers. Many readers will shy away from reading your work if you have nothing in mind for them to look out for. Also, being clear about this shows that you 1) know it isn't perfect and needs work and 2) you have insight into what the issues already are.
For Alphas, these traits are what I have found to be the most helpful:
Immediate inline reactions - particularly emotional engagement and pointing out lines that resonated with them
NO grammar/stylistic comments (unless incomprehensible)
Questioning of worldbuilding, character decisions, and character development - particularly if confusing or unclear
Comments on action sequences & their readability
Comments on believability of the plot points/progression
For Betas, these are what have been most helpful to me:
Comments on grammar, especially if repetitive
Stylistic comments, particularly for over-used words or noticeably repetitive sentence structures
Comments on pacing
Comments on plot initiation point and buildup/execution of the climax
Not questioning my worldbuilding/plot and trusting that what I have written is intentional. Only pointing out areas that have on-page evidence of inconsistencies.
Everything above is simply personal preference. You might find other comments to be better for alphas/betas. However, being upfront about which comments you want or don't want can drastically change which people want to read for you!
Some readers are obsessed with in-depth inline grammar/style comments, some aren't at all. Some writers LOVE these in-depth grammar comments, and some don't. Being clear about what you want is the best way to make sure you and your readers are compatible for the stage of editing you're at.
4. Swapping / Compensation
So this one I might have a bit of an unpopular opinion, but I wanted to cover it because so many people talk about it on here and other sites.
Again, based on my personal experience, swapping and compensation does not mean you're going to get better feedback or have a better experience or relationship with readers.
For the record, for everyone who beta reads for me—and finishes—I always offer to read theirs, even if it's a genre I don't like.
Personally, I have never tried compensation (re: money) for beta readers. However, there are a few issues I've come across with swapping:
Mine was beta ready and theirs was unpolished first draft
Our types of feedback didn't align
Our genre preferences didn't align
Their feedback was nowhere near as high quality or constructive as mine
In these cases, one or both of us burnt out on reading the others' work, and then we'd both bail. Especially with #4, it was very disheartening for me to spend hours finding their plot holes, helping them come up with ways to fix them, for them to then write 1 paragraph about what they thought of my story that was extremely surface level. To me, that wasn't even a swap, and was practically worthless. There was even one who got sensitive about the feedback I was providing (which was a queer sensitivity read) and then left almost identical comments on my story, which weren't even relevant. It was like revenge-commenting.
All this to say: I have had positive experiences with swaps. My alpha for twtr was a swap and I really enjoy her work and she enjoys mine, and we will probably continue to swap forever.
This goes back to #2 above: be picky & choose your readers well. Your story is your baby, and it deserves to be critiqued by people who value you and your story, and want to help you make it the best possible version of itself.
To summarize, I have had two good swapping experiences. I have had 10+ good uncompensated betas—with an offer for me to read their stuff when it's ready. Do with that what you will.
5. Writing Community / Groups
On to a more positive note! I have had the best experience here on writeblr, and this is coming from someone who has tried multiple other communities (which I discuss in the last section below). Having my own discord server from tumblr, joining a few other writers' discord servers, has completely changed the game regarding finding consistent betas, more resources, and just having an overall much more positive time writing and editing.
Writeblr keeps me grounded, keeps me hopeful, and even if I share something that doesn't get tons of notes, it's so nice to have interaction. It's so nice to give and get back, consistently.
I do want to emphasize the importance of giving to get back. If no one is liking/interacting with your excerpts, tag/ask games, etc. then that's probably because you're not interacting with them! It's very important to show interest in other people's work!!
I'm not saying you need to jump onto everyone's taglists for all their wips, but join the ones that genuinely interest you the most. Play in ask/tag games consistently. Follow writers back who follow you (if they post things you're interested in, ofc).
I have the same amount of followers as the people I follow right now, and I think that goes to show that people reciprocate here on writeblr! It's a lovely community and don't be afraid to reach out ❤️
I have found almost ALL my recent betas from my tumblr and discord groups. They have been lovely so far and I would highly recommend building up community here if you are interested in finding betas.
6. Websites/Resources for Finding Betas
Alright, last section. Thanks for bearing with me. I'm going to go through the sites I have used, and why I still use them, or why I dropped them.
Scribophile
So, for starters, this is one I don't use anymore. This was the site I first used when I had a polished draft in 2020 and had no idea how to get feedback. Essentially, they have a point-system. The more comments you make, the more points you get, and then when you have 3 points, you can post a chapter. It continues in a cycle.
Pros: Personally, I think the site helped me a lot in realizing what a bad critique looks like (which is helpful!) and also helped me learn which comments/feedback types work for me, and which don't. I don't regret my time there by any means, and I found one life-long friend and beta reader there I wouldn't trade for the world. It also allows you to post/remove your story and the readers don't have direct access to it—meaning if they want to download/steal/plagiarize, they'd have to copy and paste or screenshot chapter by chapter. It's a little safety precaution.
Cons: It's not the best place to get constructive feedback. The issue with their system is it encourages quantity over quality in critiques. Because of that, you'll get strangers rewriting your entire chapter in their own style so they get 2-3 points for one critique, but... was any of it actually helpful to you? Maybe, maybe not. It's also random, so you can't control who comments on your stuff, and they might just comment to get points even if they hate your genre. I also don't think it's fair to have to do 3-5 chapter critiques in order to save up enough points to post ONE chapter of your own. And if you want to post your story for full beta reads and control who reads it and who doesn't, you have to subscribe monthly.
So I keep an eye on it occasionally to look through their forums on writing, agents, publishing, etc. But most of the forums gets nasty, because there are a lot of really pretentious writers who think they know all the rules. If you join small groups (e.g. sub-groups based on diversity, etc) they tend to have better and more meaningful discussions.
Personally, I would never use it for beta/alpha/feedback ever again. This is the site where most of my bad swaps came from. But you might find it useful! So I thought I would share it.
Nanowrimo Forums
This is another one I don't use anymore, but might consider reusing in the future. The biggest issue I have with nanowrimo is that a lot, and I mean A LOT, of these participants are first-time writers and have no concept of what polished vs. unpolished even means. I did find two really good swaps there (actually the only two good full swaps I've had) but those were very hard to find.
There is also the issue that a good chunk of them only write during November, not year round. So for finding consistent, year-long partners, this is not the best option. I'm a member of 2 discords that have all fallen silent as soon as Nano actually ended.
Also, in my experience, asking questions about anything related to "controversial" topics (especially trans and minority ethnic groups) becomes toxic very quick, which is unfortunate. There are even a few moderators who seem to be contributing to the toxic/immature discussions rather than fixing them/shutting them down, which is the main reason I stopped using it.
However, it's a GREAT place to get free, simple covers! Their artisan section is fantastic and there are a lot of people there willing to make basic covers/banners for you for free.
BetaBooks
I've only been using this one about a month so far, but I'm really liking it. It's set up that you can invite betas to your story specifically, or you can look through a beta reader library, read their profiles, and invite them to see if they're interested.
This is essentially an alternative to Scribophile. It allows you to post your story online and find betas and become a beta.
Why I like it better than Scribophile: it's not a point-based system, meaning it's uncompensated so the readers have nothing to gain other than enjoying/helping your story. There's no hard feelings if someone bails. It allows you to see all comments in one place (which Scrib can't do). (And with discount codes found through google, it's cheaper, too. Message me if you need help with this 👀)
It also is all online, easily removable, so readers would have to copy/paste or screenshot chapter-by-chapter to steal it. So again, just a little safety net that makes me feel better.
Writeblr
Yep, that's right. Right here. Actually right here on tumblr has been where I have found the most beta readers and in the shortest time. I talked about this in the section before so I won't regurgitate. But there's a reason why this community is so long-lasting. It really is the best one out there I've found.
TL;DR / IN CONCLUSION:
Know where your book is in terms of reader-readiness. Know the difference between alphas/betas and polished/unpolished. Know the types of feedback that work for you and specifically request it when recruiting betas.
Interact with a community. Give interaction in order to receive, and don't expect people to reblog/like your content if you don't reach out first. Join small, niche writing community discords. Find like-minded writers.
Decide to swap or not, but this won't make or break you.
There are many writing communities out there designed to help you not only find betas, to provide beta-reading feedback forms and commentary. Try them out and see what works best for you.
And above all, thank Writeblr for being such a lovely community ❤️
How to be a Good Beta Reader (or: the difference between critique and beta)
This post is a follow-up to my ORIGINAL POST HERE "How to Have a Good Beta Reading Experience" [link embedded] so I recommend reading that one first for more info.
But I wanted to follow up because I've gotten some questions about it and I figured there was enough to make another post.
WARNING: this is SUPER LONG LOL
DISCLAIMER: Again, I want to clarify that this is based on my own experiences and what I personally look for in alpha/beta reading. Other writers/readers may disagree or have different tastes!
Topics Covered Below:
Critique vs. (Alpha &) Beta Reading
The Purpose of Beta Reading: Mindset
What Comments Should Look Like
How Much Should You Talk to the Writer About It? (Spoiler: it depends)
I want to start with this because so many times (as a writer) I have asked for beta readers, and basically gotten a critique (or "crit" as it will be called from here on). A crit can look a lot like many different things depending on the reader, but in general, here's the difference:
Critique: grammar, style, clarity, often line-by-line
Alpha/Beta: story structure, character arcs/development, plot, and overarching themes and ideas
And I say this because some writers might want both. Some want all these separately, and some want them all at once.
Generally, crits are harsher, and can resemble "tearing apart" a manuscript. They can certainly offer great feedback, but it depends on the writer and their needs.
Some writers, especially for those who have had critique partners in the past and this isn't their first story, may not want these comments at all. I generally prefer not to have them (unless it's something stark that draws you out of the immersive reading experience) because when it comes to grammar, style, and flow, these are things I can edit myself. I have had enough good critique partners in the past that I can handle that and don't need betas to do it for me.
However, some writers might not feel that way! But I definitely know I'm not alone here. Especially when manuscripts have already been critiqued and you specifically ask for a beta, it can be disheartening to receive this style of feedback (especially in large quantities).
Examples of critique-style comments:
Word choice and/or grammar edits
Line- or scene-specific comments like breaking down or giving advice on dialogue, action sequences, worldbuilding, and the writing itself
E.g. "this needs more visual description" or "this description is too long/drawn out" or "action sequences require faster pacing" etc.
Examples of alpha/beta style comments:
Character arcs/dev: "I liked this character's journey, but I didn't feel connected to them during XYZ parts of the book." or "I don't understand why this character chose to do this."
Plot: "This scene is what I consider to be the part where the plot really begins" or "I don't understand how ABC scene connects to XYZ scene."
So what's wrong with that? Nothing!
But you can see where if someone asked for an alpha/beta but the reader's comments are 90% crit-style, the writer might feel like the reader didn't like or connect with their work. If a reader is crit-style commenting x5+ per page, then they likely weren't engaged with the story so much as analyzing the writing style. And for alpha/betas, you want to be as immersed in the story as possible and analyzing the story.
Particularly if the manuscript has already been critted in depth, and is a polished draft (which, is certainly debatable, but that's a topic for another day) ready for betas, it can be frustrating to receive crit comments when that's not what you asked for. A lot of the times, for well-edited and mostly-polished drafts, these crit-style comments come down to personal preference with the reader editing your work to fit their personal taste. Which is not making the story better, just different.
But, to emphasize: if you were unclear in your expectations and the reader doesn't know that manuscript is already critted/polished going in, they might think you want these comments!
Also, some readers might be awesome critique partners, but terrible betas—and vice versa.
This is why I'm going to drive home my Big Takeaway from my first post: communication is key! Both writers and readers need to be clear on the type of feedback that's desired.
Of course, most readers probably do a mixture of both of these styles of comments, and this is fine! The important thing is to keep what the writer wants in the back on your mind. If you know the writer asked for a beta, then try to keep crit-style to <50% (or maybe even <25%) of your total comments. And vice versa, etc. etc.
TL;DR: A critique analyzes the writing. An alpha/beta analyzes the story. Many readers will look at BOTH, so it's important to discuss this beforehand and provide the feedback desired!
The Purpose of Alphas & Betas: MINDSET
So this piggybacks off of what I just discussed: if someone has asked for an alpha/beta, you should keep the GOAL of being an alpha/beta in the back of your mind. Especially if you're prone to crit-style comments, this will help you.
The goal of BOTH alpha and beta readers is to SUPPORT and ENCOURAGE the writer. I know that's obvious, but so many times I have gotten comments or questions about why some readers' comments seem rude/inconsiderate or not constructive. And, at least in my experience, it's because the readers went in with the wrong mindset—a mindset more appropriate for crit, rather than alpha/beta.
So what is the goal? To me, the goal should be to figure out what the story is the writer is trying to tell. Maybe in some cases the writer is upfront about that, or maybe you're going in blind. But when I go into a book as alpha/beta, this is the question I try to remind myself throughout the journey:
What is this story trying to tell me, and how could it be stronger?
But MJ, what does that mean??
Because no, I don't mean the genre, or the plot, or even the character arcs or writing style. I mean:
What theme is this writer exploring / what is the message they're sending to readers?
And from there: what about the narrative/writing/plot/etc. interfered with my connection with this message?
Side story: let me use avof as an example. This is an urban fantasy with vampires and werewolves and shifters (oh my!). I had some shitty "betas" for this book years ago which really threw off my groove as I was editing because I didn't know they were bad betas. But the truth is they weren't betas at all. They were critiquing it, and from the mindset of "this is vampire romance book." They went in critiquing my book for something that it wasn't. They completely disregarded that it more aligned with adventure, not romance, and the themes explored were self-discovery, self-acceptance, the impact of immortality on psyche, and gender & sexuality & identity - and because of that, they critiqued the book without engaging with the book. If they had asked themselves "what themes are being explored?" they (hopefully) would've seen it wasn't romance, and likely would've engaged better.
So, to continue on with this main goal, there are other things to consider—what kinds of mindsets you should avoid!
Whenever I have gotten insensitive (and sometimes, full-on offensive) comments, these were contributing factors. Regardless of critique, alpha, or beta, these are true:
You are not the only reader. There are going to be multiple people giving comments, and your comments are all of equal weight. You may be the only person who can't visualize that fight scene. You might be the only one who thought a plot point was too predictable. In most cases you will never know if other readers agree/disagreed with you, which is why it is the writer's decision whether to take action on your comments are not.
You are not an expert. I don't care how long you've been reading, writing, or beta reading. I don't care if you've read 100 published books in this genre before. You are not the expert on this book. The writer is. You do not know what is better for the story than the writer does.
You are not here to decide whether the writer is a good writer or not. You should not be making statements that imply that the writer is inexperienced or new to writing. You should not go into reading a manuscript with the mindset of "I have more experience than this writer and I should share my knowledge & teach them something." (But if the writer has expressed this, then it might be okay in some instances to give advice.)
If a specific minority group is being repped on the page that is not ownvoices and you are part of that community, you could offer insight that can be helpful, but should ask the writer if they want that kind of feedback prior to giving it. If you are not part of the community, you should not comment unless the writer has requested it (unless ofc you're complimenting it lol)
When betas go in without these ideals, it can lead to at best, unhelpful comments, and at worst, condescending and hurtful comments. These are the comments that make writers feel like failures, or like their book is bad, or that they are bad writers. Or, for experienced writers who know you went in with these (toxic, imo) mindsets, it can hurt relationships, break trust, and/or make a writer roll their eyes and disregard all of your comments.
That isn't to say that you should only compliment and not have any negative feedback or ignore flaws you see in the writing, narrative, character development, etc... but it is best to go in with the mindset that you are here to give them insight so they can make their story stronger, not to teach/give advice or change the story.
A note on sensitivity, authenticity, and expert readers:
In my opinion this is one of the only cases where direct education/advice should be given. I also recommend having at least 2 sensitivity readers per any group that's repped that's not ownvoices, because even two people from the same group may interpret your story differently or see different weaknesses/strengths.
That said, it is important for readers who are not of the repped groups to hold their tongue. It doesn't matter if your partner or sibling or parents are part of a group repped on the page. If you are not a member of that group, you are not an expert. If you have an inkling that the writer has not had sensitivity readers yet, you can politely suggest it. But it could also be a case of you having different life views, ideals, and/or opinions than the writer and the group being repped, and that is why you are not a sensitivity reader. I can't tell you how many times I had cis/het betas say my representation of an identity or repping gender as fluid was inaccurate/offensive when it was ownvoices, or when I'd already had 3+ sensitivity readers for the group(s).
Basically, as an alpha/beta reader, you are here to offer insight and immerse yourself in the story. It's also good to remind yourself throughout reading that "this might rub me wrong, but another reader might like it." Framing your ideas and comments this way will help you be more objective and less "this is wrong/right" because there is no such thing in writing.
TL;DR: The goal of alphas/betas is to engage with and understand the STORY, give the writer insight into how you interpret it, and help the writer figure out how to make their story stronger. It is not to give advice or teach. The writer decides what changes to make and is the expert on their story.
Ok, now I got the Beta Mindset™. So how do I comment?
Well, really this will depend on the person. Everyone is different and will notice different weaknesses and strengths in any given manuscript. And, as I said above, most people naturally will provide some crit-style comments, it's just in our nature to point out when a writing style doesn't mesh with our preferences.
From a writer's perspective, at least for me, these are the kind of comments that are the most helpful for me:
"I..." statements. For example: "I am struggling to visualize this fight scene." Instead of rewriting it or pointing out that the descriptions or actions are weak or explaining how to fix it—this is an open statement that leaves the decision up to the writer.
Immediate emotional reactions are awesome for writers to know. For example, if a line made you laugh out loud, say so! If you get to the end of a chapter and were so immersed that you forgot to comment, say so!
And on the other end, if you were immersed but then something happens that snaps you out of it, say so! But without "because..." or "you should..." advice. Just say "hey I was super immersed, but in this paragraph you lost me."
I also recommend holding comments until the end of a chapter/section (minus immediate reactions as above). Look at scenes, chapters, acts, as a whole rather than individual pieces. This will help you focus on the story, rather than the writing.
I would also recommend this post!! Excellent, and I agree 100%!!
Other critical examples: "this is my favorite character but this decision is frustrating/confusing me"; "I was bored and skimming through this chapter"; "I'm not sure what [insert worldbuilding feature] means"; "I didn't know that the magic system could do this and I feel blindsided"
Other complimentary examples: "This line of dialogue really resonates with me"; "this has been my favorite description so far"; "I didn't see this coming but it makes perfect sense!"
And here are comments I suggest you avoid:
Anything that implies that the story is unfinished, too long, too short, etc. This might be ok for crits or alphas or if the writer has said that it's unfinished, but probably not for most betas. If the writer is at the beta stage, then likely they consider their manuscript finished (minus any changes they make based on beta feedback). If you feel the need, you might say something like "this genre is usually 80-100k and yours is 150k" but avoid wording like "the story is overwritten/underwritten", which can be hurtful. (Once, a story of mine was on draft 8 and had been called polished and ready to publish by various other people, and then one beta said, "this is a good attempt at a draft of an opening scene." So yeah, avoid stuff like that.)
Wording things in a way that make them seem like Facts. As a reader, everything you say is subjective. Regardless of what you are commenting on, what you are providing are opinions. Especially for writers who tell unconventional stories/structures, comments like "this isn't the way this is done" are just annoying and are not even true half the time.
Unless you can provide sensitivity feedback personally, do not criticize the representation of a group you are not a part of. If you see something overtly harmful toward a group on the page, you can politely suggest sensitivity readers, and leave it at that.
Try your best to not give reasons or "because" statements. "This action scene felt slow because-" "I didn't feel connected to this character because-" Nope. Stop right there, unless/until the writer asks to elaborate.
Side Story: My Favorite Comment
One of the single best comments I've ever received in a beta was when they noticed a character making a decision that didn't seem right. They pointed it out and basically said, "This feels out of character to me because I don't think this character would do this. They have done XYZ in the past, and I thought their motivation was ABC, but this decision directly conflicts with that."
Why was this the best comment? Because 1) they didn't tell me how to fix it, 2) it was objective with evidence and nonjudgmental, and 3) they were 100% right.
What they had actually found was a plot device I had used to push the character in the direction the story required. But because they pointed this out, I was able to see the source of the issue and rework the scene so that the character's motivation was consistent and they still ended up in the direction of the plot.
Since I foresee questions, allow me to elaborate on the last point: so often, a reader will say "this isn't working for me because of this reason" but actually, they're wrong about the reason. Like the comment above, this beta could have easily said, "this feels out of character because you messed up their motivation." But the problem wasn't motivation, it was me using a half-assed character decision to move the plot in the right direction! The issue was the scene, not the character development. The advice to "fix the character's motivation" wouldn't have fixed anything and might've even made the problem worse.
This isn't to say that advice should never happen in an alpha/beta, but I personally believe that the best comments are not those that say "you should change/fix this" but instead say "this is working for me/this isn't working for me." It leaves it open for the writer to figure out how to solve the problem, if a problem even exists.
**Edited Summer 2024**
To paraphrase a writer I used to respect and did have some good advice, when people tell you something isn't working for them, they're always right. When they tell exactly what is wrong or how to fix it, they are always wrong.
TL;DR: Basically, you aren't here to give advice, or fix anything, or change the story in any way. You are here to show the writer how their story impacts you, what you connected with, what you didn't, how their writing style works for you. Keep your comments open-ended and use specifics to show the writer what you connected with and what you didn't. You are giving the writer insight into how readers will interpret and understand their work, and it is the writer's duty to then grow their work.
And that leads directly into our final section...
How Much Should You Talk to the Writer About It?
This depends on the writer. Sometimes, writers will do 5+ betas at once (even on the same document) in which case they might not talk individually with the readers about any of the comments. Some writers (not me lol) will have an alpha as they write the first draft so it's not even complete yet, so they would probably talk a lot.
Personally, some betas I talk to for hours trying to brainstorm fixes (see: @jamieanovels and @wildswrites lmao tysm 🙏), and some betas I will just say "thanks for reading <3" and that's about it. It depends on how much you commented, the types of comments, and if I felt like you genuinely connected with the story (or not).
Side Note: I do want to clarify that by "misinterpret" below I don't mean that the readers are wrong, I just mean that they interpreted differently than what the writer had in mind. There is no misinterpretation when it comes to any form of art. But if a writer intended for the Main Takeaway of their story to be one thing, but the majority of readers took away another—that's important for the writer to learn in the beta stage. (Also, some stories are vague or open to multiple interpretations on purpose.)
For me, I talk in-depth with alphas, and maybe some betas, but there are also a lot of betas I barely talk to. I don't think there is a right or wrong here. Because as stated above, alphas/betas are here to provide insight into how readers interpret, relate to, and understand the story.
So once the writer gets that, there may not be anything else to talk about. Or, maybe the writer has questions about something you commented, and will want to follow up. For me, especially if you interpreted something way differently than I intended, I might want to follow up to see what in the narrative made you go that direction. Or, if you interpreted exactly as I intended, I may want more insight into which parts stood out the most to you, or what your favorite parts were. Or... I might not feel the need to follow up at all, for either.
In general, in my opinion, writers should be leading these interactions. Unless the writer has welcomed it, readers shouldn't be reaching out to writers to further discuss the comments they left.
(Note: this is not the same as hype/fangirling. Please come to my dms unsolicited and go hype about my book)
You have agreed to read it and leave comments, but the writer has not agreed to have full discussions with you about their own work. The writer doesn't owe you follow-up on the comments you leave, and whether they liked or disliked, agreed or disagreed with your comments doesn't really matter.
You may leave comments that are totally out of line with what the writer wanted, and that's fine. You might leave comments that make the writer uncomfortable, and that's fine too. We can't control these things, and there is no way to know how someone will interpret a story or what comments they might leave.
That said, If a writer doesn't follow up with you on anything, that doesn't mean your comments were bad. It might just be the writer's style to process and make changes alone. Even if you "misinterpret" their work, or even dislike it, all perspectives bring something to the table. Giving the writer insight into how one might "misinterpret" and/or dislike what they've written can be just as valuable as the betas who loved it.
Regardless, it's important to comment in a respectful way—respectful to the writer and what types of feedback they request, the story itself, and yourself as a reader. We are all growing and learning together, and miscommunication or writers and betas who have misaligned goals can lead to hurt on both sides. Hopefully this longass post gave you some insight into how/why that happens, and how to avoid it in the future.
--------
ANYWAY that was a lot. I hope you got something out of this, because it took a week to write this up lmao
–mj
P.S. I am considering doing another in this series focusing on writers and how to handle comments (good and bad). If you'd be intersted in that let me know <3
P.P.S. if you'd like to be tagged in this series, message me or comment below!
A Hot Take(?) on Critique/Beta Comments: Self-Determination Policy
Consider this a spin-off from my Beta Reading Series which you can find here. (you don't have to read them to follow this post, but if you like this post, you'll like the whole series.)
I was discussing this with a friend who works for a crisis center/hotline, and we ended up agreeing that their "Self-Determination Policy" was a similar mindset that we take when beta reading each other's work.
Since it goes along with most of what I said in my previous posts, I thought I would expand on it here. Again, this has my usual disclaimer: this is all personal experience/opinion.
content warning: there is mention of suicide below
Below:
What is Self-Determination?
Self-Determination in Beta Reading
What About Giving Advice?
What To Do Instead of Advice
Tips & Examples of Comments
TL;DR at the bottom !
What is Self-Determination?
Essentially, at hotlines and other crisis centers where volunteers or workers are taking calls from those who may be a threat to themselves or others, they have a rule that the caller is responsible for any decisions they make, even if that decision is to take their own life. These policies both acknowledge that the caller retains their right to make their own decisions, as well as protects the workers from potential lawsuits or accusations.
To paraphrase from an actual policy: workers are to explore the caller's feelings and build a relationship of trust so the caller can explore all options.
So that's what I want to talk about here! This policy is exactly how I approach beta reading, and it's also how I want my readers to approach beta reading my own work.
Self-Determination in Beta Reading
First, I want to clarify there is a difference between critique partners, alpha readers, and beta readers. All readers/writers may have different expectations for each type of reader. For me, this self-determination policy is perfect for beta readers, but would not necessarily be appropriate for critiques or alphas.
For more on this, see my posts on alphas vs. betas here, and on critique vs. betas here.
There are two main self-determination points that apply to beta reading:
We won't make decisions for you. We support the decision you make.
You are the expert [on your story]. Our advice or opinions are not important*
And this is exactly the mindset beta readers should approach a story with!
Many readers come at being betas with the mindset "I want to make this story as good as possible" and this is a great mindset, however we need to dig deeper if we want to have a good beta/writer relationship and actually make the story better.
And going deeper means betas acknowledging that the writer is the expert, the writer is the one making the decisions regarding the story, and that the readers should support those decisions no matter what. Yes, even if they disregard your comments. Yes, even if they change the story in a way you think is making it worse. Yes, even if you have more writing experience.
* I do want to clarify that obviously beta comments are important. But the point here is that in the grand scheme of things, the writer's opinion is the only one that matters, and what is important is all the betas' comments together, not yours individually.
Wait, Then Should I Not Give Advice?
Honestly? No.
Just like how the crisis hotline does not offer advice or solutions, beta readers shouldn't either.
However, there is a slight deviation from the self-determination policy that I want to make here:
In the crisis hotline, a worker would not give advice or solutions to the problem but would share resources for the caller to make solutions on their own. (This might be referring to a specialist or going to a hospital.)
However, they would ask before providing these resources. The same goes for beta readers.
Providing resources would depend on the writer. Some writers might welcome craft-based resources, and some writers would see it as offensive. (I know if I was on draft 4 and satisfied with my book and a beta sent me a link teaching show vs. tell, I would be pretty upset lol)
Beta readers are here to read and give comments, but this does not open the door for advice unless the writer has explicitly asked for it. If you're beta reading and giving any type of advice, whether it be how to fix a problem in the story, how to pitch/query/publish it, what changes should be made, etc — then you are breaking this self-determination policy and not truly being a beta reader. (instead, you are more resembling a critique partner)
So What Do I Do Instead of Advice?
Rather than advice or solutions, betas should be sharing reactions, ideas and analysis.
I know, the line between these and "advice" can be blurred. This might even come down to the way it's worded, and the way the writer interprets it.
"It might be interesting if you explored [x] more."
"I can't picture this scene, you need more description."
"I'm struggling to connect to this character."
"This character interaction directly parallels the one that happened earlier and it shows how the characters have changed."
"The first act is too slow. You should work on pacing."
Which of these are reactions? Which are ideas? Which are advice?
Some are clearer than others, and ultimately some people would probably disagree.
Personally, the only ones I would consider to be advice are 2 and 5. These go against the self-determination policy because they make the step from being about how the reader is experiencing the story, to how they would change it if it were theirs.
Because that's what this comes down to. The story belongs to the writer, not the beta.
Now this is a "do as I say not as I do" situation. As a beta, every book I read I do what I call my "two-page ramble" where I do analysis for 2-3 pages (literally) about the themes in the story what I would do if I were the writer. However, I preface it, saying that. I tell the writer ahead of time and even separate it from the rest of my comments so the writer doesn't even have to read it, if they don't want to. Some writers ignore it, and some say that even though it's not what they would do, it gave them ideas they hadn't otherwise considered.
And another caveat: some writers might be totally fine with readers giving advice! This is why it's important to have good communication between betas/writers. Before reading you should not only discuss what kind of feedback the writer is looking for, but also where the story is in its development, and what the writer hopes to achieve with the story.
Tips & Examples
The key to avoiding advice and sticking to analysis, reactions, and sharing general ideas really comes down to wording and the focus of the sentence. From my experience both with counseling and beta reading, I focus on these two things:
1. "I" statements
This keeps the focus of your comments to you and how you are experiencing the story. This helps stay away from "you should" type sentences, which are always leaning towards advice/solutions.
Examples:
I am struggling to follow this plot point
I don't feel connected to this character
I can't picture this scene
I was/wasn't expecting this to happen
I'm hooked/haven't put the book down in [x] chapters
I am losing focus/bored in this paragraph/scene
2. Open-ended questions
This comes straight from my counseling class as well as my friend who works at the crisis hotline. Open-ended questions typically start with "what" with the goal of getting the writer to think—analyze their own writing and story. If you want to be extra considerate, avoid "why" questions because these are often interpreted as offensive/attacking.
These questions essentially replace advice. Instead of saying "you should do [x]" these questions guide the writer to figuring out what to do on their own.
Because ultimately that should be the goal. Instead of "I want to help this writer make their story the best it can be" we should go further: "I want to help this writer figure out what they want to do with the story, to make it exactly the story they want to tell."
Essentially, if you feel like something is missing, or something needs work, instead of directly saying "this thing is bad, here's what you should do" you ask an open-ended question instead. If you feel like a character's interaction doesn't feel genuine, or you don't understand why a character is making a decision, you might ask "What is your character thinking in this scene?"
Another thing I personally do is combine these "I" statements and open-ended questions. This does two things: 1) pinpoints the exact feeling the reader is having/problem they see and 2) asks a question that will guide the writer to hopefully finding an answer
Combo Examples:
I don't see the point of this scene, and I'm bored. What was your intention for this scene before you wrote it?
I'm confused about this character. What influenced your character to make this decision?
I'm struggling to connect with this character. What does he want/what is his goal?
To show how these comments are better (and following self-determination), let's look at the first example.
If you are bored or don't see the point in a scene, you might be tempted to give advice and tell the writer to cut the scene entirely (or tell them what to change). However, this self-determination-based comment instead tells the writer that you are bored/disconnected (which is invaluable!) but instead of giving advice, asks a question that will hopefully lead the writer to analyzing the scene and figuring out what they want to do about it—because the truth is, the writer may choose to leave the scene as is, and that's fine. Cutting the scene might not make the story better. There are so many reasons a scene might feel slow or boring, and it's not the beta's job to fix it. It's the writer's.
TL;DR —
Self-Determination means that you do not make decisions for anyone other than yourself. This means regardless of what the writer decides to do with your comments, you support it. You do not know what is best for the story, or how to fix the problems it has.
The writer is the expert in their story. As a beta reader, you should approach with the mindset that you are here to share your reactions, ideas and analysis of their story so they can make it better.
Self-Determination means: No advice. No solutions. Engage, listen, ask questions, analyze, share reactions, and support the writer in whatever they choose.
(Unless the writer explicitly asks for it. This is why you should communicate beforehand!)
I just want to thank everyone who follows me because I am so grateful 😍 I can't believe a thousand people are hanging out here and seeing my random inspo posts.
I hope you have and continue to have a good time here <3
