Beta Reading as a Writer

Beta Reading

In the last post, I described why writers need beta readers. In this one, I’m going to talk about why a writer should beta read for other writers.

Beta reading requires only two things from you; reading the book and providing feedback.

I’m a Writer. Why Should I Consider Beta Reading?

I’m happy you asked! My answer to this threefold.

First, reading someone else’s work provides them with a service. Remember how you wanted people to beta read for you? Pay it forward. Also, as a writer, you’ve struggled with some aspects of writing. Share what you’ve learned to help another writer out.

Second, reading good writing will inspire you to elevate your own. Feel an affinity for the characters? Figure out what you like about them and make sure that you flesh out your characters too. Feel satisfied with the ending? Take a look at how they crafted their climax and denouement.

“Read a thousand books, and your words will flow like a river.”  ― Lisa See

Third, bad writing will help you identify things in your own writing that you need to work on. Get annoyed at the needlessly flowery descriptions? Make sure that your writing doesn’t get bogged down by purple prose. Rolling your eyes at excessive terms of endearment? Don’t make the same mistakes in your story.

Beta Reading: My Process

I start by asking the writer what they want from me. I don’t want to put hours into critically beta reading someone’s work if they are looking for a simple thumbs up or down on a story.  Some have a very clear understanding of where they struggle as a writer and will tell me to watch for stilted dialogue or character development arcs.

Some writers know that their book isn’t working, but they’re not sure about what they want. They’ll ask me to let them know if it reads well, or if I find plot holes. Some writers have specific questions they want me to answer. I find it easier to read and provide feedback if I know what the writer’s agenda is.

I don my reader hat after I have a general idea of what they’re looking for from me.

Putting on My Reader Hat

I like to get lost in the story so strange or unfamiliar words, clunky descriptions, or inconsistent story elements will jar me from being immersed in the writer’s world. I note these things while beta reading and try to dive back into the story.

Personally, I like to add brief comments to the document when these things jump out at me. This provides the writer with concrete examples of where the flow broke, inconsistencies in the narrative, weird words, and obvious repetition (we all cut and paste!).

I don’t make line edits because it would be too easy to fall into revision mode. This is THEIR story and regardless of how I would have approached a scene, the beta read is not about me or my writing style preferences. Furthermore, I certainly don’t want to change the tone of the story or their voice.

Like any reader, I take a mental note of clues, build pictures of the characters in my mind, and delight in ideas that are new to me, or even better, old ideas that are presented in a fresh and novel way. When the writer has done a good job with the ending, the clues fall into place, the characters choose the ‘right’ choice, and I’m left wondering which of those delicious ideas could be built on for a sequel. When the ending isn’t right, I’m left holding clues that went nowhere and annoyed by the characters who I’d invested time in.

Providing Feedback After Beta Reading

When I first began beta reading, providing feedback was the part that freaked me out. I wanted to help the writer with their story but was afraid of hurting their feelings. As a compromise, I provided vague feedback. Frankly, that feedback was a waste of my time and theirs.

My comfort in providing feedback was built while I enrolled in the 100 Day Book program through The Write Practice. Each week, we were responsible for posting our latest chapter, then reviewing and providing feedback for the other writers in our group.

The program suggested using the Oreo method of feedback. When using the Oreo method, you start by saying what you found positive, then provide constructive feedback, and end with words of encouragementment. I found the feedback I received SO useless that I became determined to provide thoughtful feedback to every writer I agree to beta read for.

I think my group had about 7 writers and I made it my mission to provide weekly feedback to all of them. It was a lot of work; the material and the strength of the writing varied greatly. At times, I struggled with particularly challenging submissions. However, I learned that with effort, you can always find something you appreciate in another writer’s work. Furthermore, providing genuine encouragement reminds you to treat the writer and their work with care and respect.

Providing thoughtful feedback has certainly taken more time than a generic “good job” or “I liked it”, but so far (fingers crossed) the feedback I’ve provided after beta reading has been well received.  When I take off my writer cap and don my reader had, I let myself be immersed in a story which reminds me why people read. Reading in a way that can help out another writer and improve my own writing? That’s a win-win slam dunk with cherries on top.

Have you been beta reading? What have your experiences been?

Header photo by Yuri Efremov on Unsplash

Have an opinion? Tell me more!

One thought on “Beta Reading as a Writer