Posted in writer life, writing advice

Giving Up vs Getting Smart

I think we’ve all heard the phrase “don’t be a quitter” at some point in our lives. Giving up has this negative connotation attached to it that I tend to agree with. Throwing your hands up in the air and saying “ta hell with it” because something is difficult is never the way to go. But what if you want to explore another path to the same destination?

That’s what I ran into with NaNoWriMo this year. The traditional goal is to write 50,000 words in the month of November. I decided to go non-traditional and set a goal of finishing my first round of rewrites on the manuscript I won NaNo with last year.

It was going to be a heavy lift. I had to remove a POV, add a subplot, and fix a litany of general storytelling issues. The plan was to take the detailed notes I’d compiled during the drafting process and edit as I went. I knew the story well enough to start at the top and make the needed changes as I read through it. At least, that’s what I thought.

A week and a half into NaNo, I realized I was creating more problems than I was fixing. So I had two options; press on to win NaNo and fix it all later, or stop and take everything back to outline to get it right the first time.

I’m very goal-driven. The thought of not reaching a goal is crushing to me, so the idea that I wouldn’t win NaNo was devastating. I reached out to a fellow author friend of mine for advice, and they pointed something out to me. The only reason I was hesitating was NaNo. Not getting through the first rewrite in November wouldn’t impact my publishing timeline. In fact, forcing myself to keep going could do more harm than good because of the additional rounds of self-editing I would need. I wasn’t giving up; I was getting smart.

They were right. Not reaching my goal, while unpleasant, didn’t mean I was a quitter. It meant I was learning more about my writing process and what works best. 

I learned that pantsing of any variety doesn’t work for me. Stopping a process that is not working in favor of a new one, does not mean you quit. It means you learned and adapted. As long as I keep working on my manuscript, I’m not a failure.

Changing course is not giving up. It’s allowing yourself to find the most direct route to your ultimate goal.

Posted in publishing, writing advice

SORTING THROUGH THE NOISE: HOW TO MAKE SENSE OF BETA READER FEEDBACK

The words are a giant blur. You’ve read them so many times that they have burned themselves into the grooves on of your brain. You know the story by heart. Every detail. Every phrase. And therein lies the problem.

We become so close to our stories that it’s hard to see the flaws. It doesn’t have to be on the page. We know the backstory, the nuances. It makes it nearly impossible for us to spot issues because we know it so well. That’s where beta readers come in. A beta reader is someone who reads an unfinished manuscript and provides feedback on the overall story, characters, and so on.

Beta reader feedback is as wide and varied as the individuals giving it. Each reader will each have their own preferences and styles. They will all find different things in your story, and the more betas you have, the more feedback you have to sort through. It can easily be overwhelming. Here are a few quick tips to help make sorting through the muck and mire a bit more bearable.

Give your betas specific questions.

If you ask someone to tell you what they think about the story. They are likely to give you vague answers. “I liked it.” “This character was cool.” While that can be fun to hear, it’s not going to make your story better. Limit the risk of unhelpful feedback by asking about specific characters, settings, scenes… whatever you’d like. Just make sure you provide them with a question that requires more than a one- or two-word response.

Look for common themes.

Somebody once told me that every book is somebody’s favorite. There is also a flip side to that. That same book will be someone’s least favorite. That’s why you can’t take a single comment too seriously. If Sally is the only one that doesn’t like the allegator chasing the protagonist out of the moat, maybe it’s okay to leave it there. But if the vast majority of your beta readers tell you John is hateful in a scene where you want him to be funny, you should probably look at rewriting it. Read through all the feedback. If something is mentioned more than twice, give it a closer look.

Take everything with a grain of salt.

The whole purpose behind this madness is to find the flaws in your writing. Yes, we all want everyone to love our work and tell us how amazing we are, but that’s not what we are doing here. If that’s all you want out of your betas, give your story to a relative you adore and let them give you feedback. They’ll tell you your great, but your story won’t get any better. Understand that you are asking for readers to point out the issues. They will find things they like too, but if that’s all they tell you about, then you are wasting your time.

Beta feedback is hard to manage. That’s all there is too it, but if you take a careful, well-constructed approach, you’ll come through it just fine.

What tips and techniques have you used to sort through the feedback you’ve received? Let us know in the comments below.