The beta comments on my latest draft of Summer at the Crossroads have arrived. My readers did a stellar job, as I expected. They read the manuscript thoroughly, enjoyed the concept, liked my writing style, and gave me great feedback.

image credit: Microsoft clip art

image credit: Microsoft clip art

Once the beta comments come in, a writer must decide which of them hit the mark and which can be ignored. The book is the writer’s vision and story, no one else’s. This is a good time to again ask the question, “Who am I writing for?” Continue reading

Either I’m Getting Stronger Or The Molasses Is Getting Thinner

Even the President of the United States has to put up with unsightly public work near his home. There’s no particular reason for this photo with this post. But the juxtaposition struck me when we were there last Saturday. Well, not at the White House, but in DC.

With a title like that, you might think I’ve lost my marbles. Wait, that might be the subject of another post. Let’s try again.

Maybe you’ve seen my recent comments about revisions feeling like I’m slogging through a sea of molasses. For those of you unfamiliar with the substance, it’s a thick, brown, gooey syrup made from the by-products of sugar-making. I’m not particularly fond of it. Continue reading

Academic Writing Gets Its Revenge

Remember me? Dr. Professional is the name. Academic Writing is my game.

Back in February, I posted about keeping my “academic” writing out of my fiction. And before I sent Draft 2 of Death Out of Time for its beta read, I went through the manuscript with that in mind. I did searches for passive construction, weak verbs, loooong sentences, and the like. These are the classic elements of my “professional” writing. They are de rigueur in archaeological reports. In fiction? The kiss of death. I was confident I had slain the academic beast in the manuscript.

And then the review comments came back.

Bless Kate’s heart, she suggested that if some of my scenes were written in a style used in science fiction, then I should ignore her comments. But she noted that several scenes had no point of view (POV).

That’s right. No POV. Dialogue dominated some scenes. Descriptive passages ruled in others. But the reader wasn’t in any character’s head. The scenes were “pointless.”


I wish I could say, “Oh, yes, this is classic sci-fi writing. There’s nothing wrong with it.” But that would be a lie. A big one. The sad truth is academic writing was still entwined in my manuscript. Lying low, where it thought no one would find it.

And it was snickering, knowing I had missed it. I’d forgotten one of the major characteristics of archaeological writing. You see, few of us introduce a “point of view” into our writing. First person? Highly discouraged. We say things like “The data suggest” not “I think.” Nearly everything is presented as a straightforward recitation of facts and data.

The closest we come to a POV is when we present the results of the study. But even then, the construction is passive and oblique, like “Based on the results presented above, the assemblage represents repeated, seasonal occupation during the Late Archaic period, most likely during the summer months.”

I’d bet the scenes that Kate marked would catch your attention. Fiction writers, like Kate, would jump on the lack of POV. Fiction readers, even if they didn’t call it POV, would know the scenes were awkward. You’d rightly ask, “What’s going on here?” Or, “What’s the point of this scene?”

So my list of things to check in future drafts of this and other manuscripts keeps growing. Hopefully that means Draft 2 of future novels will be a heck of a lot better than Draft 2 of Death Out of Time. If I’m going to make it as a writer, they’d better be!

How about you? Have you ever been sure you got rid of something, only to have it raise its head again like kudzu or multiflora rosebushes in the spring?

Your Moment of Spam

The spam queue hasn’t been too interesting of late. But the other day, this one did appear.

Hello there, just became alert to your blog through Google, and found that it’s truly informative. I am going to watch out for brussels. I’ll be grateful if you continue this in future. Many people will be benefited from your writing. Cheers! — Do they mean the Belgian city? Or will sprouts fall from the sky like hail, coating everything in bitter mini-cabbage slime? And do they mean they’d be grateful if I would watch out for brussels in the future? I’m sorry, but I don’t have the time—or inclination! 😉

Beta Reading—Part 4

This is the final post in a four-part series on beta reading. If you missed the earlier entries, you can catch up with these links to Part 1, Part 2, and Part 3.

So the beta reader has sent you his comments. Your ego has recovered from the blow, and you’ve realized the reader made some excellent points. Your story will be better if you incorporate his suggestions. Ideas are coming to you about how to revise the characters and plot. (If you’re lucky, your characters will help you with the revisions.)

Is it time to start the rewrites and move on with your life? Sort of. In a good beta reading partnership, the relationship doesn’t end when the comments are sent in.

Now is a good time to talk with (or email) your beta reader. Let him know how helpful his suggestions and comments are. Tell him your ideas for the revisions. Ideally, the relationship continues and you can exchange further drafts, future works, and bounce ideas off each other. In the best-case scenario, you both enjoy each other’s writing and look forward to seeing the final version take shape and the birth of your next works.

Don’t abuse the relationship, though. Don’t email your beta reader every day asking him to read your latest revised or new scene. Wait until you have a few chapters or sections done. And then politely ask if you can send them at some point. By now, of course, you know to reciprocate when your beta reader asks for your help.

To wrap up the series, I’ve created a short “do’s and don’ts” list as a quick guide for writers and readers. I’ll create a separate page with links to these posts for easy reference. It should be up soon, and I’ll let you know when it’s ready.

The Writer’s Guidelines

  • Determine if you need a beta reader. Unless you plan to publish, this may be more critique than you need.
  • Be sure you’re ready. Beta reader comments can be extensive and cause distress.
  • Don’t send a first draft for a beta read. Wait until at least the second draft.
  • Put the manuscript aside for two or three weeks before you send it to the reader. This will help distance you emotionally and help you be objective when comments come back.
  • What do you want from the review? Make these concerns clear to the reader.
  • Set a realistic timeframe for the beta reader.
  • Determine how you will reciprocate with the reader.
  • Be prepared for the feedback. There will be suggestions for improvement. This is what you requested.
  • Remember that respectfully worded suggestions are not personal attacks on you or your work.
  • You might not incorporate all of a beta reader’s suggestions. But make sure you don’t ignore good ones that would improve your work.

The Beta Reader’s Guidelines

  • Make sure you’re ready to beta read. You must be objective and leave your personal opinions out of the review.
  • Understand what the writer seeks from the review. Do you know the genre and completeness of the manuscript? (second draft? fifth?)
  • Read the manuscript at least twice.
  • Be tactful and diplomatic with your comments. It is not acceptable to be rude, aggressive, or insensitive. Phrase them as suggestions as much as possible.
  • Be sure to address all the areas the writer noted for you.
  • Begin and end with positive comments about the work.
  • Let your comments sit for a day or two before you send them. Reread them and make sure they are tactful and diplomatic.

And there you have the basics of beta reading. I hope the series has helped you understand the process and see how such a critique should work. It can help you make your work the best it can be. Go into it prepared, and you will come out a better writer with an improved story.

If you have any questions or additional tips, please feel free to ask them or add them in the comments!

I didn’t have time to pull together some additional resources for this post. I’ll try to add them to the “Beta Reading Guidelines” page when I can. Next week, I’ll get away from the educational series and do something different.

Beta Reading—Part 3

Over the last two weeks we’ve covered an introduction to beta reading and what the writer and beta reader need to understand before beginning the work. Today, we get down to the nuts and bolts of what the beta reader should (and shouldn’t) do and how he should present his critique. We’ll also look at what the writer should expect from the review. Instead of beginning with the writer, this post starts with the beta reader.

What the Beta Reader Should Do

Read the manuscript at least twice. On the first read, note general feelings or problems with the manuscript. For example, does the opening scene leave you struggling to figure out who and where the characters are? Are too many characters presented in the first chapter? Did a character suddenly appear with the protagonist at noon while two pages ago she was across the country two hours earlier? Your questions might be answered as you read more. After all, a writer shouldn’t reveal everything in Chapter 1. But if you’re repeatedly taken out of the story by incomplete or confusing descriptions, the writer probably hasn’t provided enough information.

With the second and later reads, focus on the areas the writer asked you to check. If she’s concerned about mixed point of view (POV), read carefully and note where you encounter it. If she’s worried that her characters are flat, see if she’s right. If you think they are, be specific as to why they’re dull. Are they too perfect? Are they risking nothing by their actions? Is the antagonist too evil and gives everything away?

If you notice a problem the writer didn’t ask you to address, do point it out—tactfully and diplomatically. (We’ll come back to tact and diplomacy soon.) Maybe she didn’t ask for help with POV. But you notice she’s not only switching POV within a scene but also within a paragraph. It’s best to stick with one POV per scene, although some writers successfully break this rule. However, if her shifts mean you can’t follow the story, or you don’t think they have the desired effect, let her know. (And changing POV within a paragraph is never good).

Do tell the writer when you think a scene is good or a character resonates with you. The critique will be stressful on her. She needs some positive reinforcement. (You will, too, when someone critiques your manuscript.) Otherwise, the writer can easily think her work is garbage. So, did a character make a joke and you thought it was funny? Say so! Did a scene make you tear up in empathy with the characters? Let the writer know this. Begin and end your comments with some of these positive points.

It’s okay to let the writer know your emotional responses to a character or scene. But don’t confuse this with your personal views on the subject or your personal preferences for writing style or content. You aren’t writing the book—she is. As a writer, I want to know what emotional response the reader had and if it matched my intentions. Did a character’s action leave you angry? Let the writer know. If that’s her desired reaction, she’ll know she got it right. But if she wanted you to feel sorry for him, she needs to think about her word choices—and consider the possibility that you simply misunderstood the scene. That happens.

It’s okay to make a few personal observations, such as your experiences with something in the book. But don’t form your critique around them, and do let the writer know these are “personal asides.”

Be specific with comments so the writer understands what you mean. “This character bores me” doesn’t give her much to go on. Tell her why he bores you. It will help her fix the problems. Something like this is more helpful. “Tom doesn’t seem to have any flaws. He never has a bad thought about anyone, even the man who killed Tom’s father before his eyes and stole his horse. He doesn’t come across as a real person in his situation should.”

If a passage confuses you, explain why. “Tom has helped his friends throughout the first 15 chapters. There was no good reason for them to abandon him when he passed out at the bar after his very first taste of alcohol, and yet they did. Why? If there’s a reason, the reader needs to know it. If there isn’t one, you might want to reconsider the friends’ reactions.”

Be tactful and diplomatic with your comments and recommendations for rewrite/revision. I can’t emphasize this enough. This is an area where we shouldn’t be too direct or “action-oriented” in our word choices. Phrase your comments as suggestions rather than instructions or complaints. Comments like, “you keep dumping too much backstory at the beginning of every chapter” or “stop changing POV in every scene” may be accurate. But they generate intense feelings of negativity and depression in the writer. Take a softer tone. For example, “Readers might skim over the first part of your chapters to get to the action. You might want to rework some of the backstory elements into a character’s internal thoughts or a dialogue exchange and spread them through the story.”

Wait a day or two after writing your comments before you send them to the author. Then reread them. How would you feel if you received the comments phrased as they are? Could they be more tactful? Are they clear? Have you provided enough encouragement and pointed out areas that are working well?

What the Beta Reader SHOULD NOT Do

Never make insensitive or inflammatory comments. Beta reading and critiques should never be personal attacks on the work or the writer. If this happened to you, I’m sorry. But it’s not how things should be done. Personal or mean-spirited attacks are not a rite of passage into the writing world.

Don’t limit your comments to those of the “here’s what needs work” category. Begin and end your comments with things you enjoyed and thought the writer did well. You would need to hear it. So does she.

Don’t take it personally if the writer doesn’t incorporate all of your suggestions. Maybe five other people loved something you hated. She has to make the final call on what works.

What the Writer Should Expect

You should receive both positive and “areas for improvement” comments. Remember, you have asked for an honest critique of your draft. Don’t ask for a beta read if you think your work is perfect as is. There is always room for improvement. Well-phrased and carefully thought out suggestions for improvement are not personal attacks on you or your writing. Your beta reader is trying to help you write the best story you can.

You will feel some “negative” emotions when you read the comments—anger, hurt, depression. That’s normal. That’s why I said make sure you’re ready for this in Part 1. It gets easier as you gain more experience, but it always stings. Go ahead and console yourself with chocolate or a glass of your favorite alcoholic beverage. But remember—you wanted an honest critique, and that’s what you should get.

Put the comments aside for a few days after you’ve read them. Don’t reply to the reader at this point except for a polite “thank you I got your comments, and I’m going through them.” You’ll stew over them. You’ll think the reader missed the point completely. You’ll feel defensive about your writing, your story, and why you told it the way you did. Under no circumstances should you dash off a knee-jerk email to the beta reader or a blog post about the terrible beta reader.

You’ll soon catch yourself thinking about ways to address the beta reader’s points. You’ll realize that there is something to his comments. Now you can look at the manuscript and his comments again. And, with a calmer eye, you’ll see the validity of most of the comments. Most—not all. It’s unlikely that everything he said will apply. Maybe he misread a paragraph and the resulting comment really doesn’t matter. If he doesn’t read your genre, a point that confuses him may be clear to regular readers.

But a good beta reader will make many good points. And you need to think about them. They’ll help you make the story better. And if your goal is publication, whether traditional or independent, your story should be as good as you can make it. That’s the only way to build an audience who will read your future publications.

Finally, don’t expect the beta reader to “fix” the problems for you. He might offer suggestions, but he’s not a ghost writer. You have to do the hard work of rewrites for the next draft. Remember, it’s your book, not his.

Next Time

In the final post we’ll go over what happens after your beta reading experience—because the end of the critique should not be the end of the relationship. I’ll also summarize the main points for the writer and beta reader to remember. If I’m really organized and have the time, I’ll include some links to helpful posts and websites.

If you have any suggestions for those links or points to hit in the final post, please feel free to add them in the comments!

Beta Reading—Part 2

Last Saturday, I introduced the concept of beta reading and initial questions you should consider before diving into it. If you missed that post, you can catch up here. If you think you’re up for the challenge, keep reading!

Today, I want to focus on the importance for both the writer and the beta reader to understand the goals of the work. If you are exchanging manuscripts and will beta read each other’s works, you need to understand both sides of the process. Continue reading

Beta Reading—Part 1

Beta reading has been a hot topic on my blog and others. Most, my own included, have focused on specific aspects rather than the entire concept. I thought a short series of posts that define beta reading and lay out some guidelines for both the writer and beta reader could be useful.

When done well, a beta read can help take a writer’s manuscript from the slush pile to the bestseller list. When mishandled, it can shatter a writer’s confidence and drive him away from an activity he loves and should still be doing.

Although beta readers don’t have to be writers, this series of posts is designed for writers who want to “beta read” with another writer. The guidelines for beta readers, however, apply to non-writers as well.

Today’s post, and those on the next three Saturdays, will cover this topic. I hope to provide a clear understanding of this important act that requires extreme tact, respect, and sensitivity. Continue reading