Beta Reader Etiquette: A Guide
Hello lovely writers, and welcome to another installment of Thinly Veiled Ranting by H. P. Bitterpants!
Just kidding.
I want to make it clear, actually, that nothing in this post is aimed at any of my lovely beta readers, critique partners, or generous friends and family. You all give your valuable time to give me feedback on my trashpanda of a novel, and I love and appreciate each and every one of you.
In searching out beta readers over the last couple of weeks, though, I've been stumbling across a few examples online of people who don't have good critique etiquette. This will probably be old potato for any of you who have recently taken a creative writing class where you swapped work, or are members of a writer's group. For those of you who could use a refresher course, though, here are some guidelines that will keep you at the top of your beta game.
1. Start with the positive.
Writers are, by and large, an insecure bunch. We're also arrogant, delicate, bullheaded, and fragile, and I know that's a bunch of contradictions, and you know they're all true. It's an act of courage for many writers to put their work in front of strange eyes, so be kind. If there is anything at all even a little bit good in the work you read, maybe start there. This will not only soothe the writer's anxious ego, it will ensure that she knows you actually read what she wrote and thought deeply about it. If you honestly can't think of even one good thing to say about the work, I suggest a simple, "Thanks for letting me read! I don't think I'm the audience for this. Good luck."
2. Be honest.
Flattery may be easier when you're worried about hurting someone's feelings, but ultimately, it's unhelpful. Telling a writer you loved the detailed descriptions when you actually found them purpler than a king's mellifluously flowing velvet cape, is a huge mistake. At best, you're not going to help the writer improve; at worst, you're going to come across as inauthentic or sarcastic. Give your honest reaction. Be as tactful about it as you like, but feel free to be as frank with your criticisms as you are with your praise. That's what the author asked for.
3. Don't "fix" it, just listen.
It's not your job to figure out how to fix the problems in the book. Don't put that on yourself! Your job is just to read, as a reader, and then point out where the problems are, as they occur to you. Figuring out how to fix them is a big, complicated, stupid, job, that somebody would need to get paid for. Most likely, your efforts won't even be properly appreciated, because writers are very attached to things like "writing the story themselves."
I know, silly writers.
This is especially true for changes that you think would improve the work, but that aren't plot holes or errors, and would dramatically change the entire thing. Things like, "This should be in third person," or "The main character would be more interesting as a man." Those decisions are subjective, and not really part of your feedback. You could say "I found it hard to connect this character's attitude and actions to her femininity," and while that would still be a pretty aggravating comment to receive, it would be better than you offering the "solution" of making her a man.
4. When possible, avoid sweeping generalizations.
One of the least useful pieces of feedback a writer can get is "This was boring." That feedback is boring. It's vague, it's general, and it does nothing to help the writer spot the places that made you feel bored. All it does is make the writer feel like crap in general. Do you need to worry about every little feeling of temperamental artists for whom you are doing a favor? No. But if you really want to be a beta reader, doesn't that mean you want to help improve the book? General reactions like this don't help anything. Neither does, "It was great, I loved it." These are the cop-outs you see when a beta reader is not truly committed to delving into what parts of the book made her feel that way, which probably, again, means she's just not the right beta reader for this project.
5. Beta what you like to read.
Beta readers are, first and foremost, readers. Don't beta something you wouldn't be interested in reading. If you're a lover of cozy contemporary mysteries, maybe don't offer to beta read someone's dark fantasy. If you only like hard science fiction, don't try betaing a soft YA sci-fi. Not everyone in the world is going to have the same taste, and the range of writing styles and genres out there is truly staggering. No matter how many times you tell the Horror writer to take it easy on the gore, he's never going to write you that contemporary romance you secretly wish you were reading. No matter how eloquently you plead for more personal connection to the protagonist in that sweeping fantasy epic, it will never give you the intimacy of first-person. You, as a reader, have your preferences and your pet peeves. So be real about that! Ask questions before you agree to beta. Be selective in which projects you look at. Ask for content warnings, or about the presence of specific triggers or pet peeves. If, at any point in reading, you come across a dealbreaker you hadn't thought of ahead of time, stop reading and let the writer know what it was. This may or may not change the thing in the book, but what it will definitely do is save you and the writer both wasted time and effort, because you're just not a match. And that's ok! Not everyone can be.
A note for writers--
If you're processing beta reader feedback right now and having trouble coming to terms with some of it, don't panic. It's hard to be criticized, and it's hard to know which criticisms to listen to. The golden rule I'm using for my own work is, "Does this advice improve the story I'm telling?" Some advice doesn't improve, it only changes. Some advice would make it into a different story entirely. If someone just doesn't like the story you're telling, they may not have much helpful advice for how to make that story better. That's ok. Not everyone is going to like what you write, and not everyone has to. There are so many different tastes in this world! If the canon of classics has room for both Faulkner and Hemingway, there is room for your book, and the people who would never read it. Just make it the best that you can, and don't worry about pleasing everyone.
Thanks for reading! If you're interested in learning more about becoming a beta reader, finding beta readers, editing, or writing in general, subscribe by email and/or follow me on Facebook, Instagram, and Twitter for updates.
What I'm reading this week:
"The Gentleman's Guide to Vice and Virtue" by Mackenzi Lee
"The Know-It-All" by A.J. Jacobs (I swear, it's taking me longer to finish the book than it took him to read the Encyclopedia!)
Song Recs:
I've Got This Friend
This is On You
I Like (the Idea of) You
Just kidding.
I want to make it clear, actually, that nothing in this post is aimed at any of my lovely beta readers, critique partners, or generous friends and family. You all give your valuable time to give me feedback on my trashpanda of a novel, and I love and appreciate each and every one of you.
In searching out beta readers over the last couple of weeks, though, I've been stumbling across a few examples online of people who don't have good critique etiquette. This will probably be old potato for any of you who have recently taken a creative writing class where you swapped work, or are members of a writer's group. For those of you who could use a refresher course, though, here are some guidelines that will keep you at the top of your beta game.
1. Start with the positive.
Writers are, by and large, an insecure bunch. We're also arrogant, delicate, bullheaded, and fragile, and I know that's a bunch of contradictions, and you know they're all true. It's an act of courage for many writers to put their work in front of strange eyes, so be kind. If there is anything at all even a little bit good in the work you read, maybe start there. This will not only soothe the writer's anxious ego, it will ensure that she knows you actually read what she wrote and thought deeply about it. If you honestly can't think of even one good thing to say about the work, I suggest a simple, "Thanks for letting me read! I don't think I'm the audience for this. Good luck."
2. Be honest.
Flattery may be easier when you're worried about hurting someone's feelings, but ultimately, it's unhelpful. Telling a writer you loved the detailed descriptions when you actually found them purpler than a king's mellifluously flowing velvet cape, is a huge mistake. At best, you're not going to help the writer improve; at worst, you're going to come across as inauthentic or sarcastic. Give your honest reaction. Be as tactful about it as you like, but feel free to be as frank with your criticisms as you are with your praise. That's what the author asked for.
3. Don't "fix" it, just listen.
It's not your job to figure out how to fix the problems in the book. Don't put that on yourself! Your job is just to read, as a reader, and then point out where the problems are, as they occur to you. Figuring out how to fix them is a big, complicated, stupid, job, that somebody would need to get paid for. Most likely, your efforts won't even be properly appreciated, because writers are very attached to things like "writing the story themselves."
I know, silly writers.
This is especially true for changes that you think would improve the work, but that aren't plot holes or errors, and would dramatically change the entire thing. Things like, "This should be in third person," or "The main character would be more interesting as a man." Those decisions are subjective, and not really part of your feedback. You could say "I found it hard to connect this character's attitude and actions to her femininity," and while that would still be a pretty aggravating comment to receive, it would be better than you offering the "solution" of making her a man.
4. When possible, avoid sweeping generalizations.
One of the least useful pieces of feedback a writer can get is "This was boring." That feedback is boring. It's vague, it's general, and it does nothing to help the writer spot the places that made you feel bored. All it does is make the writer feel like crap in general. Do you need to worry about every little feeling of temperamental artists for whom you are doing a favor? No. But if you really want to be a beta reader, doesn't that mean you want to help improve the book? General reactions like this don't help anything. Neither does, "It was great, I loved it." These are the cop-outs you see when a beta reader is not truly committed to delving into what parts of the book made her feel that way, which probably, again, means she's just not the right beta reader for this project.
5. Beta what you like to read.
Beta readers are, first and foremost, readers. Don't beta something you wouldn't be interested in reading. If you're a lover of cozy contemporary mysteries, maybe don't offer to beta read someone's dark fantasy. If you only like hard science fiction, don't try betaing a soft YA sci-fi. Not everyone in the world is going to have the same taste, and the range of writing styles and genres out there is truly staggering. No matter how many times you tell the Horror writer to take it easy on the gore, he's never going to write you that contemporary romance you secretly wish you were reading. No matter how eloquently you plead for more personal connection to the protagonist in that sweeping fantasy epic, it will never give you the intimacy of first-person. You, as a reader, have your preferences and your pet peeves. So be real about that! Ask questions before you agree to beta. Be selective in which projects you look at. Ask for content warnings, or about the presence of specific triggers or pet peeves. If, at any point in reading, you come across a dealbreaker you hadn't thought of ahead of time, stop reading and let the writer know what it was. This may or may not change the thing in the book, but what it will definitely do is save you and the writer both wasted time and effort, because you're just not a match. And that's ok! Not everyone can be.
A note for writers--
If you're processing beta reader feedback right now and having trouble coming to terms with some of it, don't panic. It's hard to be criticized, and it's hard to know which criticisms to listen to. The golden rule I'm using for my own work is, "Does this advice improve the story I'm telling?" Some advice doesn't improve, it only changes. Some advice would make it into a different story entirely. If someone just doesn't like the story you're telling, they may not have much helpful advice for how to make that story better. That's ok. Not everyone is going to like what you write, and not everyone has to. There are so many different tastes in this world! If the canon of classics has room for both Faulkner and Hemingway, there is room for your book, and the people who would never read it. Just make it the best that you can, and don't worry about pleasing everyone.
Thanks for reading! If you're interested in learning more about becoming a beta reader, finding beta readers, editing, or writing in general, subscribe by email and/or follow me on Facebook, Instagram, and Twitter for updates.
What I'm reading this week:
"The Gentleman's Guide to Vice and Virtue" by Mackenzi Lee
"The Know-It-All" by A.J. Jacobs (I swear, it's taking me longer to finish the book than it took him to read the Encyclopedia!)
Song Recs:
I've Got This Friend
This is On You
I Like (the Idea of) You
Comments
Post a Comment