At the risk of repeating myself, part III: hot, hot, hot. And had I mentioned it was warm?

Ah, the gentle days of April, when the daffodils begin dancing, steel-blue storm clouds loom on the horizon, and the neighbors finally get around to burning the long-lingering remnants of their Christmas tree. Why, it seems only a few weeks ago that the locals took down their holiday lights. Perhaps because the neighbors on the other side of us still have theirs up.

Hey, winters are dark in Seattle. So, apparently, are early springs. We could all use a little extra twinkling on the block.

To set the minds of those of you who have been clutching your chests in anticipation of a house fire at ease: no, my neighbors didn’t torch it in their fireplace; I shot this photo at their fire pit. I had been prowling the environs, searching for an image to illustrate our topic du jour. I couldn’t be happier, really. What, after all, would remind a self-editing writer more of structural repetition — the phenomenon of a writer’s falling in love with a certain kind of sentence and consequently over-using it throughout a manuscript — than dry fir needles consumed in flame?

“But Anne,” redundancy enthusiasts across the writing world protest, “I don’t get it, and until I get it, I’m not going to stop repeating words, phrases, and imagery on the page. So I challenge you: how are these two apparently unrelated things akin?”

That’s a perfectly legitimate question from a writerly point of view, repetition-huggers, but from an editorial perspective, the connection is self-evident: Christmas comes but once a year. So does one’s birthday, generally speaking. No matter how much one might enjoy celebrating either, it’s not reasonable to expect others to keep bringing you presents three times a month just because you claim today, tomorrow, and next Thursday that it’s one or the other.

Too abstruse? Okay, what about this one? No matter how brightly that fir branch burns, it is pretty only for a moment. Ashes have their charm, of course, but trying to rekindle them is a futile endeavor.

Too heavy-handed? Okay, metaphor police, try this one on for size: the branch you see above looked very nice on the Christmas tree. It is also attractive in the photo, in a different context. But had the neighbors set the Christmas tree in the fire pit without setting it ablaze, passersby would have murmured, “Hey, don’t they know Christmas was months ago?”

Starting to get the picture now? Yes, the fir was lovely covered in ornaments; we all saw that through your window. It was less pretty in February. And it was downright droopy in March. Today, in April, it’s nothing but a fire hazard.

That doesn’t mean, though, that a creative person couldn’t make it pretty again, but you’re going to need to do more than just stand it up and admire it as you did before, neighbor. You’re going to need to put some effort into transforming it. It’s going to need to appear to be fundamentally different.

What do you think? Have I have milked that image for all it’s worth yet? No? Okay, in case I’ve been too subtle for the literal-minded: after using a pet phrase once, give it a rest, will ya?

I see you smirking smugly, those who believe that you never repeat yourselves on the page. “Darned good advice, Anne,” you say warmly, “but not at all applicable to me. Every syllable I commit to paper is 100% original, both in the history of literature and within my own opus.”

I applaud you if that is actually the case, smug smirkers, but if this is your first manuscript, it probably isn’t: most writers have go-to phrases, metaphors, and even sentences that they trot out at least every hundred pages or so, whether they realize it or not. And don’t even get me started on how often manuscripts repeat lines of dialogue.

We saw why last time: if phrasing or an insight sounded good the first time around, it tends to sound good the second, third, and fifty-seventh as well. And if you’re like most writers new to the game, you probably have been writing your book over an extended period. Are you absolutely positive that the great sentence you wrote yesterday is entirely different than the one you wrote six months ago? Do you truly remember every syllable you wrote back in 2008?

No longer so sure, are you? Here’s the best way to recapture that peace of mind I so rudely disrupted: sit down and re-read your submission IN HARD COPY, IN ITS ENTIRETY, and, even better, OUT LOUD, just to double-check.

It’s in your best interest to do this before you send it off to an agent, editor, or contest judge. And certainly before you smirk smugly at the rest of us.

But definitely before you submit, because, trust me, even if that simile you adore on p. 22 does not recur until p. 384, chances are better than even that our old pal, Millicent the agency screener, will notice and deplore the repetition. So will her boss, the agent of your dreams, and even if it gets past both, the editor to whom the agent shows your manuscript will almost certainly catch it.

Why am I so sure of that? Well, submissions and contest entries so often contain substantial word and phrase repetition; one does not have to read professionally for very long to begin to build an aversion to the sight of it — and an eye that zeroes in on it.

Human nature, I’m afraid. The more one wants to look away from a tragedy, the more one is compelled to look.

To most of us who read manuscripts for a living, a manuscript that keeps recycling sentence structures, pet phrases, or even individual words might as well be covered with flashing neon signs. Don’t believe me? Okay, here is a page stuffed to the gills with one of the more common types of repetition, the over-use of proper nouns in general and character names in particular. I’ve made the image a trifle larger than usual, to render the pattern easier to spot.

In fact, you don’t even have to read the text to notice it: stand up, back away from your computer until you can’t make out individual words, then walk slowly toward the screen until individual words start to come into focus. Ready, set — observe!

Let me take a wild guess: on your return trip, all of those Js and Ps were the first thing you saw, were they not? I hate to break it to you, but a sharp-eyed pro like Millicent would have had that reaction scanning the page at a normal reading distance.

Well might you gulp. Once you got close enough to read the page in its entirety, I’m guessing that it did not seem all that repetitious to you. That’s fairly normal for writers who have not yet enjoyed the traumatic scrutiny lambasting benefit of professional feedback: for some reason my extensive editing experience leaves me powerless to explain, most aspiring writers seem to believe that if the word being repeated is a name, it’s impossible to over-use it.

They are, in a word, wrong. We shall see why in a bit, once your eye has had a chance to develop.

In the meantime, let’s take a gander at how the visual pattern problem is exacerbated if the sentence structure is also repetitious. To render this tortured page even more likely to annoy our Millie, I’ve selected a common construction in the passive voice.

Again, back up from the screen, then slink forward. What does your eye notice first?

Starting to see more than one pattern? I hope so: your eye might have been drawn to the repetition of was or one before or after the capital letters in the proper nouns, but now that you’re looking for it, this page seems to contain a smaller variety of words than our first example, right?

Even if the repeated words did not jump out at you, you probably noticed that this version was quite a bit less amusing to read. I wouldn’t be at all astonished if you were tempted not to read it all the way to the end; Millicent would have had more or less the same reaction.

Why? Well, although the page was not in fact made up entirely of it was X and it was as though sentences, it certainly began to feel like it by halfway down the page, didn’t it? If you were a Millicent trying to work her way through a pile of 247 submissions before your hot date tonight, wouldn’t you at least consider shouting, “Next!” and moving down the stack?

Some of you were doing the math, weren’t you? Yes, doubters, it would in fact be possible for Millie to get through that many submissions — if, say, her agency asks queriers to send the first five pages with a query — in a single day. It would be a long day, admittedly, but if she limited herself to just a couple of minutes with each, setting aside those with promise until she had more time to attend to them, she actually could plow through that stack quite expeditiously.

Because where are most submissions rejected, camper? Chant it with me now: on page 1.

So if you were occupying her desk chair and spotted a page 1 as wording-repetitious as that last example, would you continue reading for a few pages, hoping that the vocabulary level will rise? Or would you thankfully conclude that you don’t need to spend much time on this one and reject it in 32 seconds, so you could afford to read page 2 of a submission with more promise?

Don’t tell me what you would want Millicent to do if it were your submission; we’re talking principle here. And no, she can’t spend an extra hour screening today; that hot date involves a quick drink, a play, and a late dinner. You wouldn’t want her to miss the curtain, would you, much less that post-work drink?

Okay, maybe you would, but seriously, most folks that read for a living would have a similar reaction to that page 1, even if they haven’t had a truly hot date since 1982. A trained eye would be drawn immediately toward those patterns — and thus away from other aspects of the text a savvy writer might want a professional reader to notice instead, such as the compelling storyline, the interesting characters, and/or the overall beauty of the writing.

Weren’t expecting that twist, were you? You’d better sit down, because the news gets worse: because repetition in general and structural repetition in particular are so very common in submissions, Millicent and her ilk not only find it distracting; they tend to regard it a symptom of both a small authorial vocabulary and weak writing. So you might want to think twice about incorporating much repetition into your preferred authorial voice. Especially in your opening pages — which, lest we forget, folks who screen manuscripts for a living are prone to regard, rightly or not, as representative of the writing in the rest of the manuscript.

Hey, I told you to sit down.

Now that you’re already depressed into a stupor, let’s get down to the nitty-gritty: if the sentence structure and vocabulary on page 1 don’t show much variation, Millicent’s unlikely to keep reading until page 50 to find out whether these traits are consistent features of the author’s chosen voice. Heck, she probably won’t turn to page 2 to confirm that suspicion.

It’s hard to blame her, given the provocation. As we saw in the second example, even when the word choices are diverse enough to keep things moderately interesting, it’s simply more tiring to read the same kind of sentence over and over than to read text where the form varies more.

That’s true, incidentally, regardless of the subject matter. Even an inherently fascinating topic can quickly be rendered stultifying by the simple expedient of writing about it in structurally similar sentences. Repetitive phraseology can render even the most exciting, conflict-ridden scene quite a bit less nail-biting than its activity level should dictate. That’s true, surprisingly, even if the chosen structure is quite complex.

Pop quiz to evaluate your eye’s progress: which bugged you more in that last paragraph, my reuse of the that’s true + adverb structure, or the recycling of even? By this point, I would hope that neither escaped your attention.

Let’s observe the soporific effect of a more complicated repeated structure in action. So I don’t plunge all of you into a deep, refreshing slumber, I shan’t subject you to an entire page of it, but merely a quick excerpt.

Obviously, no one deliberately plans to crash a motorcycle into the side of a cross-town bus, but that is precisely what Barnaby did. Fortunately, he was wearing his inflatable jumpsuit, saving him from significant injury, but clearly, his morning was not going to be a smooth one. Resignedly, he collected his scattered belongings, including the small thermonuclear device he later planned to smuggle stealthily into the state dinner, but he could not resist vehemently cursing under his breath.

Call me a zany idealist, but I believe in my heart of hearts that a scene with stakes this high could have been written about in a slightly more compelling manner. There’s more to good storytelling than just getting all of the facts down on the page, after all. To see why, we need look no farther than the early reader books of our youth.

You know the type, right? See Spot run. See Spot bite Dick. See Dick shiv Jane. Stab, Dick, stab.

Dull, from an adult perspective, weren’t they? But dull with a purpose: part of their point was to encourage new readers to recognize letter patterns as particular words. Varying the sentence structure enough to render the insipid story interesting to more advanced readers would merely have distracted from the task at hand.

So we were treated to the same sentence structure for what seemed like the entire book. I have a distinct memory of taking my kindergarten copy of FROG FUN home from school (Hop, frog, hop. Hop, hop, hop: hardly Thackeray), reading a two pages of it to my father, and both of us deciding simultaneously that no self-respecting human being would keep slogging through that much narrative repetition. And where was the character development? Pages on end about frogs, and the reader could not tell one from the next. What were their individual hopes, their dreams, their personal preferences in lily pads?

He wrote a very amusing little note to my teacher about it. Suffice it to say that my teacher quickly learned to send me to the library for alternate reading material. And stopped teaching kindergarten shortly thereafter. I’m told that she still winces whenever she sees a frog.

It’s even easier to make Millicent wince — at any given moment, her to-read pile overfloweth with submissions that, if not as word-repetitious as FROG FUN, have fairly obviously not been carefully revised with an eye to sentence variation. That’s a pity, because when a professional reader sees a manuscript that uses the same sentence structure or the same few verbs use over and over, the specters of Dick, Jane, and Spot seem to rise from the page, moaning, “This is not very sophisticated writing!”

Why, you gasp? Well, when one’s eye is trained to note detail, it’s doesn’t take much redundancy to trigger a negative reaction.

In fact, a good professional reader will often catch a repetition the first time it recurs — as in the second time something is mentioned in the text. It’s not unheard-of for an editorial memo to contain a livid paragraph about the vital necessity to curb your inordinate fondness for phrase X when phrase X shows up only three or four times in the entire manuscript.

As in over the course of 382 pages. Had I mentioned that we pros are trained to be extremely sensitive to redundancy?

Imagine, then, how much more annoying they find it when every third sentence begins with a structure like, Blinking, Sheila backed away or George was…” or the ever-popular, As Beatrice was doing X, Y happened.

That last one caught you a bit off guard, didn’t it? I’m not entirely surprised: if an alien from the planet Targ were to base its understanding of human life solely upon the frequency with which protagonists in first novels do something as something else occurs, it would be forced to conclude that humanity is doomed to perpetual multitasking. Either that, or it would surmise that the space-time continuum is somehow compressed by the mere fact of someone’s writing about it.

Oh, you laugh, but how else could the poor visitor to our solar system possibly interpret a passage like this?

As Monique turned the corner, she spotted Clarence. He dodged sideways as she came up to him. While he was looking for someplace convenient to hide, she calmly unearthed a crossbow from her purse.

Aiming, she cleared her throat. “The jig’s up, Clarence.”

That’s quite a bit of activity happening simultaneously — and quite a few logically similar sentence structures shouldering one another for prominence. But contrary to popular opinion amongst aspiring writers, the mere fact that two things occurred at the same time is not particularly interesting to most readers. Unless the simultaneity of the motions in question is crucial to the reader’s understanding what’s going on, as and while can be awfully easy to overuse.

How so? Well, let me put it this way: if our imaginative little run-in with the Targian had not tipped you off in advance, would you have noticed that there were two things going on contemporaneously in every sentence in that last example?

If not, you aren’t alone. Most aspiring writers — i.e., the folks who have not yet had the professional opportunity to hear an editor go on a tirade about such things — would not see a problem with that excerpt. Millicent, however, would, and that’s likely to spark some rather unpleasant consequences at submission time.

So how might a savvy reviser rearrange that passage so as to leave Millie’s eyebrows mercifully unraised? Vary the sentence structure — and cut out any extraneous activity.

While you’re at it, reserve as for those relatively rare occasions when it’s imperative that the reader be made aware that things happened at the same time. The result might look a little bit like this:

Monique strode around the corner, surprising Clarence so much that he dropped his bullwhip. While he was looking for someplace convenient to hide, she calmly unearthed a crossbow from her purse.

Carefully, she took aim at his Adam’s apple. “The jig’s up, my friend.”

The contrast between this version and the previous one is pretty stark, is it not? That’s not merely a matter of style, but of phrasing variety. To repetition-sensitive eyes, a page filled with structural and word repetition is like badly-done CGI in movies, where battle scenes between thousands of characters are created by filming 50 extras flailing at one another, copying that image, and plastering it seventeen times across the scene, perhaps alternated with two or three other images of the same actors in different positions. Honestly, to those of us who count patterns for a living, that level of repetition can be downright migraine-inducing.

“Wait just a nit-picking minute, Anne!” I hear some conscientious revisers exclaiming. “I don’t mean to cling slavishly to my dog-eared copy of Strunk & White, but English grammar only permits so many ways of arranging sentences properly. Isn’t any manuscript going to exhibit a certain amount of pattern repetition, necessarily?”

Yes, of course — but that does not give writers carte blanche to use the same structures back-to-back for paragraphs on end, or to utilize a favorite complex sentence form four times per page. And that’s unfortunate, because it’s not as though your garden-variety writer is repeating herself on purpose: in the vast majority of instances, the writer simply likes a kind of sentence or a particular verb enough to use it often.

You lucky souls, however, are going to be one up on that kind of writer come revision time, because we’re about to take a run at spotting the phenomenon in its natural habitat. Since my last post’s foray into A TALE OF TWO CITIES was so obvious, let’s tackle a comparatively subtle one this time around the submission desk.

Rubbing his sides for warmth, Sven glanced unhappily at his fellow cheerleaders. Waving his pom-poms in a wan impression of good sportsmanship, he reminded himself never to be stupid enough to accept one of his sister’s bets again. Pulling up his flesh-colored tights –- oh, why hadn’t he listened to Kenro, who had told him to wear nylons under them on this near-freezing night? –- he wondered if Tamara would be vicious enough to demand the performance of the promised splits before the game ended. Sighing, he figured she would.

How did you do? Individually, there is nothing wrong with any given sentence in this paragraph, right? Yet taken communally — as sentences in submissions invariably are — the repetition of the same kind of opening each time starts to ring like a drumbeat in Millicent’s head, distracting her from the actual subject matter, the quality of the writing, and, alas, even the blistering pace you worked so hard to achieve on the page.

That’s not just a voice problem — it’s a marketing problem. Why? Well, think about it: very, very few agents and editors can afford to work with specialists in a single type of sentence.

And don’t start waving random pages ripped from Ernest Hemingway’s oeuvre at me, either. Present-day readers expect a narrative with a broad array of sentence structures. It’s simply more amusing to read.

Sadly, most of the time, writers don’t even realize it when they’re repeating patterns. Unless the repetition bug has really bitten them, the redundancy isn’t in every sentence, and it’s not as though most writers have the foresight, patience, or even time to re-read an entire scene each time they revise a sentence or two of it. Much less to go over it IN HARD COPY, IN ITS ENTIRETY, and OUT LOUD.

Why, yes, that was redundant, now that you mention it. FROG FUN taught me that was the way to make a point memorably.

To be fair, though, repetition often lies in words or phrases that are similar, but not identical, so the writer does not think of them as the same word. Consider:

Casmir began sweating, sweating as though his sweat glands were going on strike tomorrow. Should he go to the window and throw it open, beginning the cooling-down process? Or should he go downstairs, into the basement, to the cool of the pickle cellar, to await the stellar offer on his house? Or should he wait for the seller on the cooler porch?

Subtle, isn’t it? Sometimes, the structures a writer favors may be common enough in themselves that she would need to read her pages IN HARD COPY and OUT LOUD to catch the problem. As in:

“But I didn’t steal the payroll,” Claire insisted, “because I had no reason.”

“But you did take it,” Edmund shot back, “because you needed the money for your sainted mother’s operation.”

Claire’s eyes filled with tears. “You leave my sainted mother out of it, since you don’t know her.”

These three lines of dialogue feature different words, but they sport identical structures. This may not seem like a serious problem on any given page, but once a professional reader notices a manuscript exhibiting this kind of repetition over the course of few exchanges, she will simply assume — feel free to sing along; you should know the words by now — that the pattern will recur throughout the manuscript. She’s usually right, too.

How does she know, you ask? Experience, my dears, experience. How many horror films did you have to see before you realized that the monster/killer/Creature from the Black Lagoon wasn’t really dead the first time it appeared to be?

Oh, you thought I was going to use that the monster always returns trope only once in this series? Good eye, those of you who caught it.

Rather than resting on your laurels, though, go back and re-read that last example out loud. Did you notice how similar those three paragraphs sound in the mouth, almost as though they were not the words of two different speakers? The repetitive structure here makes Claire and Edmund speak in essentially the same rhythm, as though they were echoes of the same voice.

Which, from an authorial point of view, they are. That doesn’t mean that the reader won’t want to preserve the illusion that those speeches are falling from different pairs of lips.

When two characters speak in the same rhythm, it mutes the conflict between them a little — not to mention making it harder for the reader to follow the dialogue. Check out how varying the sentence structure ramps up the tension between these characters, even in an excerpt this short:

“But I didn’t steal the payroll,” Claire insisted. “I had no conceivable reason.”

“You lie,” Edmond shot back. “You needed the money for your sainted mother’s operation.”

Her eyes filled with tears. “You leave my sainted mother out of it, me bucko, since you don’t know her.”

“Aha! I knew you were concealing a pirate past!”

“I ought to keel-haul you.” Sullenly, she tore off her eye patch. “What gave me away, the parrot?”

Nifty, eh? That, in case you were wondering, is the kind of character development benefit a writer is likely to derive from reading her work OUT LOUD. I just mention.

A writer need not only pay attention to how many times he’s using the same words or similar sentence structures in back-to-back sentences, but also on any given page, as well as over the course of a scene. Let’s take a look at how non-consecutive repetition might play out in practice.

As the car door opened, Beatrice swallowed a horrified gasp. It was Lance’s severed hand, dragging itself around the latch mechanism, one grisly fingertip at a time. As she reached for the gun, her intestines palpitated, but she forced her arm to remain steady. While she loaded the bullets into the chamber, she thought about how much she had loved Lance, back when his constituent parts were all still interconnected as a human’s should be. It was a shame, really, to have to keep blowing him to bits. But blow him to bits she would continue to do, as often as necessary.

To most self-editors, this paragraph would not seem especially problematic. Yet it contains two of the most commonly-repeated structures, our old friends, the While X was Happening, Y was Occurring and the It Was Z…. Standing alone as individual sentences, either form is perfectly valid; the problem arises when either appears too frequently on the page.

Still having trouble seeing it? To a professional reader, this is how the paragraph above would scan:

As the car door opened, Beatrice swallowed a horrified gasp. It was Lance‘s severed hand, dragging itself around the latch mechanism, one grisly fingertip at a time. As she reached for the gun, her intestines palpitated, but she forced her arm to remain steady. While she loaded the bullets into the chamber, she thought about how much she had loved Lance, back when his constituent parts were all still interconnected as a human’s should be. It was a shame, really, to have to keep blowing him to bits. But blow him to bits she would continue to do, as often as necessary.

See how even spread-out repetition jumps off the page, once you’re sensitized to it? Millicent (and her boss, and the editors at the publishing house across the street, and even the average contest judge after reading the first handful of entries) is so attuned to it that she might not even have made it as far as the end of the paragraph.

To use the most overworked word in Millie’s vocabulary: “Next!”

Of course, you may strike lucky: your submission may be read by a screener who hasn’t been at it very long, a contest judge brand-new to the game, or an agent whose tolerance for pattern repetition is unusually high. Heck, your work may even land on the desk of that rara avis, the saint who is willing to overlook some minor problems in a manuscript if the writer seems to have promising flair. In any of these cases, you may be able to put off winnowing out pattern repetition until after the book is sold to an editor.

Who, frankly, is most unlikely to be so forgiving. So do you honestly want to gamble on Millicent’s possible saintliness at the submission stage, or would you prefer to take care of this little problem now?

Where should you begin? Well, the beginning is always a nice place to start. Since editorial response to this kind of repetition tends to be so strong — I wasn’t kidding about those migraines — you would be well advised to check your first chapter, especially your opening page, for inadvertent pattern repetitions. (Actually, since quick-skimming pros tend to concentrate upon the openings of sentences, you can get away with just checking the first few words after every period, in a pinch. But you didn’t hear that from me.)

The most straightforward way to do this is to sit down with five or ten pages of your manuscript and a number of different colored pens. Highlighters are dandy for this purpose. Mark each kind of sentence in its own color; reserve a special color for nouns and verbs that turn up more than once per page. You probably already know what your favorite kinds of sentence are, but it would be an excellent idea to pre-designate colors for not only the ever-popular While X was Happening, Y was Occurring and the It Was… sentences, but also for the X happened and then Y happened and Gerund Adverb Comma (as in Sitting silently, Hortense felt like a spy) forms as well.

After you have finished coloring your pages, arrange all of the marked-up pages along some bare and visually uncomplicated surface — against the back of a couch, along a kitchen counter, diagonally across your bed — and take three steps backward. (Sorry, kitty; I didn’t mean to step on your tail.)

Does one color predominate? If you notice one color turning up many times per page — or two or three times per paragraph – you might want to think about reworking your structures a little.

If this all seems terribly nit-picky to you, well, it is. But the more you can vary the structure and rhythm of your writing, the more interesting it will be for the reader –- and, from a professional perspective, the more it will appeal to educated readers. Think about it: good literary fiction very seldom relies heavily upon a single sentence structure throughout an entire text, does it?

You know what kinds of books use the same types of sentences over and over? The ones marketed to consumers with less-developed reading skills. If that is your target readership, great — run with the repetitive structure. (Run, Jane, run! Don’t let Dick stab, stab, stab.) But for most adult markets, the industry assumes at least a 10th-grade reading level.

In my high school, Ernest Hemingway’s THE OLD MAN AND THE SEA was assigned in the 9th grade. If you catch my drift.

Then, too, agency screeners and editorial assistants typically hold liberal arts degrees from pretty darned good colleges. That’s a long, long way from the reading level that was contented to watch Dick and Jane running all over the place with Spot and frogs having fun hop, hop, hopping.

Let your structural choices be as exciting as the writing contained within them — and let your voice emerge as more than a repetitive collection of your favorite words and sentences. Incorporate your pet structures and phrases, by all means, but have them appear rarely enough that they will seem like revelations, not just narrative-as-usual.

Above all, keep mixing up those sentence structures. You may be pleasantly surprised at how much interest merely preventing a sentence from reading like the one before it can produce.

And try not to mourn too much for last year’s Christmas tree. It will twinkle all the brighter in our memories for having been unique. Keep up the good work!

“Wait, haven’t I read that someplace before?” — Millicent

old-fashioned writing desk in Victoria

Please join me in a moment of silence, campers. Today, I received one of the saddest pieces of news a person can hear from a writer friend: an extremely talented author of my acquaintance reported that her hard disk had crashed, doubtless from overwork. Not a syllable could be salvaged.

In response to those of you who just gasped audibly: yes, she was almost finished writing her next novel. She had circulated only the first four chapters to her critique group, so physical copies of that much still exist. Beyond that, however…

On a not entirely unrelated note, when was the last time you backed up your writing files? Is it recently enough that you could reconstitute your most recent revisions or new text from your unassisted memory?

If the answer to that second question is no, feel free to stop reading right now and make a back-up. At minimum, e-mail them to yourself, for heaven’s sake. I’m perfectly happy to wait, if it means that we can all sleep better tonight, confident that hours, days, weeks, and/or months of your writing time won’t just vanish in the proverbial puff of smoke.

Or ozone, as the case may be. As undoubtedly conducive to creative expression as computers are, the permanence of the results can be illusory. At times like this, I occasionally find myself longing for my father’s good old Olivetti typewriter, or even a simple Edwardian writing desk, like the one above. (Note, please, the requisite photo of a loved one and apparently equally requisite liquor tray.)

True, one had to hit the Olivetti’s keys so hard that when my parents first plopped me down in front of it at age ten to compose the term paper that everyone else in my class was writing by hand, I couldn’t actually force the q, z, p, or ? keys to hit the ribbon with sufficient force to create any impression upon paper. It took me so many hours to write the definitive history paper on the Bonus March that my mother seized the opportunity first to sketch my profile — she had never managed to convince me to sit still long enough before — then to sculpt my head in clay. Considering that my parents insisted that I write it in standard format for book manuscripts, I should probably count myself lucky that she didn’t also have time to cast the sculpture in bronze.

Yes, it was a touch on the tedious side to be forced to retype an entire page in order to rework a single sentence. On the bright side, though, to lose a year’s worth of one’s writing, an author actually had to misplace it physically.

(Were you distracted from the pithiness of that last bon mot by a mental image of a 5th grader using two hands to wrestle the z key into submission? That memory haunts me, too. My mother, however, asks me to inform you that she had faithfully typed my newspaper articles prior to that term paper, and that a little pro of my caliber shouldn’t have graduated from elementary school without learning to touch-type, anyway. And to be fair, she didn’t actually make me try it blindfolded until after I’d turned in the paper.)

Writing on a computer boasts at least one monumental advantage over the all hard copy, all the time method, however: it’s possible, and indeed easy, to check whether that wry observation that just occurred to you also struck you as the last word in style back when you were composing Chapter 3. And Chapter 7. And possibly Chapter 16.

Oh, you hadn’t noticed that you had repeated yourself? Trust me, Millicent the agency screener will.

Since aspiring writers so seldom catch their own phrasing reuse, I’m going to spend the next couple of days talking about that ever-popular birthmark of Frankenstein manuscripts everywhere, the sentence — or paragraph, or footnote, or scene — that turns up more than once in a manuscript. Or more than once in a chapter. Or — are you sitting down? — more than once in a page.

Already, I sense some of you rolling your eyes. “Yeah, right, Anne,” writers of 384-page texts huff, “I’m so uncreative, so myopic, so prone to writing only one paragraph per session that I would repeat entire sentences within just a few pages, yet Millicent remembers phrasing so well that she will catch me if I recycle a description from page 73 on page 312.”

Actually, she might — and I hate to be the one to break it to you, but otherwise quite good manuscripts reuse pet phrases all the time. You’ve probably noticed the tendency in the later works of well-established authors, in fact; as television comedy has led us all to expect, revisiting the same premises, jokes, and yes, even descriptions can elicit chortles of delighted recognition from an audience already familiar with one’s work. Heck, Oscar Wilde used to trot out the same laugh lines in play after play after play; he was monumentally good at branding.

For the overwhelming majority of writers, though, self-plagiarism does not constitute a promotional strategy so much as a simple lapse in memory. In the course of writing an entire book, it should perhaps not come as a surprise if the creative brain revisits a favorite turn of phrase, a trenchant observation on the human condition, of striking bit of imagery that strikes a writer as particularly, well, striking.

Hey, if it sounded good in the writer’s mind the first time, what’s to stop it from sounding good the second? Or the fourth? Or the forty-seventh?

Perfectly innocent and understandable, right? Well, perhaps not so much to our old pal Millicent — or her cousin Maury, the editorial assistant, or their aunt Mehitabel, the veteran contest judge. To someone who reads manuscripts for a living, such inadvertent redundancy can take on a more sinister aspect: to an uncharitable reader, even a single repetition of a pet phrase can smack of authorial laziness. Or as an aftereffect of that perennial bugbear, insufficient authorial re-reading.

Or, sacre bleu! a first indicator that what she holds in her ink-stained hands is a Frankenstein manuscript.

We’ve all seen Frankenstein manuscripts, right, even if we have not had the misfortune to write one? Many of us have at least a partial monster lurking in a bottom desk drawer or haunting our hard disks, books written over such a long period, in so many moods, at so many different levels of technical skill, and — come on, admit it — under the influence of so many and such varied favorite authors that it would take a small army of literary detectives years of close textual analysis to discern even an embryonic similarity between the authorial voices on pp. 10, 143, and 412.

In a first draft of a first novel, that’s virtually inevitable, right? Contrary to popular opinion amongst those who have never actually sat down in front of the ol’ Olivetti and cranked out a book, few writers are born with completely polished voices; it can take a great deal of trial and error to figure out how to sound original on the page. Then, too, it takes a good, long while to write a book, particularly the first time around: as Millicent would be the first to tell you, it’s not all that uncommon for the manuscript to betray significantly greater technical skill at its end than at its beginning. Or for the first chapter or two to read a great deal more like the end of the book than like the middle, because the writer went back and revised those opening pages after polishing off the draft.

Why is Millicent an expert on the two most common stripes of Frankenstein manuscript? Care to estimate how many first-time novelists and memoirists start querying and submitting their work practically the instant they polish off the first draft? Or the second?

Trust me, those of us who read for a living learn to catch the early warning signs. When Millicent sees a sentence, image, or observation from page 1 turn up on page 26, Frankenstein manuscript warning bells start chiming wildly in her head. From that point on, her already sharp critical sensors turn downright predatory, eager to swoop down upon more tell-tale signs that this is one of those texts whose author either kept changing his mind about the style he wished to embrace — or tone, or target audience, or book category — or just kept revising it so often that the narrative reads like a patchwork of different prose styles.

That does not mean, however, that self-plagiarism does not turn up quite frequently in non-Frankenstein manuscripts. How can an experienced reviser tell the difference? While the Frankenstein manuscript varies substantially as pages pass, the self-plagiarized text merely becomes redundant: passing scenery always described the same manner, for instance, or a clever line of dialogue repeated in Chapters 2, 5, and 24.

Nonfiction writing in general, and academic writing in particular, is notoriously prone to redundancy. So are book proposals. Again, that’s quite understandable. Once you’ve gotten into the habit of footnoting everything in the least questionable, it’s pretty easy to reuse a footnote, for instance, or to come to rely upon stock definitions instead of writing fresh ones every time.

Or, in a memoir, to tell the same anecdote more than once. As, indeed, people who like to talk about themselves tend to do in conversation. (Did I ever tell you about the time my mother wanted me to learn touch-typing as a fifth grader?)

Or, in any kind of writing, for a particular way of describing something to sound good. Many a writer simply finds a certain turn of phrase appealing and forgets that he’s used it before. Or just doesn’t notice, despite the fact that great way to catch this sort of redundancy is — wait for it — to read your manuscript IN HARD COPY, IN ITS ENTIRETY, and OUT LOUD, in as few sittings as possible.

Oh, had I suggested that excellent pre-submission strategy before? Had I in fact mentioned it about once per week throughout Queryfest? How silly of me not to notice.

You may laugh, but actually, it’s quite easy for even a fairly conscientious reviser to miss instances of self-plagiarism on the page, especially if — and most revisers do this — she is reading through the manuscript over several days or even weeks. After all, you have to be gifted with an unusually strong memory for phraseology to stop short in the middle of Chapter 15 and shout, “Hey, I’ve seen that image before, and it was on page 36, paragraph four!”

I don’t mean to frighten you (or do I?), but professional readers frequently have astonishingly accurate memories for text. Millicent might not be able to tell you precisely where she’s seen that Ch. 15 image before, but she will almost certainly have the dim impression that it has appeared earlier in the manuscript. I can positively guarantee you, though, that if the first instance of its use pops up on p. 36, and the second on p. 42, she will most assuredly spot the second as redundant.

She should: professional readers are trained for that.

For a self-editing writer, it can be harder to catch — and harder still to remember if you actually used that sentence elsewhere, or merely thought about it. As inveterate commenter and long-time FAAB (Friend of Author! Author! blog) Dave so rightly pointed out the last time we discussed this phenomenon, most good writers spend quite a bit of time mulling over any given scene in a book, not to mention revising it later on; it’s not uncommon, therefore, to have a positive welter of mental associations about the evolution of the aforementioned pp. 36 and 42. Add to that the fact that a reader’s eye will tend to pass over smoothly-written text pretty quickly, especially if it’s a scene he’s read before, and reading through one’s own manuscript by definition entails re-reading, and can we really be surprised when repeated phrasing passes unnoticed under the reviser’s gaze?

Even when the repeated phraseology or image does jump out at the rereading reviser (try saying that four times fast!), it won’t necessarily be for a negative reason. It’s not unheard-of for writers to prefer repeating bits of their own work: those turns of phrase are his favorites for a reason, presumably. They linger in his ears pleasingly when he reads them out loud; they strike him as some of his best writing on the page. If pressed, he might admit to wanting to see one of them chiseled on his gravestone.

Yes, those of you who have been jumping up and down with your hands raised for the last couple of paragraphs? “I know what this writer should do!” survivors of English 101 burble excitedly. “It was for precisely this kind of writer’s benefit that Dorothy Parker started urging all of us to kill your darlings. If he loves those phrases so much, they should be the first axed, right?”

Aspiring writers and the English composition teachers who love them just love this piece of revision advice, eager burblers, but if you want to hear anyone who reads for a living choke on the coffee that’s never far from her elbow (hey, you try staying awake uncaffeinated through the fiftieth YA paranormal novel you’ve seen this week), feel free to trot out this most misunderstood piece of writing advice. We’ve too often seen the slash-and-burn effects of this canonical advice in action. Indeed, going through one’s own manuscript, relentlessly slaughtering any writing that strikes one as excellent is a pretty good prescription for creating a Frankenstein manuscript, not healing one.

And it’s not even what Aunt Dorothy was advising writers to do. She wasn’t talking about ruthlessly excising every piece of writing you like and leaving the stuff you like less, people: she was suggesting that you consider taking a critical look at even your favorite sentences and paragraphs. All too often, inexperienced self-editors will simply skip over their pet bits.

That being said, kill your darlings (selectively!) is excellent advice for habitual self-plagiarists. Perhaps a writer need not sacrifice the first of the litter, but the second through seventeenth should definitely go.

That’s especially good strategy if the phrasing repetition was deliberate in the first place. If a line was clever once, many a darling-coddling writer thinks, the reader will find it so the second time — and the fifth, and the forty-seventh. Deliberate redundancy is particularly common with humor: since situation comedies tend to rely upon repetition of catch phrases, many aspiring writers believe that the mere fact of repetition will render a line funny.

On the page, it seldom works. Sorry to be the one to break it to you sitcom lovers, but it quickly becomes tedious on the stage and screen as well.

Don’t believe me? Consider this: as those of us who live in caucus states know to our perennial (or at least quadrennial) sorrow, nowhere is the practice of self-plagiarism more prevalent than in the garden-variety political speech. Not only from speech to speech — oh, you thought your favorite candidate gave a speech only once, then threw it away? She has fourteen more campaign stops today! — but throughout a political season. Heck, as anyone who has listened closely to two consecutive State of the Union addresses can tell you, they often contain the same phrases from year to year No matter how fiercely THE WEST WING tried to promote the notion of presidential speechwriters as ultra-creative writers, if you look at speeches given by the same politician over time, chances are that you’ll find self-plagiarism of epidemic proportions.

There’s a good narrative reason for that, of course: the repetition of an idea makes it memorable. The ideas — and usually even the actual phrases — of the beginning of a political speech invariably recur throughout, to drive the point home.

Doubt that? Okay, answer this: do you think people would remember that the Rev. Dr. Martin Luther King, Jr. had a dream if he had said it only once in his famous March on Washington speech?

On paper, phrase repetition is often problematic, but in and of itself, repetition does not necessarily equal self-plagiarism. On paper, repetition can seem very cool to the writer, as a means of creating a galloping rhythm. On paper, phrase repetition can be used for emphasis (as I have just done in this very paragraph, much to Millicent’s chagrin).

We all know how phrase repetition can create a sense of momentum in writing, don’t we? Take, for instance, the ending of the St. Crispin’s Day speech from HENRY V:

If we are mark’d to die, we are enow
To do our country loss; and if to live,
The fewer men, the greater share of honour.
God’s will! I pray thee, wish not one man more.
By Jove, I am not covetous for gold,
Nor care I who doth feed upon my cost;
It yearns me not if men my garments wear;
Such outward things dwell not in my desires.
But if it be a sin to covet honour,
I am the most offending soul alive.
No, faith, my coz, wish not a man from England.
God’s peace! I would not lose so great an honour
As one man more methinks would share from me
For the best hope I have. O, do not wish one more!
Rather proclaim it, Westmoreland, through my host,
That he which hath no stomach to this fight,
Let him depart; his passport shall be made,
And crowns for convoy put into his purse;
We would not die in that man’s company
That fears his fellowship to die with us.
This day is call’d the feast of Crispian.
He that outlives this day, and comes safe home,
Will stand a tip-toe when this day is nam’d,
And rouse him at the name of Crispian.
He that shall live this day, and see old age,
Will yearly on the vigil feast his neighbours,
And say ‘To-morrow is Saint Crispian.’
Then will he strip his sleeve and show his scars,
And say ‘These wounds I had on Crispian’s day.’
Old men forget; yet all shall be forgot,
But he’ll remember, with advantages,
What feats he did that day. Then shall our names,
Familiar in his mouth as household words-
Harry the King, Bedford and Exeter,
Warwick and Talbot, Salisbury and Gloucester-
Be in their flowing cups freshly rememb’red.
This story shall the good man teach his son;
And Crispin Crispian shall ne’er go by,
From this day to the ending of the world,
But we in it shall be remembered-
We few, we happy few, we band of brothers;
For he to-day that sheds his blood with me
Shall be my brother; be he ne’er so vile,
This day shall gentle his condition;
And gentlemen in England now-a-bed
Shall think themselves accurs’d they were not here,
And hold their manhoods cheap whiles any speaks
That fought with us upon Saint Crispin’s day.

Now that’s a political speech, caucus-goers: great spoken out loud, but Millicent-enragingly repetitious in print.

Did that last observation catch you by surprise? Yes, this particular speech happened to fall from an exceedingly talented pen, but unfortunately, a lot of poor writers favor this rhythmic device, too. Because it is ubiquitous, it tends to be a rather risky trick to try to pull off in a short piece, such as a synopsis, or in the first few pages of a manuscript submitted for a contest or as part of a query packet.

Please tell me that you aren’t even considering repetitive phrasing in your query. Or that the first line of your synopsis is the first line of your novel. Please. Please. Please?

Why is it dangerous? Well, to professional eyes, trained to search for the repetition of a single verb within a paragraph as evidence of boring writing, we few, we happy few will not necessarily jump off the page for the beauty of its rhythm. In an ultra-quick reading (as virtually all professional readings are, lest we forget), it may be mistaken for an incomplete edit: you meant to change we few to we happy few,” but you forgot to delete the words you did not want, Bill.

A pop quiz to see if you’ve been paying attention: why would a savvy submitter not want to convey the impression of an incomplete editing job? That’s right: because that’s the birthmark of the dreaded Frankenstein manuscript, the fish that Millicent is only too happy to throw back into the sea.

Remember, too, that it may not take many instances of repetition for Millicent to draw this conclusion. The writer may not realize that she has reused a particularly spectacular image from Ch. 1 in Ch. 3, but believe me, if there is repetition, professional readers will catch it.

And no, I don’t care how many times I have to repeat that point. It’s vital for your happiness as a writer to understand that the pros are trained to catch redundancy. Editors in particular are notorious for remembering entire pages verbatim.

It’s a specialized brain function, sharpened by use. When I was teaching at the University of Washington, I was known for noticing when term papers resubmitted in subsequent quarters, even though I read literally hundreds of papers per term. I would even frequently remember who wrote the original. As you may well imagine, I quickly acquired a reputation amongst the fraternities and sororities who kept files of A term papers for their members to, ahem, borrow.

Which is why, in case those of you who have had the good fortune/petrifying experience of receiving professional feedback, paraphrasing what you’ve said earlier in the manuscript tends to be significantly less frowned-upon in editorial circles than outright literal repetition. While very similar passages may earn you an ill-humored rebuke from Millicent, Maury, or Mehitabel, generalized repetition usually will not knock you out of consideration if the recurring bits occur far apart, such as at the beginning and end of a book.

In a shorter piece, however — such as, say, those first 50 pages of your novel that nice agent asked you to send for consideration, or the 15 pages plus synopsis — it certainly can cost you. Repetition sticks in the professional reader’s craw, nagging at her psyche like a pebble in a shoe. It’s in your best interest to do it as little as possible.

“Now wait a minute,” I hear some of you out there grumbling. “You told us just a few minutes ago that Oscar Wilde repeated the same quips in one play after another. It became his trademark, in fact. So why should I be punished for using a single particularly sterling line 150 pages apart in my novel?”

You have a point, of course, grumblers. The next time you trot out this argument, you might bolster it by mentioning that Aaron Sorkin reused not only lines and speeches from SPORTS NIGHTin THE WEST WING, but entire plot lines and basic characters.

Tell you what: after you make it big, I give you permission to establish a trademark phrase and use it as often as you like. Until you do — as I sincerely hope you will — all I can do is tell you that phrasing repetition tends to annoy agents, editors, and contest judges.

Seriously, I will repeat it all night. Don’t tempt me.

“But Anne,” I hear the well-read among you protest, and with good reason, “many of the classic novelists I studied in my English 101 class used phrasing repetition to create invocatory rhythms. They also repeated dialogue, because, as you like to point out early and often, real-life dialogue is hugely redundant. If it’s good enough for those long-ago greats, why isn’t it good enough for me — or for Millicent?”

One reason leaps to mind: you’re not writing on a typewriter, are you? You’re probably composing your book in a word processing program. Not only can you spell- and grammar-check with an ease that would have made the late, great Ms. Parker gasp with envy — with the touch of a button or two, you can search your own writing to see if you have used a phrase before.

You think Millicent is unaware of that capacity?

You are perfectly right, though, close readers: all writers of book-length works have repeated themselves at one time or another. If a simile struck us as the height of cleverness last week, chances are good that we will like it next week as well. Each time we use it, it may seem fresh to us. These little forays into self-indulgence are so common, in fact, that literary critics have a name for them: tropes.

F. Scott Fitzgerald was a notorious troper in his short stories. My least favorite: a thwarted heroine’s sobbing out (usually with her face hidden by her smartly-bobbed hair), “I’m so beautiful – why can’t I be happy?” immediately before she does something self-immolatingly stupid to remove herself from the possibility of marrying the story’s protagonist occurs at least four times throughout his collected works.

It may well pop up more; I merely stopped counting after four. That was, not entirely coincidentally, when I threw the book across the room.

Why Uncle Scott found that particular line so very attractive in a pretty woman’s mouth remains a mystery eternal — it’s hard to believe he ever actually heard a sane female utter it, even in jest. But he did, evidently, and now it’s stuck to his name for all eternity.

Learn from his unhappy fate, I beg of you: no matter how marvelous a line of text is, use it only once.

This will require careful reading to enforce. Your garden-variety self-plagiarism is less obvious to the untrained eye than ol’ Scott’s outright dialogue reuse. Spread out over an entire text — or, as it often appears in the case of successful authors of series, once per book — it may be fairly innocuous, the kind of thing that might only bug someone who read manuscripts for a living.

Like, say, Millicent or yours truly. Do not underestimate, for your own sake, our memories. Unbound manuscripts do not typically survive intact being flung across the room.

E.F. Benson, author of two delightful series, the Lucia books and the Dodo books, was evidently extraordinarily fond of using Arctic analogies for one person suddenly grown cold to another. To gather but a small nosegay of examples:

“It was as if an iceberg had spoken,”

“It was as if the North Pole had spoken,”

“icebergs passing in the North Sea” must speak to one another as two characters had, and

“Mapp turned to ice.”

See the problem? As a Benson enthusiast, I was able to come up with four of them without even pulling any of his books off the shelf These repetitions, deliberate or not, stick with the reader, just as surely as repeated phrases stick with the audience of a political speech.

That doesn’t mean it is a bad analogy, of course, if not a startlingly original one. Like any other literary device, however, time it’s used, it becomes less effective.

Yet again, we see an awfully good reason to read your entire book (or requested chapters, or contest submission) out loud before you submit it — and not just as a cursory mumble-through, either. Believe it or not, just as dialogue that seemed fine on the page can suddenly seem stilted when spoken aloud, phrases, sentences, and images that your eye might not catch as repetitious are often quite obvious to the ear.

Another good reason to read aloud: to make sure that each of your major characters speaks in a different cadence. It’s substantially easier for the reader to follow who is speaking when that way.

Don’t stand there and tell me that all of Aaron Sorkin’s and David Mamet’s characters speak in identical cadences, as though they all shared one vast collective mind. To my sensitive antennae, nothing is more potentially migraine-inducing than an evening of the percussive prose of Mamet. (Unless it’s a chamber concert of Stephen Sondheim’s greatest hits.)

As if the prospect of annoying your humble correspondent were not sufficient incentive to eschew identical dialogue patterns for every character, remember what I said back in Queryfest about the dangers of those new to the biz assuming that what the already-established have done, they may get away with as well?

Uh-huh. In a first manuscript, it would be considered poor craft to have every character in the book sound the same. Not to mention poor character development. While I’m on the subject, keep an ear out in your read-through for lines of dialogue that cannot be said aloud in a single breath without passing out — they tend to pull professional readers out of the story.

Why, you shout breathlessly? Well, in real life, listeners tend to interrupt speakers when the latter pause for — wait for it — breath. Cramming too many syllables into an uninterrupted speech usually doesn’t ring true on the page. Allow your characters to breathe occasionally, and your dialogue will seem more realistic.

I’d give you a concrete example, but I meant to post a short blog today, and here I have gone long again. Which begs the question: I’m so beautiful — why can’t I be happy?

There, now at least one real, live human female has said it; don’t say I never did anything for you, Uncle Scott. Keep up the good work!

Entr’acte: tracing the patterns of a life, or, just because something really happened doesn’t mean a writer is excused from making it dramatically appealing on the page

One of the great liabilities of editing for a living — or one of the great advantages, depending upon how one chooses to look at it — is that over time, the dedicated editor becomes decreasingly able to read anything without scrawling corrections in the margins. I’m not merely talking about manuscripts, synopses, and queries here, mind you, but all typed words on a page. The New York Times, for instance, once the standard of American prose, now seldom passes under my long-lashed eyes without picking up some entirely justified marginalia. Nor do any of my alumni magazines go unscathed: I’m looking at you, Radcliffe Quarterly. I routinely take a corrective pen to menus, fliers, and wedding programs. Last November, I had to be restrained bodily from correcting a grievous misprint on my ballot for a county election; the correction apparently would have confused the counting machine.

More confusing than asking the citizenry to select a superior court joge? I think not.

While in some walks of life this level of nit-pickiness would prove somewhat problematic, for professional readers like agents, editors, and contest judges (or, in this county, joges), it’s a positive boon. So what if in some benighted professions, it is neither expected nor considered particularly sane to look one’s coworker in the eye and say, “I like the content of you’re saying, Ziggy, but the fact that you uttered the word exciting fourteen times over the course of a six-minute speech, insisted — wrongly — that impact is a verb, and failed to define a good third of your basic terms detracted from its effectiveness,” without finding oneself cordially disinvited from all future meetings? Someone has to defend the language. And by gum, if that means rending our garments and wailing to the heavens, “You’ve used this metaphor twice in 137 pages! And phrased it almost identically each time, you…you?torturer,” well, we’re up to the task.

Oh, you thought I was kidding about that last one? Half the good professional readers I know would not only have become impatient at the metaphor repetition — they would have assumed that the writer did it on purpose. As opposed to, say, not recognizing the insight of today as the insight of three months, eight days, and sixteen hours ago.

How could you? You know how much such things upset Millicent the agency screener.

All of which is to say: I tried — really, I did — to devote this weekend’s post to the delightful task of critiquing and presenting two more reader-generated query letters, missives devoted to the promotion of what sound like some very interesting memoirs. In pondering the all-too-often misunderstood mysteries of memoir voice, however, and how to present it effectively in a letter as short as a single page, I found my text-addled mind drifting back to a novel-cum-memoir I had read, I kid you not, in junior high school. A pivotal scene in it, I felt, would provide such a glorious illustration of a common memoir querier’s mistake that I just had to drop everything and track down the book.

That’s how little girls with braids grow up to be editors, in case you had been wondering. Sometimes, even other editors are surprised at how well I remember text. A few years ago, when my own memoir was lumbering its way through the publication process, my acquiring editor scrawled in my margins, “Oh, yeah, right — you remember a biography of the Wright Brothers that you read in the third grade? Prove it!” I was able not only to give him a chapter breakdown of the book, but tell him the publisher and correctly identify the typeface.

Do I need to follow up with the story of what happened when one of my students at the University of Washington turned in the same term paper another of my students had submitted a scant five semesters before? I thought not. But the undergraduate disciplinary board couldn’t believe I caught the repetition, either.

So I had good reason to believe that my recollection of a fictionalized memoir ostensibly by a childhood friend of Joan of Arc was reasonably accurate. A lighthearted burrow through the roughly two thousand volumes I carted up from California after my mother moved from my childhood home, so she would have to take only the remaining eight thousand with her (long story), and voil? ! The author of the otherwise charming book had tumbled into a multitude of ubiquitous first-time memoirists’ traps. Including, of course, the one that had jumped up and down in my mind after so many years.

You know, the kind of thing that Millicent thinks so many of you writers of the real do on purpose, just to annoy her. Echoing the all-too-common verbal habit of using and as a substitute for a period in your first-person narration, for instance, in a misguided attempt to make the narrative voice sound more like everyday speech. (It works, but let’s face it, quite a bit of everyday speech is so repetitious that it would be stultifying transcribed directly to the printed page.) Or telling an anecdote on the page as one might do out loud at a cocktail party, with practically every sentence a summary statement. (Hey, there’s a reason that show, don’t tell is such a pervasive piece of editorial feedback.) Or, most common of all, not doing much character development for anyone but the protagonist.

Speaking of showing, not telling, here’s the scene that popped to mind. To render the parallels to what Millicent sees on a daily basis more obvious, I’m presenting it here in standard format for book manuscripts. (And if it’s news to you that such a thing exists, or that it differs from what is proper for submitting short stories, articles, or academic pieces, may I suggest a quick foray into the posts under the HOW TO FORMAT A BOOK MANUSCRIPT category on the archive list at right?) As always, my blogging program is a trifle hostile to page shots, so if you are having trouble reading individual words, try holding down the COMMAND key and pressing + to enlarge the images.



Come on, admit it — while you might have excused all of those ands if you had heard this told out loud, they’re a trifle eye-distracting on the page, are they not? Ditto with the word repetition — could this author possibly have crammed any more uses of to be, to get, or to see into these three pages? And don’t even get me started on concept repetition.

As a story on a page, it’s lacking quite a few elements. A sense of place, for one — is there a reason, the reader must wonder, not to give us some sense of what either the woods or the village were like? As so often happens in memoir, we’re just told that the action is happening here or there, with too little description to enable us to picture Joan and her young friends in a specific place. Nor are those friends fleshed out much, either in character or physically.

Heck, we don’t even get to see the frightening Benoist: instead, the memoirist merely tells us repeatedly that he and Joan were getting closer, without showing us what that might have looked like to a bystander. Like, say, the narrator.

Speaking of the narrator, do you get much of a sense of who he is as a person? How about what his relationship is to Joan? Are you even sure of their respective ages? Any idea what year it is? Heck, if you did not already know that the girl would grow up to be the patron saint of France — actually, one of four, but Joan of Arc is certainly the best known in this country — would anything but the children’s names tip you off about what part of the world these characters inhabit?

While I’m asking so many rhetorical questions in a row — another occupational hazard, I’m afraid — let me ask a more fundamental one: did you notice that while this passage is apparently about how the village’s children reacted to Joan, there’s practically no character development for her at all?

That’s at least marginally problematic, in a book entitled, wait for it, JOAN OF ARC. What, we are left to wonder, does she look like? Why doesn’t she stand up to her playmates (beyond, of course, the justification of being “so girlish and shrinking in all ways”) or, failing that, why doesn’t she simply walk away from the nasty little beasts? Most mysteriously, why can’t a kid brave enough to face down the village madman’s axe (or ax, depending upon where it falls in this passage; the error is in the hard copy in front of me), a rather interesting thing for a person to do, come up with more revealing answers to questions than a simple yes?

And would it be too much to ask the narrator to explain why the villagers left an axe lying anywhere near the madman’s cage in the first place? Might not the locals’ efforts be more productively expended making sure he can’t get out than chopping off his fingers?

More important to the story at large, if you did have more than an inkling of what the real-life Jeanne d’Arc achieved, wouldn’t you find it at least a trifle too pat that her playmates choose to picture her doing more or less what she grew up to do — and to laugh at her about it? If the girl had suggested this role herself, it might merely have been not-particularly-subtle foreshadowing, but honestly, can you think of any reason to include this at all except to make the reader feel cleverer than St. Joan’s playmates?

Millicent wouldn’t think of one. Neither would most professional readers; it’s our job to deplore this sort of narrative ham-handedness.

“Just how ill-informed would a reader have to be not to find that first bit clumsy?” we mutter into our much-beloved coffee mugs. “Isn’t it safe to assume that anyone who would pick up a book about Joan of Arc would know that she lead an army and was burned at the stake, even if that reader knew nothing else about her? And if your garden-variety reader knows that much, isn’t it an insult to his intelligence to drop a giant sign reading Hey, dummy, this is foreshadowing?”

Was that mighty gust of wind that just whipped the cosmos the sound of half of the memoirists out there huffing with annoyance, or was it the first-person novelists sighing gustily? Do you have some insight into this phenomenon that you would like to share? “But Anne,” both groups think loudly in unison, rather like the remarkably collective-minded children in the anecdote above, “this is how I was taught to write first-person narration: it’s supposed to sound exactly like a real person’s speech. So why shouldn’t St. Joan’s childhood buddy sound like anybody telling anecdotes out loud?”

A couple of reasons, actually. Yes, good first-person narration takes into account the narrator’s speech patterns. It also typically reflects the narrator’s social status and education, personal prejudices, and what s/he could conceivably know. And then there are those pesky individual quirks and, yes, the century in which s/he lived.

So I ask you, first-person writers: just how does the narrative voice in this passage indicate that this particular anecdote took place, according to the narrative, not too long after the Battle of Agincourt in 1415? As opposed to, say, the 1890s, when this account was first published?

Operating on the assumption that internal monologues have both always sounded pretty much like modern speech and don’t vary much from individual to individual is as common a mistake in first-person narratives as having all teenage characters sigh and roll their eyes is in YA submissions. Yes, some people do think and talk that way, but must everybody? Should Helen of Troy formulate her innermost thoughts in the same way as, say, Eleanor Roosevelt, Louisa May Alcott, or Confucius? (There’s a dinner party, eh?)

In case I’m being too subtle about it here: doesn’t it make for more interesting narration if your narrator’s speech bears at least some marks of time? And if she has some individual quirks of thought and expression?

Besides, if we are going to be true to the rules of first-person narration, shouldn’t we be objecting to how often our narrator here professes to read the other children’s minds — although, notably, not Joan’s? I don’t know about you, but I find that most of the time, my thoughts are located in my own head, not floating somewhere in the middle of a group of bystanders. So are we supposed to believe that our narrator in this instance is a mind-reader, or that the local children were too simple-minded to be able to form individual opinions about what is going on in front of them?

In fairness to the huffers and sighers above, however, it’s not beyond belief that they were taught to write first-person narration this way — in short stories in their high school English classes. In short bursts, run-on sentences do indeed come across as ordinary speech-like. In the professional examples of this type of narration that tend to turn up in class, it’s not all that unusual for the author’s voice and the first-person narrator’s voice to merge into colloquial harmony: Mark Twain tends to sound like Mark Twain, for instance, no matter whose perspective is dominating a particular story. That’s part of his branding as an author, right, a distinctive narrative voice?

As a strategy, adopting a chatty voice makes quite a bit of sense for narrative voice in memoir. The reader is going to have to like how the narrator/protagonist talks about her life well enough to want to follow the story for a few hundred pages, after all; we might as well get friendly. Yet in practice, the primary danger of relying on the repetitive phrasing, clich?s, and percussive and use to achieve realistic-sounding narrative cadence is precisely that it will put off the reader because as the pages pass, it can become, well, boring.

Think about it: even if a memoir were being told as a verbal anecdote, wouldn’t you rather listen to a storyteller with some individual flair for phrasing, instead of someone who just sounded like everyone else? No matter how inherently exciting a personal story is, a great telling can make it better reading. So can a narrative voice reflective of the time, place, and society in which that tale takes place.

But just try telling that to Mark Twain — who, as the sharper-eyed among you may already have noticed, wrote the scene above, in what he considered his best book. Although that retrospective assessment is a trifle hard to take seriously, in light of the fact that he published the book both under a pen and in serial form. Actually, he took it to even one more remove: he wrote a preface under a nom de plume, presenting himself as the translator of a memoir written by one of Joan’s contemporaries.

Why go to all that trouble? Because by all accounts, he felt that the poor sales of THE PRINCE AND THE PAUPER were largely attributable to his established audience’s expecting anything published under the name of Mark Twain to be a comedy.

Take that, purists who would like to believe that writing with an eye toward market concerns is a product of an increasingly cynical publishing industry over the last twenty or thirty years. Twain and his publisher worked out that tactic in the 1890s.

But I digress. As a reader, how well do you think his narrative choices worked here, either as fiction narration or as the memoir narration it originally professed to be? In your opinion as a writer, how do you feel about those slips into the first person plural — is the reader carried along with the we perspective as a narrative choice, as we were in Jeffrey Eugenides’ THE VIRGIN SUICIDES, or does it read like a perspective slip?

Moving back to my earlier point, do you feel that the mostly distinctly modern narrative voice, coupled with the almost entirely uncritical view of Joan, was the best way to tell this tale? Critics in Twain’s time did not think so — they believed (and I must say I agreed with them back in junior high school) that a protagonist who never does anything wrong is a trifle on the dull side, as far as the reader is concerned. Twain’s Joan never sets a wee foot wrong; even in her earliest youth, he tells us, she raised her voice in anger only once, and even then it was to voice a patriotic thought.

A taciturnity unusual in a rabble-rouser, you must admit. Also an unusual characteristic for someone who challenged social norms enough for anyone to want to burn her at the stake: Twain’s narrator presents her as a quiet, universally beloved little girl. Butter, as folks used to say, would not melt in her mouth. No matter how outside-the-box her observations or actions are shown to be (or, as we saw above, summarized to be), in this narrative, nothing she did or said from birth to the age of fourteen so much as ruffled the composure of the inhabitants of a querulous small village in wartime. Surprising, to say the least, in a young lady who by her own account had been engaging in frequent heart-to-heart chats with a couple of your more illustrious virgin martyrs since the age of twelve.

Perhaps the querulous small village where I spent my formative years was atypical, but I’m inclined to think that had I gone around snatching murder weapons from local lunatics or holding confabs with ancient Roman maidens, the Old Lady Mafia might have had a thing or two to say about it. I’m also inclined to think that their observations would not have been entirely favorable, regardless of how winsome and girlish I might have been while disarming the maniac in question. It doesn’t strike me as the type of endeavor best undertaken in a party dress.

I’m not saying that Twain is necessarily factually incorrect about all this; naturally, his best guess is as good as ours on a lot of these points. The lady lived rather a long time ago, so the issue here is less historical accuracy than dramatic plausibility. Still, just because something really happened does not mean it will necessarily come across as plausible on the page; as agents like to say, it all depends on the writing.

As an editor, I think it was the writer’s job to make me believe his take on this. Presuming you agree with me — speak now or forever hold your peace — I ask you: was this narrative choice the best fit for the story?

Literary taste is, of course, to a very great extent individual, so only you can answer that question to your own satisfaction. Am I correct in presuming, however, that you are at least a tiny bit curious about how an editor currently holding down the literary fort in the U.S. publishing world might respond to this particular set of narrative choices? Glad you asked.



What am I hoping you will take from this, you ask, eyes wide with horror? Not merely that being a brilliant writer does not necessarily preclude turning out a clunker of a first draft from time to time — although that’s not a bad thing for aspiring writers to bear in mind. The popular conception of true literary talent’s consisting of perfect creative phrasing dripping from the fingertips directly onto the page, with no further polishing necessary, does not match up particularly well with reality. As any experienced editor could tell you, most of the books people regard as productions of pure inspiration have actually been worked, reworked, and run past half a dozen critical readers.

Remember that, please, the next time you’re struggling with a scene that just doesn’t seem to want to hit the page gracefully — or with much specificity. In moments like that, it can be very tempting to embrace the tack Twain did above, to write up the scene in summary form as quickly as possible, with few vivid details, just to get the darned thing committed to paper.

What makes me think that this was written quickly? Editorial instinct, mostly: I find it hard to believe that a humorist as gifted at reading out loud as I know Twain to have been would have killed the comedy — or bored the reader — with this much word repetition unless he was writing on a deadline. Had he taken the time to revisit this scene and iron out its wrinkles, I don’t think there would have been quite so many references to eyes — and I don’t think that he would have had his narrator faint at the climax of the scene.

Certainly saved the author the trouble of having to figure out how the girl convinced the wild man to give up the axe, though, didn’t it? Trust me on this one: experienced editors — and Millicents — see this type of narrative shortcut often enough to recognize it for what it is.

So what should a savvy writer do when faced with this sort of first-draft dilemma? Go ahead: give in to temptation; there is value in getting a full scene on paper. Just make sure to set aside time later in the writing process to return to that scene and flesh it out. Unless you would prefer to have your future editor bark at you, “This is lazy writing, Ambrose. Didn’t anybody ever tell you to show, don’t tell?”

Just in case nobody has yet snarled that in the general direction of your manuscript: show, don’t tell. Immerse your reader in sufficient details for her to be able to feel as though she is part of the scene, rather than leaving her to fill in the specifics for herself.

Oh, you don’t think that’s what Twain is doing here? Okay, rise from your chair, grab the nearest willing partner, and try to act out this interaction between young Joan and Benoist, based solely upon the choreography the narrator above chose to provide us:

She stood up and faced the man, and remained so. As we reached the wood that borders the grassy clearing and jumped into its shelter, two or three of us glanced back to see if Benoist was gaining on us, and this is what we saw — Joan standing, and the maniac gliding stealthily toward her with his axe lifted. The sight was sickening. We stood where we were, trembling and not able to move. I did not want to see murder done, and yet I could not take my eyes away. Now I saw Joan step forward to meet the man, though I believed my eyes must be deceiving me. Then I saw him stop. He threatened her with his ax, as if to warn her not to come further, but went steadily on, until she was right in front of him — right under his axe. Then she stopped, and seemed to begin to talk with him. It made me sick, yes, giddy, and everything swam around me, and I could not see anything for a time — whether long or brief I do not know. When this passed and I looked again, Joan was walking by the man’s side toward the village, holding him by his hand. The axe was in her other hand.

Not much practical guidance for the actors there, eh? Other than all of that seeing, the actual movements mentioned here are pretty routine: one party standing still, the other moving toward her. The mover threatens, but we are not told how. Admittedly, a lifted axe doesn’t have to move much to seem threatening, but see how pretty much all of the sense of danger is conveyed via the narrator’s dread, rather than through showing the reader vivid, terrifying specifics? And how virtually all of that dread is summarized, rather than shown in any detail?

That lack of specificity distances the reader from what should have been a thrilling scene: by leaving the reader to fill in the details, the narrator abdicates his proper role here. Yes, he grounds us in his experience by telling us repeatedly that he is seeing this or that, and that these sights made him feel sick (and ultimately pass out), but great heavens, man, if you’re going to narrate a story like this, isn’t it your job to at least ask a bystander what happened, so you could share that information with the reader?

Don’t tell me that once you’ve seen one axe-wielding madman, you’ve seen ‘em all. As both a reader and an editor, I want to know what this particular madman looked, sounded, moved, smelled, and felt like. I want to know precisely what our heroine did that gave Benoist pause; I want to be shown how he crept up on her stealthily while apparently walking straight into her line of vision. And gosh darn it, I want to know how an axe of 1415 differed from one I might buy at the corner hardware store today.

Without those details, and phrased in fairly ordinary terms, this is indeed like everyday speech, despite the inherently exciting subject matter. Substitute a memo-wielding boss for the axe-bearing madman, and this could have been an anecdote overheard in a coffee house after work.

Distancing the reader from the action in this manner is an unfortunately common tactic in memoirs and first-person fictional narratives alike. Instead of showing the reader what happened through a fully realized scene, the narrator simply summarizes; rather than demonstrating relationship dynamics through dialogue or action, the narrator just sums up what was said. And by describing subsequent actions in the same words or in hackneyed terms (I believed my eyes must be deceiving me? Really, Mark?), the action may move forward, but the reader’s understanding of what’s going on does not.

Joan stood; Benoist glided. Then Joan stood while Benoist glided. Then she stopped — odd as the narrative had not shown her going forward. Then the narrator conveniently blacks out so we cannot see what is going on. Then the problem is solved. The end.

Seldom is this the most interesting way to convey a story, in my experience. Like having characters answer yes-or-no questions with yes or no, as opposed to more detailed (and thus more character-revealing) responses, the summary route closes off story possibilities. And by definition, repeated phrasing adds nothing new to the scene.

Neither, incidentally, do all of those thens: in a story in which events are being presented in chronological order, the occurrences in Sentence 1 are presumed to have happened before those in Sentence 2, which in turn came before what’s described in Sentence 3. Thens, then, as we have seen them used in that last example, are logically redundant; most editors would advise you to reserve them for moments when what happens next is genuinely unexpected.

Joan stood; Benoist glided toward her with an axe. Then the Wright Brothers and their sister, Katherine, swooped through an opening in the forest canopy in a motorized glider to snatch the weapon away.

Admit it — you didn’t see that last twist coming, did you?

Remember, there’s more to telling a story than simply listing its events in chronological order — or racing from its beginning to its end. You want the journey to be both memorable and enjoyable for the reader, do you not? And if the narrative can manage either to surprise the reader with an unanticipated turn of events, delight her with astonishing imagery, or intrigue her with beautiful phrasing — ideally, all three — all the better.

Before I release you to ponder the challenges of expanding a first-person narrative from the anecdotal level into a completely inhabited scene, I want to talk about another common faux pas: the further distancing effect of the narrative’s reminding us repeatedly that the narrator is seeing this or that. Obviously — at least from a professional reader’s perspective — if an action or object is depicted in a first-person narrative, the narrator perceived it; otherwise, she could not legitimately bring it up, right? So when Twain’s narrator tells us repeatedly that he saw Joan do this or Benoist do that, it’s logically redundant.

Of course, he saw it: he was standing right there. Why bother to remind the reader of that self-evident fact? Or, to put it as a garment-rending professional reader might, does the author think the reader is too brain-dead to remember who the narrator is and that he is present?

Oh, you don’t want the pros to take every word you commit to the page that seriously?

Again: if it’s on the page and the writer appears to possess even the slightest vestige of talent, Millicent is going to assume that it’s there on purpose. She’s also going to assume, with good reason, that if a writer has set up rules for how the story is to be told — in this case, from the point of view of a childhood friend of Joan’s, and only from his perspective — the narrative will follow those rules consistently.

This, too, trips up quite a lot of memoirists and other first-person narrator-wranglers. Once a narrative is committed to a single perspective, it cannot report anything outside of it without shattering the illusion of a limited point of view. Thus, when the narrator slips into the first person plural, informing us that we saw this or thought that, it’s jarring to the reader’s sensibilities.

And when, like Twain’s narrator, he professes to know what we all are thinking…well, let’s just say that maybe Joan isn’t the only one who needs to be worrying about going on trial for dabbling in the supernatural. Unless the narrative establishes some means by which a first-person narrator could possibly have reliable insight into other characters’ thoughts and feelings, he should really stick to his own. If his thoughts and feelings are somehow different from every Tom, Dick, and Benoist’s who might be hanging around in the same place at the same time, great; if he can manage to express them in language evocative, memorable, and tailored to his individual worldview, even better.

Which is not a bad definition of memoir voice, if you think about it: a narrator with a strong personality and specific worldview recounting situations of significance to an overall dramatic story arc in language and from a perspective unique to the teller. If every sentence of your memoir — and, to bring this back to our series-in-progress, every sentence of your query’s book description — does not rise to that level, you might want to think about revising it. Millicent will thank you. So will your readers.

So Mark, darling, as much as I admire your writing in general and short stories in particular, if I were your editor — oh, you thought that editors don’t hope this type of activity would be the first, best use of a time machine? — I would insist that you sat down and revised these three pages. Actually, I would do it because I admire your writing: your narrative voice, even in this rather serious book, is better than what we’re seeing here.

And that axe you keep telling us you’re seeing, narrator? That’s your editor, chopping away all of that phrasing and conceptual redundancy. Trust your reader’s intelligence a bit more, please.

I know, I know: this is a heck of a lot to absorb for a single post. Fear not; I shall be revisiting many of these issues after I polish off the last of the reader-volunteered queries. For that limited purpose — that is, for your edification prior to my next post — just bear in mind that not only does Millicent expect a memoir to have a well-defined voice and story arc; she presumes that by the time that memoirist sends her boss a query, the projected voice and story will be so clear in the writer’s mind that both can be adequately (nay, compellingly) conveyed in a paragraph or two.

Piece o’ cake, right? Well, no, but we can give it the old college try.

Just don’t turn in a term paper I’ve clapped eyes upon before, okay? Keep up the good work!

Bringing those unbelievable stories to life on the page, or, well-mannered camel seeks wiser man

It’s Christmas Day, campers, but my tree has gone dark: the electricity has been out for the last two hours. The local authorities claim that gigantic boom we all heard around noon resulted from a frantic windstorm’s having taken out a transformer. A less literary-minded analyst might take this story at face value. You can’t fool me, though. This is obviously Phase I of the Grinch’s most recent plan to steal Christmas.

Either that, or the Great Celestial Plotmaster(s) have been reading a lot of classic mystery lately. The day has all the hallmarks of the genre: while stoplight at the top of the hill’s being on the blink (or, rather, uncharacteristically not being on the blink) is admittedly the kind of thoughtfully-selected, pragmatic detail that makes a fictional world spring to life on the page, my brunch guests’ finding themselves plunged into darkness — or as close to darkness as a deep gray Seattle afternoon will permit — must hardly have come as a surprise to those familiar with the genre. I’ll bet you saw it coming the proverbial mile away. What’s next, a cat leaping out of nowhere to startle us at a suspenseful moment?

I mean, really: all of the characters are gathered in one place, and the lights go out? Even the Agatha Christie-impaired around the table immediately began making nervous jokes about which one of us was about to meet a grisly fate.

That’s why, in case any of you have been wondering since last spring’s foray into editorial pet peeves and how to avoid them, I tend to urge savvy revisers not only to scan their manuscripts for places where summary statements (such as All the lights went out could be productively replaced with character- or situation-revealing details (In the middle of the soup course, the chandelier suddenly gave up on emitting light. Even the stoplight at the corner had ceased blinking annoyingly in Montel’s peripheral vision. The butler fumbled in the sideboard for matches.), but for opportunities to surprise and delight the reader with unexpected specifics (In the middle of the soup course — a clear, sherry-laced leek broth with a jaunty dollop of crème fraîche floating gaily on top — the dusty chandelier suddenly gave up on its losing battle to shed light on the table. Even the stoplight at the corner had ceased blinking annoyingly in Montel’s peripheral vision. Startled, he knocked his shrimp fork onto a passing cat.).

My, but that was a long sentence. Somewhere in the literary stratosphere, the late Henry James must be chortling over his holiday goose, muttering to Edith Wharton, “They just don’t make ‘em like that anymore.”

“Too few semicolons for my taste,” Edith replies. “And watch your elbow: if you knock the figgy pudding over, you are sure to set the tablecloth on fire.”

My point, should any of you by some remote chance have lost sight of it in the midst of all that frenetic activity, is that while every type of book — and certainly every genre of fiction — has its own conventions, tropes, and characterization expectations, word for word, a writer is going to get substantially more expressive mileage out of a creative telling deal than one that any inveterate reader of that book category could guess. Or even, if it’s a common enough element, add subconsciously to the scene if it does not appear on the page.

Oh, when you read that second description of the lights going out, you didn’t murmur, “I bet the butler did it,” before your eyes passed the parenthesis at the end of the example?

Yes, Millicent the agency screener is encouraged — indeed, is often explicitly trained — to be on the look-out for manuscripts that read like, well, books in their chosen categories, and yes, each book category, particularly each genre fiction category, has its own recognized and recognizable plot twists, plot lines, stock characters, and, yes, types of details. Because agents specialize in particular types of book, as well as certain types of voices — a fact well worth bearing in mind when selecting which agents to query — it does tend to be to a writer’s advantage at submission time if the manuscript fulfills category-specific expectations. (That’s as true in a query’s descriptive paragraph as in a submission’s first few pages, by the way: if the text doesn’t sound as though it would fit comfortably within the manuscript’s chosen book category, it will usually be rejected.)

Let’s face it, though, the line between making your text read like it belongs shelved with others like it and like a cliché fest can sometimes be pretty thin. Many an aspiring writer believes, mistakenly, that producing a pale replica of a famous author’s writing is a better way to win friends and influence people at an agency than to come up with something more original. Or, even more mistakenly, does not become familiar enough with what’s currently being published in that book category to be aware what conventions would now strike someone who deals with those manuscripts for a living as passé.

To put it another way: when was the last time you read a mystery in which the butler actually did it?

The result, unfortunately, is that our poor Millicent tends to see the same types of specific — as well as the same plot twists, character types, and even phrasing — over and over and over again. When you consider the sheer volume of stories within the same category any agent successful in selling such books receives in any given year, that’s hardly astonishing.

The trouble is, most submitters remain woefully in the dark (and not because the lights went out) about how such elements are likely to be received at an agency. Good writing in a particular book category is good writing, right?

Sheer repetition has made Millicent believe otherwise, alas — but honestly, it’s hard to blame her for feeling that way. What might strike Writer A as requisite for that genre is frequently precisely what Writer B considers an homage to a classic and what Writer C will decide to drop in as a humorous riff on a cliché. And that’s not even counting what Writers D-F will honestly believe is original, but is actually a subconscious lifting of material or phrasing from an admired book.

“Oh, come on,” Millicent mutters, scalding her lip on that too-hot latte she forgot in her annoyance she had set aside to cool. “Does this writer honestly think that someone who reads as much as I do can possibly read an opening line like Yesterday, I fantasized that I returned to Ottawa without Daphne du Maurier’s REBECCA springing to mind? Last night I dreamt I went to Manderlay again is arguably the most famous first line in the genre!”

Wondering why I am bringing all of this up in the midst of a series on querying? Well, several reasons. First, I wasn’t going to post today at all, but as my guests went home when the soup got cold, I had a bit of extra time on my hands. I also had a charged-up laptop, as it happens, so clearly, this is kismet.

Especially as I had a holiday-themed anecdote I had been itching to recycle, anyway. I could have worked it into a series of queries, but hey, it’s a holiday — I thought everyone might enjoy a little break from our two solid months of query consideration. And correct me if I’m wrong, but I’m guessing that those of you devoted enough to your writing to be checking in at Author! Author! today might be more seriously interested in a discussion of craft than your garden-variety casual Internet browser.

Either that, or you might be trying to avoid your nearest and dearest. I’m happy to help you do that, too.

So gather close to the Yule log, campers, and let me spin my tale. As you read, try to think like Millicent: does the narrative contain enough specifics to provide all of the characterization needed? Does it occasionally stumble into the realm of cliché? While you’re at it, why not embrace the chance to embrace the Author! Author! tradition of trying to figure out what editorial tweaks could improve the story?

Curly the camel, Moe the donkey, and, to mix Christmas traditions as thoroughly as possible, Donner the reindeer have been on tour together, strip mall manger scene after strip mall manger scene, since they were just small, furry refugees from the petting zoo where they were born. Despite their years of entertainment experience, my local nursery — plants, not animals — plasters the six-foot wire fence around their enclosure with warnings to wreath-buying patrons about keeping their fingers, gloves, hat pom-poms, scarf tassels, and bundled-up infants away from Curly’s long reach, Moe’s strong teeth, and Donner’s oddly-shaped antlers.

They also, somewhat less emphatically, erect a sign informing dog-owners that crèche livestock are not, to put it mildly, best friends with man’s best friend. Since dogs cannot, unfortunately, read and many leash-tugging owners apparently do not, poor Curly frequently thrusts himself between some yapping visitor and his hoofed friends. Nearby, nursery personnel visibly restrain themselves from shouting, “Hey, can’t you read?”

On the whole, though, human behavior seemed to leave the trio unfazed. Scores of children flung hay at them, bellowing, “Hey, Reindeer!” — or “Hey, Dog,” from those who had never seen a miniature donkey before or were confused by the ambient barking. The trio just stood there, blinking slowly, eyes glazed. Most of the time, the parents would intervene before the children grew too frustrated with their passivity and rushed the pens.

One small pink-clad screamer simply would not leave the animals alone, however. She kicked at the metal fencing, screaming words I was a surprised a kindergartener would be able to use correctly in a sentence, or, indeed, incorporate into her everyday vocabulary without getting expelled. When she picked up a rock, I wandered over to the fence to distract her with a hastily-constructed fairy tale about our barnyard friends. And camels.

Almost immediately, a bulbous man in shorts and a t-shirt materialized by my side. Despite ambient cold that left our breath visible, his exposed arms and legs were not even goose-bumped. “Come over here,” he barked at the little girl, dragging her along the fence until they were directly in front of Curly.

Was he going to make her apologize to the camel? Curly did not seem to be expecting it, but perhaps his furry friends would appreciate the gesture.

Releasing the quivering child, the man — whose clothing, I noticed, was emblazoned with advertisements for a local band and Nike, respectively, not the nursery — reached up and over the chain-link fence, snapping his fingers. Placidly, Curly dipped his head, extending his hyper-mobile lips toward the hand.

Curious to hear what happened next, aren’t you? That’s a good indicator that a scene is paced well. See how selecting those details carefully, as well as not over-burdening the text with explanations, can increase suspense while simultaneously moving the plot along?

So why, I ask you, would our old pal Millicent, have stopped reading part-way through paragraph #3? Because, I assure you, most would have: one of her most notorious pet peeves has reared its ugly head here.

If you pointed out that the narration switched tenses between the second and third paragraphs, congratulations! Paragraphs Nos. 1 and 2 are in the present tense; paragraph #3 is in the past.

Submissions and contest entries do that all the time; so do, believe it or not, descriptive paragraphs in query letters. Sometimes, they even switch back to the original tense later in the text, or vacillate from sentence to sentence.

Already, I can spot some raised hands out there. “But Anne,” adherents of variable tenses point out, and with some reason, “Paragraphs #1 and #2 describe ongoing conditions, while paragraph #3 on focuses upon one-time events. Doesn’t that mean that the tense choices here are appropriate, or at least defensible?”

Good question, lovers of the present tense. Professional readers — agents, editors, contest judges, writing teachers, etc. — are trained to spot redundancies in a manuscript. They’re also taught to leap upon inconsistencies.

In other words, Millicent is likely to assume that the change of tense is not the result of well thought-out authorial choice, but simply a mistake that did not get caught in the proofreading process — or, if this were a descriptive paragraph in a query, the after-effects of an incomplete merger of two different versions, one in the present tense and one in the past.

Why might that make her stop reading altogether? Like other commonly-made errors, the tense inconsistency may well jar her out of the flow of the story. Next!

You habitual tense-switchers are not particularly happy with that answer, are you? “Okay, so she’s detail-oriented, but this isn’t a writing mistake; this is a stylistic choice. So why would Millicent be annoyed by it?”

On its face, your logic is pretty sound, tense-switchers: it would indeed be possible, within the context of a civil conversation between author and reader, to justify the tense choices in the example above. A writer might ostensibly win an argument with, say, a writing teacher, critique group, or even an editor about keeping the switch in the text. But that doesn’t mean it would be a good idea to submit pages with tense inconsistencies to Millicent — or to her aunt Mehitabel the contest judge, for that matter.

Why, you ask? Long-time readers of this blog, chant it with me now: because the writer is seldom present when an agency screener, editorial assistant, or contest judge encounters his manuscript for the first time. Successful manuscripts, queries, synopses, and contest entries are thus those that do not require additional verbal explanation.

So even if the writer is technically correct, if a tense switch seems unjustified to Millicent — if it appears to be, say, an incomplete revision between a manuscript originally in the present tense and a subsequent draft in the past, or vice-versa — that’s usually the ball game. So why risk it? Especially when, as in this case, making the tense consistent does not detract at all from either the meaning or the voice of the section. Lookee:

Curly the camel, Moe the donkey, and, to mix Christmas traditions as thoroughly as possible, Donner the reindeer had been on tour together, strip mall manger scene after strip mall manger scene, since they were just small, furry refugees from the petting zoo where they were born. Despite their years of entertainment experience, my local nursery — plants, not animals — plastered the six-foot wire fence around their enclosure with warnings to wreath-buying patrons about keeping their fingers, gloves, hat pom-poms, scarf tassels, and bundled-up infants away from Curly’s long reach, Moe’s strong teeth, and Donner’s oddly-shaped antlers.

They also, somewhat less emphatically, erected a sign informing dog-owners that crèche livestock are not, to put it mildly, best friends with man’s best friend. Since dogs cannot, unfortunately, read and many leash-tugging owners apparently would not, poor Curly frequently thrust himself between some yapping visitor and his hoofed friends. Nearby, nursery personnel visibly restrained themselves from shouting, “Hey, can’t you read?”

On the whole, though, human behavior seemed to leave the trio unfazed. Scores of children flung hay at them, bellowing, “Hey, Reindeer!” — or “Hey, Dog,” from those who had never seen a miniature donkey before or were confused by the ambient barking. The trio just stood there, blinking slowly, eyes glazed. Most of the time, the parents would intervene before the children grew too frustrated with their passivity and rushed the pens.

That’s as painless a revision as you’re ever likely to encounter, folks, by see how big a difference it makes to the text? All it requires is a good proofreading eye and a willingness to view the story from Millicent’s perspective, not the writer’s. (The latter, after all, is already familiar with the storyline.) And need I even add that this variety of inconsistency is easiest to catch if one reads one’s submission or contest entry IN HARD COPY, IN ITS ENTIRETY, and OUT LOUD?

I thought not. Let’s move on with the story, to see if we can catch any other Millicent-displeasers.

Delicately, politely, as if he were extracting an egg from beneath a mother hen, Curly took the man’s fingers into his gargantuan mouth. The hand did not budge. The camel paused meditatively for a few seconds, tasting, then sucked the hand into his mouth up to the elbow, dragging the man up to his tiptoes.

Instinctively, I took a step toward the child. If the object lesson about the dangers of violating animals’ personal space was about to go horribly awry, the least I could do was shield her from seeing the bloody denouement.

The man waved me back with his free hand. “See, Tanya?” he told the saucer-eyed girl. “They like people. If you treat them nicely, they’ll treat you nicely.”

“That’s right, sweetie,” a stringy-haired woman called from the nearby wreath display. “Be nice to the animals, and they’ll never hurt you.”

“You just have to learn what they like.” A helpful bystander kicked a tall crate toward the man’s feet, so he could follow his arm skyward. “Camels love sucking on things.”

Mentally, I began taking notes, in preparation for my inevitable testimony in a court of law. “I think she’s got the point. Maybe it’s time to back off now?”

Okay, what’s the problem this time? Hint: it’s even harder to catch than the last.

No? What about all of that redundancy in the dialogue?

That made some of you do a double-take, didn’t it? “But Anne,” several exclaim, “that’s how people talk in real life! You’re not gearing up to tell us that Millicent finds realistic dialogue annoying, are you?”

Um, sort of. At least the parts of real-life speech that are redundant. Or not germane to what’s going on. Or just plain boring.

Which is to say, as any close listener to everyday speech would happily tell you, most of it.

Oh, how often writers forget that real-life dialogue generally does not reproduce well on the page! If I had a nickel for every time I’ve heard a writer say, “But s/he really said that!” or “But that’s what people really sound like!” I would buy my own Caribbean island and send my entire readers on free writing retreats.

“But Anne,” I hear some of you protest, “isn’t that pretty self-evident? Just as absolutely faithful recreations of real-life events often don’t translate well into fiction, neither does most dialogue. Am I missing an additional nuance here?”

Perhaps one: aspiring writers are also apt to forget that real-life dialogue is seldom character-revealing — and thus reproducing it in a manuscript will often not convey as much about a character as we sometimes expect. Take, for instance, the oh-so-common writerly habit of placing the speeches of an annoying co-worker, relative, ex-lover, nasty dental receptionist, etc. into fictional mouth of a minor novel character as a passive-aggressive form of revenge.

Come on, every writer’s at least thought about it. To a professional reader, the very plausibility of this type dialogue often labels it as lifted from real life:

“Oh, wait a minute, Sarah.” Pausing in mid-gossip, Theresa picked up the overturned plastic cup before anyone else could step on it, placing it neatly on the dining hall checker’s desk.

Dina the checker glared at it as if it was covered in baboon’s spit. “Don’t you dare leave your trash on my desk. Do you think I have nothing to do but clean up your messes?”

“It was on the floor,” Theresa stammered awkwardly.

“Don’t you give me your excuses.” Dina grew large in her seat, like a bullfrog about to emit a great big ribbet. “You walk that right over to the trash can. Now, missy.”

“I thought you had dropped it.”

“Go!”

“I’ll save you a seat,” Sarah offered, embarrassed.

Inwardly seething and repenting of her Good Samaritanism, Theresa obediently gave up her place in the block-long lunch line in order to take the walk of shame to the garbage receptacles on the far end of the dining hall. How quickly a good mood could evaporate!

Tell me: what about this scene would tip off Millicent that this really happened, and that Dina is a character, if not from Christmas Past, at least ripped from the writer’s actual experience? And why would her being able to tell this be a liability? Why, in fact, would Millicent be surprised if Dina never showed later in the book any side other than the touchy one displayed here — or, indeed, if she never appeared again?

Actually, that was a set of trick questions. The answer to each part is the same: because the narrative doesn’t provide enough motivation for the intensity of Dina’s response. Fairly clearly, the writer doesn’t think that any such explanation is necessary.

That’s usually an indication that the writer has a fully-formed mental image (negative, in this case) of the villain in question — something that Millicent, by definition, would not walk into the scene possessing. Nor would any other reader who was neither there when the incident occurred nor had heard the author complain vociferously about it.

In other words, what we have here is a rather subtle manifestation of the telling, rather than showing phenomenon. Because the writer experienced this exchange as nasty because Dina was nasty, she has assumed that the reader will perceive it that way as well. But without more character development for Dina — or indeed, some indication of whether this kind of insistence was typical for her — the reader isn’t really getting enough information to draw that conclusion.

Or any other, for that matter. It’s just an anecdote. Yet most self-editing writers, especially those who happen to be writing memoir, wouldn’t notice this narrative lack. Any guesses why?

If you immediately shouted that it was due to the fact that his memory of Dina the real person is so strong, help yourself to four peppermint cookies from the holiday table. In the writer’s mind, her character is so well established that he can just write about her, rather than helping the reader get to know her.

The other tip-off that this was a real exchange is that Theresa is presented as a completely innocent victim of an unprovoked attack. The pure villain vs. completely blameless protagonist is a dead giveaway that dear self is concerned.

And yes, I WAS darned annoyed when Dina — in real life, a very nice woman named Ellen who happened to be having a spectacularly bad day — misinterpreted my act of good citizenship. If I crave well-deserved vindication from the total strangers who might conceivably read this story, however, it’s incumbent upon me to do quite a bit more character development. Not to mention integrating the incident into the storyline well enough that it’s actually interesting to read.

Of course, we want to be true-to-life in our dialogue: as Virginia Woolf tells us, “fiction must stick to the facts, and the truer the facts, the better the fiction.” But let’s not forget that in order to maintain a reader’s interest, a book has to have entertainment value, too — and that however amusing a verbal tic might be in person, repetition is often annoying in on the page.

This is especially true when a character is tired, angry, or in pain, I notice: all of a sudden, the dialogue sounds as though all of the characters are trapped in one of those interminable Samuel Beckett plays where the people are doomed to move immense piles of sand from one end of the stage to the other with teaspoons. See if this dialogue sounds familiar, theatre-goers:

A: “Oh. You’re home.”

B: (nursing the thumb the elephant trod upon in the last scene) “Yeah.”

A: “Have a nice day?”

B: “Um-hm.”

A: “I was cleaning out the attic today, and I came across that picnic blanket we used when we went out to Goat’s Rock Beach to scatter Father’s ashes. How it rained that day, and then the sun broke out as if Father and God had joined forces to drag the clouds aside to smile upon our picnic.”

B: “Yeah. “

A: “Ham sound good for dinner?”

B: “Yeah.”

A good third of the dialogue Millicent sees runs approximately like this, I tremble to report. Understand now why she might become just a tad touchy at the sight of dialogue that provides neither character development nor moves the plot along?

As a general rule of thumb — sore or otherwise — I like to flag any piece of dialogue that contains more than one use of yeah, really, yes, no, uh-huh, or, often, um. Almost invariably, these are an indication that the dialogue could either be tightened considerably or needs to be pepped up.

Similarly, anyway and however in dialogue are pretty reliable flares, indicating that the speaker has gotten off-topic and is trying to regain his point — thus warning the manuscript reviser that perhaps this dialogue could be tightened so that it stays ON point.

My fictional characters tend to be chatty (dialogue is action, right?), and I was once taken to task for it by a fairly well-known author of short stories. She had just managed to crank out her first novella — 48 pages typeset, so possibly 70 in standard manuscript format — so perhaps unsurprisingly, she found my style a trifle generous with words.

“Only show the dialogue that is absolutely necessary,” she advised me, “and is character-revealing.”

Hard to argue with that, eh? Yet, like most writers receiving critical feedback, I fought it at first. Since the dialogue in my advisor’s published works has seldom, if ever, strayed beyond three lines, regardless of situation or character, I was not particularly inclined to heed this advice — have you noticed how often it’s true that established writers with little or no teaching background spout aphorisms that all boil down to write as I do? — but I have to say, it has been useful in editing, both for others’ work and my own.

I can even derive an axiom of my own from it: if a person said it in real life, think twice before including it. If it isn’t either inherently interesting, plot-advancing, or character-revealing, does it really need to be there?

One more insight, then I’ll let you get back to your relatives: you’ve been having just a little trouble paying attention to my arguments, haven’t you? I’m betting that some substantial part of your mind has been distracted, wondering what happened to the arm in the camel’s mouth.

That, my friends, is how Millicent — and most other readers, professional and non-pro alike — feels when an interesting one- or two-paragraph teaser, the kind that aspiring writers so love placing within italics at the beginning of their manuscripts, gives way to an apparently or only tangentially unrelated second scene. Yes, we see it in published books all the time, but in a submission, it’s a risky strategy.

“Hey!” Millicent cries, spitting out her mouthful of scalding latte, “what happened to that darn interesting plot I’d gotten absorbed in? What’s this writer trying to do, hook me with something exciting, then drop me into a comparatively mundane storyline?”

Let’s be honest, folks: that’s precisely what most writers who use this trick are trying to do. Professional readers are wise to it by now.

Remember, part of being a good storyteller involves knowing when to relieve the suspense — and frankly, in the case of my camel story, Alfred Hitchcock himself would have chosen to do so by now. Ahem:

“Give me a boost,” the man asked calmly, but his eyes were beaming panic over his daughter’s head. Curly’s lips were exploring the first few inches of his t-shirt sleeve.

Since his arm appeared to be on the verge of being ripped off at the shoulder, the crate-kicker and I hastily complied. With his uneaten hand, he began tickling the camel’s lips, rubbing the gums as if he were a mammalian dentist. Curly face elongated, as though he were going to sneeze. A loud pop, a slurp, and the man’s arm returned to the land of the living.

He strutted his way down from the crate. “See?” he told the girl. “If you know what you’re doing, they won’t hurt you.”

“Yes, Daddy,” she whispered, staring aghast at his friction-reddened arm, manifestly resolving never to have anything whatsoever to do with an animal larger than herself again.

The moral, if I may venture one: just because something seems like a good idea at first blush doesn’t mean that it’s worth stubbornly adhering to it. One of the keys to successful self-editing is flexibility.

That, and keeping any parts of your body involved in typing out of animals’ mouths. Happy holidays, everybody, and keep up the good work!

Queryfest X: all of these questions aren’t burning you out on querying, are they?

How are you faring, Queryfest participants? (I was on the cusp of dubbing you Queryfesters, but the image the word evoked was a trifle distasteful. An editor never stops thinking about how words will scan on a page, as well as what they mean and how they might sound spoken aloud.) Are your queries looking bright, shiny, and relatively free of the straightforward errors and omissions that dog the garden-variety letter to agents?

Or — and please be honest with me; I can take it — is your original query concept now hanging in tatters, wafting in the wind, mournfully longing for the day when it felt ready to stride out the door and into Millicent the agency’s screener’s overflowing inbox, blithely unaware of just how stiff the competition is there?

Oh, those of you who felt this way thought you were alone? Actually, it’s a pretty common response to realizing for the first time that in the publishing world, every syllable of everything a writer submits is a writing sample. There’s no such thing, then, as a successful query that’s just kinda close to what Millicent has been trained to seek, nor is just hitting every point on an agency’s posted querying guidelines generally sufficient.

I feel an aphorism coming on: while those new to querying often presume that the query is just a formality, composed of a series of hoops through which an aspiring writer must jump, and that their writing will not be judged until an agent requests and receives manuscript pages, that is simply not how the system works. For the overwhelming majority of aspiring writers out there, the query letter is literally the only sample of their writing anyone at the agency will read.

To put it another way, in order to get an agent (or editor, at a small publisher) to read any of your manuscript at all, you will first have to convince her to do so. Querying and pitching are your only options to do that politely — and frankly, most writers’ conferences that allow pitching are quite expensive. As querying is the lower-cost option, a good agent’s inbox, either tangible or virtual, constantly overflows with missives from aspiring writers.

A good half of those communications will be so unprofessionally put together, poorly written, and/or missing crucial pieces of information — the type of book it is, for instance — that Millicent the agency screener will be able to tell at a glance that her boss, the agent, will not be interested. Another third will be better written and contain most or all of the necessary elements, but will arrive at agencies that just don’t represent that kind of book. (Yes, really — you’d be astonished at how few queriers seem to research agents before hitting SEND.)

Then there’s that top 17% or so, the conscientious writers that have taken the time to learn something about how agencies actually work. Their queries tend to be aimed at agents who represent books like theirs, at least, but they often undersell their own stories by trying to make them sound too much like a recent bestseller. Or mystify Millicent by not indicating a book category at all. Or even — sacre bleu! — inadvertently make themselves look unprofessional by adopting an inappropriately informal tone (Hi, George. Looking for solid memoirs by self-made businesspeople — well, have I got a book for you!), engaging in a generic hard sell instead of demonstrating the book’s market appeal (This is the next Great American novel, and you’d be a fool to pass up your chance to get in on the ground floor of what’s sure to be a blockbuster series!, or making claims that reveal they’ve just not bothered to do very much research about what books like theirs are gracing bookstore shelves these days (This is the only novel ever written about a woodcarver’s deep love of his craft, a devotion so profound that his pieces seem alive to him.)

“Yeah, right!” Millicent chortles, reaching for the omnipresent stack of form-letter rejections. “Hey, Geppetto, ever heard of an obscure book called PINOCCHIO?”

I sensed at least 5% of you shifting in your seats. “Gracious, Anne,” the time-strapped cry, clutching their suddenly pale cheeks. “I get that it’s in my best interest to pick a book category and target only agents who represent it, but what makes you think I have TIME to keep up with all of the latest publications in my chosen genre? It took me years to carve out the requisite hours to write my manuscript/draft my book proposal, and having to query at all, much less construct a synopsis, is eating great big holes into my revision time. Isn’t it more important to write a good book than to figure out how to sell it to an agent?”

Well, yes and no, pale clock-watchers. Yes, your chances of getting published are substantially higher if you have written a good book, but that alone is not sufficient endeavor to land an equally good agent for it — a fact which, unfortunately, most first-time writers of good books don’t figure out until they have been querying for a while.

Often not even then. Hands up, everyone who has heard a rejected fellow writer complain that the publishing world just isn’t ready for his book — that it’s too revolutionary, uses language too well, presents an entirely new spin on human relationships, exposes a secret unlike any that has been seen on the printed page before, etc. Keep those hands in the air if, upon subsequent questioning, you discovered that this paragon of literature got rejected at the query stage, rather than as a submission. And wave those hands mightily if you said, either to yourself or to the huffy writer, “Excuse me, Ambrose, but if all the agent saw was your query, how could your startling insights, blistering prose, and/or trenchant analysis of the human condition have been the reason she rejected it? Mightn’t the problem have been, you know, the query?”

Because I love you people, I’m not going to ask those of you who have been the Ambrose in this situation to raise your hands. You know who you are.

I am, however, going to ask Ambrose and those who happen to be personally fond of him to take a moment to ponder the possibilities here. Far too many talented aspiring writers assume that the only reasons their queries could have been rejected is some problem with the book: the story’s not marketable enough, publishers stopped buying chick lit two years ago, the protagonist sounds like a downer, etc. Accordingly, they become discouraged — what would be the point of continuing to query a rejected book? — and just give up.

I get why giving up on querying might be tempting — honestly, I do. However, there’s no denying that the book that isn’t particularly marketable today may well be next year, or even next month; keeping a weather eye on recent releases could help you there. It’s also undoubtedly true that agents’ tastes often change over time, as do agencies’ plans for where they want to place their focus, so the agency that rejected your last book flat might well be interested in your next. And let’s face it, where one agent (or, more likely, his Millicent) does not see market potential, another will, but you’re not going to find that out unless you persevere.

Then, too, if your query lands on the wrong desk, no matter how great the book in question is, or even how beautifully the query is written, it doesn’t stand a chance, right? The same principle applies if you approach the wrong agent within an agency; since the standard etiquette dictates that a writer may query only one, it honestly is worth doing your homework first. You can also kiss that agent goodbye– and you wouldn’t believe how common this is — if you queried the perfect agent too soon after you finished writing the book, before you’ve had an opportunity to go back over it with the proverbial fine-toothed revision comb.

You were aware, right, that you’re only supposed to query any given agent once with any given writing project? Oh, Millicent turnover is so rapid these days that it’s unlikely that the same human being will screen your query two years apart, but if you realize three months hence that Chapter 2 contains a huge continuity problem, sending a repeat query isn’t likely to revivify your prospects at that agency.

As frequently as Millicent sees all of these faux pas — especially the one about beginning to query too soon: now that many agencies allow queriers to include the first few pages in their query packets, it’s apparent far earlier in the process who has and has not taken the time to re-read or even proofread her work — there’s one that crosses her desk even more. I am referring, of course. to the query that reads exactly like 30 others she has read that day, for the exceedingly simple reason that there’s a template out there that 31 of the day’s queriers heard somewhere was sure-fire.

Trust me on this one: a personalized query will stand out in that crowd — and one that sounds remotely like you’ve done some reading of recent releases in your chosen book category will practically bring tears of relief to Millicent’s weary eyes. Returning to our query troubleshooting list…

(25) Is it clear from my query that I’m familiar with recent releases like mine? Even better, do I sound as though I have picked this agent based upon that familiarity?
This may seem like a subtle one from the writer’s side of the querying relationship, but on the query page, it’s often painfully obvious if the querier is thinking of both his book and his query list in generic terms: he has a book to sell, and agents sell books for writers, so any agent who sells remotely similar books will do, right?

Wrong. No agent represents every kind of fiction — and certainly not every conceivable kind of memoir. Actually, although it may be hard to tell this from a brief blurb in an agency guide, it’s relatively rare for agents not to specialize within a particular book category. And I’m not just talking about an agent’s preference for Highland romance over romances set in Ancient Rome, either: these people often like to see particular types of sentence describing those lads and lassies. As will soon be apparent if you take the time to go to a bookstore, pull recent books by three or four of the agent’s clients of the shelves, and read a few opening pages.

Research, my dears, research; there’s just no substitute for it — and the more specifically you can show the fruits of that research, the better. Why, you ask? In the interest of inculcating good writing habits, instead of telling you, I shall show you.

Let’s say, for the sake of example, that Desperate Togetpublishedson has written a YA novel set against the backdrop of the highly competitive junior show jumping circuit, a sterling piece of literature entitled NEVER SAY NEIGH. Let’s further assume that Desperate wants to query Literate McSalesperson, an agent with a long-established track record of selling books about horses and the preteens who love them.

That’s a great choice, probably based upon some solid research on who’s selling books like Desperate’s these days. But Literate’s Millicent would never know it from a query that opened like this:

Because you represent YA aimed at young girls, I hope you will be interested in my novel, NEVER SAY NEIGH. Fifteen-year-old Fifi never dreamed she would be faced with a wall that high…

That’s not bad, but Desperate’s honest-to-goodness market research doesn’t really shine here, does it? The bit about Literate’s representing YA for young girls could have been gleaned by the most cursory glance at one of the standard agency guides — or even a simple web search. (And news flash: most YA is aimed at young girls; they tend to read more than young boys.)

Let’s take a peek at what happens if our Desperate decides to be a trifle more specific.

I read in Jeff Herman’s Guide to Literary Agents that you were “looking for YA with strong female protagonists.” My novel, NEVER SAY NEIGH, definitely fits the bill: it’s about a young girl overcoming obstacles ranging from low tree branches to high walls to uncaring adults in her pursuit of becoming a champion show jumper.

Fifteen-year-old Fifi never dreamed she would be faced with a wall that high…

Better, isn’t it? If a trifle literal-minded: does the direct quote of what anyone in the industry would consider a fairly generic preference honestly help the case here? And does it really matter where Desperate picked up this information? A less pedantic presentation of the same information would make the same point without — please forgive my putting it this way, but it is how Millicent would think of it — sounding as though Desperate had read somewhere that he should include a reason for approaching Literate, but couldn’t come up with anything specific?

Calm down, Desperate, and try it again. Literate isn’t really looking for citations here.

Since you represent YA with strong female protagonists, you may be interested in my novel, NEVER SAY NEIGH. It’s the story of a young girl overcoming obstacles ranging from low tree branches to high walls to uncaring adults in her pursuit of becoming a champion show jumper.

Fifteen-year-old Fifi never dreamed she would be faced with a wall that high…

Ah, that’s nice — but if Desperate actually did go to the trouble of tracking down some other books Literate represented, that professional-level effort is not apparent here. Citing a specific book would leave no doubt on the matter. It’s an especially nice touch to bring up a first-time author’s title, underscoring that Desperate has done the requisite research to realize that Literate does take a chance on a new voice from time to time. (Not a foregone conclusion in the agenting world, by the way; it’s worth your while to check.)

Since you so ably represented Debuty de Firsttimer’s HOW AM I EVER GOING TO CLIMB INTO THAT SADDLE? I hope you will be interested in my YA novel, NEVER SAY NEIGH. It’s the story of a strong, determined young girl overcoming obstacles ranging from low tree branches to high walls to uncaring adults in her pursuit of becoming a champion show jumper.

Fifteen-year-old Fifi never dreamed she would be faced with a wall that high…

“But Anne!” the literal-minded cry, and who can blame you? “That nifty bit about the strong protagonists fell out of this version! Since Literate feels strongly enough about that preference to have mentioned it in her guide listing, shouldn’t Desperate bring it up?”

Ah, but Desperate did bring it up — by depicting his protagonist as strong, rather than just saying she was. Nifty trick, eh?

Do be certain, though, that any book you cite actually is comparable to yours. Don’t stray outside your book’s category, or you’ll defeat the purpose here. I hate to show a bad example, just in case blog-skimmer out there decides to copy it under the assumption that I meant it as a guide (oh, you’d be astonished at some of the comments I get from people who don’t read carefully), but as Desperate has been generous to make this mistake first, I’d like you to benefit from his sad experience.

Since you handled science fiction writer Outta Myleague’s extraordinary debut, THIS STORY HAS ABSOLUTELY NOTHING TO DO WITH YOUNG GIRLS OR HORSES, I am writing you in the hope that you will be willing to represent my YA novel, NEVER SAY NEIGH, the story of a strong, determined young girl overcoming obstacles ranging from low tree branches to high walls to uncaring adults in her pursuit of becoming a champion show jumper.

“Excuse me?” Millicent cries. “Do you not understand the term science fiction? Why on earth would an agent interested in one book want to read the other?”

Good question, Millie. Unfortunately, you’ve already rejected Desperate’s query, so I doubt you’re going to have the opportunity to discuss the matter with him anytime soon.

Do all of those glazed eyes out there indicate that some of you are frantically searching through your memories, trying to recall tidbits you have read about various agents and the books they have represented? Excellent. I have a bit more to say about how you might turn that information to your advantage, but in order to give you all some processing time, I’m going to veer our discussion back toward matters more technical.

(26) If I intend to submit this query to agents based in the United States, have I used ONLY US-spellings throughout my query packet? Or U.K. spellings, if I am sending it there or to Canada?
Hey, I told you the next one was going to be technical. While honour, judgement, and centre are perfectly correct in some places in the English-speaking world, they are incorrect in the US, just as honor, judgment, and center are on the other side of the pond, or even north of the border. And while your spell-checker may not find fault with either version, a New York-based Millicent is going to take one look at the former and say, “Great. Now some poor soul is going to have to comb through this manuscript, changing everything to U.S. spellings.”

I hate to burst any bubbles currently floating outside U.S. borders, but the publishing world’s opinion is united about who that poor soul should be: the writer. Who, let’s face it, might not be all that happy about the prospect. So in practice, when a query turns up here with U.K. or Canadian spellings, it says to Millicent, “Hi! If you ask to see this manuscript, not only will your finely-tuned editorial sense have you longing to correct the spelling every other page, but if your boss falls in love with the writing, she will have to have a rather unpleasant conversation with the writer.”

Yes, I am saying what you think I am, far-flung writers: if you’re planning to write for the American market, Millicent will expect you to use U.S. spellings in your query. Her boss is going to insist that you alter every single instance in your manuscript, anyway, so why not beat the Christmas rush and do it now?

You’re quite right — it’s annoying, but honestly, Millicent and her ilk have a point here. While books that have already hit the big time in the U.K. or Canada are routinely available in their original forms here, the original publication site dictates what is considered proper. Since a previously-unpublished manuscript with U.K. spellings would have to be altered before it could be released in the U.S. market, can you blame an agent for considering such a manuscript not ready for circulation to domestic agents?

At the query stage, though, the presumption of further revision’s being needed is not the only danger. You don’t want Millicent to think that you just don’t know how to spell, do you, oh centred, honourable person of sound judgement?

The same principle applies in reverse, of course: tailor your query and submission to what will look right to your intended audience, the agent, based upon where he resides. If you’re a Yank approaching a U.K.-based agent, you’ll be better off conforming to his view of the English language. (Unless, of course, you happen to be an American celebrity — then, your oddball spellings will be part of your complicated charm.)

Ready to start talking about books like yours again? Dandy.

(27) When I mentioned the book category in the first paragraph of my query, did I use one of the established categories already in use by the publishing industry, or did I make up one of my own?
Queriers new to the game often believe, mistakenly, that claiming that their books are so completely original, so unlike anything else currently for sale to the English-reading public, that even trying to squeeze them into one of the conceptual boxes provided by the industry would undersell their originality. Instead, these well-meaning souls just make up their own categories with names like Hilarious Western Romance with a Futuristic Feel to It or Time-Travel Thriller with Magical Realist Elements.

They think — again, mistakenly — that such descriptors are helpful to agents. How could being more specific than the average bookseller’s shelving system be bad?

In quite a number of ways, actually. To name but two, mythical book categories are unprofessional, and using them betrays a misunderstanding of why agents want to see them in query letters: to figure out whether the book presented is the kind that they currently want to sell. Also, an aspiring writer who clearly knows that she’s supposed to name a book category but tries to wiggle around it is playing rules lawyer, not a strategy likely to convince Millicent and her boss that she’s the type who just loves following directions without a fight.

Do it because they say so. If you’re at a loss about how to go about narrowing down the choices, please see the HOW TO FIGURE OUT YOUR BOOK’S CATEGORY section on the archive list at right.

“Can’t make me!” some rebels shout. “No one’s going to put my book in a conceptual box.”

That’s quite true: no one can force an aspiring writer to commit to a book category — at least before she’s signed with an agent, of course. Agents make their clients commit all the time. In fact, it’s not all that unusual for an agent to accept a new project as one category, ask for targeted revisions, then pitch it to editors as a different category.

A book category is nothing but a — wait for it — conceptual box, after all, a marketing label used to get a manuscript to the people who represent and sell similar books. So a categorical (so to speak) refusal to allow your work to be labeled at the query stage isn’t going to impress anybody familiar with how books are sold in this country.

Especially not Millicent — and especially if she happens to open your query at an inopportune moment.

Don’t believe me? Okay, picture this: Millicent’s subway train from her tiny apartment in Brooklyn that she shares with four other underpaid office workers has broken down, so she has arrived at work half an hour late. There’s an agency-wide meeting in an hour, and she needs to clear her desk of the 200 query letters that came yesterday, in order to be ready for the 14 manuscripts her boss is likely to hand her at the meeting. (Starting to read like a word problem in a math class, isn’t it?) After she has speed-read her way through 65 of the queries, a kind co-worker makes a Starbucks run. Just before Millicent slits open your query (#126), she takes a big gulp of much-needed caffeine — and scalds her tongue badly.

Oh, as though long-time readers of this blog didn’t see that coming.

Your query with its fanciful pseudo book category is now in her hand. What is she more likely to do, to humor your reluctance to place your book in the traditional conceptual box, as her boss will require her to do if she recommends picking you up as a client, or to shrug, say, “Here’s another one who doesn’t understand how the business works,” and move on to the next envelope?

Blistered tongue or not, do you really want to bait her? More to the point, is it really in your best interest to bait her?

If you’re absolutely, positively convinced that it would be an outrage upon the very name of truth to commit your novel to any one category, PLEASE don’t make up a hyphenate like Western-Vampire Romance-How-to, in order to try to nail it with scientific precision. In a pinch, if your novel doesn’t fall clearly into at least a general category, just label it FICTION and let the agent decide.

Provided, of course, that you are querying an agent who routinely represents fiction that does not fit neatly into any of the major established categories. I definitely wouldn’t advise this with, say, an agent who represents only romantica or hard-boiled mysteries.

But whatever you do, avoid cluttering up your query letter, synopsis — or indeed, any communication you may have with an agent or editor prior to clutching a signed contract with them in your hot little hand — with explanations about how your book transcends genre, shatters boundaries, or boldly goes where no novel has gone before.

Even if it’s true. Perhaps especially if it’s true.

Yes, such a speech makes a statement, but probably not the one the writer intends. Here’s how it translates into agent-speak: “This writer doesn’t know how books are sold.”

(28) Have I listed my credentials well in my platform paragraph? Do I come across as a competent, professional writer, regardless of my educational level or awards won?
I’m going to be revisiting the platform paragraph in more detail in a future post, but here’s the short version: if you have any background that substantially aided you in writing this book, you need to make sure you mention it in your query.

Period. Even your camp trophy for woodworking can be a selling point, in the proper context. Ditto with any publication, anytime, anywhere, regardless of whether you were paid for writing it. A publication is a publication is a publication.

But truthfully, unless you are writing a book that requires very specific expertise, most of your credentials will not actually be relevant to your book. But do say where you went to school, if you did, and any awards you have won, if you have. To professional eyes, these too are what I like to call ECQLC (Eye-Catching Query Letter Candy).

If you are a member of a regularly-meeting critique group, feel free to mention that as well, although this one is less effective than it used to be 10 or 20 years ago. (The Internet has spawned some pretty wacky writers’ groups, and Millicent knows it.) Anything that makes you sound like a serious professional is appropriate to include, though.

If you don’t have anything you feel you can legitimately report here, don’t stretch the truth; writers who do this almost invariably get caught in the long run. (The same holds true for queriers who include recommendations from people who didn’t actually recommend them, by the way.) Just leave out this paragraph. Unless, of course, you happen to be trying to find an agent or editor for a nonfiction work. Which brings me to…

(29) If I am querying nonfiction, have I made my platform absolutely plain? Would even a Millicent in a hurry understand why I am uniquely qualified to write this book, if not actually the best-qualified person in the known universe to do it?
A platform, for those of you unfamiliar with the term, is the background that renders a nonfiction author qualified to write a particular book. Consequently, “What’s the author’s platform?” is pretty much always the first question either an agent or an editor will ask about any nonfiction book.

Which means, in practice, that a nonfiction query that does not make its writer’s platform absolutely clear and appealing will practically always be rejected. And yes, you do need to satisfy this criterion if your nonfiction field happens to be memoir.

I know, I know: it’s self-evident that a memoirist is the world’s leading authority on his own life, but as I’ve mentioned before, a memoir is almost invariably about something other than the author’s sitting in a room alone. If your memoir deals with other subject matter, the platform paragraph of your query letter is the ideal place to make the case that you are an expert on that.

(30) Have I made any of the standard faux pas, the ones about which agents complain early and often?
I like to think of this as a primary reason to attend writers’ conferences regularly: they are some of the best places on earth to collect massive lists of the most recent additions to agents and editors’ pet peeves. I’ve been going through most of the major ones throughout this series, but some of them can be quite itty-bitty.

Referring to your book as a fiction novel, for instance, is invariably on the top of every agent’s list; in point of fact, all novels are fiction, by definition. A nonfiction memoir, a real-life memoir, a true memoirand nonfiction based on a true story, as well as permutations on these themes, are all similarly redundant.

Just don’t do it. If you thought Millicent was in a bad mood after she burned her tongue, trust me, you don’t want to see how she reacts to that memoir based on something that really happened to me.

Waffling about the book category is also a popular Millicent-irritant, as are queries longer than a single page, including promotional blurbs from people of whom the agent has never heard (Delphine Margason says this is the most moving book about figure skating she’s ever read!), or — chant it with me now, folks — ANY mention of the book’s potential for landing the author on a show hosted by someone like Oprah. Or Jon Stewart. Or Stephen Colbert. Or Charlie Rose.

Or…well, you get the picture.

Violating any or all of these will generally result in the query being tossed aside, unread. Especially the last; the average screener at a major NYC agency could easily wallpaper her third-floor walk-up in Brooklyn seven times over with query letters that make this claim — and I’m talking about ones that fell onto her desk within the last month.

Believe it or not, we still haven’t run through all of the common Millicent-irritants out there — and we have barely begun taking a serious gander at examples of what does and doesn’t work on the query page. Join me next time for more on these exciting topics, and, of course, to keep up the good work!

Queryfest, Part VIII: Millicent! Let us in! Millicent!

angry mob2

A quick announcement before I launch into today’s installment of Queryfest, aimed specifically at writers between the ages of 18 and 30 seeking some Eye-Catching Query Letter Candy (ECQLC). The deadline for Narrative Magazine’s annual 30 Below Story Contest is October 29th. Entry is limited to young adult writers — that’s writers who are themselves young adults, folks, not YA writers — and delightfully, there are some actual cash prizes not only for the top few entries, but for the finalists as well.

They will also consider all entries for publication, and my, is the range of what they are opening to publishing broad. Quoth the contest’s organizers:

Narrative is calling on writers, visual artists, photographers, performers, and filmmakers between eighteen and thirty years old, to tell us a story. We are interested in narrative in the many forms it takes: the word and the image, the traditional and the innovative, the true and the imaginary. We’re looking for short stories, short shorts, essays, memoirs, photo essays, audio and video stories, graphic stories, all forms of literary nonfiction, and excerpts from longer works of both fiction and nonfiction. The editors of Narrative have published the works of many new and emerging writers, who have gone on to become household names, and we continue to look for and to encourage the best new talent we can find.

So you might want to consider checking it out, ECQLC-seekers. Fair warning, though: there is an entrance fee.

Back to the topic at hand. Every time I devote a few weeks to a serious examination of all things query-related, I hear from many, many would-be queriers whose first (or at least second) reaction is to glance at the sheer number and length of the posts and back away quickly, clicking hastily away to another, less challenging writerly forum.

So if you have stuck with it so far, congratulations. Queryfest is not for the faint of heart, but then, neither is querying. Currently, it’s as hard as it has ever been for a first-time writer to catch an agent’s eye. The combination of a rise in home computer ownership, coupled with a slow economy, have caused the tide of queries pouring onto Millicent the agency screener’s desk on any given day to swell from its usual flood to something akin to a tsunami.

Hey, it’s tough out there. The why I have been urging you to take a hard, critical look at your query letter, to make sure that you are projecting the impression that you are an impressively qualified, impeccably professional writer waiting to be discovered.

As opposed to the other kind, who in agents’ minds swarm in legions like the mobs in Frankenstein movies, wielding pitchforks, pitch-soaked flaming torches, unbound manuscripts, and, of course, query letters, chanting endlessly, “Represent my book! Represent my book!” (Alternated with, of course, “It’s a natural for Oprah!”) It’s like a bad horror film: no matter how many of those manuscripts Millicent rejects, they just keep coming, relentlessly, pouring into the agency seemingly through every crack and crevice, appearing magically from some ever-renewing source.

Oh, you hadn’t been thinking of your query as part of an implacable daily onslaught on Millicent’s defenses? It’s no accident that she keeps burning her lip on lattés — her task can be so repetitious, so seemingly endless that even Sisyphus occasionally glances up from that immense boulder the unkind gods sentenced him to roll up a hill for all eternity, only to see it roll down again as soon as he reaches the top, mops his weary brow, and murmurs, “Wow, am I glad that I don’t have Millicent’s job.”

Contemplating how many queries she might have read prior to yours — not to mention the mountainous piles she may have to peruse between the thirty seconds she can devote to your letter and when she can go home for the day — can either be deeply depressing for a querier. Yes, it’s a bit intimidating to consider that the chances of a randomly-selected query’s leading to the book in question’s being picked up by a great agent and sold to a good publishing house fall somewhere between getting accepted to a top medical school and being hit by lightning while holding an umbrella. I remember thinking when I sold my memoir, gee, I’m about to get published, I’m a woman with a doctorate, and I’m ambidextrous. Statistically speaking, I’m about as likely to exist as a purple gorilla.

Just because something is unlikely, however, doesn’t mean that it can’t happen; there’s a vast difference between difficult and impossible. As I like to tell discouraged aspiring writers early and often, the only manuscripts that have no chance of getting published are those that just sit in a drawer or on a hard disk, unqueried, unsubmitted, and unseen by the literary establishment.

In case I’m being too subtle here: don’t let the intense competition keep you from trying. You might just end up being the gorilla with the all-over mauve highlights.

Don’t underestimate how much doing your homework about what a good querying entails improve your changes, either. Just think of what a high percentage of queries either do not contain all of the necessary information, or are improperly formatted, or are downright rude, mistakes you intrepid souls working your way through Queryfest are unlikely to make. Nor are your queries likely to be among the unfortunate many that substitute hard-sell tactics for description, picking an agent’s name out of a hat for serious research into what the query recipient represents, or a vague, rambling paragraph about what the book is about for the one- or two-word book category already in use by the U.S. publishing industry.

Feeling luckier already, aren’t you, Jungle Jim?

You’re also, if you follow my advice, going to separate yourself from the crowd by not forcing your book concept into a boilerplate that a third of the aspiring writers out there happen to be using at the moment. You wouldn’t believe how many query letters read virtually identically. And that’s bad for aspiring writers, because generic queries are among the easiest to reject: not only are they comparatively unmemorable — a boilerplate account of even a thrilling plotline tends to fall a bit flat — but your garden-variety Millicent finds them somewhat insulting.

And not merely because so many cut-and-paste operations intended to update old queries for reuse end up in disaster. Even when the address and salutation match AND end up in the right envelope, recycling the same query for every conceivable agent renders it effectively impossible to make sure your query ends up on the right desk.

Oh, it could happen, but so could Millicent’s coffee cup being hit by a meteor. Want to wait around to see if it happens, or would you prefer to make the effort to improve the odds?

No, but seriously, folks, the way that most first-time queriers approach figuring out whom to query is close enough to random that it’s surprising that they ever hit the right target. It just doesn’t make sense as a strategy for making a decision vital to the success of your writing career: if you don’t do individual research on each agent’s likes, dislikes, and placement record, how can you possibly know that any given one will be the best fit for your book? You don’t want just any agent to handle it, after all — your manuscript deserves the professional assistance of an agent with a proven track record of (and concomitant connections for) selling books like yours.

Agents are not generalists, any more than writers are: they specialize. That means, in practice, that a writer is unlikely to find such an agent by the simple (and unfortunately common) means of doing a web search on agents + {insert book category here}. Or by the formerly most popular alternative, snatching one of the standard agency guides off the shelf at the nearest bookstore, flipping to the index, and making a list of every agency that lists itself as representing that category.

While neither is a bad first step toward tracking down the ideal agent for a particular book, you must admit that neither is exactly a fine-tuned agent-seeking instrument. Yes, limiting your efforts to only those agents who represent manuscripts in your category is a necessary first step toward finding the best agent for your work — chant it with me now, campers: one of the most common reasons queries get rejected is being aimed at an agent who doesn’t represent that kind of book — but as many a query-fatigued aspiring writer can attest, it can result in a long, undifferentiated list. How does one decide whom to approach first?

Based on the comparative popularity of agencies whose names begin with A, B, or C, as well as those beginning with W, Y, or Z, my guess would be that most queriers simply proceed alphabetically — or in reverse alphabetical order. The fact that the D-V agencies tend to see fewer queries would indicate that embracers of this approach often give up in frustration before they get very far into their lists.

In the face of this undeniable reality, you can’t really fault Millicent for regarding the lack of a clear statement of why a writer selected her boss off a list of agents representing that book category as evidence that he might not have done his homework, can you? Most of the mob beating on the gate at any given moment is made up of homework-avoiders, after all.

Which brings me to the other primary reason for striving for an individual voice in your query letter: to Millicent, a well-written, personalized letter that describes a manuscript in clear, enticing, market-oriented terms is — wait for it — professional. As in exhibiting the minimum level of performance for getting her stamp of approval.

That means, in practice, being specific. And yes, I know that’s hard, in a document must contain a an extremely brief summary of your book.

Therein lies the problem, often. The first thing most aspiring writers learn about a query is that it should contain a description of the book it is hoping the agent will represent. (Okay, the second thing: the requirement that a query be a page or less is quite widely known.) To the first-time querier, that can sound an awful lot like you have only a page to summarize a 400-page manuscript!

That’s ridiculous, of course — a querier has only a paragraph (or two, at most) to describe her book. Less, if the description isn’t particularly interesting or doesn’t make the book seem like a good fit for either the agent to whom the query is addressed or the current literary market.

A 1-page synopsis is where that writer has to summarize her 400-page book. Note the distinction, please: it’s vital to your sanity while composing a query — or trying to keep it under a single page, for that matter. In fact, I feel an aphorism coming on:

broken-recordA query’s descriptive paragraph describes the manuscript; a synopsis summarizes it. The query presents the premise and central conflict (or, for nonfiction, the subject matter and central question), while the summary gives a complete, if brief, overview of the plot, including some indication of its resolution.

Why is being aware of this distinction vital for a savvy querier’s sanity? Because if you try to summarize the entire plot of your book in a query letter, you will drive yourself mad.

And, frankly, you will annoy Millicent. We may see why all too clearly manifested in the generality-fest that is average descriptive paragraph:

THE SIMPLEST PLOT OF ALL tells the story of boy meets girl set against the turbulent backdrop of the type of war aptly described as hell. Although Dwayne and Mimette initially don’t click, circumstances throw them together and they fall madly in love. Through confronting numerous obstacles, they come to know themselves better and learn important life lessons before finding their very own happy ending.

Quite the a cliché-fest, isn’t it? That isn’t always the case with a too-general descriptive paragraph, of course, but the two often go hand-in-hand. As far as Millicent is concerned, they can keep on walking hand-in-hand right into the sunset, just like Dwayne and Mimette: her job is to look for original stories.

Which THE SIMPLEST PLOT OF ALL might be, for all we know. But how on earth could Millicent tell, given the vagueness of this description?

Aspiring writers with a bit more knowledge about how agencies work may veer off into another type of generality, the lit class description. It tends to run a little something like this:

THE NUCLEAR FALLOUT WITHIN is a classic political thriller written in a literary fiction voice. Told in the first person from four different and conflicting points of view: a handsome protagonist (Senator Lance Manlison, 38), a brainy yet uninhibited love interest (Dr. Bambi-Pearl Dignityfree, 23), an odious antagonist (Snarly Weaponwielder, 52), and a deaf-mute unrelated bystander (Cheapdevice Smith, 13). Deftly alternating between these distinct voices, the narrative draws the reader into a beautifully-described world of intrigue, power, and intense introspection.

Both of these examples are probably factually correct statements about what occurs in the book, but that’s really beside the point at the querying stage. “What specifically are these books about?” Millicent is left muttering. “And why aren’t either of these writers using the scant space afforded in a query to demonstrate that they know how to tell a story? Are they under the impression that how they write doesn’t matter?”

I can answer that one, Millie: at the querying stage, that’s precisely what most aspiring writers do think; many regard the query as little more than an annoying-but-necessary piece of busywork, rather than an opportunity to show that they can write. But they’re wrong: the goal here is to stand out from that teeming population of queriers by coming across as a good writer with a good, marketable story.

The idea of your writing being judged solely by how you construct a single-page letter is making some of you squirm, isn’t it? “But Anne,” wiggle worms everywhere protest, and with good reason, “I’m a novelist. My gift lies in expressing myself at length. Why would any agent who represents book-length works allow, much less instruct, his trusty Millicent to make snap judgments about books without reading them?”

I sympathize with your feelings, but that agent cannot afford to: remember that tsunami of queries washing over Millicent’s desk? If she had to read even the first few pages of every single one of those manuscripts before ruling out those that are out of the question, she would constantly be swimming through an ocean of required reading.

Can you honestly blame her for draining the pool a little by rejecting the vague and the publishing world-inappropriate book descriptions on sight?

Most descriptive paragraphs don’t go to either of these extremes, of course; many are combinations of both, with perhaps a sprinkling here and there of detail. That’s not all that astonishing, given the comparatively scant attention most query-writing classes/seminars/online discussions seem to devote to the part of the letter where Millicent is most solidly within her rights to expect your writing to shine.

Hey, every writer can talk compellingly about his own manuscript, right? It’s the rest of the query that really matters, doesn’t it? And if the query reads just like what the writer has seen online, it has to be fine, doesn’t it?

Apparently and unfortunately, no, on all counts. I feel an aphorism coming on: the overwhelming majority of descriptive paragraphs are not sufficiently descriptive — a real shame, because the descriptive paragraph is the querier’s single best opportunity to make the case that her manuscript is unique. Preferably in the a voice similar to the narrative voice of the book.

Does that gargantuan gulping sound I heard out there in the ether mean that two-thirds of you with queries already circulating just realized that they did not do justice to the storytelling magic of your manuscript? Or did you think the point of the description was to make your book sound identical the most recent bestseller? Or — and I suspect that this is going to be the more common gulp-generator — were you previously unaware that the descriptive paragraph (and the query in general) is a writing sample?

On the off chance that it was any of the above, I’m going to drag out the broken record player again:

broken-recordEverything an aspiring writer submits to an agency is in fact a writing sample. Since the agent of your dreams is new to your writing, it’s only reasonable to expect that he will use your query letter, your synopsis, any requested pages, and even your e-mails and cover letters for submissions as bases for evaluating your writing ability. These are literate people; they expect good writers to express themselves well 100% of the time.

At minimum: spell-check everything before you hit the SEND key. Proofread everything — preferable in hard copy, as it’s easier to catch typos and logic problems that way. If you don’t know the difference between its (belonging to it) and it’s (a contraction for it is), or how to make a word plural (hint: almost never by adding an apostrophe + s), learn it. And if you have any doubts about your own grammar or proofreading abilities, run, don’t walk, to someone whose skills are impeccable.

But most of all, use your query as an opportunity to demonstrate to Millicent that, in addition to being charming, literate, and creative enough to come up with a great premise, you can tell a story well. Specifically, the story of your book.

Generally speaking, summary statements are not the best way to pull this off. Too many aspiring writers mistakenly believe that a generic query filled either with overly-broad generalities (my protagonist is Everyman struggling with quotidian life’s most common challenges.), promotional copy (this is the most exciting book featuring childbirth since GONE WITH THE WIND!”), or just plain one-size-fits-all rhetoric (This is a fiction novel with great writing based on a true story.) will be sufficient to pique an agent’s interest. All of these tactics are problematic, because a vague query will sound just like a good two-thirds of the query letters Millicent’s seen that week, and thus hardly likely to stand out amongst the forest of torches storming the castle.

Or, as she likes to put it: “Next!” But the news is not all bad here, campers: our Millie has a pretty good eye for spotting the rare purple gorilla.

When a query is simultaneously unique and yet professional, the result can be semi-miraculous. That means, in practice, that for a talented querier, the ubiquity of poorly-constructed queries is actually helpful.

How so? Call up that angry mob in your mind, the one that’s casually dropping by en masse to ask Dr. Frankenstein if that undead thing that’s been lurching about Geneva lately could possibly be his houseguest. Now picture yourself pushing through that crowd, impeccably dressed, to knock on that castle door. For Dr. F’s assigned gate-keeper, Igor, to open the door, he’s going to have to believe that you’re not merely a cleverly-disguised villager intent upon destroying the secret laboratory where his master dabbles in revivifying the dead, right?

So, too, with Millicent: a politely-worded, grammatically impeccable, well-written query is going to leap off the page at her, simply because such a low percentage of what crosses her desk meets those criteria. And frankly, that fact is very useful to her, because she can quickly reject the vast majority of the angry mob’s attempts to knock down that door.

Okay, so maybe that analogy was a trifle forced. Very few of the agents of my acquaintance actually make a habit of prying open those well-known doors that mankind is not meant to open, and not all rejections are that knee-jerk. But you can’t deny that picturing Millicent triple-bolting the castle door made a change from imagining her burning her lip on yet another too-hot latté, right?

broken-recordA good agent typically receives in the neighborhood of 800-1500 queries per week — more, if the agency makes it easy for aspiring writers to submit pages online with their queries or happens to fall at the beginning or end of an alphabetical listing. In the face of that constant barrage, even the most prose-loving Millicent is going to have to reject the vast majority that cross her desk, if only in self-defense. The generally-accepted figure is 98%.

Starting to make more sense that I’ve been pushing you to concentrate this hard upon a page of writing that isn’t even in your manuscript? I’m just trying to save you some time, and some misery — and a whole lot of rejection.

So print up your latest query letter draft, please, and ask yourself a few more probing questions before you pop that puppy in the mail. To prepare yourself properly for this level of analysis, take a moment now to read your current draft in its entirety and aloud, so it is clear in your mind — and to catch any lapses in logic or grammar, of course.

To stop the protest already halfway out of your mouth: I don’t care if you reread (or wrote) it yesterday, or already today, or fifteen minutes ago. Do it again, because now you’re doing it in hard copy, where you’re significantly more likely to catch itty-bitty errors like missed periods.

Why aloud? Because it’s the best way to catch a left-out word or logic problem. Haven’t you been paying attention?

Don’t feel bad if you find a few: believe me, every successful author has a story about the time that she realized only after a query or a manuscript was in the mailbox that it was missing a necessary pronoun or possessive. Or misspelled something really basic, like the book category.

Yes, it happens. All the time. Millicent has good reason to regard queries as miniature Frankenstein manuscripts.

And if you don’t read it ALOUD, IN HARD COPY, and IN ITS ENTIRETY one final time between when you are happy with it on your computer screen and when you apply your soon-to-be-famous signature to it…well, all I can do is rend my garments and wonder where I went wrong in bringing you up.

Now that you’re thinking of your query as a writing sample, let’s take a quick foray back up the page before we move on to that pesky descriptive paragraph.

(15) Does the first paragraph of my query show that I am a good writer, as well as convey the necessary information? Does it get to the point immediately? Or, to but it a bit more bluntly, if I were an agency screener with 200 other queries on my desk or in my inbox, would I keep reading into the descriptive paragraph?
This may seem like draconian questions, but think about it from Millicent’s perspective: if you had to get through all of those queries before the end of the afternoon, would you keep reading the one in front of you if its first paragraph rambled? Or if, heaven forfend, it contained a typo or two?

Oh, you say you would. But honestly, would you?

It’s worth revisiting the first paragraph of the query letter because — oh, it pains me to be the one to tell you this, if you did not already know — countless query letters are discarded by agents and their screeners every day based upon the first paragraph alone. That’s another reason I favor paper over e-mailed queries, incidentally, except in the case of agents who specifically state they prefer them over the paper version: it’s too easy to delete an e-mail after reading only a line or two of it.

Take a good, hard look at your first paragraph, and make sure it is one that will make the agent want keep reading. Does it present the relevant information — why you are querying this particular agent, book category, title, etc. — in a professional, compelling manner?

Cut to the chase. All too often, when writers do not make their intentions clear up front — say, by neglecting to mention the book category — the letter simply gets tossed aside after the first paragraph.

All right, on to paragraph two:

(16) Is my descriptive paragraph short, clear, and exciting to read? Have I actually conveyed what the book is ABOUT?
Frequently, aspiring writers get so carried away with conveying the premise of the book that they forget to mention the theme at all. Or, as we discussed above, they try to cram the entire synopsis into the query letter. Given that the letter should never be longer than a page, that strategy tends to result in a missive that neither presents the book’s story or argument well nor leaves room for the necessary other elements of the query.

So what should you do instead? Limit the scope of what you are trying to achieve to making the book’s premise or argument sound fascinating.

How might one go about that? Well, for starters, buy yourself some space by axing the lit class terminology: this is not the place to talk about protagonists, antagonists, or plot twists, at least not using those words. Ditto with introductory statements like ALTERED REALITIES is the story of… or SIMILAR FANTASIES tells the tale of… If the opening paragraph has done its job properly, these kind of clauses are never actually necessary.

Second, concentrate upon presenting the protagonist as an interesting person in an interesting situation. A time-honored one-paragraph descriptive structure demonstrates why the lead is special in the first sentence or two (utilizing parenthetical age references to save space), devotes the second sentence to the plot’s central conflict, and the third to what’s at stake for the protagonist. As in:

Photojournalist Nana Angelopoulos (27) is far from an inexperienced traveler: her passion for documenting vanishing wildlife has brought her face-to-face with more charging rhinos, furious rattlesnakes, and irate, weapon-brandishing game wardens than even her worried mother (Irene, 56) can remember. Yet now that her favorite preserve is going to be sealed off from human contact forever, she has abruptly begun having panic attacks the moment she steps on a plane. Has the shutter come down permanently on both Nana’s career and the endangered red pandas she loves?

For a character-driven plot, you can focus even more closely on the protagonist. Try opening with your main character’s hopes and dreams, moving on to the primary barriers to his achieving them, and then wrap up by telling Millicent what he stands to win if he overcomes those obstacles — or what he stands to lose if he doesn’t. For example:

All retired paleontologist Sven Olafson (87) wants is a little peace and quiet, but who could relax with intrepid junior explorer Tammi Butterfingers (11) constantly digging for dinosaur bones in his back yard? Or twin grandsons borrowing in his stone tool collection to reconfigure the neighbors’ treasured marble birdbath? Or, worst of all, a malignant postman (Marvin, 62) determined to drive Sven from the only settled home he has ever had outside of a dig site?

Either structure will work for memoir, of course: treat yourself as a character in the book, change the pronouns to I, and tell Millicent what happened to you. Easy as the proverbial pie.

For other nonfiction, just set out the central problem of the book and give some indication of how you plan to address it. If you want to get fancy, toss in a sentence or two making the case that the problem is important, and to whom:

Sasquatches once roamed North America freely, but thanks to human overpopulation, few living children have ever even seen one. Once-mighty herds are now reduced to just a few square acres next to a Bigfoot preserve in southwestern Oregon. Ironically, just as human needs have nearly wiped out these magnificent beasts, human needs may save them from total extinction: new research indicates that molted sloth hair may be the long-sought cure for male pattern baldness. Begging the question: is the recent establishment of megalonychid-shaving factories a triumph in the fight against extinction, or merely vanity-induced animal abuse?

Reads like a well thought-out argument, does it not? What you’re doing here is not generalizing — you’re winnowing down the story to its essential elements. That’s doable, even in just a few lines.

When in doubt, err on the side of brevity over completeness. Remember, you honestly do have only — chant it with me now, long-time readers — 3-5 sentences to grab an agent’s interest, so generally speaking, you are usually better off emphasizing how interesting your characters are and how unusual your premise is, rather than trying to outline more of the plot.

But do make sure it sounds like a great story or fascinating argument on an important subject. As in a pitch, the first commandment of querying is thou shalt not bore — and believe me, nothing is more boring to someone who reads for a living than seeing the same kind of descriptions over and over again.

One of those torches waving in the night might be pretty, but when everyone in the village is brandishing one, it gets old fast.

Hark! Do I hear an angry mob beating on my battlements, chanting, “How may we both brief and interesting simultaneously?” In a word: juicy details.

Okay, so that was two words; it’s still a great strategy. Why not spice things up with details that only you could devise, described in lovely language? If you’re feeling even bolder, why not try waking Millicent up a little?

(17) Does my description use unusual details and surprising juxtapositions to make my story come across as unique or my argument as original? Or is the descriptive paragraph a collection of generalities that might apply to many different books within my chosen category?
What makes a book description memorable, whether it is fiction or nonfiction, is not merely its overall arc, but also its vividly-rendered details. Especially to a reader like Millicent who reads 50 such descriptions in a sitting, the difference between a ho-hum descriptive paragraph and one that makes her sit up and say, “Hey, I’d like to read this book!” tends to lie in the minutiae.

Not in a superabundance of minutiae, mind you: just a few careful-selected details she’s not likely to have seen before.

Unsure where the line between too many generalities and too much detail lies, flaming torch-bearers? When in doubt, stick to the central conflict; subplots, while perhaps integral to the book as a whole, tend to water down the storytelling impact of a descriptive paragraphs.

Why, you ask? Okay, let’s step into Millie’s shoes for a minute. Read these three summaries: which would make you ask to see the first fifty pages of the book and why?

Basil Q. Zink, a color-blind clarinetist who fills his hours away from his music stand with pinball and romance novels, has never fallen in love — until he meets Gisèle Démodé, the baton-wielding conductor with a will of steel and a temper of fire. But what chance does a man who cannot reliably make his socks match have with a Paris-trained beauty? Ever since Gisèle was dumped by the world’s greatest bassoonist, a sociopath prone to torturing innocent kittens in his spare time, she has never had a kind word for anyone in the woodwind section. Can Basil win the heart of his secret love without compromising his reputation as he navigates the take-no-prisoners world of the symphony orchestra?

Quite a few unique and unexpected quirks packed in there, aren’t there? I’d ask to read that book. Contrast this description with the far more common style of entry #2:

Clarinetist Basil Zink has fallen hopelessly in love with his conductor, temperamental and beautiful Gisèle Démodé. She’s emotionally unavailable, however: on the rebound from a ten-year marriage with sociopathic bassoonist Serge, she scarcely casts a glance in Basil’s direction; she hardly seems to be aware that he’s alive. Menaced by an ultra-competitive co-worker, Basil must overcome his fears to capture the woman he loves and save his orchestra.

Interesting how different it is from the first, isn’t it, considering that both describe the same story? Yet since #2 relies so heavily on generalities and is so light on unusual details, it comes across as a tad generic, not to say cliché-ridden.

How does a writer know when to say when on the specifics? Let’s take a gander at version #3, where a love of detail has apparently run amok:

BATON OF MY HEART is a love story that follows protagonist Basil Q. Zink, whose congenital color-blindness was exacerbated (as the reader learns through an extended flashback) by a freak toaster-meets-tuning-fork accident when he was six. Ever since, Basil has hated and feared English muffins, which causes him to avoid the other boys’ games: even a carelessly-flung Frisbee can bring on a blistering flashback. This circle metaphor continues into his adult life, as his job as a clarinetist for a major symphony orchestra requires him to spend his days and most of his nights starting at little dots printed on paper.

Life isn’t easy for Basil. Eventually, he gets a job with a new symphony, where he doesn’t know anybody; he’s always been shy. Sure, he can make friends in the woodwind section, but in this orchestra, they are the geeks of the school, hated by the sexy woman conductor and taunted by the Sousaphonist, an antagonist who is exactly the type of Frisbee-tossing lunkhead Basil has spent a lifetime loathing. The conductor poses different a problem for Basil: he has never been directed by a woman before. This brings up his issues with his long-dead mother, Yvonne, who had an affair with little Basil’s first music teacher in a raucous backstage incident that sent music stands crashing to the ground and left two dozen musically-minded six-year-olds agape in horror. Basil’s father never got over the debacle, and Basil…”

Okay, ersatz agency screener: how much longer would you keep reading? We’re all the way through a second descriptive paragraph, and we still don’t know what the central conflict of the book is!

Contrary to popular belief amongst queriers frightened by the prospect of having to talk about their manuscripts in marketing terms in Paragraph 1, what makes a descriptive paragraph great is not its ability to show how similar the book is to what is already published, but rather how it is different.

Oh, I don’t mean that a querier is likely to get anywhere with Millicent by claiming that his manuscript is like nothing she has ever seen before — that, too, has been said so often in queries that it has become a cliché — or that it’s a good idea to ignore the current literary market. You won’t, and it isn’t.

In order to sell any first book, however, a writer needs to be able to demonstrate that (a) it fits into an existing book category but (b) offers readers who already buy books in that category something they can’t already get by just walking into a bookstore.

Or, to cast it in grander terms: what will your book add to the literary world that it hasn’t already got, purple gorilla? Why will the reading world be a better place if your book is published?

Deep questions, eh? I leave you to ponder them. But as you do, don’t lose sight of the fact that part of what a writer is marketing is her unique voice. How could a query letter that sounds just like everyone else’s possibly do justice to that?

Keep up the good work!

Premises, premises

I honestly hadn’t intended to take the last few days off from blogging, but I assure you, I have a dandy excuse. To give you a hint, I invite you to contemplate the riddle of the Sphinx: what animal walks on four legs in the morning, two at noon, and three at night?

On to the day’s business — or rather, the business of last week. Scouring my to-blog-about list for amusing and thought-provoking topics to while away the time before the advent of Queryfest, my annual foray into all things query-related, I came across a terrific question from reader Kelly:

I have a question about plot clichés, if you have the chance to address it. Obviously, the “it was all a dream” won’t fly. What other common plot twists do those of you who see so many manuscripts just groan about? Thanks and feel better soon.

That bit at the end will tell you just how long even very good questions sometimes linger in my hey, that would make a great post pile: kind Kelly was wafting me positive energies immediately after my car crash last year. There’s been some recent progress in that area, by the way: after 14 months, I’m finally walking without a cane.

Can tap-dancing be far behind?

So if I’m honest about it, responding to Kelly’s question is really the business of last year. That seems oddly appropriate, given one of the publishing world’s most common complaints about writers: a fondness for procrastination.

Oh, don’t grimace; everyone procrastinates a little. It’s healthy not to be too rigid. Besides, one of the most important lessons any writer of book-length work has to learn is that a full-length manuscript is not the kind of thing that even the most gifted crafter of prose can polish off in a day, a week, or a month.

Oh, some writers (including yours truly) can indeed draft new text very quickly, but that’s not the issue. Writing a book requires consistent, patient application, not merely short, intense bursts of endeavor. So does revising a manuscript. Yet since most of us do our best work if we can devote some unbroken time to it, it can be very tempting to put off diving in — or diving back in — until we can devote a whole day, week, or month to it, isn’t it?

And that temptation, boys and girls, is why most serious writers have woken up on at least one fine spring morning, sat bolt upright in bed, and shouted, “Wait — how much time has passed since I swore that I was going to finish that revision? Or start it?”

Or exclaimed, “Hey, wasn’t my New Year’s resolution to send out ten queries per week? Have I sent out even one this month?”

Or moaned, “Oh, my God — the agent of my dreams requested pages six months ago, and I’m still revising. Should I take another run at Chapter 152, or should I pop the whole shebang in the mail as is? What if she doesn’t want it anymore?”

I’m not bringing this up to depress all of you who swore that Labor Day (or the Fourth of July, or Valentine’s day, or St. Swithin’s day) was going to be the moment you sprung into action, honest. Nor am I passing judgment on the many, many aspiring writers whose lives swamped their good intentions. I’m not even changing the subject so that I may put off answering Kelly’s excellent question for a few more minutes.

I’m bringing it up, if you must know, because writers who procrastinate so often create characters that procrastinate. Seriously, it’s one of Millicent the agency screener’s most frequent complaints about how novelists and memoirists plot books: characters irk her by sitting around and thinking too much.

Or, to mix things up a little, by sitting around and talking through the problems with their best friends, coworkers, mothers, fathers, or, depending upon book category, the people they are about to try to murder. Especially, as is often the case in novel submissions, when these little chats over coffee, in bars, over lunch, over a telephone, or in hastily-improvised torture chambers consist largely of the protagonist recapping conflict that reader has already seen.

How, from an editorial standpoint, could that not seem redundant? “Criminy, move on,” Millicent scolds the text in front of her. “The point of novel narration is not to convey every single thing that happened in the book’s world, but to tell a story in a lively and entertaining manner!”

Because I love you people, I shall spare you what she hisses at memoir submissions in which the narrator agonizes for fifty or sixty pages on end about whether to confront someone who clearly needs some confrontation — only to decide not to do it after all. In fiction and nonfiction alike, her preference nearly always leans toward the active protagonist given to making things happen, rather than a passive one to whom things happen.

Half of you clutched your chests at some point over the last four paragraphs, didn’t you? Relax; I’m not about to suggest the all-too-often-heard advice on this point: telling writers never to show their protagonists thinking is akin to asserting that no character, however devoted to the color pink, may ever be depicted wearing it. Intelligent characters frequently think, and one-size-fits-all writing rules are almost invariably wrong a great deal of the time.

What I am suggesting, heart-clutchers, is merely that Millicent, like most professional readers, has from long experience developed a finely-tuned sense of how much rumination is too much, as well as when it starts to feel repetitious. To eyes trained to spot textual and conceptual redundancy, even a single repeated thought pattern can jump off the page. Small wonder, then, that showing the complexity of a problem by depicting the protagonist revisiting the same set of doubts over and over again is a notorious professional readers’ pet peeve.

Frequently, their impatience is justified: while deeply-felt internal conflict can be quite interesting on the page, most protagonists in first-person and tight third-person narratives don’t think about problems differently each time. Instead, the writer seeks to have the page mirror the way people mull over problems in real life: with redundant logic, facing the same fears and rehashing the same options on Monday as on Friday.

Or the following Friday. Or two years from Friday.

“God, I wish that this writer had never seen a production of Hamlet,” Millicent has been known to murmur over the fourth slow-moving protagonist of the day. “Would it be too much to ask the narrative to get out of this character’s head long enough for her to do something? It wouldn’t even have to advance the plot — I’d settle for her taking up lion-taming or developing a sudden passion for spelunking. Anything, so she gets out of her chair and moves around the world!”

“But Anne!” I hear some of you chest-clutchers point out, and with good reason, “people honestly do fall into thought loops when they’re worried about something, especially if they lean toward the compulsive in general. I’m sorry if it bores Millicent, but I’m trying to represent reality here: the human psyche is not always bent upon producing entertainingly diverse thought patterns.”

Perhaps it isn’t, but you should be. It’s a writer’s job not just to hold, as ’twere, the mirror up to nature, but to create a result that will be a pleasure to read. Redundant thoughts, like redundant action, have a nasty habit of discouraging readers from continuing to turn pages. Obsessive characters can be very interesting, but as the pros like to say, it all depends on the writing: it’s very, very easy for realistic depictions of recurrent thought or even feeling to become positively soporific on the printed page.

Not as easily spotted a cliché as it was a dark and stormy night or you may be wondering why I called you all here, admittedly, but the rumination-obsessed protagonist is actually more common in submissions these days than either of these well-worn tropes. None of these are as ubiquitous as teenagers who roll their eyes, of course, or people under 50 who say whatever and like, but all are equal-opportunity Millicent-annoyers.

Now the rest of you are clutching your chests, but at this late date, most adult readers, even non-professional ones, have seen enough compulsive thought patterns on the page to recognize it within a line or two. At most, it will take them a couple of paragraphs to catch on. How, then, is the writer to maintain interest and tension throughout pages and pages of it?

Honestly, a little obsessive-compulsion goes a long way on the page. Millicent’s seeing less of it these days than when the TV show MONK rendered OCD such a popular character quirk; if a hit TV show or movie contains a noteworthy character trait or plot twist, it’s a safe bet that agencies will be receiving hundreds of iterations of it over the next 2-5 years. The Millies of the early 1980s could have wallpapered both North and South Korea entirely in manuscripts that resembled M*A*S*H, for instance; for the last decade, it’s been rare that a police procedural submission does not include a scene reminiscent of LAW AND ORDER or CSI. And frankly, our time on earth is too precious to waste time toting up how many SF and fantasy submissions fairly reeked of the influence of STAR WARS and STAR TREK.

It’s not that some of the borrowed characters and quirks are not inherently entertaining; in a good writer’s hands, they certainly can be. There’s also something to be said for adhering to the conventions of one’s chosen book category: in a Western, readers expect a confrontation between the fellows in the white hats and the black, just as readers of women’s fiction expect their protagonists to grow and change over the course of the story.

By definition, though, what none of these elements can ever be is fresh.

Which goes right to the heart of Kelly’s question, does it not? While the list of premises, plot twists, and character traits that might set Millicent’s teeth on edge changes perpetually — what might have riled her Aunt Mehitabel when she was just starting out as a reader in the mid-1970s is substantially different from what might occur often enough to get on Millie’s nerves today, or her younger sister Margie five years from now — the basic principle remains the same: even if the writing is good, if she’s seen it before, it’s not going to seem fresh or surprising on the page.

Remember, Millicent is not only charged with the task of sifting through submissions to find great writing and original voices; she’s also looking for unique takes on reality and plots that she hasn’t seen before. While imitation may be the sincerest form of flattery (which I sincerely doubt), at submission time, not seeming like a rehash of the most recent bestseller or blockbuster film is a significant asset.

I know, I know: it’s not all that uncommon for agency submission guidelines to sound as though their Millicents are eagerly awaiting a carbon-copy of whatever is hitting the top of the bestseller lists today. Indeed, sometimes they are looking for copycats. Even with monumental bestsellers like the TWILIGHT series or BRIDGET JONES’ DIARY, though, it usually doesn’t take too long before Millie and her boss are saying, “Oh, no, another knock-off? I want the next great bestseller, not what was hot two years ago.”

Don’t believe me? How hard do you think it would be to sell BRIDGET JONES’ DIARY as a fresh manuscript today? It would simply seem derivative.

That’s why, in case you had been wondering, those oft-repeated experiments in which some bright soul submits the first 50 pages of some classic like PRIDE AND PREJUDICE (1813) to an array of present-day agents and/or publishing houses, in an attempt to test whether their Millicents would know great literature if it fell in their laps, invariably fall flat. Of course, PRIDE AND PREJUDICE would get rejected today; as a new manuscript, it would seem completely lifted from Jane Austen. To a reader familiar with English novels of the period, even the title would seem unoriginal: the phrase PRIDE AND PREJUDICE (in all caps, no less) is repeated no fewer than three times in Fanny Burney’s novel of a generation before, CECELIA, OR, MEMOIRS OF AN HEIRESS (1782).

Besides, have you seen how much time Austen’s protagonists spend thinking?

I know that this might come as a shock to the many, many writers raised on 19th-century literature, but what seemed fresh on the page in 1813 is unlikely to strike Millicent as original or even market-appropriate today. Ditto for 1913, 1943, 1983, or 2003. In fact, what would have wowed ‘em at the agency in any of those years is likely to seem positively dated now, even if the cultural references did not.

Remember, too, that Millie lives in the same media-heavy culture you do: while she might not watch enough T.V. to know what a Snooki is, to catch an Arrested Development reference, or to be able to pick any of the current crop of presidential contenders out of a police line-up, it’s unlikely that she would be lucky enough to have missed any public discussion of these phenomena. If you loved the Saw movies enough to borrow some elements of them for your horror manuscript, chances are that a Millicent working in a horror-representing agency will be harboring some affection for those movies, too.

Which is not to say that a plot similar to the Saw movies might not have done very well, had it hit Millicent’s desk right after the first film in the series came out. Many a writer who has been toiling away quietly for years on a manuscript has suddenly seen it become sought-after as soon as a similar book, movie, or TV show hits the big time. Agents and editors do often clamor for something similar to what’s hot at the moment. Since it takes so long to write a book, however, it’s generally the writers that were already working on a book, not because it was cool, but because they liked the subject matter, who are in the best position to take advantage of such a trend. Or writers who can produce a manuscript with similar appeal within a year or two. After that, imitation is likely to make the book seem dated.

Not sure what a dated manuscript is, or why it might be hard to sell? Okay, let me ask you: if you picked up a book stuffed to the gills with references to Ross Perot, would you (a) embrace it as a book about contemporary politics, (b) assume that it had been published sometime in the mid-1990s, and turn to another book for insights on the current political scene or (c) wonder who in the heck Ross Perot was?

If you said (b), you’re beginning to think like Millicent: the 1992 election was a long time ago. If you said (a), I’m guessing you do not follow politics very closely. And if you said (c), well, ask your parents, but don’t be surprised if they remember his ears more than his politics.

Even if a manuscript avoids the specific pop references that tend to age so poorly on the page — nothing seems more tired than yesterday’s catchphrases, right? — borrowing the plot twists and premises of yesteryear can make a book seem dated. One of the surprisingly immortal premises: neighborhoods where none of the mothers work outside the home, or even consider it. While it’s not beyond belief that such communities still exist, it’s far enough from the mainstream American experience these days that it would require fairly extensive textual explanation.

Embracing writing fads of years past also tends to make a manuscript seem dated. When STAR WARS embraced the Jungian heroic journey structure, it generated a lot of buzz — and for the next two decades, the viewing public was inundated with movies with that same structure. Then, in the late 1990s and early 2000s, advocating that structure for novels became extremely popular, resulting in manuscript after manuscript with essentially the same story arc falling on Millicent’s desk with clockwork regularity. Because Millicent’s boss was screening manuscripts back then, Millie’s been trained to regard that structure as old-fashioned.

Not to mention predictable. And speaking of repetitive premises, does it bother anyone but me that the mortality rate for mothers in the STAR WARS movies is close to 100%?

Seriously, it doesn’t pay to underestimate just how predictable adhering to a well-worn plot device can render a manuscript, especially to someone who reads as much as Millicent. People drawn to work in publishing tend to be both plot-retentive and detail-oriented: I was surely not the only future editor who walked out of the original STAR WARS saying to her big brother, “You know what would make more sense than that ending? If Leah was Luke’s sister? I mean, honestly — why begin their names with the same first letter, something screenwriters usually take wincing pains to avoid, unless we’re supposed to guess that there’s a familial relationship?”

Okay, so this was probably not how most elementary schoolers reacted to the film, but I read a great deal. Not only science fiction, but fables — and the heroic journey story arc was supposed to surprise me? Nice try, Mr. Lucas.

An original plot twist or premise should surprise the reader — and that’s legitimately hard to do. It’s also often difficult for an isolated writer to spot just how much his plot, premise, or characters might resemble what Millicent is receiving from other writers. Even if the writer can successfully weed out conceptions of dramatic fitness culled from stories floating around the zeitgeist — from movies, television, books, even major news stories — that might be turning up in other submissions, rooting out or even noticing stereotypes (what? The guy with tape on his glasses is a computer expert? Who saw that coming?), stock plot twists (the murderer isn’t the first person the police arrest? Alert the media!), overused premises (the police partners who made the arrest are experiencing some romantic tension? The school bully targeting the gay teen is himself fighting urges in that direction? The guy bent on revenge is actuated by the trauma of having seen his wife and small child murdered out of the reader’s sight and before the story began?) and hackneyed phrasing (“I’m sorry for your loss,” anyone?) can often require an outside eye.

Why? Often, such well-worn story elements are so familiar to the writer, as well as to her nearest and dearest, that they don’t seem like clichés. They just seem like the constituent parts of a story. Therein lies the essential paradox of trafficking in the already-done: that plot twist that feels dramatically right may well come across that way because you’ve seen it before.

And so has Millicent. Remember, clichés don’t irritate agents, editors, and contest judges the first time these fine folks spot them on the manuscript page, typically, or even because the pesky things are repeated over the course of a particular submission or contest entry. What chafes their sensibilities is seeing the same phrases, characters, plot twists, and even premises over and over across hundreds of manuscripts.

Hey, if you’ve seen one completely selfless mother, a lady completely devoid of any personal preferences unrelated to her children, you might not actually have seen ‘em all. After screening the forty-seventh synopsis featuring a selfless mother within a week, however, it might well start to feel that way.

That’s a pretty good test of whether a manuscript might have strayed into over-nibbled pastures, by the way: if the synopsis — or, sacre bleu, the descriptive paragraph in the query letter — makes reference to a well-established stereotype, it’s well worth looking into how to make the characters less, well, predictable.

And now two-thirds of you chest-clutchers are mopping your weary brows. Honestly, this is beginning to read like a word problem on the math section of the S.A.T.

By definition, stereotypes and clichés are predictable: they are the shorthand a culture uses for archetypes. The mean tenth-grade girl, for instance, or the dumb jock. The absent-minded professor who can’t find the glasses perched on top of his head. The sociopathic lawyer who cares only about winning cases, not justice. The tough drill sergeant/teacher/physical therapist who seems like a bully at first, but turns out to be concealing a heart of gold.

Hey, what happened to all the floozies harboring hearts of gold? When did they fall out of the collective mind? Sometime during the Reagan administration? Or was it a decade earlier, when librarians and schoolteachers lost the right to yank the pencils from their collective hair, remove the eyeglasses that they apparently don’t require in order to see, and have the nearest male exclaim, “Why, Miss Jones — you’re beautiful!”

Now, poor Miss Jones would to be an expert in particle physics, save the world in the third act of the story, and look as though she had never eaten a cookie in order to engender that reaction. It’s enough to make an educated woman bob her hair.

Naturally, what constitutes a cliché evolves over time, just as what seems dated in a plot does, but as far as characterization goes, one factor remains the same: a stereotype telegraphs to the reader what kind of behavior, motivations, and actions to expect from a character. A pop quiz for long-time readers of this blog: why might that present a problem in a manuscript submission?

For precisely the same reason that a savvy submitter should avoid every other form of predictability, especially in the opening pages of a manuscript or contest entry:: because being able to see what’s going to happen in advance tends to bore Millicent. If a professional reader can tell instantly from a story’s first description of a character precisely how he is going to act and how he is likely to speak, where’s the suspense?

The same holds true for too-common premises, by the way. Those two coworkers of opposite sexes squabbling? They’ll be in love within fifty pages. That child the woman who swore she never wanted children inadvertently acquires, by accident, theft, or some inconsiderate relative’s leaving him on her doorstep. It will completely transform her life. The completely irresponsible man who discovers he’s had an unknown child for decades? He’s going to be integral to that kid’s life, and vice versa. That wish the protagonist makes on page 2, even though the text explicitly tells us that she never wishes on passing stars? It’s going to come true.

In spades. It’s written on the sand.

Oh, you thought that Millie wouldn’t catch on that teenage Billy was going to wreck his new motorcycle by the second time his parents are shown to be worried about it? I hate to burst anyone’s plotting bubble, but at this juncture in literary history, most professional readers would have said, “Oh, he’s doing to crash it,” halfway through the scene where he bought the bike.

She’s also going to foresee that the character a bystander identifies as having had a hard childhood is going to be the mysterious murderer decimating the summer camp/isolated hotel/submarine’s crew, the grandmother/grandfather/elderly neighbor giving the youthful protagonist with nowhere else to turn sterling (if predictable) advice is going to have some sort of a health scare by three-quarters of the way through the book, and that the otherwise clear-thinking lady who wisely retreated to someplace her violent ex-husband/evil boss/corrupt Congressman isn’t will be startled when he shows up.

Quite possibly standing behind her while she is gazing soulfully into a mirror. A cat will have startled her first, however. That fellow also not going to be dead the first time she, her knight in shining armor, or the few remaining members of that light-hearted weekend canoeing party think they have dispatched him.

Hey, the monster always returns is a cliché for a reason.

I don’t mean to alarm you, but reading manuscripts for a living often results in a serious decrease in the ability to be astonished by plot twist at all. Avert your eyes if you have never seen The Sixth Sense, but I had twice suggested to my date that the psychologist was a ghost before the end of the first therapy scene. I kept asking, “But if he’s alive, why isn’t he talking to the kid’s mother? And why doesn’t she have any interests or concerns unrelated to her child?”

To anyone who has been reading manuscripts for a living for more than a week or two, there’s another problem with stock characters. Millicent tends to associate them with rather lazy writing — and certainly with lax research. I’m not just talking about the astonishingly common phenomenon of novels saddling their protagonists with professions with which their writers are clearly unfamiliar (if I had a nickel for every tax specialist character who takes an annual month-long holiday on April 16th because the writer who created her isn’t aware of how many people file their taxes late, I would be able to afford a month-long holiday right now) or the equally common fish-out-of-water stories in which the writer seems as out of his depth in the new environment as his protagonist (my personal pet peeve: protagonists who inherit wineries, then proceed to run them with a whole lot of heart — and learning valuable life lessons — while clearly learning virtually nothing about the actual practicalities of making wine).

I’m talking about characters, usually secondary ones, that are different in some fundamental way from the protagonist. You wouldn’t believe how often subtly-drawn primary characters share page space with downright cartoonish villains or minor characters.

When writers just guess at the probable life details and reactions of characters unlike themselves, they tend to end up writing in generalities, not plausible, reality-based specifics. A common result: characters whose beauty and brains are inversely proportional, whose behavior and/or speech can be predicted as soon as the narrative drops a hint about their race/gender/sexual orientation/national origin/job/whatever, and/or who act exactly as though some great celestial casting director called up the nearest muse and said, “Hello, Euterpe? Got anything in a bimbo cheerleader? Great — send me twelve.”

Seen once on the page, one-note characters are kind of annoying. When those cheerleaders come cartwheeling across a good 40% of YA set in high schools, even a hint of waved pom-pom can get downright annoying.

Even amongst agents, editors, and judges who are not easily affronted, stereotypes tend not to engender positive reactions. What tends to get caught by the broom of a sweeping generalization is not Millicent’s imagination, but the submission. If it seems too stereotypical, it’s often swept all the way into the rejection pile.

Why, you ask? Because by definition, a characterization that we’ve all seen a hundred times before, if not a thousand, is not fresh. Nor do stereotypes tend to be all that subtle. And that’s a problem in Millicent’s eyes, because in a new writer, what she’s looking to see — feel free to chant it with me now — originality of worldview and strength of voice, in addition to serious writing talent.

When a writer speaks in stereotypes, it’s extremely difficult to see where her authorial voice differs markedly from, say, the average episodic TV writer’s. It’s just not all that impressive — or, frankly, all that memorable.

“But Anne,” writers of reality-based fiction and nonfiction alike protest, “sometimes, stereotypes have a kernel of truth to them, just as clichéd truisms are frequently, well, true. Isn’t it possible that Millicent sees certain character types over and over again because they pop up in real life so often, and writers are simply reflecting that? Should she not, in short, get over it?”

Ah, editors hear that one all the time from those writing the real, either in memoir form or in the ever-popular reality-thinly-disguised-as-fiction manuscript. In fact, it’s an argument heard in general conversation with some fair frequency: many, many people, including writers, genuinely believe various stereotypes to be true; therein lies the power of a cliché. The very pervasiveness of certain hackneyed icons in the cultural lexicon — the policeman enraged at the system, the intellectually brilliant woman with no social skills, the father-to-be who faints in the delivery room, that same father helpless if he is left alone with the child in question, to name but four — render them very tempting to incorporate in a manuscript as shortcuts, especially when trying to tell a story in an expeditious manner.

Oh, you don’t regard stereotypes as shortcuts? Okay, which would require more narrative description and character development, the high school cheerleader without a brain in her head, or the one who burns to become a nuclear physicist? At this point in dramatic history, all a pressed-for-time writer really has to do is use the word cheerleader to evoke the former for a reader, right?

Unless, of course, a submission that uses this shortcut happens to fall upon the desk of a Millicent who not only was a high school cheerleader, but also was the captain of the chess team. At Dartmouth. To her, a manuscript that relies upon the usual stereotype isn’t going to look as though it’s appealing to universal understandings of human interaction; it’s going to come across as a sweeping generalization.

Can you really blame her fingers for itching to reach for the broom?

“But Anne,” some of you point out, and who could blame you? “Isn’t this all going a little far afield from Kelly’s original question? Wasn’t she really asking for a list of overused plot twists and premises a savvy aspiring writer should avoid?”

Possibly, but that’s precisely the conundrum of freshness. What would have struck Millicent as fresh a year ago, when Kelly first brought this up, is not what would seem so to her now. Freshness is an ever-moving target, difficult for an aspiring writer — who, after all, usually takes at least a year or two to fashion a premise into a full manuscript — to hit predictably. Since nobody can legitimately claim to know what will be selling well a couple of years from now, committing to a premise is always going to be something of a risky proposition.

All a writer can do is strive to make her plot and characterization as original as her voice — and, ideally, as surprising. The best means of figuring out what will come as a pleasant surprise to her is to read widely in your chosen book category. What kinds of plot twists are used, and which overused? What’s been done to death, and what’s new and exciting? What’s considered characteristic and expected in your type of book these days, and what’s considered out of bounds?

Once you have come up with provisional answers to those questions, ask yourself another: how can I make my book’s premise, characterization, and plot even better than what’s already on the literary market?

Speaking of conundrums, have you solved the riddle of the Sphinx yet? It’s the humble human being: as babies, we crawl; in our prime, we walk on two legs; in old age, we use canes.

Actually, people tend to use walkers now, but who are we to question the wisdom of the Sphinx? All I know — and this is so far from a standard premise that I can’t recall a bestselling novel of the last twenty years that has dealt with this subject in any significant depth — is that after one has been hobbling around on three legs, it’s astonishingly tiring to wander around on just two. And that, my friends, is the explanation for my recent blogging silence: I’ve been taking a long change-of-season nap.

All the better to launch into Queryfest next time, my dears. Keep up the good work!

Phrases a savvy writer should not touch with a hundred-foot pole

Hello, campers —

I’m planning on posting a lovely, long post this evening, an in-depth answer to a reader’s intelligent question about writing clichés, but until the dark and no doubt stormy night allows me to suggest that perhaps you have all been wondering why I asked you all here, let me state here and now that the murder is — BANG!

Just kidding. Seriously, I’ve been swamped the last couple of days (speaking of editorial clichés), and I want to devote some serious time to this important and under-discussed topic. Rather than leave you pining for a fresh post another twelve or fifteen hours (or longer, should I decide to do something radical like take a nap before blogging next), I’m rerunning a post from last February. Not only does it strike me as a perfect lead-in to any discussion of hackneyed phrases and concepts, but it addresses an extremely common professional readers’ pet peeve: manuscripts that misappropriate or misuse the aforementioned well-worn tropes.

Oh, and I’m going to nag you a little on submission strategy first. So fasten your seatbelts, everybody — it’s going to be a bumpy night day. Enjoy!

Can we talk?

Actually, I’ve been meaning to bring this up for quite some time now, but the moment never seemed quite right. You were gearing up to send out a flotilla of queries, perhaps, or were intent upon getting a submission out the door. Maybe we were all focused upon how to prep a writing contest entry, a verbal pitch, or a synopsis.

In short, there always seemed to be something more pressing than having this painful discussion. But as your writing advisor and, I’d like to think, your friend, I just can’t stand around and watch you hurting yourself any longer without saying something. I say this with love, but you’ve been engaging in self-destructive behavior, behavior that is making it harder for you to land an agent, get published, and get your good writing in front of the readership it deserves.

Oh, I see you roll your eyes. It’s easy, isn’t it, to blame a system stacked against the new writer? But this is something you are doing to yourself, I’m afraid, something as lethal to your manuscript’s marketability as taking a match and setting it on fire instead of mailing it to the agent who requested it.

I refer, of course, to the average aspiring writer’s addiction to sending out requested materials without taking the time to proofread them — or having someone else proofread them.

I’m not even talking about the to-my-mind deplorable practice of submitting those pages before reading them IN THEIR ENTIRETY, IN HARD COPY, and OUT LOUD — although as I may have mentioned several hundred times before in this very forum, that’s the single best way to catch typos, dropped words, logic problems, half-revised sentences, and the fact that your protagonist’s hated coworker was called Tisha for the first 57 pages, Patricia in Chapters 4, 8, 17, and parts of 24, and Trish for the rest of the book. I’m talking about just assuming that a quick computerized spell-check will be sufficient because, hey, you’ve got a busy life.

Or, as is common with contest entries that need to be postmarked by a certain date and time, performing it when one is so tired that one inadvertently hits the REPLACE ALL button instead of IGNORE ALL. The result: 300 pages in which political coalitions are invariably described as political cotillions, leaving the poor judge in that historical fiction contest to wonder why nobody ever seems to be dancing.

Or, even more common, dispensing with even the computerized spell-check in your eagerness to get the pages a real, live agent has requested sent off before another sunset has passed. Never mind that Millicent the agency screener is unlikely to have any sympathy whatsoever for your unfortunate habit of consistently mistyping receive with the e and the i inverted, or the fact that somehow, you missed the day of English class when the difference between there, their, and they’re was clarified beyond any risk of future confusion. You had been working on that manuscript for years — you simply couldn’t bear to wait the additional few hours it would take to proof those requested pages.

Oh, it’s all quite understandable. Speaking as someone who reads manuscripts for a living and has served as a writing contest judge, however, it’s also completely understandable that a professional reader might reject those pages on the basis of all of those typos alone.

Yes, you read that correctly: it’s not at all uncommon for a professional reader to stop reading at the second or third typo, skipped word, or grammatical problem. So if you are not routinely proofreading your work before you submit it or enter it in a contest — or having some sharp-eyed soul do it — you may well be dooming your manuscript to rejection.

So I ask you: what are you actually gaining by not taking the time to make sure that your pages are clean?

A clean manuscript, for the benefit of those of you new to the term, is industry-speak for a manuscript completely devoid of misspelled words, grammatical gaffes, dropped words, incorrect punctuation, logic problems, formatting errors, clichés, or any of the many, many other small errors that make those of us trained to read for a living grit our teeth because we see them so very often. Indeed, Millicents and contest judges are often specifically instructed to consider seriously only clean manuscripts.

What happens to the rest, you ask with fear and trembling? They are subjected to the most common word in our Millie’s vocabulary: “Next!”

Why? Well, several reasons — and far better ones than you might expect.

The first and most straightforward: if a manuscript is riddled with errors, some luckless soul is going to have to fix them all before an agent could possibly submit it to an editor with any hope of placing it successfully. The same holds true for a submission to a publishing house: copyediting is very time-consuming and costs real money. And few literary contests will want their good names sullied by awarding top honors to an entry that looks as though the entrant conceived of it 24 hours before the contest deadline, typed it with fingers blurring across the keyboard, and ran panting to the post office three minutes before it closed.

Nobody, but nobody, likes to read a first draft. And I say that as a writer who once actually did pull together a literary contest entry — the first chapter of a book, synopsis, and entry form — in 23 hours and 32 minutes.

I won, too, despite the never-sufficiently-to-be-deplored typo on page 17. Do as I say, not as I did.

Why? Well, to a professional reader — like, say, Millicent, her boss the agent, the editor to whom the agent might conceivably sell your book, or a contest judge — all of these seemingly little writing problems are not merely the hallmark of a writer in a hurry or easily-fixed trivialities that merely mar the surface of the deep, deep pool that is a brilliantly-written story, annoying but not particularly important. They are a sign that the writer is not professional enough to realize that this is an industry in which spelling does in fact count.

Or that presentation in general counts. One of the hallmarks of an aspiring writer who has yet to learn much about how publishing works is an apparent belief that agents and editors sit around all day, casually reading through submissions and acquiring any that happen to catch their fancy.

“Oh, this writer has promise,” these fantasy pros murmur over their snifters of warm cognac as they leisurely turn pages, perched on intricately tufted chaise longues. “He can’t spell, but that’s easily fixed at the editorial stage. I’m so fascinated by this story and the voice in which it is written that I’m just going to ignore the fact that the writer clearly didn’t bother to read his own book. I’m going to read it until the very last word of the very last page before I make up my mind about it, but I have a strong feeling that the answer is going to be yes.”

I hate to burst anyone’s bubble, but that’s simply not how professional readers operate: they just don’t have time to read every submission in its entirety. Nor could they possibly take on every writing project that tickled their fancy. An agent or editor who routinely embraced projects without thinking about her ability to sell them would soon be out of a job, after all.

As a direct result, the fine folks who work in agencies and publishing houses look first for reasons to reject manuscripts, scouring each line for problems. Only those submissions that pass this scrutiny for hundreds of pages stand a chance of getting picked up. Even setting the bar this high, a well-respected agency or contest will still receive so many perfectly clean (or nearly so), nicely-written submissions that they can afford to reject everything else.

I sense some trembling hands tentatively raised out there. “What do you mean by scouring each line?” some of you quaver, thinking perhaps of that writing sample you entered into that online submission form without proofreading. “It would be impossibly time-consuming to read an entire manuscript that closely, especially with the high volume of submissions the average agency receives. Why, the only way they could possibly pull it off would be to stop reading when they encounter a problem, and move on to the next one.”

That’s precisely what they do. Oh, not necessarily at the first problem, but certainly before the fourth or fifth.

Was that great whooshing sound that just deafened us all the result of half of you gasping as you frantically tried to open your manuscript files to begin revising them? A clean manuscript suddenly sounds like a very, very desirable thing, doesn’t it?

That’s a smart orientation. The competition for those very few client openings at agencies — and even fewer new author openings at publishing houses — is unbelievably fierce, far too fierce to expect a charitable reading.

Millicent forms the first line of defense — I feel you cringing, but that’s how agents and editors think of her — against the blizzard of submissions battering against their mailroom doors. Even an agent unusually hungry for clients usually can take on only three or four a year. That means, in practical terms, that for every submission she approves, there are hundreds she or her Millicent must reject.

The same holds true for queries, of course. Except that for hundreds, substitute tens of thousands.

Fortunately for Millicent (but unfortunately for writers), most submissions honestly are self-rejecting. How so? Well, one of the most popular methods is by combining improper formatting with a few typos on page 1.

You know, the sort of thing that the combination of a little research into how the publishing industry works and a few minutes of proofreading would easily have caught. To Millicent, a writer who hasn’t put in the time to do either isn’t ready for the publishing world. The hypercritical way that professional readers scrutinize manuscripts might kill him.

Which is to say: a savvy writer expects her future agent and editor to expect a completely clean manuscript every time. Yes, even when the writer has only three weeks to revise the last quarter of the book because a new editor has just taken over the project from the acquiring editor, and the newbie has some exciting new ideas about plot resolution.

Oh, it happens. To an agent, a good client is a flexible client.

Which brings me to another excellent reason Millicent is specifically trained to regard a clean manuscript as the minimum requirement for serious consideration: a client who does not proofread (or possess the skills to do it well) is inherently more time-consuming for an agency to represent than one who habitually produces clean manuscripts. While an established author can get away with being high-maintenance, one trying to break into the biz for the first time cannot.

Oh, an agent expects to hold a new client’s hand a little; submitting to publishing houses can be a long, drawn-out, and extremely stressful process. But if that client cannot be relied upon to provide the agent with clean pages, who is going to end up proofing them?

The agent, that’s who. See why she might instruct her Millicent to select clients likely to spare her the trouble? Or why if the writer hasn’t bothered to read this manuscript, why should I? is such a common mantra amongst professional readers?

Or, to be blunt about it, why I saw fit to stage an intervention for those of you who aren’t already scrutinizing your submissions to prevent them from falling into this most common of self-rejection pitfalls?

To be fair, though, not all rejection-triggers would necessarily turn up in a quick proofreading — or even when reading a manuscript IN ITS ENTIRETY, IN HARD COPY, and OUT LOUD. Often, for instance, writers new to the game will miss another of Millicent’s pet peeves, the use of clichés.

Or, an even surer professional reader-annoyer, the misuse of clichés.

That caused some of you to do a double-take, didn’t it? “But Anne,” you cry, rubbing your sore necks, “isn’t a misused cliché not a cliché, by definition? Doesn’t it at least have the charm of surprise?”

Yes and no, in that order — to professional readers, at least. Allow me to explain.

Since so many aspiring writers are under the mistaken impressions that (a) dialogue in a book should read precisely like conversations in real life, despite the fact that most real-world conversations are so repetitious that they would plunge readers into profound slumber, (b) a narrative voice should sound like the way someone might actually talk, regardless of whether the narration is in the first person or not, and/or (c) an essential tactic for achieving either (a) or (b) is to incorporate those pat little catchphrases most speakers use into one’s writing, discovering clichés on the submission page is the norm, not the exception.

Because writers who embrace (a), (b), or (c) believe — and with some reason — that there is inherent virtue in echoing everyday speech, they usually don’t think of these common phrases as clichés. Let’s take a gander at a few dozen of them in action.

Jeremy strode through the door, bold as brass. “Hey, Mom. It’s raining cats and dogs out there.” He mussed little Tad’s hair as he passed; the boy was glued to the family’s pride and joy, the new black-and-white TV. “Hey, shrimp. Where’s the beef?”

“Blow it out your ear,” Tad snarled without taking his eyes off the nine-inch screen. His Davy Crockett cap had slid off his head onto his cowboy suit. His discarded hula-hoop rested on top of the crumpled Twister set and a signed photo of Marilyn Monroe. “And sit on it. It’s almost Howdy Doody time.”

Betsy rolled her eyes, gritted her teeth, and shrugged her shoulders. Playing host family to a time-traveling teen from 1984 wasn’t as easy as pie, despite what the brochure had promised. But then, you couldn’t believe everything you read. Let the buyer beware. “Does that mean it’s time to put on the feedbag? I’ve been slaving over a hot stove all day, waiting for you to traipse through that door.”

Jeremy had already tuned her out: his Walkman, whatever that was, was turned up too high. One day, she was going to smack him upside the head and give him a piece of her mind.

“You’ll go deaf from all that noise,” she shouted at him. “And don’t sit so close to the TV, Tad; you’ll ruin your eyes. My goodness, if I had a dime for every time I’ve told you…”

Jeremy rolled his eyes like James Dean, as all the kids seemed to be doing these days. He seemed to expect the world — or at least his supper — to be handed to him on a silver platter. When she was a girl, walking to school through three feet of snow, year in, year out, rain or shine, come hell or high water, without fail, her mother would have given her what for if she had flounced into the house like a movie star. Just who did he think he was?

“Just wait ’til your father gets home,” she muttered under her breath.

Granddad shuffled into the kitchen, shoving his false teeth into his mouth, clutching his low-hanging pants, and longing for the return of the Taft Administration. “Is dinner ready yet? I’m starved.”

She sighed, mopping her weary brow. “There’s only so much I can do. I only have two hands. I do and do and do for you people, and this is the thanks I get. A woman’s work is never done.”

The old man caught sight of Jeremy. “Looking sharp, kiddo.” When the boy did not respond, Granddad lifted a speaker from his ear. “Think you’re the cat’s meow, don’t you, you young whippersnapper?”

“Hey, chill.” Jeremy took off his headphones before the old man messed up his ‘do. “You look mahvelous.”

“Marvelous,” Betsy corrected under her breath. “I have such a headache, Dad. The kids have been running me ragged.”

“You think you have a headache? Back in my day, we had headaches.” Granddad peered through the window. “‘Bout time we had some rain. Sure do need it.”

“We sure do,” she agreed, mopping her brow, nodding her head, and nervously playing with her apron while the clouds rolled by. It looked like stormy weather. Still, she could look for the silver lining and the pot of gold at the end of the rainbow. Every time it rained, it rained pennies from heaven. “I’ve been worried sick about Jeremy. Could you find out where he has been while I set the table, since I don’t have a daughter to do it for me, and I can’t ask either of the boys to do it in this time period?”

“Boys will be boys.” Granddad shuffled back to Jeremy. “Where have you been, son? Jitterbugging at the malt shop to that newfangled jazz? Doing the Charleston with some flibbertigibbet with rouged knees and a beaded dress?”

“You should come clubbing with me sometime, Granddad. We are two wild and crazy guys.”

Tad’s curly head popped up behind the couch. “Isn’t that misplaced cultural reference from the 1970s?”

“Mind your own business,” Jeremy growled. “Sometimes, you just gotta say…”

Had enough? Millicent has — and did, by the middle of the second paragraph.

Stock phrases are problematic on the page for much the same reasons that standard polite exchanges are. They’re predictable, and because everyone does say them, a character’s uttering them does not reveal anything about his emotional state, mental gymnastics, or even the situation at hand. (Sorry — once one starts generating hackneyed phrases, it’s hard to stop.)

Oh, hadn’t I mentioned that polite chitchat is also a common type of cliché? Because literally anyone might say these phrases, they are the opposite of character-revealing. Take a gander:

“Why, hello there, Gladys,” Ambrose said. “How are you today?”

“Fine. How are you?”

“Fine. How is your husband, Terrence, and your four children, Maude, Eleanor, Franklin Delano, and Frances? All well, I trust.”

“Yes, fine. How’s your cocker spaniel, Macguffin?”

“Oh, fine, fine. Nice weather we’re having, isn’t it?”

“Very. We could use some rain, though.”

“Sure could use it.”

“Sure could. Ah-choo!”

“Bless you.”

“Thank you.”

“Still have those nasal allergies, eh? They must be quite annoying.”

“Oh, they’re not so bad. At least I don’t have toe fungus.”

“Thank goodness for that. May I hold the door for you? Ladies first.”

“Thanks. Watch out for that puddle.”

“I appreciate your telling me. I wonder how it got here, considering that we haven’t had any rain. O day and night, but this is wondrous strange!”

“And therefore as a stranger give it welcome. There are more things in heaven and earth, Ambrose, than are dreamt of in your philosophy. But come, here, as before, never, so help you mercy, how strange or odd soe’er I bear myself, as I perchance hereafter shall think meet to put an antic disposition on, that you, at such times seeing me, never shall, with arms encumber’d thus, or this headshake, or by pronouncing of some doubtful phrase, as ‘Well, well, we know,’ or ‘We could, an if we would,’ or ‘If we list to speak,’ or ‘There be, an if they might,’ or such ambiguous giving out, to note
that you know aught of me: this not to do, so grace and mercy at your most need help you, swear.”

“Whatever you say, Gladys.” Ambrose tipped his hat politely. “Have a good day.”

“You, too, Ambrose.”

Okay, so I got bored enough to throw a slight twist in there. But see how stultifying all of that politeness is on the page?

Once again, I spot some timid hands in the air. “But Anne, isn’t this just what nice people say? And if I want the reader to like my protagonist, don’t I need to show that he’s polite, rather than telling it by some such statement as Nate was a polite guy?”

If you really want to induce Millicent to take a shine to ol’ Nate, I would strongly suggest that you do neither. Most readers will come to dislike a protagonist who bores them, not matter how nice his words or actions are. Since Millicent is paid to get bored a whole lot faster than the ordinary reader (see earlier comments about weeding out as many submissions as possible), her threshold of impatience with nondescript polite conversation is exceedingly low.

I wouldn’t push it. Instead, why not have Nate win her heart by doing and saying unexpected kind things?

“Okay, Anne,” those of you prone to flinging your hands skyward concede reluctantly. “I can see why I might need to trim both the stock phrases and purely polite exchanges. But weren’t you going to tell us about misused clichés?”

Ah, yes, I was, campers; thank you so much for reminding me. And how’s your mother doing?

No, but seriously, folks, while stock phrases bore professional readers, misstatements of these same phrases tend to drive Millicent into apoplexy. While such clichés as it’s a dog-eat-dog world, take another tack, and I couldn’t care less often — and incorrectly — turn up in conversation as it’s a doggie-dog world, take another tact, and the irritatingly immortal I could care less, the only reason to use the incorrect versions on the page would be to make the character saying them seem ignorant, right?

Right? Anyone out there?

Even ironic use is dangerous, though: because Millicent sees these misstatements so often, she’s likely to have a knee-jerk reaction to their appearance. And it’s hard to blame her, isn’t it? Not only do these phrases imply that the writer has a rather poor ear for dialogue, but even had these tropes been rendered correctly, they would still be hackneyed phrases, and thus unoriginal.

Call me zany, but don’t you want Millicent to judge you on your writing, rather than someone else’s?

Then, too, misstated clichés often reveal a fundamental misunderstanding of the meaning of the original. What would a doggie-dog world look like, anyway? Why bother to mention that someone could care less than he currently does? And while taking a different tack while sailing makes some sense as a metaphor, what would taking a different tact involve? Diplomacy in another language?

My favorite example comes by way of a roommate of mine in graduate school, a young lady who had grown up without a television in the house. She loved stock phrases, but she was perpetually getting them wrong.

“What do you mean, you wouldn’t touch it with a 100-foot pole?” I would cackle. “The standard length is ten. How would you even lift a hundred-foot pole?”

She was also prone to misapplying such metaphors. “I can’t find my keys,” she would say. “They’re like a needle in a haystack.”

“I wish you would tell me how,” I would say, lifting the sofa cushion under which her personal items so often worked themselves. “Not everything that’s lost is like a needle in a haystack, you know.”

She would look as startled as a deer in the head lice. “It isn’t?”

Okay, so perhaps there were some undiagnosed mental health issues involved. And now that I see it in print, as startled as a deer in the head lice may well be my new favorite faux cliché. It’s actually quite evocative of panic, is it not?

But you see the overall point, right? A misused familiar term may well produce a laugh, but even if you are writing comedy, you might want to use it sparingly. In submissions, misappropriated clichés often result in bad laughter, a chuckle at the expense of the story, a giggle that the author did not intend.

Now that you know what such misstatements look like individually, let’s revisit our first example, so you may see how and why they might annoy Millicent on the page.

Jeremy scrod through the door, bold as copper. “Hey, Mom. It’s raining cats and ducks out there.” He missed little Tad’s hair as he passed; the boy was taped to the family’s pride and happiness, the new black-and-white TV. “Hey, petunia. Where’s the mutton?”

“Blow it out your nose,” Tad snarled without taking his gaze off the nine-inch screen. His Daniel Webster cap had slid off his head onto his sailor suit. His discarded Pet Rock rested on top of the Pong remote and a signed photo of Theda Bara. “Sit on something. It’s almost time for the Miniskiteers.”

Betsy rolled her mouth, gritted her ribs, and shrugged her arms. Playing host family to a time-traveling teen from 1984 wasn’t as easy as cake, despite what the brochure had promised. But then, you couldn’t believe everything. Let the biller beware. “Does that mean it’s time to don the fedbag? I’ve been praying over a hot stove all day, waiting for you to lapse through that door.”

Jeremy had already turned her out: his Walkmen, whoever they were, were turned up too high. One day, she was going to smack him beside the head and give him a place of her mind.

“You’ll go deaf from all that sound,” she shouted at him. “And don’t sit so close to the TV, Tad; you’ll ruin your posture. My goodness, if I had an orangutan for every time I’ve told you…”

Jeremy rolled his cigarette like James Dean, as all the kids seemed to be these days. He seemed to expect the world — or at least his supper — to be handled to him on a silver tray. When she was a girl, walking to school through three inches of snow, year in, bear out, rain or more rain, come Milwaukee or high water, without failure, her mother would have given her what for it if she had flounced into the house like a movie preen. Just who did he think he could be?

“Just wait ’til your father gets here,” she muttered under her breathe.

Granddad snuffled into the kitchen, shoving his false teeth into his and clutching his low-hanging tie. “Is dinner prepared yet? I’m staved.”

She sighed, mopping her weary hair. “There’s only so many I can do. I only have two hand. I do and do and do and do and do for your people, and this is the thanks I git. A woman’s work is never down.”

The old man caught sight of Jeremy. “Looking bark, kiddo.” When the boy did not respond, Granddad lifted a speaker from his ear. “Think you’re the cat’s leisure suit, don’t you, you young whipperstinger?”

“Hey, take a bill pill.” Jeremy took off his headphones before the old man messed up his ‘roo. “You look mahvelous.”

“Marvelous,” Betsy corrected under her breath. “I have such a backache, Dad. The kids have been running me rugged.”

“You think you have an ague? Back in the day, we had agues.” Granddad peered through the window. “‘Bout time we accumulated some significant rainfall. Sure do need it.”

“We sure do,” she agreed, mopping her blow, nodding her head, and nervously playing with her ape while the clouds rolled near. It looked like stormy seasons. Still, she could look for the silver pining and the pot of gold at the end of the rainblow. Every time it pains, it pains good fortune. “I’ve been worried ill about Jeremy. Could you find out where he has been while I set the table with silverware, plates, and gasses?”

“Boys well be boys.” Granddad sniffled back to Jeremy. “Where have you been, son? Jitterbeetling at the salt shop to that newfinagled bock-and-roll?”

“You should come with me sometime, Granddad. We are two wild and lazy guys.”

Tad’s curly head popped up behind the couch. “Isn’t that misplaced cultural reference from the 1970s?”

“Mind your own bees’ honey,” Jeremy growled. “Sometimes, you just gotta say what the Buick…”

Have I made my point yet, or do I need to keep greeting that red horse?

In the days to come, I shall be going over more seemingly small Millicent-irritants. Not the big stuff, mind you, but the tiny, niggling narrative choices that make her teeth…well, I was going to say grind, but that would be a cliché. Once you are aware of precisely how and why these tidbits annoy the pros, you may keep an eye out for them while you are proofreading.

That’s while, right, not if? Keep up the good work!

But enough about you — what about me?

Today, I had planned to launch headlong into my annual foray into how to construct a graceful and effective query letter, campers, but frankly, didn’t we devote an awful lot of the summer to discussing how to pitch? After so many weeks on end of dealing with practicalities, I feel that the artist in each of us deserves a little holiday.

So let’s refresh ourselves by talking craft for a while. Queryfest will be every bit as useful next week.

Memoir-writing and writing about reality as fiction has been much on my mind of late, and not merely because my memoir remains in publishing limbo. (Yes, still. Let’s just be grateful that not every memoirist’s extended family has the wherewithal to make credible $2 million dollar lawsuit threats.) While we writers talk endlessly amongst ourselves about craft and structure for fiction, it’s actually quite rare to stumble into a knot of literary conference attendees avidly discussing how to make a personal anecdote spring to life on the page.

Why is that, when it is so very hard to write memoir well? All too often, the prevailing wisdom dictates that all a writer needs to produce a successful memoir is an exciting life, an ability to write clearly, and, if at all possible, celebrity in another field, so the writing will matter even less. The writer’s platform and the inherent interest of the story, we’re told, are all that matter in a memoir. Anything beyond that, presumably, is gravy.

As to structure, that’s held to be self-evident. In the immortal words of Lewis Carroll,

The White Rabbit put on his spectacles. “Where shall I begin, please, your Majesty?” he asked.

“Begin at the beginning,” the King said gravely, “and go on till you come to the end: then stop.”

As a memoirist and an editor who works regularly with same, I must disagree. While a chronological structure can work, not all human events start out scintillating; depending upon the story, another structure might work better.

Then, too, a memoir cannot really be deemed a success unless readers find it entertaining, enlightening, or at the very least, interesting. That’s not merely a matter of story. Any long-form writing, be it fiction or nonfiction, will benefit from a strong narrative structure, a consistent, likable narrative voice, a plausible and engaging story arc, believable, well-drawn characters, a protagonist the reader would be happy to follow for a few hundred pages…

In short, many of the elements one might find in a well-constructed novel. But that’s not all that a good reality-based story requires, is it? After all, few readers will want to read a story, whether it is presented as memoir or as fiction, simply because it really happened. It needs to feel real on the page — and it needs to be enjoyable to read.

What makes me think that this might be news to many writers of memoir and reality-based fiction, you ask? For my sins, I have served quite frequently as a contest judge, assessing both memoir and novel entries, and I’m here to tell you, they look more similar on the page than one might think.

How so? They tend to share a few characteristics: a one-sided approach to scenes, as if the protagonist’s perspective were the only possible one; an apparent assumption that the reader will automatically side with the protagonist, regardless of what is going on, and bolstering both, a propensity for relating conflictual exchanges as though they were verbal anecdotes, light on detail but strong on emotion. Or, to boil all of these down to a single trait, these narratives tend to be disproportionately weighted toward a single point of view.

And memoirists’ hands fly heavenward all over the world. “But Anne,” they point out, and who could blame them? “My memoir is my story. Why wouldn’t it be biased toward my perspective?”

It should, of course — but in the interests of representing one’s own point of view, memoirists and writers of the real often render the narrative so one-sided that the situation neither seems plausible nor fairly presented. It just reads like a diatribe in scene form, a piece of prose whose primary point is not storytelling, but getting back at someone.

About half of you have started to blush, have you not? I’m not surprised; in both memoir and reality-based fiction, the scene where the reader is evidently expected to take the protagonist’s side, not because the antagonist is shown to be particularly awful, but because the narrative presents the antagonist without any sympathy — or, usually, any redeeming characteristics — is a notorious pet peeve of our old pal, Millicent the agency screener. And not just as a generality, either. When Millicents, their boss agents, and the editors to whom they cater gather to share mutual complaints in that bar that’s never more than 100 yards from any writers’ conference in North America, the annoying coworker stereotype often crops up in conversation.

As in, “You think you’re tired of conceptual repetition? I’ve read fourteen submissions this week alone with omitable annoying coworker scenes.”

It’s perhaps not altogether astonishing that memoirs would be rife with interactions between the protagonist/narrator and the people who happen to rile her, told in a breathlessly outraged tone, but aspiring writers of fact-based fiction are often stunned to discover that they were not the first to think of inserting actual conflicts into fictional stories. They shouldn’t be: there’s a pretty good reason that such scenes are ubiquitous in manuscript submissions and contest entries. Care to guess?

If you immediately cried out, “By gum, Anne, every writer currently crawling the crust of the earth has in fact had to work with someone less than pleasant at one time or another,” give yourself a gold star for the day. Given how often aspiring writers resent their day jobs — and, by extension, the people with whom they must interact there — that such unsavory souls would end up populating the pages of submissions follows as night the day.

If these charming souls appeared in novel and memoir submissions in vividly-drawn, fully fleshed-out glory, that actually might not be a problem. 99% of the time, however, the annoying co-worker is presented in exactly the same way as any other stereotype: without detail, under the apparent writerly assumption that what rankles the author will necessarily irk the reader.

Unfortunately, that’s seldom the case — it can take a lot of page space for a character to start to irritate a reader. So instead of having the character to demonstrate annoying traits and allowing the reader to draw his own conclusions, many a narrative will convey that a particular character is grating by telling the reader directly (“Georgette was grating”), providing the conclusion indirectly (through the subtle use of such phrases as, “Georgette had a grating voice that cut through my concentration like nails on a chalkboard”), or through the protagonist’s thoughts (“God, Georgette is grating!”)

Pardon my asking, but as a reader, I need to know: what about Georgette was so darned irritating? For that matter, what about her voice made it grating? It’s the writer’s job to show me, not tell me, right?

I cannot even begin to count the number of memoirs and novels I have edited that contained scenes where the reader is clearly supposed to be incensed at one of the characters, yet it is not at all apparent from the action of the scene why.

Invariably, when I have asked the authors about these scenes, the response is identical: “But it really happened that way!”

No surprise there. These scenes are pretty easy for professionals to spot, because the protagonist is ALWAYS presented as in the right for every instant of the scene, a state of grace quite unusual in real life. It doesn’t ring true.

The author is always quite astonished that his own take on the real-life scene did not translate into instantaneous sympathy in every conceivable reader. Ultimately, this is a point-of-view problem — the author is just too close to the material to be able to tell that the scene doesn’t read the way she anticipated.

Did I just see some antennae springing up out there? “Hey, wait a minute. Mightn’t an author’s maintaining objective distance from the material — in this case, the annoying co-worker — have helped nip this particular problem in the bud long before the manuscript landed on Millicent’s desk?”

Why, yes, now that you mention it, it would. Let’s look at the benefits of some objective distance in action.

Many writers assume, wrongly, that if someone is irritating in real life, and they reproduce the guy down to the last whisker follicle, he will be annoying on the page as well, but that is not necessarily true. Often, the author’s anger so spills into the account that the villain starts to appear maligned, from the reader’s perspective. If his presentation is too obviously biased, the reader may start to identify with him, and in the worst cases, actually take the villain’s side against the hero. I have read scenes where the case against the villain is so marked that most readers would decide that the hero is the impossible one, not the villain.

This character assassination has clearly not gone as planned. A little more objective distance might have made it go better. Who was it that said, revenge is a dish best served cold?

Yes, I called it revenge, because revenge it usually is. Most writers are very aware of the retributive powers of their work. As my beloved old mentor, the science fiction writer Philip K. Dick, was fond of saying, “Never screw over a living writer. They can always get back at you on the page.”

Oh, stop blushing. You didn’t honestly think that when you included that horrible co-worker in three scenes of your novel that you were doing her a FAVOR, did you?

My most vivid personal experience of this species of writerly vitriol was not as the author, thank goodness, but as the intended victim. And at the risk of having this story backfire on me, I’m going to tell you about it as nonfiction.

Call it a memoir excerpt. To prevent confusion, I’m going to offset the narrative from the discussion.

A few years before I began blogging, I was in residence at an artists’ colony. Now, retreats vary a great deal; mine have ranged from a fragrant month-long stay in a cedar cabin in far-northern Minnesota, where all of the writers were asked to remain silent until 4 p.m. each day to a sojourn in a medieval village in southwestern France to a let’s-revisit-the-early-1970s meat market, complete with hot tub, in the Sierra foothills.

A word to the wise: it pays to do your homework before you apply.

This particular colony had more or less taken over a small, rural New England town, so almost everyone I saw for the month of March was a writer, sculptor, photographer, or painter. While world-class painters and sculptors were imported up ice-covered rural roads every few days to critique and encourage those newer to their respective arts, the National Book Award winner scheduled to give feedback to the writers didn’t bother to show up for the first week of her residency. Amenities like kilns, darkrooms, and ladders to facilitate the construction of 20-foot woven cardboard cocoons seemed to appear whenever the visual artists so much as blinked. The writers, a tiny minority, had been shoved into a dank, dark cellar with cinder block walls; you could see the resentment flash in their eyes when they visited the painters’ massive, light-drenched studios, and compared them to the caves to which they had been assigned.

See what I just did there? I skewed the narrative so you would resent the visual artists.

But was that necessary? Objectively speaking, they were not the villains in this situation; they, like me, were visitors to the retreat. Besides, since the overwhelming majority of the Author! Author! community is made up of writers, couldn’t I simply have assumed that my readers would identify with the cave residents pretty much automatically?

Or, better yet, couldn’t I have included a vivid detail or two that would have nudged the reader in that direction without the narration’s appearing to be presenting a myopic account?

What kind of detail, you ask? Let’s try this one on for size.

Due to the musty dampness of the writers’ cellar, I elected to write in my assigned bedroom, in order to catch the occasional ray of sunlight. Sure, there were certain drawbacks — the desk had been designed for a hulking brute twice my size, while the desk chair had apparently been filched from a nearby kindergarten — but at least the heat worked. Too well, in fact: an hour and a half into my first afternoon of writing, a sleepy hornet emerged from the gaping hole around the charming antique light fixture and aimed straight for my head.

It was not the best moment to learn that the windows had been sealed for the winter. You know writers: we can’t be trusted not to let all of the heat out. Unlike, say, painters, whose windows might safely open onto vast vistas of forested hillside.

As the afternoon sun warmed the room, hornet after hornet emerged from its long winter’s nap. After the eighth had expressed its displeasure at my having had the temerity to have turned on either the light or the heat, I shook the bees off my jacket, wrapped my head and shoulders in several scarves, and plunged into a blizzard. By the time I reached the administration building, I was chilled to the bone.

Perhaps naïvely, I had assumed that the hornet’s nest in my room would come as a surprise to the retreat’s administrators. The writer who’d had the room the previous November — the local authorities had deemed it inadequately heated for winter residence — had complained about the bees, too. The painter-in-residence charged with rooting them out had simply not gotten around to it.

And didn’t for three days. He was too busy with a canvas that just couldn’t wait to be handed down to posterity. The administrators encouraged me to regard sleeping on a couch next to the dining hall as my contribution to the world’s supply of art. I had to wait until after dark in order to retrieve my laptop.

That engaged your sympathies more robustly, didn’t it? It’s still my experience and my perspective, told in my voice — but I’ve allowed you to draw the conclusion. That’s simply better storytelling.

Don’t see it? Okay, contrast the fleshed-out account above with the following series of summary statements.

Sharing meals in a dining hall was a bit high school-like, conducive to tensions about who would get to sit at the Living Legend in Residence’s table, squabbles between the writers and the painters about whether one should wait until after lunch to start drinking, or break out the bottles at breakfast (most of the writers were on the first-mentioned side, most of the painters on the latter), and the usual bickerings and flirtations, serious and otherwise, endemic to any group of people forced to spend time together whether or not they have a great deal in common.

An environment ripe, in other words, for people to start to find their co-residents annoying.

Aren’t you already longing for me to show you how specifically they were annoying, rather than merely telling you that they were? Let’s exacerbate the problem in the manner so many writers of the real do, creating the illusion of narrative distance by switching the text almost entirely into the passive voice.

Of course, such problems are endemic to large artists’ colonies. One classic means of dealing with the inevitable annoying co-resident problem is to bring a buddy or three along on a retreat; that way, if the writer in the next cubicle becomes too irritating, one has some back-up when one goes to demand that she stop snapping her gum every 27 seconds, for Pete’s sake. I am of the school of thought that retreating entails leaving the trappings and the personnel of my quotidian life behind, but there’s no denying that at a retreat of any size, there can be real value in having someone to whom to vent about that darned gum-popper. (Who taught her to blow bubbles? A horse?)

Doubtless for this reason, several artists had brought their significant others to the hornet-ridden New England village. Or, to be more accurate, these pairs had applied together: writer and photographer, painter and writer, etc. One of these pairs was a very talented young couple, she a writer brimming with potential, he a sculptor of great promise. Although every fiber of my being longs to use their real names, I shall not.

Let’s call them Hansel and Gretel, to remove all temptation.

And let’s see how this telling, not showing thing I’ve got going works for character development, shall we?

Hansel was an extremely friendly guy, always eager to have a spirited conversation on topics artistic, social, or his personal favorite, explicitly sexual. The dining hall’s Lothario, one constantly spotted him flirting with…hmm, let’s see how best to represent how he directed his attentions…everything with skin.

Amusing, but wouldn’t some details have brought his predilections more clearly before the reader’s eyes? Let’s try showing some of his work.

His eyes flickered over the female residents so persistently that I wondered if he was looking for a model. On day three, when he invited me to his palatial sculpture studio, I realized that he might have been seeking a lady to encase in plaster of Paris: practically every flat surface held representations of breasts, legs, pudenda, and breasts. He practically backed me into a backside. Murmuring some hasty excuse about needing to get back to my hornets, I slipped away from his grasping hands and dashed out into the pelting snow.

Still don’t see why that was better? Okay, let’s revert to generalities.

Being possessed of skin myself, I naturally came in for my fair share of Hansel’s attentions. (How’s that for a colorless summary of the proceeding story?) Generally speaking, though, I tend to reserve serious romantic intentions for…again, how to put this…people capable of talking about something other than themselves. Oh, and perhaps I’m shallow, but I harbor an absurd prejudice in favor of the attractive.

This is precisely the type of paragraph that will absolutely slay ‘em in a verbal anecdote, or even in a blog, but often falls flat on the page. Yes, it’s amusing; yes, people actually do speak this way, so it’s a plausible a first-person narrative voice. But it’s vague. It’s character development, in the sense that it purports to tell the reader something about the narrator, but the reader just has to take the narrative’s word for it. Is that really the best way to convince the reader what a protagonist is like?

An artists’ retreat tends to be a small community, however; one usually ends up faking friendliness with an annoying co-resident or two. Since there was no getting away from the guy — believe me, I tried — I listened to him with some amusement whenever we happened to sit at the same table. I was, after all, the only other artist in residence who had read any Henry Miller. We had coffee a couple of times when there was nobody else in the town’s only coffee shop. And then I went back to my room, battled away the wildlife, and wrote for 50 hours a week.

Imagine my surprise, then, when Gretel started fuming at me like a dragon over the salad bar. Apparently, she thought I was after her man.

Now, I don’t know anything about the internal workings of their marriage; perhaps they derived pleasure from manufacturing jealousy scenes. I don’t, but there’s just no polite way of saying, “HIM? Please; I do have standards” to an angry wife, is there? So I simply started sitting at a different table in the dining hall.

A little junior high schoolish? Yes, but better that than Gretel’s being miserable — and frankly, who needed the drama? I was there to write.

Let’s pause here to consider: what do you, the reader, actually know about Gretel at this point? Are your feelings about her based upon what you have actually seen her do or my conclusions about her motivations? And are the facts even clear: was I the only resident of whom Gretel was jealous, or did she fume over the salad bar with anyone possessing two X chromosomes?

Wouldn’t it have worked better had I just shown her slapping peanut butter violently onto some white bread while I tried to make pleasant conversation with her, or depicted her veering away from me with her cracked metal tray? In short, wouldn’t it have made more sense to show this as a scene, rather than telling it as an anecdote?

Often, this fix is expressed rather confusingly: writers are told to insert some narrative distance into such scenes. I’m not a big fan of this language, for the simple reason that most memoirists and writers of the real new to editor-speak tend to interpret it as a call to make the narrative appear objective by, you guessed it, retreating into the passive voice. Let’s take a gander at this strategy in action.

Another phenomenon that often characterizes a mixed residency — i.e., one where different types of artists cohabitate — is a requirement to share one’s work-in-progress. At this particular retreat, painters and sculptors had to fling their studios open to public scrutiny once a week. Each writer had to do at least one public reading in the course of the month.

Feels like you’ve been shoved back from the story, doesn’t it? That’s how verbal anecdotes tend to read on the page: as rather vague summaries. When they are in the passive voice as well, the narrator can come across as the passive puppet of circumstances, rather than as the primary actor of the piece, the person who makes things happen.

Let’s borrow a tool from the novelist’s kit and make the protagonist active, shall we?

Being a “Hey – I’ve got a barn, and you’ve got costumes!” sort of person, I organized other, informal readings as well, so we writers could benefit from feedback and hearing one another’s work. I invited Gretel to each of these shindigs; she never came. By the end of the second week, my only contact with her was being on the receiving end of homicidal stares in the dining hall, as if I’d poisoned her cat or something.

It was almost enough to make me wish that I had flirted with her mostly unattractive husband.

But I was writing twelve hours a day (yes, Virginia, there IS a good reason to go on a retreat!), so I didn’t think about it much. I had made friends at the retreat, my work was going well, and if Gretel didn’t like me, well, we wouldn’t do our laundry at the same time. (You have to do your own laundry at every artists’ retreat on earth; don’t harbor any fantasies about that.) My friends teased me a little about being such a femme fatale that I didn’t even need to do anything but eat a sandwich near the couple to spark a fit of jealous pique, but that was it.

Aha, so Gretel had singled me out. Was there a good narrative reason not to make that plain earlier? It almost certainly would have been funnier — and made both my reactions and my conclusions as narrator make more sense to the reader.

At the end of the third week of our residency, it was Gretel’s turn to give her formal reading to the entire population of the colony, a few local residents who wandered in because there was nothing else to do in town, and National Book Award winner who had finally deigned dropped by (in exchange for a hefty honorarium) to shed the effulgence of her decades of success upon the resident writers. Since it was such a critical audience, most of the writers elected to read highly polished work, short stories they had already published, excerpts from novels long on the shelves. Unlike my more congenial, small reading groups, it wasn’t an atmosphere conducive to experimentation.

Wow, I’ve left you to fill in a lot of details here, have I not? How could you possibly, when the narrative so far has given you only a very sketchy view of time, place, and character?

Four writers were scheduled to read that night. The first two shared beautifully varnished work, safe stuff, clearly written long before they’d arrived at the retreat. Then Gretel stood up and announced that she was going to read two short pieces she had written here at the colony. She glanced over at me venomously, and my guts told me there was going to be trouble.

See how I worked in the false suspense there? Rather than showing precisely what her venomous glance was like — impossible for you to picture, right, since I have yet to tell you what she looks like? — I embraced the ever-popular storytelling shortcut of having the protagonist’s reaction to an event or person take the place of showing what was actually going on. Think that was the best strategy for this story?

Let’s try another tack. How about getting a little closer to what’s happening in that crowded room, so the reader may feel more like she is there? Or at least more like she’s standing in the narrator’s shoes?

Gretel settled a much-abused spiral notebook onto the podium and began to read a lengthy interior monologue in stentorian tones. Her eyes never left the paper, and with good reason: the plotless account depicted Hansel and Gretel — both mentioned by name on page 1, incidentally — having sex in vivid detail. Just sex, without any emotional content to the interaction, in terms neither titillating nor instructive. It was simply a straightforward account of a mechanical act, structured within a literal countdown to the final climax: “Ten…nine…eight…”

It was so like a late-1960’s journalistic account of a rocket launching that I kept expecting her to say, “Houston, we’ve got a problem.”

I cringed for her — honestly, I did. I’d read some of Gretel’s other work: she was a better writer than this. So what point was she trying to make by reading this…how shall I put it?…a literarily uninteresting piece whose primary point seemed to be to inform the uncomfortable audience that she and her husband had consummated their marriage?

See how I used my response to develop the narrator’s character? Memoirists and writers of the real too often forget that the narrator is the protagonist of the story they are telling, and thus needs to be fleshed out as a character. If I’d attacked that last paragraph with a big more descriptive vim, I might have worked in some interesting insights into both Gretel and Hansel’s characters — how did her account jibe with his sculptural depictions of the act, for instance?

Oh, you thought that all of those body parts were languishing around his studio solo? Alas, no; I’ve seen less accurate models in biology classes. Again, wouldn’t it have been more effective storytelling to have shown that — or even made that last comment — while the protagonist was in the studio?

That would also have been the natural time to work in that Hansel’s sculptures did not…again, how to put this tactfully?…appear to have been based upon his wife’s womanly attributes. Artistically, he favored curves; she was so angular that she could have cut vegetables on her hip bones.

Lingering too long in the narrator’s head can be distracting from the action, though. Throughout the next paragraph, I invite you to consider: as a reader, would you have preferred to see the action more directly, or entirely through the narrator’s perspective?

Maybe I just wasn’t the right audience for her piece: the painters in the back row, the ones who had been drinking since breakfast, waved their bottles, hooting and hollering. They seemed not to notice that although the monologue was from a female perspective, there were no references whatsoever to the narrator’s physical sensations, only what Hansel was doing. The part of Gretel might have been quite adequately played by a robot.

Call me judgmental, but I tend to think that when half the participants seem to be counting the seconds until the act is over, it’s not the best romantic coupling imaginable. Still, looking around the auditorium, I didn’t seem to be the only auditor relieved when it ended. “Three…two…one.” No one applauded but Hansel.

In first-person pieces, the narration will often switch abruptly from inside the protagonist’s head to an ostensibly objective set of descriptions. Sometimes it works, sometimes it doesn’t. You be the judge: how well do you think the next paragraph carries the story forward from the last?

Gretel’s second piece took place at a wedding reception. Again, it was written in the first person, again with herself and her husband identified by name, again an interior monologue. However, this had some legitimately comic moments in the course of the first few paragraphs. As I said, Gretel could write.

Somewhere in the middle of page 2, a new character entered the scene, sat down at a table, picked up a sandwich — and suddenly, the interior monologue shifted from a gently amused description of a social event to a jealously-inflamed tirade that included the immortal lines, “Keep away from my husband, {expletive deleted}!” and “Are those real?”

Need I even mention that her physical description of the object of these jabs would have enabled anyone within the sound of her voice to pick me out of a police line-up?

Wouldn’t it have been both more interesting and better character development to have shown the opening of Gretel’s second piece, rather than leaving it to the reader’s imagination? Ponder how that choice might have affected your perception of whether this scene is funny or tragic, please, as the narrative belatedly tells what it should have shown in the previous section.

She read it extremely well; her voice, her entire demeanor altered, like a hissing cat, arching her back in preparation for a fight. Fury looked great on her. From a literary standpoint, though, the piece fell flat: the character that everyone in the room knew perfectly well was me never actually said or did anything seductive at all; her mere presence was enough to spark almost incoherent rage in the narrator. While that might have been interesting as a dramatic device, Gretel hadn’t done enough character development for either “Jan”– cleverly disguised name, eh?– for the reader either to sympathize with the former or find the latter threatening in any way.

There was no ending to the story. She just stopped, worn out from passion. And Hansel sat there, purple-faced, avoiding the eyes of his sculptor friends, until she finished.

The first comment from the audience was, “Why did the narrator hate Jan so much? What had she done to the narrator?”

Had I been telling this anecdote verbally — and believe me, I have — this spate of summary statements and analysis of what the reader has not been shown might well work beautifully. Memoirists tend to be fond of paragraphs like this, commenting upon the action as if the reader had also been there. It makes abundant sense, from the writer’s perspective: after all, I was actually there, right?

But talking about events creates a very different impression on the page than writing about them vividly enough that the reader can picture the action and characters for herself. If I had shown you the story Gretel was reading, at least in part, you could have judged this character based on her own words — much more powerful than the narrator’s simply telling you what you should think about her.

A professional reader like Millicent — or, heck, like me — might well raise another objection to that last section: since the narration is so skewed to the protagonist’s side, some readers may feel that this account lacks credibility. Could Gretel actually have been as vitriolic (or unstrategic) as I’ve depicted her here?

Actually, she was, every bit — but does that matter, if the narrative can’t make her seem plausible on the page? The fact that Gretel existed and that she chose to act in this extraordinary manner is not sufficient justification for the reader to finish this story. It also has to work as a story, and that’s going to require some serious character development for not only the narrator, but the other characters as well.

You’d be astonished at how often memoir submissions do not treat either as characters. Frequently, Millicent sees memoirs — and slice-of-life fiction, for that matter — that are simply commentary upon what was going on around the protagonist. Yet a memoir isn’t a transcript of events, interesting to the reader simply because they happened to the narrator; it’s one person’s story, skillfully pruned to leave out the dull parts. If the reader doesn’t get to know that narrator, though, or come to experience the other characters as real, the memoir is likely to fall flat.

Why? Because it will read like a series of anecdotes, rather than like a book.

Fictionalizers of real life tend to have an easier time thinking of their protagonists as protagonists, I notice, but as any Millicent could tell you, they often give away the narrative’s bias by clearly siding with one character over another. Or by depicting one character as all sweetness and light and the other as all evil. A popular secondary strategy: describing other characters’ reactions to the antagonist as universally in line with the protagonist’s, as though any onlooker would have had exactly the same response.

I was very nice to Gretel afterward; what else could I do? I laughed at her in-text jokes whenever it was remotely possible, congratulated her warmly on her vibrant dialogue in front of the National Book Award nominee, and made a point of passing along a book of Dorothy Parker short stories to her the next day.

Others were not so kind, either to her or to Hansel. The more considerate ones merely laughed at them behind their backs. (“Three…two…one.”) Others depicted her in cartoon form, or acted out her performance; someone even wrote a parody of her piece and passed it around.

True, I did have to live for the next week with the nickname Mata Hari, but compared to being known as the writer whose act of fictional revenge had so badly belly flopped, I wouldn’t have cared if everyone had called me Lizzie Borden. And, of course, it became quite apparent that every time I went out of my way to be courteous to Gretel after that, every time I smiled at her in a hallway when others wouldn’t, I was only pouring salt on her wounded ego.

Is there anything more stinging than someone you hate feeling sorry for you?

At last, we come full circle, back to my original point in sharing this anecdote in the first place: if your answer was any flavor of yes, you might want to consider waiting until you’ve developed some objective distance from your annoying co-worker before committing her to print. Think at least twice about what you’re putting on the page, particularly for work you are submitting to contests, agencies, or small presses.

Or, heaven forbid, reading to a group of people you want to like you. Or your narrator.

If you’re still angry, maybe it’s not the right time to write about it for publication. Your journal, fine. But until you have gained some perspective — at least enough to perform some legitimate character development for that person you hate — consider giving it a rest. Otherwise, your readers’ sympathies may ricochet, and move in directions that you may not like.

It’s always a good idea to get objective feedback on anything you write before you loose it on the world, but if you incorporate painful real-life scenes into your fiction, sharing before promotion becomes ABSOLUTELY IMPERATIVE. If you work out your aggressions at your computer — and, let’s face it, a lot of us do — please seriously consider joining a writing group. To be blunt about it, finding good first readers you can trust can save you from looking like an irate junior high schooler on a rampage.

And Gretel, honey, in the unlikely event that you ever read this, you might want to remember: revenge is a dish best served cold. Or, as Philip used to say, never screw over a living writer. You never know who might end up writing a blog.

Hey, I’m only human — which renders me a more interesting protagonist in a memoir, right? As a memoirist, I have to assume that my readers too intelligent to believe that I was 100% perfect in this trying situation (I must admit, I did make an unkind joke or two in private), or that Gretel was 100% nasty (in actuality, she was rather nice to people her husband did not appear to be obsessed with sculpting), I suspect that most readers would also wonder whether Hansel actually stood by passively while his wife seethed with jealousy (he didn’t: he egged her on, in what appeared to me to be characteristic of their relationship). Were I planning to use this dynamic in a memoir, it would be in the story’s best interest to develop those less-neat elements into a more plausibly complete account.

If I hoped to fold this frankly pretty darned annoying incident into a novel, the imperative to flesh these people out into fully-rounded characters would be even stronger. Showing their foibles through action and dialogue, rather than just telling the reader what conclusions to draw, is not only better storytelling — it’s less intrusive narration.

Would I feel as vindicated? Perhaps not. Enough time has passed, however, that I now see this story as fundamentally sad: instead of befriending a more experienced writer who could have conceivably helped her on the long, twisty road to publication, Gretel allowed the troubled dynamic of her marriage to become the central focus of a bunch of not-particularly-sympathetic strangers. She, too, was in that dank basement, while her husband created his fantasies of women who did not resemble her in comparative comfort. If he hadn’t chosen me to as the prod with which to keep poking her insecurities, I’m sure he would have found somebody else.

So who is the actual villain of this piece? You decide; that’s the reader’s job, after all.

Keep up the good work!

The logic behind the SASE, or, how to be prepared for something falling on you from a zeppelin

Last time, I broached the subject of the infamous and ubiquitously-requested SASE, industry-speak for the Stamped, Self-Addressed Envelope (get it?) that should accompany every mailed query letter and/or submission packet. (E-mailed queries and submissions cannot include them, obviously, as these forms of communication have no temporal heft to them.) There’s no such thing as a Get Out of Thinking About It pass on this one, I’m afraid: forgetting to include a SASE in a query is an instant-rejection offense at virtually every agency in North America.

Or, to put that in terms even Narcissus could understand, no matter how gifted, talented, and/or beautiful a writer or his work may happen to be, neglecting this small piece of industry etiquette effectively assures that Millicent the agency screener will not spend enough time with ol’ Narcissus’ query packet to find out that he and his work display any or all of these delightful attributes. The packet will simply be rejected unread.

And not merely because Narcissus’ nasty habit of assuming that the rules that apply to ordinary mortals could not possibly apply to him is darned annoying to anyone who has to deal with him professionally. If the agent decides to pick up the manuscript, the writer’s having included the expected SASE demonstrates a pleasing ability to follow directions — and if the agent decides to pass, s/he may return rejected pages at the writer’s expense.

Yes, I know: it’s trying to be expected to underwrite one’s own rejection, but there actually are some benefits for the SASE-provider in this arrangement. To name but one: actually finding out that your query has in fact been rejected, rather than gnawing your fingernails in perpetual worry for a year or two.

Oh, you would prefer to be left to wonder whether (a) the agency has a policy of not informing rejected queriers if the answer is no (quite common), (b) the agency has a policy of not reading incomplete query packets (like, say, those that omit a SASE), or (c) your packet got stuck sideways in the mailbox, and never reached the agency at all?

The expectation that an aspiring writer will always include a SASE with any kind of paper query or submission is universal, at least among U.S. agencies and publishers, so much so that I’ve noticed that many agencies don’t even explain what it means on their websites or listings in the standard guides anymore. It’s become one of those secret handshake things, a practice that the industry just assumes that any writer who is serious about getting published will magically know all about without being told.

Call me zany, but as those of you have been reading this blog for a while are already aware, I’m not a big fan of unspoken assumptions; they place the writer new to the game at a serious strategic disadvantage. So I hope those of you who have been at this for some time will forgive my taking a second post to explain to those new to querying what a SASE is and why, to put it bluntly, the writer is expected to pay the postage for a rejection letter or returned manuscript.

SASE logic seems to be counterintuitive for many aspiring writers. Contrary to popular opinion, a SASE shouldn’t always take the form of a business-size envelope; it varies according to what was sent in the first place. To accompany a single-page query, it’s letter-sized, but should you happen to be querying an agency whose guidelines call for writers to include more than five pages of additional materials (e.g., writing sample, synopsis, author bio, book proposal, a chapter or two), you’d be sending that in a Manila envelope, right? In that case, the SASE would need to be a second Manila envelope, stuffed inside the first, carrying sufficient materials to ship all of those additional materials back to you.

Oh, you hadn’t been thinking of the SASE in those terms? Or was that giant whoosh I heard not a collective gasp, but a whole bunch of eyebrows out there hitting the ceiling?

Probably the latter, I’m guessing, because I’m constantly meeting aspiring writers who are unaware that a SASE should also accompany a manuscript submission. That tends to come as a great big surprise to even writers who have been querying and submitting for a while: since the prevailing wisdom is that the point of the SASE is ease of getting back to a writer to say yes or no, it’s far from uncommon for submitters of 500-page manuscripts to include a simple business-size envelope as a SASE. While certainly understandable, this misses the primary goal of the SASE: ensuring the safe return of whatever a writer sends to an agency.

Thus, you should always include enough postage on your SASE that everything you submitted may be popped into it and mailed with a minimum of effort on the sender’s part. That means, in practice, including a shipping container (second envelope, box, or a shipping label to affix to the box in which you sent the manuscript) already addressed to you with enough postage to get all of those requested pages back to you in one piece.

Since all of that will need to be tucked into the same envelope or box that contains your query, any materials the agency’s submission guidelines request, and/or requested materials, it can get cumbersome, once the time comes to pack it all up. Not to say expensive, especially for writer submitting to US-based agencies from outside the country, who not only have to figure out what the return postage would be in dollars instead of their local currency, but have to wrap their eager fingertips around some US stamps.

Don’t worry, foreign readers: there’s a trick to it. I’ll be getting to that.

I’m constantly barraged with questions from readers about why, in the age of fairly universal paper recycling and cheap, high-quality printers, a writer shouldn’t just ask an agent to recycle a rejected manuscript. Quoth, for instance, clever reader Melospiza:

Why on earth would you want your manuscript back (after it has been rejected)? It won’t be pristine enough to send out again. Why spend the money? And any parcel over one pound can’t be dropped in a mailbox, but must be taken to the post office, not something an agent will appreciate. Let the agent recycle the paper and enclose a (business-size) SASE only.

Oh, would only that were possible, Melospiza, but there’s a rather basic, practical reason to include the SASE for safe return of the manuscript. Chant it with me now, campers: as with a SASEless query, not including a SASE in a submission is usually an automatic-rejection trigger.

Yes, you read that correctly: leaving a SASE out of the submission packet can, and often does, result in a submission’s being rejected unread; ask about it sometime at a writers’ conference. The vast majority of agents will be perfectly up front about the fact that they train their screeners accordingly.

The owners of all of those eyebrows are clutching their heads now, aren’t they, thinking of all of those SASEless submissions — or, more likely, submissions accompanied by only a #10 SASE, rather than one with sufficient postage for the manuscript’s return — they sent out in the dark days of yore. “Okay, I can understand why Millicent would reject SASE-free queries without reading them,” the head-clutchers cry, “but why, in heaven’s name, would an agent who asked to see pages reject them unread?”

Good question, retrospective panickers. The short answer: because it’s obvious to Millicent that a writer who submits without a manuscript-size SASE doesn’t know the secret handshake.

The longer answer is hardly more comforting, I’m afraid. In the publishing industry, it’s considered downright rude for a writer not to include a SASE both large enough and loaded down with enough pre-paid postage to send — wait for it — EVERYTHING enclosed back to the sender. If the SASE isn’t tucked into the packet, or if the postage is not sufficient, and if the agency is going to keep its side of the tacit agreement allowing it to read a writer’s unpublished work, it is going to have to shell out the dosh to mail the rejected manuscript back. Ditto with a query letter that arrives unaccompanied by a SASE.

The result in both cases is generally a form-letter rejection — which costs the agency not only the price of the return postage, but also an envelope and Millicent’s time to address it — or, as is increasingly popular, no response at all. Yes, even for a submission. Pages often go bye-bye, because it would be expensive for the agency to ship back the whole shebang.

I implore you, no matter how little you want to see that manuscript again, do not omit the SASE for the return of the manuscript. Unless, of course, the agency’s website or listing in one of the standard agency guides says specifically that they will recycle rejected manuscripts. (Practically none of them do, but check anyway.)

“You must be pulling our collective leg, Anne,” I hear some of you muttering. “Okay, maybe SASEless queries do tend to get rejected unread, but I can’t believe that it happens to submitted manuscripts or book proposals. By the time an agent is sufficiently interested in you to want to see actual chapters of your book, your foot is too firmly in the door for your submission to be tossed aside unread for a reason as unrelated to the quality of the writing as not including a SASE. I mean, really, what purpose would being that touchy serve?”

A fairly tangible one, actually: it would be one less manuscript for Millicent to read.

Remember, it’s her job to reject 98% of what crosses her desk; even a very successful agent at a giant agency seldom picks up more then 5 or 6 new clients per year, even including ones poached from other agencies. (Which happens all the time, by the way. It would astonish most aspiring writers to know just how many of us agented writers are unhappy with our current representation. As I say early and often, you don’t want just any agent to represent you — you want a well-connected, fully engaged agent who loves your writing and will defend it to the death.) Every submission that disqualifies itself on technical grounds is another step toward that ongoing goal of thinning the pack of contenders.

Do you really want to volunteer your precious manuscript for that particular kamikaze mission?

Admittedly, from the submitter’s point of view, a good argument could be made that this practice inevitably leads to, as Melospiza rightly points out, a big ol’ waste of money, not to mention trees, without really providing much benefit to the gentle, tolerant souls who actually pay for the return postage. After all, from the writer’s perspective, a SASE included with a submission is only going to be used if the news is bad. If the agency likes a partial, they’re going to ask to see the entire manuscript — which means your initial submission will get filed, you will send another packet (with another SASE), and your first SASE may well end up in the trash.

Or, if you’re really lucky, you’ll never see it again, because it will end up in a file drawer in your new agent’s office. Fingers crossed!

If, on the other hand, the agent of your dreams does not like it, all you are doing by providing the postage is paying to get the news that they’re turning you down in a way that will make your postal carrier’s back ache, rather than via a nice, light #10 envelope. So why not just send the manuscript along with a business-size SASE, and be done with it?

Because that’s not how the industry works, that’s why. (See commentary above re: secret handshakes.)

If you’re willing to risk it, you could always include a line in the cover letter, politely asking the agency to recycle the manuscript if they decide not to offer representation and mentioning the business-sized SASE enclosed for their reply. Do be aware, however, that this strategy sometimes backfires with screeners trained to check first for a manuscript-sized SASE: it’s not unheard-of for the Millicents of the world to toss aside such a manuscript without reading the cover letter.

As I believe I may have mentioned before, I don’t make the rules of submission; I only try to render them comprehensible. Let’s all pray that when Millicent does engage in the summary rejection of the SASEless, she flings that precious ream of paper into a recycling bin.

Originally, the whole paper-wasting arrangement was set up this way in order to protect writers. The logic behind this one is so pre-computer — heck, it’s pre-recycling, if you don’t count Abe Lincoln’s scrawling the Gettysburg Address on the back of a used envelope — that it’s likely to be counterintuitive to anyone querying or submitting for the first time today.

Return with me now to those thrilling days of yesteryear, when books were widely read, writers didn’t need agents because publishing houses still read through their slush piles, and the photocopier had not yet been invented. Prior to the advent of personal computers (and nice laser printers in workplaces that might conceivably be accessible after the boss goes home for the day), you could not print out spare copies of your precious manuscript to submit to every Tom, Dick, and Random House in the biz, obviously. Nor could you attach a Word document to an e-mail and send it off via Pony Express. Or even pop down to the corner copy store to run off half a dozen copies.

Equally obviously, no sane human being would entrust her only copy of a manuscript to the vagaries of the mails. So how did writers reproduce their work to submit to several publishing houses or agencies simultaneously?

They retyped it, that’s how. Every single page, every single syllable, every single time.

Think those hardy souls wanted to get their rejected manuscripts back? Darned tootin’. It might save them weeks of retyping time.

My long-term readers will have heard my favorite concrete example of how these returned manuscripts helped writers before, but it’s such a terrific illustration of just how much the SASE used to assist the average aspiring writer that I have no qualms about trotting it out again. Back in the far-away 1950s, my mother, Kleo, was married to Philip, a struggling science fiction writer. While she toiled away at work and went to school, Philip spent his days composing short stories.

Dozens of them. Type, type, type, week in, week out. She would come home and edit them; he would type a revised version. One or the other of them would get a good idea, and they would collaborate in writing the result: one dictating, one typing. She would take them to writing classes and the magazine editors who were already publishing her brother’s SF short stories, returning with still more feedback. Off he went to type another draft.

From scratch. Every single time either of them wanted to change a word. Hard for those of us who write on computers even to imagine, isn’t it?

As writers did in those dark days prior to e-mail, Philip and Kleo stuffed each of those short stories into gray Manila envelopes with a second envelope folded up inside as a SASE and sent them off to any magazine that had evinced even the remotest interest in SF or fantasy. (Except for the ones that Kleo hand-sold by taking to a magazine editor, which is actually how Philip got his first story published. She was, in effect, his original agent. But I digress.)

Each time a short story was rejected — as, in the beginning, all of Philip’s and Kleo’s were — and landed once again in their mailbox with the accuracy of a well-flung boomerang, they acted as professional writers should act: they submitted the rejected story to another magazine immediately. To minimize retyping, they would iron any pages that had gotten bent in the mail, slip the manuscript into a fresh envelope (yes, with a fresh SASE), and pop it into the mail.

Since there were not very many magazines that accepted SF or fantasy back then, they had to keep impeccable records, to avoid sending a rejected story back to a magazine that had already refused it. But Philip kept typing away, and kept as many stories in circulation at once as possible.

How many? Well, no one knows for sure anymore — since occasionally the only copy of a story got sent by mistake, some inevitably got lost.

(Which reminds me to nag those of you sending out manuscripts in the computer age: when was the last time you made a back-up of your manuscript? If, heaven forfend, a gigantic anvil fell from one of those anvil-toting zeppelins we’re always seeing overhead these days onto your main writing space, would it crush both your computer and your back-ups? Do you really want to be crawling about in the ashes, frantically trying to find the remnants of your hard disk?)

One day, the young couple opened their front door to find 17 rejected manuscripts spread all over their minuscule front porch. Their tiny mailbox apparently hadn’t been able to hold that many emphatic expressions of “No!”

So what did the aspiring writers of yesteryear do when faced with that many rejections on the same day? Did they toss all of that paper into the recycling bins that had not yet been invented? Did they rend their garments and give up writing forever? Did they poison their perfectly nice mail carrier for bringing so much bad news all at once?

No, they did what professional writers did back then: Philip had his wife iron the pages so they could be sent out again and resubmitted.

Lest you find the story depressing, the science fiction writer was Philip K. Dick, and one of those stories was THE MINORITY REPORT. Which a director who shall remain nameless (because he changed the ending in a way that would have caused any author’s resentful spectre to dive-bomb LA, howling) made into a rather lucrative movie, decades later.

Which only goes to show you: contrary to the common writerly fantasy/daydream/self-flagellation-after-rejection theme, even the best writers generally have to brazen through quite a bit of rejection before hitting the big time. As my mother likes to say, the only manuscript that stands NO chance of getting published is the one that sits in the bottom drawer, unseen by human eyes.

Admittedly, it was not the most comforting lullaby to have sung above one’s cradle, but she knew whereat she spoke. It’s as true today as it was six decades ago, when there were no photocopying machines, no computers, and no guarantee that the copy you sent would ever be retrievable if it went astray in some publisher’s office.

For our purposes today, the important thing to take away from this story is not the warm glow from the implied pep talk (although that’s nice, too), but the understanding that agencies don’t ask for SASEs in order to inconvenience, annoy, or impoverish aspiring writers. They do it today for precisely the same reason that they did it in the 1950s: to get your work back to you as expeditiously as possible, so you may try its fortunes elsewhere.

You’re welcome.

Also, as I mentioned last time, the practice was intended to protect the writer’s copyright. Just as an e-mailed attachment could conceivably end up, through the magic of multiple forwarding, anywhere on the planet, a loose manuscript that isn’t either in an agent or editor’s office, safely tucked away in that proverbial bottom desk drawer, or being conveyed through sleet, snow, and/or dark of night between one and the other could in fact be stolen.

I know; creepy even to consider. But think about it: is it more or less likely than something pointy falling on your house from a zeppelin?

I’ll answer that one for you: it does happen from time to time, so a savvy writer keeps very, very good track of who precisely has his manuscript when. (If this prospect tends to keep you up at night, please see the SHOULD I WORRY ABOUT MY WORK BEING STOLEN? category on the list at right for tips on how to protect your work.)

Three other things of which a savvy writer keeps very good track: which agents she has already queried (and with what unsolicited-but-permitted extra materials), which already-queried agents have requested materials (and what they requested; every agency asks for the submission packet to contain different components), and which agents are still waiting for her to send them those materials. If an aspiring writer is querying and/or submitting to multiple agents at once — and she should, unless the agent of her dreams has a no simultaneous submissions policy — she had better maintain excellent records; otherwise, it’s just too easy to mix things up.

Or not to know where to send Query #18 when the first 17 SASEs turn up in her mailbox. Or her inbox.

Speaking of minding the details, a savvy writer also takes care when applies postage to her SASE. Let’s take a gander at what postage-related fears were keeping intrepid reader Rachel up at night:

I have a question about the SASE that you put in with your materials. I understand it was always better to use stamps so that the agent can just toss it in the outgoing mail bin at the agency. But I was talking to the postal clerks yesterday and they said that post-911 rules are now in effect: any stamped package over 13 ounces has to be brought to the post. I asked to get metered mail instead, and they said it wouldn’t work because it would have that date (yesterday) on it. A dilemma!

I explained my situation to them and the clerks suggested just using a priority stamp (and the same shipping box), because if a SASE were expected, then stamps are really the only way to go. Is that how they’re doing it now?

Good question, Rachel. Before I answer it, let’s clarify the situation by reiterating the difference between a query packet’s SASE (a missive containing the query letter + any unsolicited materials an agency’s website said were permissible to send with it) and one tucked into a submission (requested materials).

When sending a query, SASE use is pretty straightforward: the writer takes a second envelope, writes his own address on it, adds appropriate postage, folds it, and stuffs it — neatly, please, as becomes a Sanitary Author — into the query envelope. (Oh, like you’ve been able to get the SA out of your mind since yesterday’s post.)

When sending a submission packet, the process is similar, but the packaging is different. If the agent only asks to see limited number of pages, few enough that they could be comfortably placed in a Manila envelope without wrinkling them (the Sanitary Author deplores crumpled pages; so do many agents), all you need to do is take a second Manila envelope, self-address it, affix the same amount of postage you’re going to use to send the whole packet to the agency, fold it, and place it neatly within the submission envelope.

Don’t worry; I shall be devoting some of our collective time in the week to come to explaining how to handle a request for a partial. I wouldn’t leave you hanging.

SASE-wrangling becomes a bit trickier if you’ve been asked to send the entire manuscript, because that generally entails using a box. (For a detailed explanation of what types of box should and shouldn’t be used, complete with glamorous photographs of cardboard in its various manifestations, again, tune in tomorrow.)

Obviously, it’s going to be unwieldy to stuff a second box inside the first, so it’s completely acceptable just to include a self-addressed mailing label and postage. Be sure to mention both in your cover letter, so they won’t get lost on the agency end. (Again, don’t panic: I’ll be talking about how to pull off including such necessary-but-prosaic details gracefully early next week.

If you have already submitted a partial, and then the agent asks for the whole manuscript, don’t just send the rest of the pages: by the time they arrive, Millicent probably will not have a clear enough recollection of the partial just to pick up the story where your initial submission left off. (Heck, by then, Millicent may already have moved on to pastures new; the turnover amongst screeners can be pretty remarkable.) Send the entire manuscript, in the aforementioned box.

Equally obviously (but I’m going to mention it anyway, just in case), the stamps on the SASE need to be US stamps, if the agency is US-based. That requirement means that SASEing is invariably a great deal more challenging — and expensive — for writers in foreign climes querying or submitting to US agencies. The far-flung are not exempt from the SASE expectation, I’m afraid, which can make e-mailed querying a more attractive option.

Good news for the far-flung: the US Postal Service’s website sells stamps at face value, rather than at the exorbitant mark-up one frequently finds for them abroad. The USPS more than happy to ship ‘em to your doorstep in exotic climes so you may stick ‘em onto your SASE before popping your submission into the mail.

But let’s get back to the crux of Rachel’s question: has the post-9/11 alteration in post office policy altered what agencies expect to see on a SASE?

The last decade has indeed seen some changes in how agencies handle packages, but actually, most of them date from before 9/11, back to the anthrax scare. Before that, virtually no agency accepted electronic submissions. A few scary mailings later, and suddenly, agencies all over New York were opening e-mail accounts. Hey, they may not pay their Millicents much, but the average agency certainly doesn’t want its screeners to get sick from opening a poisoned query envelope.

E-mailed queries and submissions don’t carry the risk of that sort of infection (and I think we can all guess how the Sanitary Author would feel about that). They do, however, occasionally contain computer viruses, so few agents will open an attachment unless they have already specifically requested an electronic submission from a writer.

That’s why, in case you’d been wondering, most agencies have policies forbidding e-queriers from sending unsolicited materials as attachments. Too much risk of computer contamination. Instead, they will usually ask queriers to copy any permissible additional materials and paste them into the body of an e-mail.

Rachel’s clerk was quite right about heavier packages having to be physically carried into the post office by human being, rather than blithely dropped into a mailbox or dumped in a mailroom — a policy shift that would affect virtually any submitted full manuscript, since they tend to be heavy little critters. However, that most emphatically does not mean is that the agent is going to be taking a rejected manuscript to the post office herself, or even that the Millicent who screened it will. Some luckless agency intern will be toting a whole mess of them there every few days.

Or not; since the USPS changed its regulations in this respect, many agencies have side-stepped the return mail problem by ceasing to return submitted manuscripts to their writers at all. (Sensing a pattern here?) Check policies before you submit.

Interestingly, agencies that operate this way virtually always still expect submitters to include SASEs with their submissions. Go figure. The moral: unless you are querying or submitting electronically OR an agency specifically says it doesn’t use SASEs, you should always include one.

And always use actual stamps, rather than metered postage. It’s called a STAMPED, self-addressed envelope for a reason, you know. The goal here is not merely convenience in mailing, but the submitter’s paying for his own manuscript’s return. Regardless of whether that means tossing it into the nearest mailbox (which would still be possible for most partial manuscripts) or assigning Millicent to do it, stamps have always served the purpose best.

That being said, I must confess that I don’t quite understand the clerk’s recommendation to Rachel to affix Priority Mail postage to the SASE, unless he was either lobbying her to use a flat-rate Priority Mail envelope as a SASE (not a bad idea, especially if the submission is just a few chapters; they fold nicely into a submission envelope) or simply trying to hawk a more expensive stamp. The distinction between Priority Mail and regular mail is the speed with which it arrives; the ease of mailing is identical.

Buying a more expensive stamp or a cheaper one to affix to the SASE is entirely up to the writer; coughing up the dosh for speedier return is not going to impress Millicent. Like overnighting requested materials vs. sending them regular mail, whether a submitter elects to pay a shipper extra money to convey a manuscript from point A to point B is generally a matter of complete indifference to the agent receiving it, as long as it gets there in one piece.

(“And looking pretty,” adds the Sanitary Author. “None of those pesky wrinkles. Print your manuscript on nice, bright-white, 20-pound paper while you’re at it, please. It’s aesthetically more pleasing than the cheap stuff.”)

To be blunt about it, the agent has absolutely no reason to care how quickly a rejected manuscript reaches its submitter. All she’s going to care about is whether you’ve included the means to mail it back to you at your expense, not hers.

And that, my friends, is the logic that most agencies’ listings in the standard agency guides and websites compress into the terse advice Include SASE. Apparently, somewhere on earth, there lurks a tribe of natural-born queriers who realize from infancy precisely what that means, so it requires no further explanation.

I’ll bet our old pal, the Sanitary Author, is one of that happy breed. For the rest of us, learning how agencies work requires a bit of homework — and the asking of trenchant questions. Keep up the good work!

Nicely stamping your SASE and other Millicent-pleasing habits of the Sanitary Author

sanitary-author

Why, yes, now that you mention it, long-time Author! Author! habitués, I have used this photograph before. Several times, in fact: it’s one of my favorites, for reasons I shall discuss below. Although, really, does cultivating and maintaining an affection for the mythical Sanitary Author require much defense?

Before I launch into that very defense, however, I have some good news to announce about a member of our little community: Austin Gary’s novel, Miss Madeira has just come out in paperback and as an e-book. Congratulations, Austin!

If Austin’s name sounds familiar, it should: he was one of the literary fiction winners in the Author! Author! Rings True Competition earlier this year, albeit for another work. Nor his he a stranger to award winning: under the name Gary Heyde, he is also a BMI award-winning songwriter, with recordings by Tammy Wynette, John Berry, and Jeff Carson.

Miss Madeira was semi-finalist in the 2009 Faulkner-Wisdom fiction competition. Here’s the blurb:

Brilliant teacher Amelia Madeira is torn between her love for the woman who will eventually become her sister-in-law and a gifted male student. Despite producing several generations of students forever known as Madeira’s Kids, gossip begins to grow like apples on a poison tree. As anyone with an intimate knowledge of the workings of small-town America knows, episodic memory is the bailiwick of barbershops, beauty shops, and pool halls.

Keep that good news rolling in, folks. Celebrating our fellow writers’ triumphs substantially eases the long and curvy road to publication.

Back to business. Since I’m aware that many of you are rushing about madly, pulling together flotillas of post-Labor Day queries and submissions, I thought it would be a good time to devote a few days to how query and submission packets should be put together.

Yes, yes, I know: not the sexiest of topics, but lest we forget, Millicent the agency screener is charged not only with assessing the aptness of a queried or submitted manuscript for her agency’s representation list; she’s also going to be drawing some conclusions from the packets about the querier or submitter’s professionalism. Why is that relevant, you ask? Because a writer who has taken the time to learn how the publishing industry expects to see writing presented is going to be less energy-consuming to represent.

Before anyone bristles at the idea that an agency — not a non-profit entity, usually — might consider non-literary factors such as the ability to present writing professionally when weighing the pros and cons of picking up a particular writer, let me recommend that those of you who feel strongly on the subject have a spirited discussion about it in the comments. My goal here is not to judge how agencies operate, but to help good writers navigate the often opaque and counterintuitive querying and submission process.

For the next few days, then, I am going to be talking in minute detail about how to put together professional-looking query and submission packets. To lead gently into that noble endeavor, let us pause and consider the mystery of the Sanitary Author.

I’m not much given to double-takes, campers, but I must admit, I did a lulu when I spotted this sign standing by the side of a two-lane highway in unincorporated Neskowin, Oregon. To the casual observer, Neskowin is a blink-and-you-miss-it collection of buildings, but to the observant passerby, it is fraught with enigma. Among its mysteries: according to its ostensibly unofficial municipal website (last updated, apparently, in 2008) Neskowin’s population is a sparse 170, a human density that renders the two golf courses located there, well, surprising.

Who is playing golf in such high numbers that a lone course wasn’t deemed sufficient for local needs? Bears? Sea lions? Migratory Scots with an affection for Pacific Rim cuisine?

All of these legitimate wonders pale, however, next to the enigma of the Sanitary Author. What makes him or her so darned clean, the passing motorist is left to speculate, and why is the population of Neskowin so proud of that particular resident’s hygiene habits that the non-city fathers saw fit to erect a sign to commemorate the SA’s immaculate practices? Did s/he win some sort of international award for cleanliness, a plaudit akin to the Nobel Prize, in order to raise him or her so very high in the town’s esteem?

Not, obviously, as high as videos, coffee, or ice cream, but let’s face it, it’s more recognition than most authors get.

Does the SA reside in remote forest because such cleanly writing practices would not have been feasible within the confines of a large city like New York, Los Angeles, or even charming and nearby Portland? More importantly from the point of view of fellow authors, how does being so sanitary affect the quality of the SA’s writing — and if it has a net positive effect, should we all be beating a path to Oregon, clamoring to follow in the SA’s spotless footsteps?

And I don’t want to alarm anybody, but should we be worried about all of the unsanitary authors running around out there? The mind positively reels at the vast array of germs Millicent could conceivably pick up from their query and submission packets.

Oh, I know what prosaic types out there are likely to say: since the period after AUTHOR would tend to indicate an abbreviation, this sign probably only refers to the local sanitary authority, the fine municipal employees who look after water quality and maintain the sewer system. So much for impenetrable ambiguity, the literal would doubtless conclude. Just ignore that sasquatch strolling by; there’s nothing to see here.

But look closely at that sign: there’s a period after SANITARY, too. Complete words are seldom abbreviations, I find.

So the mystery continues. I shall make a valiant effort to wrest my mind away from the Sanitary Author and concentrate on the matter at hand: queries and the things that accompany them.

Oh, it’s no use: the image is burned into my brainpan. A psychologist friend of mine once told me that recent research demonstrates that the brain can respond as dramatically to recalled memories as to present life; sometimes, she says, the mind will experience flashbacks as current events. I’m fascinated by this, not only as a memoirist (and yes, the memoir that was supposed to come out a few years ago is still tied up in legal knots; thanks for asking), but as a novelist.

The writer’s descent into a creative trance is one of the least-understood of human phenomena, isn’t it? Don’t know what I’m talking about? Ask your kith and kin what you’re like during periods of intensive writing.

Personally, when I’m in mid-chapter, I have been known to lose my sense of the passage of time. If my cats didn’t remind me occasionally that they do not possess opposable thumbs or the ability to open cabinets (well, okay, most cabinets), they would probably be forced to start nibbling on my toes under my desk to stave off imminent starvation.

I’m inclined to blame this on the way that the creative process colonizes the writer’s brain. The cats seem inclined to blame it on me, which I suppose amounts to more or less the same thing: if a task can’t wait until I polish the scene in front of me to a high gloss, it’s probably not going to happen.

You may be unusually good at jumping back and forth between the creative and observational parts of your brain, but if you’re writing on a regular basis, I’m betting that those who have the good fortune to live and work with you have built up a stockpile of anecdotes about how you space out on the minutiae of quotidian life when you’re writing hard. Or — and I honestly am getting around to the point of today’s post again — when you are embroiled in sending out the aforementioned flotilla of queries.

Oh, you thought you were the only one who spaced out? Far from it. Little things like laundry, taking vitamins, watering plants, and checking e-mail seem to slip unnoticed out of the working writers’ consciousness in the middle of a querying binge or writing jag — and don’t even get me started on how the amnesia about practicalities can intensify in the face of an imminent deadline or, heaven help us, immediately after an agent asks to see a partial or full manuscript.

I suspect that this checking out from the everyday world is a necessary side effect of the alchemy of creation. Because, really, in order to render our characters’ lifeworlds gripping on the page, we writers have to create them in our minds every bit as vividly and in all of the detail of a vitally important memory. That’s a pretty absorbing task, isn’t it?

With a pretty gratifying payoff, potentially: if we do our job very well indeed, we might create a story, a situation, a character that seems to the reader to have stepped straight out of real life. Only better.

Is it that same is-it-real-or-is-it-Memorex trick of the brain, I wonder, that would allow a reader to fall in love with a character in a novel? As recent Nobel laureate — and about time, too — Mario Vargas Llosa wrote in THE PERPETUAL ORGY:

A handful of fictional characters have marked my life more profoundly than a great number of the flesh-and-blood beings I have known.

He’s talking about a literary orgy, incidentally, not a physical one: quite a lot of the book is devoted to his passionate decades-long love affair with the entirely fictional Emma Bovary. And who can blame him for falling in love with her, really? She’s a pretty absorbing character.

Do I sense those of you who intended to get queries and/or submissions out the door now that the annual post-Labor Day return of the publishing world to New York has arrived becoming a bit restless in the face of these musings? “I’m as fond of the creative haze as anyone else,” I hear some of you stalwart souls say, “but right now, most of my writing time is getting eaten up by the process of trying to find an agent. So if you don’t mind my asking, what does any of this have to do with the very practical marketing concerns we’ve spent much of the summer discussing?”

A couple of things, actually. First, in the throes of agent-seeking, it can be pretty easy to forget that query-screeners like Millicent actually are looking to fall in love with some writer’s work.

The querying hurdle is, at least in principle, set in place to maximize the probability of discovering the next Great American Novel — or memoir, or nonfiction book — by freeing agency staff from the necessity of reading pages from every ambitious soul currently writing in English. That way, the theory goes, Millicent can concentrate on deciding amongst the crème de la crème.

Your mind is still focused on the paragraph before last, isn’t it? Yes, you did indeed read that correctly: even the most virulent rejection-generator is usually eager to discover a novel that pulls her immediately into its lifeworld, or a memoir that wrings her heart, or the next Emma Bovary. I don’t think it’s at all coincidental that agents and editors so often describe their first responses to submissions in the language of attraction: you’re going to love this book, it’s a sexy topic, it didn’t grab me, I can’t get this book off my mind, I just didn’t fall in love with the protagonist.

Set those to music, and you’ve got a pop song. (Perhaps Austin could do something with it.) As hard as it may be to believe, Millicent is waiting to be swept off her feet.

Which is why, in case any of you have been wondering, I tend to discuss querying and submission in romantic terms: the query letter is a personal ad for your book; you want attract not just any agent, but the one that’s the best match for you and your work; the first page needs to seduce Millicent into wanting to read on; the chemistry between an agent and a book matters deeply. Ditto between a book and an editor.

So in addition to everything else we writers are trying to create, our writing also need to inspire love.

The interminable and annoying querying/submission process sounds substantially nobler put that way, doesn’t it? Feel free to use this argument the next time some non-writer gapes at the amount of time you’ve invested in trying to land an agent; generating love can take some time.

My second reason for bringing up this high-falutin’ topic is, I’m afraid, disappointingly prosaic. I meant to begin this post by talking about SASEs (Self-Addressed Stamped Envelopes), and I seem to have gotten sidetracked.

I can only plead that I was absorbed in my writing. Excuse me a moment while I feed my languishing cats.

Or perhaps I zoned out because, let’s face it, SASEs are not the most thrilling of topics. But they are absolutely vital to discuss, because a mailed query or submission unaccompanied by a SASE will get rejected automatically at virtually every U.S. agency. Almost invariably without being read.

Pause to ponder the implications, please: if Millicent doesn’t read your query, it’s literally impossible for her to decide to request your manuscript, and therefore impossible for her to fall in love with your writing. Which, in turn, renders it impossible for her boss, the agent, to fall in love with your writing, for the agent to convince an editor to fall in love with your writing, for the editor to convince an editorial committee to fall in love with your writing, and for the publishing house’s marketing department to convince readers to fall in love with your writing.

So omitting the SASE isn’t just a technical gaffe; it’s the catalyst in a tragic tale of lost love.

That’s the writer’s opportunity cost of neglecting to include a SASE in a query packet, but there are costs on the agency end as well. Think about it: having the SASE arrive in the same envelope with the query means that Millicent can grab either a form-letter rejection or please-send-us-pages note (oh, didn’t you realize that both were boilerplates?) the very instant after she makes up her mind which is appropriate.

It takes very little time, and the writers themselves are providing the resources for their own rejection. What’s not for the agency to like?

In fact, they like it so much that that most agencies have standing policies against accepting SASE-free queries at all. Providing an envelope and a stamp to reject a single forgetful writer may seem like a negligible expense — but multiply it by the 800-1500 queries the average agency receives every week, and we’re talking about a considerable investment in writers whose work they have already decided not to represent.

So if you didn’t hear back on that last raft of queries — you know, the ones where you glibly told Millicent to contact you via e-mail if she wanted to see pages — that’s probably why.

Yes, in answer to what half of you just thought so loudly, answering your mailed query via e-mail would have been costly for the agency, too, although obviously, not as costly as hauling an envelope from the supply cabinet and donating a stamp to your ongoing quest to be published. The Millicent charged with opening all of those envelopes and scanning the paper queries would have to stop what she was doing, carry your query — and only yours — to a computer, open the agency’s e-mail server, type a rejection (which would probably be identical to the form letter she’s been stuffing in SASEs all day), hit SEND, then head back to that waist-high pile of queries that came in last week.

Multiply that effort by every querier who thinks he’s being clever, considerate, and/or paper-saving by making a cavalier suggestion to contact him by e-mail, and it would add up to a lot of unnecessarily expended energy over the course of a year. Far, far cheaper for the agency just to tell its Millicents to toss any query unaccompanied by a SASE into the recycling bin.

Although if she does decide to ask for pages, she will probably let you know via e-mail, rather than by sending a reply in the SASE you so thoughtfully provided. I like to think of this as the SASE Utility Paradox: the rejected writer must pay for the postage and envelope that carry the bad news; the accepted writer must offer the stamp and envelope as a sacrifice to the gods of querying.

Either way, you’re going to be buying some envelopes and stamps. (Don’t forget to keep receipts; if you file a Schedule C for your writing business, you may be able to deduct these costs as promotional expenses. Talk to a tax expert with experience handling writers’ returns — which I am not –before you deduct anything, however, because the IRS rules governing writers are, I am told, both strange and different than those applicable to other kinds of artist.)

Believe it or not, part of the SASE’s original purpose was not just to save agencies the cost of postage, but to render the querying and submission processes cheaper for the writer: it was substantially less expensive than if the agencies sent back manuscripts with postage due. (Which used to be the alternative, by the way.) It was also intended to preserve copyright by allowing the writer ostensible control about whose grimy paws were on the manuscript when.

Writers tend to forget this in the cyber age, when huge chunks of writing can be transferred from one end of the planet to the other with the simple push of a button (yes, of course I know that the world is not as flat as that image implies. Don’t quibble at me now; I’m on a roll), but technically, in order to prove copyright over unpublished writing, the writer needs to know at all times where all the extant copies are, saying who can and cannot read it. Writing I post on this blog, for instance, is under my control, since I dictate where people can view it; I could disable RSS feeds, if I wanted. (Oh, the power! The power!) If I sent the same posts out via e-mail, they could end up anywhere, forwarded far beyond my knowledge.

That’s why, in case any of you had been wondering, writing posted online is technically published. It makes it easier for writers to prove that they were the original authors of their online work.

The control-who-reads-it doctrine still governs how agencies operate. When you send previously unpublished material off to an agency — to a credible one, anyway — you are operating on the tacit assumption that no one on the other end will reproduce your writing without your permission. You are not, in effect, authorizing them to show it to anyone else until you sign a contract that explicitly grants them the right to do so.

(Which means, by the way, that you should be very wary of an agent who implies, as some have been known to do in order to edge out the competition, that she has already shown submitted materials to an editor as an inducement for you to sign with her. Technically, she cannot market your writing to anyone until you give her explicit permission to do so — but a writer who has just won a literary contest and is juggling manuscript requests from several agents might not be aware of that.)

When you send a SASE with a submission, you are implicitly asserting your right to control where your work is sent next. It conveys an expectation that if the agency rejects it, they will mail the pages back to you, rather than forwarding it to the kind of pirate press that is currently cranking out the 18th, 19th, and 20th installments in the Harry Potter series.

I hear the one in which Harry fights a dragon actually isn’t bad.

As I believe I have mentioned seventeen or eighteen hundred times before, this is a tradition-bound industry; it has historically been slow to change. No matter how good the logic against some of its long-held norms, this one did not change at all until there were some very tangible benefits on the agencies’ end to altering it.

For example, the anthrax scare convinced some agencies to accept e-mailed queries and submissions; prior to that, virtually none of them did. (Some still don’t; double-check before you press SEND.) And the post 9/11 requirement to tote heavy packages to the post office prompted some agencies to start recycling rejected manuscripts, rather than having the lowest intern on the totem pole wheel a paper-loaded dolly up out of the building.

Like so many other aspects of the querying and submission process, at one time, the use of the SASE carried greater benefits to the writer than it does now, but time has hardened courtesies into demands, and habits into traditions. Today, if you do not include a SASE with your submission, you may well be perceived as thumbing your nose at the traditions of people you are trying to impress.

As satisfying as that may be to contemplate, allow me to suggest that it might not be the best way to convince Millicent of your Socratic intellect, encyclopedic knowledge of how publishing works, and lamb-like willingness to take direction. So while my long-standing affection for writers, trees, and the printed pages both work to produce would love to be able to say dispense with the SASE, it would not be in your best interest to fling away the old norms.

I feel as though I should go off and plant a tree now. Or perhaps reread MADAME BOVARY. Instead, I’m going to be intensely practical for a few moments and tell you precisely how to play the SASE game correctly.

When you send a paper query (as opposed to the e-mail variety), tuck a stamped (not metered) envelope addressed to yourself into the envelope. Do this every time, regardless of whether the agency you’re querying actually asks for a SASE on its website or in its blurb in the standard agency guides. It’s expected, whether they say so or not.

If you are sending more than 4 pages of text along with your query — if the agent asked for an author bio, for instance, or a synopsis — make sure that the postage on your query’s SASE is sufficient to get all of those pages back to you. A #10 (business-size) envelope is the norm to accompany queries, and stamps are universally preferred over metered postage.

Since the agency will be popping the returned materials into the nearest mailbox, the stamps you use should be those currently in use in the AGENCY’s country of residence, not yours. This means that if you are submitting to a US-based agency or publishing house from outside the country, you will need to dig up some US stamps. Since foreign post offices often sell these at a considerable mark-up, you can save a lot of money if you buy the stamps directly from the US Postal Service online.

When you send requested materials via mail (again, as opposed to e-mail submissions), include in your submission packet an envelope or box addressed to yourself, along with sufficient postage for the safe return of EVERYTHING you have submitted. (If you want to be really considerate, you may also include a #10 SASE, so the agent may contact you to ask for more pages. This isn’t really necessary, though: in the age of e-mail and relatively inexpensive long-distance calling, that particular request is unlikely to come via regular mail.)

Again, do this every time, regardless of whether the agency (or publishing house) to whom you are submitting has actually asked for a SASE. Omit it only if the agency specifically asks in its guidelines that you not include it. (I know of only one agency that currently makes this request; need I remind you to read each and every agency’s submission guidelines, in case they differ?)

If the requested pages fit in a Manila envelope, it’s perfectly acceptable to fold a second one in half, stamp and address it, and tuck it in the submission packet. If you have been asked to send so many pages that you need to pack ‘em in a box, paper-clip a return mailing label and stamps to your cover letter, along with a polite request that the agent would affix both to the shipping box in the event of rejection.

You HAVE been sending cover letters with your submissions, right? Just sending a manuscript all by itself is considered a bit rude.

Relax, those of you who just clutched your chests: I’ll be talking about how to put together a cover letter for a submission packet as soon as I polish off this series on SASEs. Who knew there were so many different things that needed to go into a submission packet, eh?

Next time, we’ll delve a bit deeper into the practicalities of the e-mailed query, as well as the ins and outs of submission. You wouldn’t want to be caught unprepared if your query is successful, would you?

In the meantime, keep your eyes peeled for the Sanitary Author. You wouldn’t want to miss him/her/it, would you? Keep up the good work!

Pet Peeves on Parade, part XXXIII, and Structural Repetition, part X: a parting glance before we move to pastures new

Are you still palpitating over that false suspense I managed to build up by the end of yesterday’s post, campers? Or is that heavy panting I hear all of you who are planning to give verbal pitches this summer tumbling onto my virtual doorstep, breathlessly eager to begin our long-anticipated Pitchingpalooza bright and early tomorrow?

Well, it probably won’t be bright and early, unless you are prone to measure such things by moonrise, rather than sunrise; tomorrow is going to be a rather full day. But I shall be launching our latest ‘Palooza, never fear.

“Um, Anne?” the more pacing-minded among you murmur, tapping your watches meaningfully. “Is it my imagination, or did you just extend the false suspense about today’s promised professional readers’ pet peeve by another two whole paragraphs by the simple expedient of digressing into another topic?”

Quite right, pace-minders — and you lengthened it by another paragraph through pointing it out. Now, I’m stretching it to four. Whee! We could keep this up for hours.

But we won’t, because we’ve all gotten the message by now, right? When our old pal, Millicent the agency screener, picks up a page 1, she expects the story (or argument, in the case of nonfiction) to get going right away. When the opening lines dither, evade, and generally avoid leaping right into the meat of the story, she has been known to become just a trifle impatient.

“What is this story about?” she fumes over her latte. “And why isn’t this writer getting on with it?”

Certainly an understandable reaction — and if it isn’t, I can only advise you to go back and read the first four paragraphs of this post again. Perhaps it’s the circles in which I move, but personally, I’ve never met a Millicent — or agent, editor, or contest judge, for that matter — who didn’t share this preference for a book’s opening to get on with it, already. Rarely, if ever, does one hear a professional reader say, “I liked that book, but do you know what would have made it better? A slower page 1. Heck, it would have benefitted from not beginning the central story at all until, oh, page 12 or so.”

I bring this up not only because a page 1 that drags is very frequently enough to trigger rejection — yes, even if the writing that lulls the reader along is beautifully constructed — and this will be my last post in our long-lingering Pet Peeves on Parade series. No, I’ve treated you to this last-minute admonition as a segue into one of the most important rules for a revising writer to remember: just as each authorial voice is individual — good authorial voice, anyway — so is each writer’s pattern of problems. Some very talented writers just can’t manage to get their stories started until page 34; others use and in every other sentence, and still others are purely incapable of remembering the difference between there, they’re, and their. Some rechristen their characters every thirty pages, then forget to go back and change earlier names; some meant to do background research on their protagonist’s mother’s job as a beekeeper, but never seemed to get around to it.

Yes, falling prey to any or all of these tendencies could result in Millicent’s shouting, “Next!” over your submission. You could waste endless energy worrying about that outcome. But rather than fearing her ire or resenting the professional reader’s notoriously sharp eye, may I make a suggestion for a better use of your time? Why not devote yourself to learning what your personal writing patterns are, and figuring out which ones you like enough to keep?

After all, there is no secret formula for writing success: what works for one story will be appallingly inappropriate in another, and vice versa. A thoughtful writer often experiments with a number of different voices, literary devices, and writing styles before settling on the best fit for her book. That’s healthy and a necessary part of a good writer’s learning process — hey, nobody is born knowing every craft trick in the book — but it’s vital to get into the habit of re-reading one’s own manuscripts (ideally, IN THEIR ENTIRETY, IN HARD COPY, and OUT LOUD, of course) with an eye to figuring out which of those experiments are worth incorporating into the book’s overall voice.

Why? Chant it with me now, those of you who have been intrepid enough to follow this series all the way through to the bitter end: because the hallmark of a really good authorial voice is consistency.

That’s not going to happen all by itself, you know — but you’d be surprised at how many submitters seem to act as though it would. As Millicent would be only too happy to tell you if you take her out for a latte (you think it’s easy to stay awake through all of those slow openings?), submissions and contest entries that begin in one voice and switch to another 2, 10, or 100 pages in are almost as common as manuscripts that have no distinctive voice at all.

It may seem self-evident, but in order to clarify your authorial voice or make it consistent across a manuscript, you’re going to need to recognize what it is. How are you going to know what’s good about your writing if you don’t read it? And reread it with each subsequent draft? Not only to catch your personal pattern of mistakes, but to learn what you sound like at your best.

“That’s a lovely sentiment, Anne,” the clock-watchers we met above chime in, “and I’m sure it’s practical advice, well worth heeding. But haven’t you also just distracted us from the fact that you STILL haven’t filled us in on the identity of the Millicent-baiter you teased us about on Monday? Jeez, Alfred Hitchcock himself would have revealed the culprit by now.”

Quite right, pacing-minders. The notorious species of structural repetition that causes professional readers to gnash their teeth and mutter under their breath is — wait, Millie, put down that ice pick! Help! Hel…

Just kidding. You watch-tappers didn’t think you were going to walk away unscathed after the Hitchcock crack, did you?

Actually, one eagle-eyed reader delved into her own manuscript and diagnosed this dreaded form of repetition for herself. Kudos to intrepid Anne A. for bringing it up in the comments a couple of months back:

I’d been looking back at my writing and trying to get rid of my characters’ excessive nodding, shrugging, and looking…especially looking. I’m having a lot of trouble with the looking.

I’ve found that I tend to use looking as a cue in the dialogue for whom a particular phrase is targeted; that is, there are four or five characters standing around and if one character says something directed specifically to another (e.g., “Can you fight?”), I have the speaker look at the target first. I’m finding these terribly difficult to get rid of, because without them the conversation makes little sense.

Any advice on how to handle this? It appears I cycle through, in decreasing frequency: “looked to”, “turned to”, “said to”, and direct address by name. I have a terrible feeling that all of these sound far too repetitive.

We have a winner: looked is one of the most frequently repeated words in manuscript submissions. If I had a nickel for every time I had spotted look, watch, saw, etc. on the manuscript page, well, I’d have a heck of a lot of nickels.

I’m not talking about enough to buy my own publishing house, mind you. Don’t be ridiculous. I’m talking about enough nickels to build a publishing house from sub-basement to rafters entirely out of the things.

Why is look so pervasive? Well, aspiring writers rely upon it, and upon vision-related verb phrases in general, quite heavily, and not always because most human beings glean most of their information about the world around them through their eyes. Often, characters — particularly protagonists — will look things as a means of introducing those things into the narrative. Essentially, the character’s eyes act like a laser pointer, directing the reader’s attention someplace specific. Lookee:

“Oh, I give up,” Albert said crossly. “I’m tired of trying to find that last Easter egg. It can rot, for all I care.”

Sharon cast her eyes around the room, taking in the disordered bookcase, the emptied-out desk drawers, and the overturned couch. She saw no trace of an eggshell of any sort.

Effectively, Sharon is acting as the reader’s eyes in this passage: she moves her eyes, and we are shown objects. Although she is acting, she is passive; she’s not commenting upon those objects — say, drawing the conclusion that Albert is not a particularly well-organized searcher or that the hotel’s maid is likely to find his pastime annoying — nor is she changing the situation through doing anything like knocking over a bookcase herself. She’s not so much advancing the scene as allowing herself to be used as a narrative device.

That’s good news for the self-editor, believe it or not. Instead of showing us the room via a seeing-eye Sharon, the reviser can radically reduce the number of looking references by simply showing what is in the room. That would free up Sharon to engage in activities of her own.

Albert sat in the midst of chaos of his own making. He had disordered the bookcase, emptied out several well-packed desk drawers, and upended the couch. “Oh, I give up. I’m tired of trying to find that last Easter egg. It can rot, for all I care.”

“And I’m tired of cleaning up after you.” Slowly, Sharon withdrew a brace of pistols from her fashionable purse. “We duel at dawn. The maid has offered to be my second.”

Another popular use for looking verbs is to remind the reader from whose perspective she’s approaching the story. This is particularly common in first-person or tight third-person narratives. As in:

I looked at the beautiful blue sky and the hopeful buds on the green trees; they made me sad.

That’s one way to alert the reader to the existence of the buds on the trees and the beauty of the sky — which is, we are told explicitly, blue, as opposed to all of those other colors beautiful skies are always sporting — but it’s not the only narrative possibility, and usually not the most imaginative one. It also slightly blurs the author’s intention: is the reader supposed to concentrate upon the fact that the trees are budding hopefully, or the fact that our narrator saw the buds and projected hope onto them?

Even if the image hitting the narrator’s cornea actually were the most important aspect of this particular sentence — in this example, it isn’t — often, the point of the protagonist’s looking at things is not the action itself, but to alert the reader that the objects being seen exist. Unless this device is used very sparingly, though, most readers will tire pretty quickly of being told over and over again that the protagonist is — stop the presses — seeing or noticing everything around her.

Hard to blame the reader for that, you must admit. From his point of view, it’s self-evident: the object is present in the environment, so naturally, the protagonist sees it. So?

Millicent’s reaction, predictably, is quite a bit less forgiving. “Stop telling me over and over that the protagonist is seeing things!” she will mutter, reaching for her third latte of the afternoon. “You don’t need to keep reminding me of the narrative perspective!”

So what’s a reviser to do with this type of Millicent-annoying look? Cut ‘em without mercy. With a little careful planning, it’s almost always possible simply to have stimuli external to the protagonist just show up, without reminding the reader that the players in the scene have seen them or having the protagonist acknowledge their existence.

Fringe benefit: because this approach encourages the things in question to be more active, the result is often a more vibrant narrative. Take a peek:

The sun shone in a cloudless sky, sending a caressing warmth to encourage the hopeful buds on the green trees. Their very exuberance made me sad.

Anne A’s concern sounds like combination of these two types of looking patterns, a mélange that used to be quite widespread in YA and many categories of genre fiction. In this combo, not only do the characters’ eyeballs serve as the narrator’s means of calling the reader’s attention to something in the physical environment as a sort of, “Hey, you — notice at that!” substitute — those busy, busy peepers also provide the transition between description (often presented as the result of observation) and the next set of actions.

What might that look like on the page, you ask? Let us turn to our next example. While I’m at it, I’ll toss in a little name repetition, since Anne A. mentioned that it was one of her personal bugbears.

Helene looked around the room. Not much there; the occupants must have moved out in a hurry. Suddenly, she saw a glint of silver on the mantelpiece.

She turned to Karen. “Look, Karen! Could that be Aunt Monica’s long-lost broach, the one we have been seeking for hours? If it is, maybe we will be able to figure out how to open its secret compartment and find the combination to the wall safe our beloved aunt told us three times a week throughout our collective girlhood was stored there.” She looked to her cousin for confirmation. “Well? Is it her broach?”

Karen picked up the round pin, examining it. “Possibly, Helene. Strange…”

Helene looked at her cousin expectantly. “What’s strange?”

Karen glanced nervously back toward the door. Did she hear movement out there? “Oh, that the search party, the militia, and the bloodhounds would have missed its being in such an obvious location.”

As you may see — looking verbs are addictive, aren’t they? — it’s not difficult for this type of looking to turn into Hollywood narration, dialogue in which the speaker tells the hearer things both parties already know, purely to convey the information to the reader. Like most dialogue plagued by this phenomenon, this passage benefits from trimming it. All of that visual activity could easily go, too, making room for some more revealing details or more action. (Why didn’t Helene pick up the darned broach herself, if she was so interested in it?) Also, if we really put our editorial minds to it, we could probably stop our heroines from squawking their names at each other constantly like hyacinth macaws.

The room’s dark wood paneling emphasized how quickly the former occupants had decamped. Dust outlines showed where a sinuously curved sofa, an ornate-footed chair, an old-fashioned two-sided partner desk had rested for decades. Only the mantelpiece seemed to have been cleaned within the last year. Silver glinted against the mahogany.

“Aunt Monica’s broach!” She dashed across the room, but Karen beat her to it.

Her cousin ran her fingertips across the polished surface. “How could it be this shiny, if it’s been lying here for a year?”

Helene completed the thought: “And why would everyone else who’s traipsed through here miss it? This was planted!”

Another tendency to keep an eye out for (oh, you think it’s easy to keep coming up with these?) is looking used as a stand-in for other, more interesting activity. It’s indigenous to recently revised manuscripts, as a means of identifying speakers without cluttering up the dialogue with all of those tag lines that graced the first draft. Unfortunately, not every alternative to he said makes for particularly scintillating reading.

Art looked askance at his adopted brother. “You’re not afraid, are you, Kay?”

Kay glanced at the dragon breathing fire nearby. Surely, any sane human being would be afraid. “Not if you will hand me that sword over there on your right. No, farther, next to the tumbledown shack in which that strange old man lives. That’s it, right next to the bronze chicken our grandmother smelted in her dotage. Oh, now you’ve gone too far. Don’t you see it there, beside that gently rippling stream?”

Art recoiled at the sight of it. “You mean the sword stuck in the stone?”

Here, the narrative falls into another Millicent-annoying trap: presentation of the physical environment not via explicit description, but by talking about it as though the narrator (or in this case, the character Kay) and the reader were watching a film of the scene together. Rather than giving us enough detail to be able to picture it as the writer imagines it, we’re left to guess what type of landscape could possibly contain all of those disparate elements.

And why might that narrative choice irritate Millicent? Sing it out loud and clear, campers: it’s the writer’s job to convey a sense of place, not the reader’s job to fill in descriptive details.

Another extremely common use of looked is as a substitute for showing emotional reactions. As any Millicent who has been at it for a while knows to her cost, aspiring writers just love having characters look at one another instead of evincing a more revealing response to something that has just happened.

All of a sudden, the wind chime over Violet’s left shoulder began ringing violently; Llewellyn’s chair seemed to be slipping sideways beneath him. They looked at each other.

“What’s happening?” Violet cried.

Doesn’t add all that much to the scene, does it? That’s because from the reader’s perspective, the mere fact that Violet and Llewellyn chose that moment to train their eyeballs on each other isn’t all that illuminating. Described this flatly, it’s such a generic act that mentioning it doesn’t either advance the plot or reveal character. It begs the question: how did they look at each other? Why did they look at each other?

Okay, so that was two questions. Here’s a third: is there something else that one or both of them could do or say here that would do a better job of advancing the plot and/or revealing what these people are thinking or feeling in this particular moment?

And, of course, there’s the ever-popular self-sufficient glare:

Not looking where he was going, Armand tripped over Patrice’s extended feet. She shot him a look.

Again, what kind of look? What did she intend it to convey, and was it in fact an accurate external representation of her internal mental processes? And while we readers are asking so many questions, why on earth didn’t the writer save us all this trouble by coughing up a substantive description of a meaningful response in the first place?

Be on the lookout, so to speak, for versions of she looked away, a sentence widely used as shorthand for a character’s conscious attempt to avoid conveying emotion to another character. While flesh-and-blood people do actually look away from one another from time to time, and for that very reason, this phrasing, too, can start to feel pretty redundant if characters do it very often.

At the risk of giving away a trade secret, looking away is also not usually the most interesting reaction a character can have to a stressful situation. Frequently, this action is a drama-killer, a means of allowing a character to avoid a direct confrontation. That may be desirable in real life, but since Millicent likes to see conflict on every single page of a novel or memoir — you knew that, right? — do you really want to squander a golden opportunity for injecting more of it into your story?

In short, you’re going to want to take a close look at all of those looks, evaluating on a case-by-case basis. Each time it appears, ask yourself: is this an effective way to convey the meaning I want to the reader, or is this just shorthand? Is it a stand-in for something else, a more revealing action, perhaps, or more interesting possibility? Would the plot or characterization would benefit from a different kind of sentence?

What you should most emphatically not do, however, is simply do a search for the word and cut every use indiscriminately. You’re going to want to exercise your judgment — always bearing in mind, of course, that the reader cannot read your mind, and thus may not interpret shorthand in quite the way you intended. You can’t blame her for that: since all she knows about the story you are telling is what the narrative shows and tells her, if you don’t fill in the details, she has to rely upon her imagination.

Don’t make me start the chanting again. You know the tune by now, right?

Remember, too, that what might work perfectly well in an individual sentence may well become a distracting pattern over the course of a paragraph, page, or even scene. Look is a sneaky one; it is used in so many context to mean so many things. To sharpen your eye to its many means of imbedding itself in text, let’s take a gander at few frolicking in their natural habitat.

He looked at me passionately. “But I want you to marry me, Mary!”

Quickly, I looked down at the fringe decorating my skirt. “I think you should go, Didier.

“Go?” He gave me a look of disbelief. “Didn’t you hear what I just said?”

I looked up. “Didn’t you hear what I just said?”

Taken individually, each of these uses of look is perfectly legitimate. But the problem here isn’t just the word repetition — it’s that looking is acting as a stand-in for a whole lot of potentially interesting human interaction. Over and over and over again.

Don’t look away — we already know what do in this situation, right? When confronted with characters merely looking in response to stimuli, we ask: could they have more character-revealing (or situation-revealing) responses?

The possibilities are endless, of course — which is precisely why I’m a big fan of this particular revision strategy; it can open a simple scene up in some fascinating ways. For instance:

He kissed my hand passionately. “But I want you to marry me, Mary!”

I abruptly became absorbed in studying the fringe decorating my skirt. “I think you should go, Didier.”

“Go?” His tone implied that I’d just asked him to leap off a fifty-foot cliff. “Didn’t you hear what I just said?”

So much for sparing his feelings. “Didn’t you hear what I just said?”

Is everyone comfortable with the prospect of tackling all of those looks in context, retaining some, and coming up with interesting and creative substitutes for others? Good. Now that you’ve started thinking about revising with your reader’s reaction in mind, let’s go back and apply the principles we’ve been discussing to the problem of proper noun repetition in a manuscript.

Oh, did you think that you were through with practical examples, because we were so close to the end of this series? Not a chance — over the past few weeks, we have established a method for dealing with word repetition. Now that we have added the last tool, placing ourselves behind the reader’s spectacles in order to figure out whether the over-used word in question is serving the narrative well, to our writer’s tool belt, aren’t you just dying to trot out the whole set of wrenches?

I’m going to take that look you’re all giving me as a yes. Perhaps if I’m really lucky, you’ll exchange glances. Maybe even meaningful ones.

Suppose for a moment that in mid-revision, you have suddenly become overwhelmed with doubt: have you been over-using proper names? Rather than panic in the face of such a dreadful possibility, you know precisely what to do: first, ascertain just how many of the darned things there are in your manuscript, so you may see just how serious the problem is — and where to begin to attack it.

So you, wise soul, print up a hard copy of your manuscript, pull out your trusty highlighter pens, and mark every time a character’s name appears, dedicating one color to each character. After highlighting up a storm for a chapter or two, you go back and flip through the pages. If a single color appears more than a couple of times on a page, you know that you might want to see where you could trim.

This test, which can be used to diagnose any suspected repetitive pattern in a manuscript, will reveal the most about Millicent’s probable reaction if you begin marking on page 1, of course, rather than at some random point in Chapter 12. If you can only find time to do a few pages, though, you might not want to start marking on page 1. A good, quick check on your name-usage habits is to highlight a two-person dialogue between major characters from the middle of the manuscript.

Why a two-character scene, you ask? See if this pattern seems at all familiar:

”I’ve never seen that giant centipede before,” Tyrone lied. “It just crawled into the house, Mom.”

Angela placed her fists upon her ample hips. “I suppose it opened the back door by itself?”

“It certainly has enough legs to do it,” Tyrone said, examining it. “Or it could have crawled through the keyhole.”

“Next you’ll be telling me that the cat is the one who has been opening the kitchen cabinets,” Angela retorted.

“I’ve seen her do it!” Tyrone insisted.

Angela placed her hand upon his head. “Tyrone, I hate to break it to you, but cats don’t have opposable thumbs. Neither do centipedes. So unless you’re harboring a chimpanzee I don’t know about, I’m going to assume that human hands did all these things.”

The boy cast a nervous glance at his closet door; did Mom know about Archie? “If you say so.”

Did you catch the patterns here? If you immediately said, “By gum, a skimming reader’s eye might mix up Angela and Archie, since they both start with the letter A,” give yourself a gold star for being able to remember that far back in this series. Take another star out of petty cash if you also murmured, “This writer is identifying speakers far, far more often than necessary. I wonder if the same pattern persists throughout the manuscript?”

In this excerpt, the pattern is clear, right? In case those baleful looks you’re giving me mean no, let me ask a follow-up question: how do we know that this scene doesn’t really require this many tag lines?

After the first set of exchanges, there really isn’t any doubt about who is speaking when, is there? So why does the reader need to be reminded so frequently who is who, when the speeches are alternating in a predictable rhythm?

The over-use of tag lines is quite pervasive in submissions, and for good reason: like over-abundant proper names, aspiring writers often believe that they reduce confusion. But to professional eyes, the author of the example above has apparently invented unnecessary opportunities for repeating her characters’ names.

Be on the lookout, too, for frequent use of relational terms as substitutes for names: her mother, my brother, her boss. Often, writers who lean heavily upon name usage will pepper their manuscripts with these, too — and again, physically marking them in the text is generally the best way to figure out if there’s too much pepper in your manuscript.

Okay, so that was a bad joke, but it was intended to soften a hard reality: until repetitions of these phrases are actually highlighted on the manuscript page, it’s well-nigh impossible for most aspiring writers to understand fully why this particular type of repetition drives the pros mad. Relationship repetition may seem merely descriptive or innocuous to a casual reader, but it reduces professional readers to apoplexy; they read it as the writer’s insecurity about the reader’s caring enough – or not being smart enough — to remember how these people are related.

Speaking of over-reactions: “Criminy,” Millicent has been known to mutter. “Is there a REASON you feel the need to tell me three times per page that Roger is Yvette’s son?” Do you think I have no memory at all?”

Sound at all familiar?

In this instance, I think Millicent has some justification for feeling that the writer is talking down to the reader. Unless you are writing a story that will be published in serial form, as so many of Dickens’ works were, it’s not necessary, and can be downright annoying, to keep referring to a character by her relationship to the protagonist.

Especially when, as often happens, the reader is presented with the relationship from several different perspectives. As in:

Brenda looked up at her mother. “Are you sure he’s dead? Couldn’t it be another false alarm?”

Mona cradled her husband’s blue-tinted face in her wrinkled but bejeweled hands. “You’re thinking of my last husband, Martin, the swimmer. Bert’s not capable of holding his breath this long.”

“I didn’t say he was faking it.” Brenda lifted her stepfather’s lifeless arm, dropped it. “I’m just saying that there’s a big difference between comatose and dead.”

“Fine.” Mona kicked her purse at her daughter. “Root through there until you find my compact, and hold the mirror under his nose. If he’s alive, it’ll fog up.”

“For heaven’s sake!” Millicent will be crying by this point in the manuscript, startling fellow screeners in adjacent cubicles. “If Mona is the mother, OF COURSE Brenda is the daughter! What do you think, I’m an idiot?”

Generally speaking, the formal relationship between two characters, particularly if one of those characters is the protagonist, needs to be mentioned to the reader only once in a chapter, at most. If it’s a significant relationship, it may well need to be brought up only once in the book, unless there honestly are issues of mistaken identity involved.

Otherwise, try giving the reminders a bit of a rest.

While you have your marking pens out, it’s not a bad idea to check your submission pages for other instances of phrase repetition as well. I’m not talking about pet phrases here — come on, admit it: every writer has a few phrases and words he likes enough to reuse with some frequency — but overworked nouns and descriptive phrases. Those have a nasty habit of offending the professional eye, too.

You’d be astonished at how much the repetition of even a single verb in two consecutive sentences, for instance, can make a manuscript seem less interesting. Especially — and this is almost impossible to catch when editing on screen, but genuinely irksome to see on a printed page — if the same word or phrase begins or ends two or more sentences in a row.

If you are clever and professional-minded enough to scan your manuscript IN ITS ENTIRETY, IN HARD COPY and OUT LOUD (gee, where have I heard that advice before?), it will immediately become apparent why: it reads as though the point of the paragraph is to get through the information within it as quickly as possible, rather than to write about it as beautifully as possible.

In a race run amongst the stylish, my friends, even a couple of lines that fall down on the job can cost you a head start. You’re in this to express yourself marvelously: try to be consistent about it, but use your best judgment on a case-by-case basis.

That’s such a pretty thought that I am going to sign off here for the day — and the series. Next time, it’s on to the rigors and joys of pitching. Keep up the good work!

Pet Peeves on Parade, part XXXII, and Structural Repetition, part IX: who is that handsome devil in the mirror, and why shouldn’t I consider him the sole arbiter of clarity?

Before I launch into what we all devoutly hope will be my next-to-last post on structural repetition (for the nonce, at least), a recommendation for all of you who write YA: because it’s always a good idea to familiarize oneself with the roots of one’s chosen book category, I would highly recommend that you take a gander at this quite interesting interview with YA grande dame Beverly Cleary. Actually, any writer planning to be a legend in her own time might want to take a peek at it. It’s both fascinating and falls into an interview trap that’s become surprisingly common of late — when asked what books she reads in her own category, Cleary, said that she doesn’t read any. Not too long ago, Philip Roth told a reporter essentially the same thing: readers should continue to pick up his novels, but he no longer reads fiction.

“I wised up,” he said.

I have to say, this strikes me as a trifle tone-deaf, given the difficulties the literary market has been facing of late. If writers don’t read (and buy) books in their own categories, who will? And how is a writer to know how his type of book — and his type of reader — is growing and changing unless he keeps an eye on what’s come out recently?

To be fair, it used to be considered rather chic for authors to pretend that they never thought about their readerships’ tastes while constructing what turned out to be bestsellers. No, art was art and commerce was commerce, and ne’er the twain shall meet: the only thing on the author’s mind, we were given to understand, was the inspiration descending from on high and his own fine sense of what would work on the page literary.

This, like the still-pervasive interview implication that what ends up on the page is first draft, is not a reflection of the realities of authorial life; it’s spin. And it’s unfortunate spin, because statements like these give aspiring writers everywhere the false impression that being a successful author has nothing to do with pleasing one’s readership, or even bothering to learn anything about their tastes. No, this argument goes, a truly gifted writer never seeks to please anyone on the page but himself.

It sounds tempting at first blush, doesn’t it? Art for art’s sake has always appealed to artists. But as a reader — as the overwhelming majority of good writers are, bless your hearts — doesn’t it strike you as a trifle insulting to be told what to like? Especially if the person telling you to like his work one moment is telling you the next moment that he doesn’t read anyone else’s work, and thus cannot provide a well-informed comparative assessment?

I leave the answers to those salient questions to further debate between you and your muse. For our purposes today, let’s take away three things. First, interview styles are as subject to change over time as writing styles; what sounded cool in 1963 may produce a significantly different impression now. It’s not a bad idea, then, for a first-time author to invest some time in reading and listening to recent author interviews, to see what works now and what seems like an idea whose time has passed.

Second, while established authors can sometimes afford to be cavalier about how their writing will strike their readers (although I suspect that you’d be hard-pressed to find a publishing house that would be thrilled about one of its authors doing so in public), those seeking to break into the biz cannot. It’s just not smart marketing to avoid thinking about who your target reader is, why your book will appeal to him or her, and how your book will satisfy an already-existing group of book-buyers’ literary tastes and/or interests in a manner that nothing else on the market currently does.

Obviously, in order to answer those questions, a writer is going to have to learn something about who is reading books like hers already and why. Sensing a pattern here?

Third, and most important for revision purposes, it’s vital to recognize that what the writer takes away from any given scene or paragraph might not be what a reader takes away – or what a reader who does not know the writer personally would glean from it. If the action on the page is confusing to a reader — especially if that reader happens to be an agent, editor, or contest judge — it’s the writer’s responsibility to clarify the writing, not the reader’s to figure out what is going on. Especially if that would mean going back and re-reading the sentences in question; Millicent simply doesn’t have time to do that.

I feel an editing axiom coming on: if a reader finds a passage unclear, it does not matter that the writer can explain glibly what’s going on; the reader can judge only what’s actually on the page.

This is especially important precept to bear in mind if you are editing for humor. All too often, aspiring humorists proceed upon the assumptions that

(a) anything that makes them laugh is inherently funny,

(b) anything that makes their kith and kin laugh is funny,

(c) any anecdote they have ever told out loud and elicited a chuckle is funny, and/or

(d) any reader will find writing based on assumptions (a)-(c) funny.

All of these are palpably untrue, as Millicent the agency screener would be only too happy to tell you, and she should know: humor that doesn’t quite work on the page shows up in submissions so often that it has become one of her pet peeves. It’s also untrue that

(e) having a character laugh at something either he or another character has just said will render it funny to a reader.

That’s likely to come as a surprise to all of those submitters who tried to convince Millicent that their protagonist was the next Hawkeye Pierce by depicting bystanders roaring with laughter at his antics and quips. This exceedingly pervasive professional readers’ pet peeve tends to run a little something like this:

Bored with the lesson, Chuck glanced out the window, searching for amusement. He leap to his feet. “Look, Miss McStraightlacedson! A tiger’s escaped from the zoo!”

Half the class ran to the window while he leaned back in his chair, grinning while his classmates searched for a beast that existed only in his imagination. His friends leaned forward on their desks, cracking up at how gullible the others were.

The teacher alone had not budged. “Back to your seats, everyone. I’m afraid Mr. Hilariouskid has been putting us on again.”

Several boys slapped him on the back as they regained their seats. “That was a good one, Chuckles!” Mopey Wanabefunny cried.

A professional reader’s response to this subtle giggle-prompting tactic is seldom laughter, I’m sorry to report, but eye-rolling. Most often, accompanied by, “Next!”

In other words, it might make Millicent laugh, but not for the right reasons.

While we’re talking about editing for humor, did you catch the other problem with this passage? Hint: the writer probably thought this made this scene’s hilarity clearer, but from the reader’s perspective, it watered down the joke.

If you immediately leapt out of your chair, yelling, “I know the answer, Miss McStraightlacedson! The narrative over-sold the joke,” allow me to hand you the Milton Berle Award; feel free to hang onto it for a while. While the old writing truism that brevity is the soul of wit is not always accurate (as anyone who has ever enjoyed a shaggy dog story can attest), explaining to the reader after the fact why something is humorous almost always renders it less amusing.

As we discussed earlier in this series, this kind of overkill also has another side effect: to a professional reader like Millicent, it indicates some doubt in the writer’s mind that the situation itself is funny enough to prompt laughter without the explanation, which in itself raises a question about its humor value. Basically, it’s a sign that the writer doesn’t trust the reader to get it.

In my experience, though, most of the writers who fall into this trap do so not because they are thinking poorly of their audience’s reading comprehension skills, but because they are not thinking of the reader at all. Something strikes the writer as amusing — so it must be so to the reader, right?

Frequently, no. If it isn’t, the text’s going on to tell the reader why something that hasn’t been shown to be funny should make her laugh is not going to help.

Don’t believe me? Okay, here is that scene again, with the laughter prompts excised, as well as the explanation; while I’m at it, I’m going to change the too-obvious character names as well. Judge for yourself whether the humor doesn’t stand up better.

Bored with the lesson, Charles glanced out the window. He leap to his feet. “Look, Miss Bates! A tiger’s escaped from the zoo!”

Half the class ran to the window. Only a pellucidly blue sky and well-kept lawns greeted them.

The teacher alone had not budged. “Back to your seats, everyone. And you, Mr. Spencer, will report for detention after…Mr. Spencer? Where are you?”

Even the kids who hadn’t rushed to see the tiger screamed. All that remained of Charles was a red-stained tennis shoe occupying his chair.

While his classmates wept and Miss Bates dashed to the principal’s office, Charles walked whistling down the path to the river. Fishing was a much better use of a sunny day than learning about how Hannibal crossed the Alps.

Come on, admit it — you weren’t expecting one new plot twist, were you, much less two? The unexpected is often funny on the page. So much so that if I were editing this piece, I might recommend that the last paragraph be beefed up with another surprise.

While his classmates wept and Miss Bates dashed to the principal’s office, Charles walked whistling down the path to the river. Fishing was a much better use of a sunny day than learning about how Hannibal crossed the Alps. As he slipped through the hedge and off school grounds, he heard a low growl behind him, the faint sound of padded feet.

Whether the pursuer turns out to be a tiger or Miss Bates teaching him a lesson, you must admit, the revised version is quite a bit more amusing than the original. In the second, the writer trusts the reader to be able to follow what’s going on AND to have a sense of the absurd.

Should the writer have explained that Charles reddened his shoe with the ketchup packets he always kept concealed in his desk? Possibly, but not necessarily. If the reader already knew from an earlier scene that the boy believed in being prepared in case any stray hot dogs might find their way to his desk, smuggled from the lunchroom (oh, that rapscallion!), the joke would fly just fine without it. Ditto if we’d already seen him brandishing a red Magic Marker or dabbing a cut with iodine.

There is, in short, no single, hard-and-fast editing rule dictating the right amount of set-up for humor. It all depends on the situation — and the target audience.

Why bring any of this up while either author interviews or revision are on our collective mind? Simple: not taking your reader’s likely response into account renders pulling off either well quite a bit more difficult. A writer who thinks only of his own reaction to what’s on the page tends to overlook clarity problems, logical leaps, redundancy, and anything else that didn’t strike him as important when he composed the passage.

He also is inclined not to consider the reader’s enjoyment — and that’s a real drawback, as far as Millicent is concerned. As we’ve seen in this series on structural repetition, it’s not nearly as much fun to read prose that’s repetitive in sentence structure or vocabulary as writing that’s more varied.

Because writing is a solitary art — yes, even after one lands an agent and sells one’s book to an editor — it’s astonishingly easy to lose sight of the end reader, particularly in the revision stage. When we writers are up on our high horses, we tend to talk about our artistic visions and the importance of being true to our voices, but while we’re being down-to-earth about it, we have to admit that if we can’t (or won’t) take the time to make those visions and voices accessible to the reader AND at least somewhat pleasant to read, we aren’t completing our mission successfully.

Does that mean dumbing down complex concepts or compromising original voices? No, not if revision is performed intelligently. It does mean, however, that the writer of a Frankenstein manuscript owes it to any complex concept that might be lingering with in it, as well as to her own narrative voice, to try to read the text as a reader might.

An author reading I attended last year provided a glorious pragmatic illustration of the necessity for a good reviser (or good writer, for that matter) to consider not only his own point of view when deciding whether a passage of text was clear, but also a reader’s. As is lamentably often the case at such readings, the author read excerpts from her book in a monotone, without once lifting her eyes from the page to connect with her audience.

The result, unsurprisingly, was that her gorgeous prose fell flat. The characters blurred together; the dramatic arc of the scene was lost; the quite amusing punch line failed to invoke even a single smile in an audience member. A great and preventable pity, because the scene she chose to read was well-written, beautifully paced, and contained some genuinely astonishing plot twists.

As if the muses had gone out of their way to demonstrate to this author just how much she was underselling her own excellent prose stylings, the venue had booked a second author to read at the same event, one whose obviously well-rehearsed, excitingly voiced reading, punctuated by frequent merry glances up at her fans, kept the crowd enthralled. Guess which author sold more books?

Now, I have nothing but sympathy for the shy; I happen to enjoy public speaking, but I know that it positively terrifies many. Reading one’s own work in public is hard, so I would STRENUOUSLY recommend that any and all of you who intend to see your work in print some day start practicing reading it in front of others as soon as humanly possible. Reading well out loud is something that few of us manage the very first time we try, after all.

Like so many other skills required of a professional writer, giving good public readings is a learned skill, one that requires practice to perfect. It also requires — you saw this coming, didn’t you? — the writer to take the time to consider what that passage of perfect prose might sound like to someone who, unlike herself, might not have read it before.

I’ve said it before, and I shall no doubt say it again: a writer’s ability to step outside his own head and consider what’s actually on the page, rather than what he thinks is on the page, is crucial to good revision.

Case in point: the question we have been discussing over the last couple of posts, the delicate balance between referring to characters by name often enough for clarity, but not so much that all of those capital letters distract the reader’s eye and prompt Millicent to grope for the form-letter rejection stack. This is a problem that’s not likely to trouble the sleep of a writer who doesn’t think much about what her readers might be taking away from any particular page of his story, right?

In fact, the very question might strike him as just a little bit stupid. “Why, I should have thought that was obvious,” he would huff.

If the writing on that page is clear, his intended meaning may well be obvious. If not, his submission could well end up confusing Millicent — or, still worse, expecting her to fill in gaps in logic, background scenery, character motivation…

You know, all of those thrilling, character- and plot-revealing details that we talk about so much here at Author! Author! as the hallmark of expressive prose. Millicent’s on the lookout for style, recall, not just a gripping story. If she — or any reader, for that matter — has to devote even a few seconds of her scant time with your submission to sorting out confusing logistics, unclear character motivations, or just plain trying to figure out what’s going on, that’s a few less seconds she is spending noticing how likable your protagonist is and how gracefully you describe cloud patterns.

I couldn’t help but notice that not all of you immediately shouted, “Right, by Jove!” Does it strike you as a trifle hostile to literature that our Millie tends to concentrate far more on a submission’s faults than its beauties? Okay, let’s step into in her practical two-inch heels for a moment, and consider the strengths and weaknesses of the kinds of manuscripts we’ve been discussing.

Got your Millicent cap firmly pulled down around your ears? Excellent. Picture four manuscripts before you, each written by a talented writer eager for a break. Which one will you decide to show to your boss, the bigwig agent, and which three will you reject?

Your choices are (1) a narrative that assumes you will put in extra effort to sort out what is going on in certain confusing passages, like so:

He woke up with her hair in his mouth. She rolled sideways. Trees swayed outside the unfamiliar window, giving him no clue of his whereabouts. Ow — his knee! He pulled on his boots.

(2) A submission that just summarizes the story, leaving you to fill in most of the details, rather than providing interesting and surprising specifics from which you might derive your own impression of what’s going on, thus:

Bart woke up dazed, disoriented, under what seemed to be a pouf of somebody else’s hair. There was a girl next to him; for the life of him, he could not remember her name, nor did the trees swaying outside the window give him any clue about where he was. His knee hurt, as if something had smashed against it recently. He had to get out of there. He crept out of bed, pulled on his boots, and left.

(3) the most extreme form of Frankenstein manuscript, one so rife with spelling, grammar, perspective, and consistency problems that even its author appears not to have taken the time to read it all the way through:

But, I wake up with her hair in his mouth. She rolled sideways, pearing at the unshaven face near to her foot. No help there so quite as a mouse, I syruptitiously looked at the trees outside the window, but they didn’t tell me where I had managed to get myself to. Something had cracked against his knee. Where had those darned boots gotten to, and who was this girl anyway?

(That one was genuinely hard for me to write, by the way; I kept having to undo my instinctive corrections.)

(4) A manuscript where the writer has taken the reader’s perspective into account sufficiently to clarify all of the relevant issues of the page, skillfully using a plethora of vivid details to convey to the reader a complex reality and consistent enough in tone that you can discern, however faintly, an individual authorial voice:

Bart woke up gasping for breath. Was he being smothered under a fuzzy scarlet blanket, or had his bangs grown down to his mouth, choking him with a lamb-like pouf of curly hair? Wait — his hair hadn’t been curly since he had been the spelling champion of Mrs. Chellini’s third-grade class. His dim memories of her classroom seemed like Technicolor spectaculars, compared to his recollection of last night.

He yanked a particularly wavy red lock from the corner of his mouth, following it gingerly — better not move too much, head — across the rough Navaho blanket to its source. The mascara-streaked face wasn’t familiar, but the Hooters t-shirt was. Tammy, maybe? Tina? And was that blood on his bare knee? No wonder it hurt: that gash would need stitches.

Tell me, Millicent-for-a-day: which would you choose to pass on to your boss, and which would you reject?

There’s nothing wrong with expecting your reader to draw conclusions from what you say on the page, but as some well-meaning English teacher may have pointed out to you once or twice in the past, style often lies in the essential difference between showing and telling. If the writer chooses to beguile the reader with enough details about a situation that he walks away from the scene with the mental image the author intended, that’s showing. If, on the other hand, the writer elects to tell her tale in generalities, or to spell all of the necessary conclusions for the reader instead of allowing the reader to draw them for himself, that’s telling.

Of course, to write a complex tale, you’re probably going to have to do both. Let’s face it, telling can be quite useful from time to time, particularly in a fast-paced action scene or a chunk of narrative that needs to cover a hefty chunk of passing time. More often than not, however, writers use summary statements as a kind of shorthand writers to get past activities that are necessary to the plot, but just don’t interest them that much.

Which brings me, conveniently enough, to one of the most commonly over-used verbs in manuscript submissions — and, not entirely coincidentally, to one of Millicent’s lesser-known pet peeves. Contest judges complain vociferously about it, too, so I could not in good conscience polish off our discussion of textual redundancy without talking about it. Not that I mind: this particular phenomenon is a favorite bugbear of mine as well, because its astonishingly pervasive use tends, in my experience, to flatten description and characterization.

Have I piqued your curiosity sufficiently yet? Too bad — you’re going to have to wait until tomorrow’s post to find out what this classic Millicent-annoyer is. I know what I’m talking about here, and that’s enough for now.

See how frustrating it is when the writer considers only what she needs to get out of the words on the page, rather than her readers’ desire to know what’s going on? And have I given you strong enough evidence of the point I made yesterday, that false suspense — withholding information from the reader purely for the sake of building suspense — is darned annoying?

My work is done here for the day, clearly. Tune in next time for a few last concrete examples of Millicent-irritants before Pitchingpalooza begins on Wednesday. In the meantime, remember your readers, and keep up the good work!

As individual as a snowflake — but my, don’t those snowflakes start to look alike when they start to pile up (or, as we like to call this post around here, Pet Peeves on Parade, part XXXI, and Structural Repetition, part VIII)

My, that’s a mighty cool image for a midsummer day, is it not? After catching the tail end of a national weather report, I thought some of you fine people could use some visual air conditioning.

And what a refreshing breeze was caused by all of those hands suddenly shooting into the air. “But Anne,” those of you who have been following this series on self-editing and rigorously applying its principles, “air conditioning is felt viscerally, and visual images are seen by the eyes! Is this not, therefore, a mixed metaphor — and aren’t mixed metaphors one of the many, many things that get our old pal Millicent the agency screener’s goat?”

Quite right, sharp-eyed revisers, and well caught. Our Millie has indeed been known to gnash her teeth over analogies that are not quite analogous, as well as sensual organs that pick up sensations beyond their traditional ken. Hearts that skip a pulse, rather than a beat, eyes that observe inflections in tone, facial expressions that convey emotions of such complexity that Marcel Proust would consider their fullness over-examined on the page — all have done their part over the years in depleting Millicent’s goat herd.

She doesn’t have awfully many goats left, people. Choose your words with care.

In an effort to help her conserve a few cloven-footed beasts, I went on at some length last time about the yawn-inducing effect of mentioning characters’ names too often within a short stretch of text. As I tried to show in what was probably an excess of examples, the repetitive force of all those capital letters can be somewhat hypnotic. More seriously, they can be distracting from the story the book is telling.

And that, my friends, is bad news for any submission. It’s worth a novelist’s while, then, to massage the text a little to try to reduce the frequency of those monikers. It’s also worth the memoirist’s while, and the creative nonfictionist’s. Heck, if we going to be honest about it, it would behoove pretty much any writer who presents characters in a format other than a list.

Especially someone who has already performed one (three, five, a hundred and seventeen) revisions on a manuscript. Why? Well, think about it: the more worked-over a manuscript is, the more likely names are to have changed over the course of the revision process, right?

Oh, you thought Millicent wouldn’t notice if your protagonist’s sister was Emily for the first third of the book and Evie thereafter? I can hear her pet goats saying, “Meh!” at the very notion.

Even if this is your first attempt at editing your manuscript, it’s in your best interest to keep an eye on the percussive repetition of those proper nouns, particularly if the names in question begin with the same first letters or sound similar. As we saw last time, repeated first letters in different names can cause the reading eye to leap to unwarranted assumptions, or even — brace yourself, similar name-lovers — cause the reader to mix up the relevant characters.

While you’re already well-braced, I might as well continue with the bad news: character blurring is particularly likely to occur in the opening pages of a manuscript, where many characters are often introduced quite close together.

Resist the temptation, please, to blame the skimming eye, rather than authorial choices, for this species of confusion. It’s hard to blame Millicent for getting confused when eight characters are tossed at her within half a page — especially when that half a page happens to be on page 1, when she cannot reasonably be expected to know which of this cast of thousands is the protagonist.

Oh, you think it’s easy to keep track? Okay, skim over the following sterling piece of literature as rapidly as you can. As always, if you’re having a bit of trouble making out the words, try holding down the COMMAND key and pressing + to enlarge the image.

similar name page 1

Be honest, now: right now, based on that rapid reading alone — no fair referring back to the page — could you draw Cheryl’s family tree? Not as easy for a skimmer to keep track of everyone as one might have at first supposed, is it?

The good news (yes, there is some) is that this problem is at least partially avoidable with a little advance planning on the writer’s part. Since skimming eyes zero in on capital letters, readers are likely to confuse Beryl, Bunnie, and Benny. Adopting the old screenwriters’ axiom of avoiding christening characters with names that begin with the same letter will help alleviate reader confusion.

Repetitive capital letters are not the only avoidable bugbears in naming, however. Swift readers will also frequently mix up names with similar sequences of letters, such as Cheryl, Meryl, and Beryl. Or Jenny and Benny. Or even Bunnie and Billie.

Starting to get the picture, or rather the pattern? Millicent is. And her goat is getting antsy.

Believe it or not, even names that merely sound similar can be hard to tell apart on the page. Why? Well, many readers (not usually the speediest text-absorbers, admittedly, but still, potential enjoyers of your prose) will pronounce names in their minds, at least the first time those monikers appear on the page. So while it may seem unnecessary to worry about anyone’s confusing Cheryl and Sherrill in the same manner that they might mix up Cheryl and Meryl, or Meryl and Beryl, it’s actually not beyond belief.

Try saying that last sentence out loud three times fast, and you’ll see why.

Again, advance planning (or most writers’ preferred method, after-the-fact tedious alteration) is your friend here: name your people so they don’t sound so much alike. Millicent will thank you — and, speaking as someone who survived editing a manuscript whose characters were Maureen, Marlene, Doreen, Arleen, and Darlene, I will thank you, too.

There’s another species of naming conducive to character-blurring, one that seldom involves any capital letters at all: avoiding proper nouns altogether. Such narratives have a nickname amongst editors: he said/she said texts.

Or, as I like to call them, he said/he said/he said.

Don’t laugh: name-eschewing is a more common practice than you might think, and not only in mid-book chapters, where the relevant characters are already established. In fact, leaving identification entirely to pronouns is a fairly popular type of book opening, intended (one assumes) to hook the reader by making him guess who the mysterious he (or, more often, she) of the opening paragraphs could possibly be.

Perhaps not altogether surprisingly, given its ubiquity, this type of opening turns up on practically every Millicent’s pet peeve list. Judge for yourself why it might be a goat-getter:

pronoun-only text

Well, are you hooked? Or, to put it in the terms that a professional reader would, are you eager to turn to page 2? If so, how much of the appeal lay in the inherent excitement of the situation and how it was presented — and how much in the fact that the narrative didn’t bother to tell you who any of these people were or much of anything about them?

“Meh,” says the goat. “I could take this story or leave it, at this point.”

I’m with you, Flossie. For the false suspense device to work, the reader has to find being kept in the dark titillating — and overwhelmingly, Millicents do not. When presented with an opening like this, they are all too prone to start asking practical questions along the lines of Who is this broad?, What on earth is going on here?, and Why is this writer withholding relevant information from me? Is this lady’s name a state secret?

Trust me on this one: in a submission (or contest entry, for that matter), it’s the writer’s job to show what’s going on, not the reader’s job to guess. Letting the reader know who is who is more than good Millicent-pleasing; it’s generally considered better writing than false suspense.

Or any other tactic that’s like to result in reader confusion, really. Millicent’s usual response to being confused by what’s in front of her on the page is generally quite dramatic: a cry of “Next!”

Oh, those hands are in the air again. Yes? “Um, Anne?” those of you joining us mid-series inquire meekly. “I have to admit, I rather like this kind of opening. I can see that it’s suspenseful, but what’s false about it? I’ve seen it in plenty of published books. And if there’s only one character in a scene — or only one whose name the protagonist knows, as in that last example — what’s so confusing about not telling the reader who she is?”

Valid questions all, meek inquirers. Yes, this opening is exciting, and yes, there was a time when this strategy was considered pretty nifty, particularly in fantasy circles. But really, hasn’t it been done to death by now?

The rather hackneyed nature of the tactic is not its primary drawback, however: the problem is that the suspense arises not solely from the considerable inherent stress of the situation upon the protagonist, but from the fact that the reader knows neither who she is nor why she is being pursued. (And why is she wearing a party dress in the woods?) Obviously, though, the narrator, the woman, and the author do know the answers to these questions — so the only possible reason not to share this information with the reader is to prompt the reader to be curious about it.

Hey, you — put Millicent’s goat right back where you found it. It’s not her fault (or the goat’s, for that matter) that the author didn’t have enough faith in the action of his opening scene to let it speak for itself. No, he thought had to introduce a narrative device (and a rather tired one at that) in order to interest the reader in his heroine’s plight.

Frankly, this opening doesn’t need it. Take a gander at the same page 1 with the withheld evidence added in:

“Come on, admit it,” the goat says. “It’s every bit as suspenseful, isn’t it?”

Good point, surprisingly articulate barnyard animal. For many readers, it may even be more suspenseful — having a bit of background to this chase enables us to empathize with Alice’s plight more fully.

Let’s go ahead and establish an axiom: unless there is a very, very good reason for denying the reader information as basic as a character’s name — particularly if, as in that last example, it’s the protagonist in a tight third-person narrative where the narrative voice evidently knows everything there is to know about that character — go ahead and call your characters by name the first time they appear in a scene (or the book), rather than referring to them constantly by only a generic he or she.

Believe me, Millicent doesn’t like to guess — and she has a point in this instance. Too little name-calling can be as harmful to the reader’s experience as too much. Even if the reader should in theory already know who is who, even a relatively mild policy of principled name avoidance can often lead to confusion, especially in action scenes.

Take, for example, the following little number — and to make it a fair test, I shall valiantly resist the temptation to give all of the combatants similar names.

Paul poked Herman in the chest, shoving him into Benjamin. Outraged, he pushed back, sending him tumbling backward into Ed.

“Hey!” he cried, unable to save himself from toppling over onto Josh.

Now, I’m guessing that most of you were able to follow what was happening, even without drawing a diagram of the domino effect. (Although that would have been fun to see, wouldn’t it?) All a reader would really have to do is read slowly and carefully, perhaps going back and re-reading as necessary to answer any lingering questions.

It is indeed possible, then, for the reader to emerge at the end of this passage unconfused. But is it a good idea for a writer to expect the reader to put in the work?

I can answer that one for you: not if that reader is Millicent — or, indeed, any professional reader. Because clarity is, after all, the absolute minimum requirement of publishable writing, the pros typically regard an unclear passage as a poorly-written one, period. Or if not precisely poorly-written, then at least lazily revised.

At best, it’s an abdication of authorial responsibility: the gap between what the writer meant the reader to take away from the text and what’s actually on the page needs to be bridged by someone. The writer who submits the text at this stage is tacitly conveying the belief that it’s the reader’s job to fill in the necessary details; Millicent, by contrast, will be quite sure that it’s the writer’s job — and that the writer called in sick that day.

Here, Flossie. Where has she gone?

Millicent is also quite sure — and this comes as a nasty surprise to a lot of first-time submitters — that it’s not her job to go back and re-read a sentence because she found it confusing the first time around. So positive is she on this point that if such a sentence (or paragraph, or page) appears on page 1 of a submission, as we saw in the example above, she will often simply stop reading altogether.

Chant it with me now, campers: “Next!”

Does that low, despairing moan mean that some of you remain confused about when to name and when not to name? “But Anne, aren’t you presenting us with a Catch-22? I’m afraid that once I start adding all of the proper nouns necessary for clarity to my manuscript, I shall almost instantly run afoul of our bugbear from last time, too-frequent name repetition. Help! And why is this goat following me?”

Fear not, low moaners: you are not alone. Fortunately for all, the last time I brought this up, perplexed reader Elizabeth was brave enough to speak up:

Reading about repetition in manuscripts has me quaking in my boots. I understand that poor Millicent doesn’t want to read the same 15 words strung in a different order for 300 pages, but I was also under the impression that it was better to use a character’s name over a pronoun nine times out of ten, for clarity.

Obviously, it depends on how many times I replace the pronoun with the character name, as well as if Jason is the only “he” in the room, then there is less of a chance for confusion (unless there is also a transsexual in the room as well). One shouldn’t change every “he” to “Jason” just to be clear, or vice versa.

Now that I fully recognize the evils of repetition, I want to do my part and squelch it in my manuscript. I am just in agony over what to do about character names versus pronouns now that you mention that repeating the character’s name over and over is tiresome.

Elizabeth speaks for many here: I frequently meet aspiring writers who tell me that their early writing teachers insisted (wrongly, as it happens) that the only conceivable way to avoid confusing a reader by in a scene with more than one he or she is to avoid using pronouns altogether. The result, as she points out, can be name repetition of the most annoying variety.

Let’s see why. To revisit our earlier pronoun-problem example:

Paul poked Herman in the chest, shoving him into Benjamin. Outraged, Herman pushed Paul back, sending Paul tumbling backward into Ed.

“Hey!” Ed cried, unable to save himself from toppling over onto Josh.

Oh, dear: that won’t do at all, will it? Unless a writer wants to stock up on Goat Chow, this seems like a strategic mistake.

It does serve, however, to illustrate an important reason to approach writing advice with caution: all too often, writing guidelines that aren’t applicable to every situation are presented as inviolable rules. Certainly, many, many aspiring writers are prone to take them as such. Matters of style are, unfortunately, often discussed as if they were matters of fact. As a result, accepting sweeping generalizations like the one Elizabeth cites above may actually be harmful to your writing.

Yes, you read that correctly. So here is my advice: never — and I do mean NEVER — accept a writing rule as universal unless you are absolutely satisfied that it will work in every single applicable instance. If you are not positive that you understand why a writing axiom or piece of feedback will improve your manuscript, do not apply it to your pages.

What should you do instead? Ask questions, plenty of them, and don’t accept, “Well, everybody knows it should be this way,” as an answer. Plenty of stylistic preferences have been foisted upon fledgling writers over the years as laws inviolable, and it actually not all that uncommon for writing teachers not to make — how shall I put this? — as strong a distinction between what is indispensably necessary for good writing and what is simply one possible fix for a common problem.

Take the 9/10th truism Elizabeth mentioned, for instance: it’s not uncommon generic writing advice, but it’s not particularly helpful, is it? I suspect that the real intention behind it is for multiplayer scenes — and, as is true of many pieces of specific writing advice that get passed on as if they were hard-and-fast rules, probably was first scrawled in the margins of a scene with a large cast, most of whom were merely described as he or she. Somehow, through the dim mists of time, what may well have started out as a relatively minor revision suggestion (you might want to think about giving that lady in the forest a name, Gerald), transmogrified into an imperative (thou shalt not use pronouns!).

But that imperative does not exist: there’s plenty of good writing that uses pronouns in abundance. Great writing, even, as even the most cursory flip through the volumes at any well-stocked bookstore or library will rapidly demonstrate. I’ve seen it, and I’m sure you have, too.

Heck, even the goat’s seen it.

That’s why, in case you’d been wondering for the past ten paragraphs, I specified that I often hear the proper-name-at-all-costs rule from aspiring writers; professional writers know better. They know that there are many, many means of achieving clarity in writing about people without treating pronouns as if they were infected with some dreadful communicable disease.

Seriously, professional readers see practically pronoun-free first pages more than you might think — although nowhere near as often as the type of proper name-withholding opening we saw above. The trick, as is so often the case for good revision, is to approach each potential name vs. pronoun conundrum on an individual basis, rather than seeking to force every imaginable use of either into a one-size-fits-all rule.

Don’t be afraid to apply your common sense. As Aristotle liked to point out, moderation is the key.

Okay, so he was talking about something else, but obviously, where there are several characters of the same gender, referring to each by name, at least occasionally, could reduce confusion quite a bit. (And before anybody asks, the rule of thumb for transgendered characters is pretty straightforward in American literature, though: use the pronoun the character would use to refer to him- or herself at the time, regardless of the stage of physical transition. While Marci is introducing herself as Marci, rather than Marc, use she; when he would introduce himself as Marc, use he. It’s only polite to call people what they wish to be called, after all, and it will save the narrative from having to indulge in pointlessly confusing back-and-forth shifts.)

Once the reader knows who the players in a scene are, a clever writer can easily structure the narrative so pronoun use isn’t confusing at all. Remember, moderation is your friend, and clarity is your goal.

Let me guess: you want to see those principles in action, don’t you? Okay, let’s revisit a proper name-heavy example from last time, one that might easily have been composed by a writer who believed pronouns were to be eschewed because they have cooties. Behold the predictable result.

“I don’t think that’s fair of you, Susan,” Louisa snapped.

“Why ever not?” Sue asked.

“Oh, don’t be disingenuous with me, Sue. I’ve known you too long.”

Susan played with a nearby paperweight. Was she testing its weight for throwing? “Honestly, Lou, I haven’t the slightest idea what you’re talking about. Unless this is about John?”

“Of course it’s about John,” Louisa huffed. “How many husbands do you think I have?”

“Just one,” Susan said, smiling. “It’s been just John since the seventh grade.”

Louisa’s eyes stung for a moment. Susan always had known how to push her buttons. “Don’t change the subject, Susan. Next, you’ll be reminiscing about that time we hacked our classmate Elaine to death with sharpened rulers when we were in the fourth grade.”

Susan sighed. “Those were the days, eh, Lou?”

“I’ll say,” Louisa said, edging out of paperweight-tossing range. “She should have known better than to beat you at tetherball.”

“Meh,” the goat observes, shaking its horned head, “that’s quite a lot of proper names for such a short scene, isn’t it?”

Far more than Millicent would deem necessary, certainly — which is to say, far, far more than are necessary for clarity, yet more than enough to feel repetitious on the page. Yet simply replacing all of the names with she (or, in John’s case, he) would leave the reader wondering what was going on. Lookee:

“I don’t think that’s fair of you,” she snapped.

“Why ever not?” she asked.

“Oh, don’t be disingenuous with me. I’ve known you too long.”

She played with a nearby paperweight. Was she testing its weight for throwing? “Honestly, I haven’t the slightest idea what you’re talking about. Unless this is about him?”

“Of course it’s about him,” she huffed. “How many husbands do you think I have?”

“Just one,” she said, smiling. “It’s been just him since the seventh grade.”

Her eyes stung for a moment. She always had known how to push her buttons. “Don’t change the subject. Next, you’ll be reminiscing about that time we hacked our classmate to death with sharpened rulers when we were in the fourth grade.”

She sighed. “Those were the days, eh?”

“I’ll say,” she said, edging out of paperweight-tossing range. “She should have known better than to beat you at tetherball.”

Fortunately, those two options aren’t the only tools we have up our writerly sleeves, are they? Let’s try a combination of minimizing the proper nouns by incorporating a little light pronoun use and reworking the dialogue a little:

“I don’t think that’s fair of you,” Louisa snapped.

“Why ever not?”

“Oh, don’t be disingenuous with me, Sue. I’ve known you too long.”

Susan played with a nearby paperweight. Was she testing its weight for throwing? “Honestly, I haven’t the slightest idea what you’re talking about. Unless this is about John?”

“Of course it’s about him. How many husbands do you think I have?”

“Just one,” she said, smiling. “It’s been just him since the seventh grade.”

Louisa’s eyes stung for a moment. Susan always had known how to push her buttons. “Don’t change the subject. Next, you’ll be reminiscing about that time we hacked our classmate Elaine to death with sharpened rulers when we were in the fourth grade.”

“Those were the days, eh?”

“I’ll say,” Louisa said, edging out of paperweight-tossing range. “She should have known better than to beat you at tetherball.”

Experience even momentary confusion about who was who, or who was saying what when? The goat and I think not. All it took was a touch of creativity, a spot of flexibility, and a willingness to read the scene from the reader’s perspective, rather than the writer’s.

After all, clarity, like beauty, is in the eye of the beholder. As the writer, it’s your job to keep that pupil happy by making your narrative a pleasure to read.

Oh, come back, Flossie — Millicent doesn’t like bad puns, either. Keep up the good work!

And how could I round off a series on Millicent’s pet peeves (part XXX) or one on Structural Repetition (part VII) without bringing up this little number?


Before I launch into today’s magnum opus, allow me to present you with a challenge: what do all of the men above have in common? Other than being, you know, men?

While you are pondering the possibilities, this seems like a good time to mention that beginning next week, I shall begin my much-anticipated Pitchingpalooza series. Because getting through that before my local pitch-centric writers’ conference will require daily posting — in the finest ‘palooza tradition — I will be warming up by tackling a few more pet peeves over the weekend. That will give you time, if you are so inclined, to leave any pitch-related questions, concerns, or special requests in the comments section of this post. The more I know about what you hope and fear in a verbal pitch, the better I can gear Pitchingpalooza to be truly helpful.

Back to today’s business. Have you given up on the brain-teaser above?

Here’s a hint: these are pictures (from left to right and top to bottom) of Man in Black Johnny Cash, John Bunyan (author of a book those of you who grew up loving LITTLE WOMEN may know indirectly, PILGRIM’S PROGRESS), a post-Beatle John Lennon, President John Quincy Adams (in a beefcake portrait, obviously painted prior to his mutton-chops phase), the Great Profile himself, John Barrymore, and John Smythe Pemberton, the inventor of Coca-Cola. Sensing a pattern here?

I should hope so, now that you’ve been sharpening your eye throughout this series on spotting Millicent the agency screener’s pet peeves. But are you as talented at spotting the problem in its native environment?

name repetition example

How did you do? Award yourself a gold star if you spotted all 9 iterations of John in the body of the text — and another if you caught it in the header. (No, that wouldn’t count as repetition in the text, now that you mention it, but to a redundancy-weary Millicent at the end of a long day of screening manuscript submissions, it might contribute subconsciously to her sense of being bombarded by Johns. She’s only human, you know.)

But let me ask you: did the 5 Paulines bug you at all? Or did they simply fade into the woodwork, because your brain automatically accepted them as necessary to the text?

If you’re like 99.99% of the reading public, the repetition of Pauline’s name probably didn’t strike you as at all unusual, but to that other .01% — a demographic that includes practically everyone who has ever read for a living, including agents, editors, and contest judges — it might well have been distracting. Amongst Millicents, submissions (and first drafts in general) are positively notorious for this type of redundancy.

As is so often the case with Millie’s pet peeves, name repetition drives her nuts precisely because it so common — and it’s so common because most aspiring writers don’t notice it in their own work at all. You’d be astonished at just how often a given character’s name will pop up within a single page of text in the average manuscript submission. Like the bugbear of our last few posts, the ubiquitous and, major characters’ names seem to become practically invisible to self-editing writers.

While I’m on the subject of ways to drive Millicent to madness without even trying, let’s talk about a pet peeve shared by practically all of us who read for a living, at least in the U.S.: the radical overuse of the character name John.

Although John is only the second most popular male name in the United States (James has been #1 for a while now), writers can’t get enough of our pal John. Next to him, poor old Jim, as well as lonely old Robert (#3), bereft Michael (#4), and left-at-loose-ends William (#5) lead lives undocumented by the creative pen. As a group, we also have a practically unbounded affection for Jon and Jack. And don’t even get me started on how many Johnnies there are running around YA landscapes, taunting our heroines with their bad-boy ways.

On some days, Millicent’s desk so overfloweth with J-men that he can seem to be stalking her from manuscript to manuscript. “Leave me alone!” she moans, and who can blame her? “And bring me a character named Leopold!”

Of course, even as unusual a name choice as Leopold could become annoying if it appears too often on a single page — but let’s face it, Leo is infinitely less likely to have been popping out at Millie all day as John. L is also not nearly as often the first letter of a proper noun as J, and thus less susceptible to confusing a skimming eye.

Oh, you weren’t aware that many a reader-in-haste would read no farther into a proper noun than its first letter? That fact alone should lead those of you fond of John, John, and Jack to avoid christening any of your other characters Jim, Jason, or Jeremy. For abundant proof why, stand up now, take a few steps back from your computer, and try reading the following as fast as you can:

John jerked Jeremy’s arm sharply. Jostled, Jeremy joked, “Jason, are you going to let John jumble our chess pieces?”

“Jeez, Jason,” John jeered. “You can’t take jesting anywhere near as well as Jared, Jimmy, or Jamal.”

Jared jutted his head from behind the jerry-rigged doorjamb. “Did you call me, John?”

“Just joshing, Jared.” John just missed Jeremy’s playful shove, sending him sprawling into Jason. “Jeremy here can’t take a joke.”

Actually, it’s not a bad idea to avoid giving any other character a name that begins with the same first letter as your protagonist’s. If John had been the only J rambling across the passage above, his too-common moniker might still have irritated Millicent a trifle, but it certainly would have been easier for her to keep track of who was doing what when. Take a gander:

John jerked Harry’s arm sharply. Jostled, Harry joked, “Arnold, are you going to let John jumble our chess pieces?”

“Jeez, Harry,” John jeered. “You can’t take jesting anywhere near as well as Bertrand, Georgie, or Douglas.”

Bertrand jutted his head from behind the jerry-rigged doorjamb. “Did you call me, John?”

“Just joshing, Bertie.” John just missed Harry’s playful shove, sending him sprawling into Arnold. “Harry here can’t take a joke.”

Better already, isn’t it? Still, that’s a lot of capital Hs, Js, and Bs on the page.

News flash: proper nouns are as susceptible to over-use in writing as any other kind of words. Although aspiring writers’ eyes often glide over character and place names during revision, thinking of them as special cases, there is no such thing as a word exempt from being counted as repetitive if it pops up too often on the page.

In fact, proper noun repetition is actually more likely to annoy your garden-variety Millicent than repetition of other nouns. Why? Repetition across submission, of course, as well as within them. Too-frequent reminders of who the characters are and the space on the map they happen to occupy makes the average editor rend her garments and the middle-of-the-road agent moan.

If it’s any consolation, they’ve been rending and moaning for years; proper nouns have been asserting and re-asserting themselves on the manuscript page for a couple of decades now. Pros used to attribute this problem to the itsy-bitsy computer screens that writers were working upon back in the 80s– remember the early Macs, with those postcard-sized screens? They weren’t even tall enough to give a life-sized reflection of an adult face. If the user made the text large enough to read, the screen would only hold a dozen or so lines.

But as technology has progressed, the screens on even inexpensive computers have gotten rather large, haven’t they? Even on a laptop, you can usually have a view of half a page, at least, at full size. My extra-spiffy editor’s monitor can display two full-sized manuscript pages side by side. I could serve a Thanksgiving dinner for eight upon it, if I so chose.

I doubt I shall so choose. But it’s nice to have the option, I suppose.

“So why,” Millicent demands, shuddering at the sight of her co-workers’ disheveled wardrobes, “given how much easier it is to see words on a screen than in days of yore, do submitting writers so seldom have a clear idea of how distracting name repetition can be on a printed page? Is it merely that writers christen their major characters with their favorite names — like, say, the dreaded John — and want to see them in print again and again?”

A good guess, Millie, but I don’t think that’s the primary reason. Partially, it has to do with how differently the eye reads text on a backlit screen: it definitely encourages skimming, if not great big leaps down the page. So does re-reading the same scene for the 157th time. But mostly, I believe it has to do with how infrequently writers read their own work in hard copy.

Hear that Gregorian-like chanting floating through the ether? That’s every writer for whom I’ve ever edited so much as a paragraph automatically murmuring, “Before submission, I must read my manuscript IN ITS ENTIRETY, IN HARD COPY, and OUT LOUD. Particularly the opening pages, because if Millicent has a problem with those, she’s not going to read beyond them.”

I MAY have mentioned this two or three thousand times before. I repeat this advice so often that writers who read this blog religiously have been heard to mutter this inspiring little rule of thumb unconsciously in their sleep, under their breath during important meetings, just after saying, “I do,” to their no doubt adorable spouses, on their deathbeds…

So yes, I admit it: I’m a broken record on this subject. But for some very, very good reasons, I assure you.

To name but the two most relevant for our purposes today: first, reading in hard copy makes patterns in the text far more apparent to the reading eye than scanning text on a computer screen. Hard copy is also how most editors, a hefty proportion of agents, and practically every contest judge currently deciding between finalists will be seeing your submissions.

Yes, even in this advanced electronic age. Many agencies still don’t accept e-mailed submissions; neither do most editors at publishing houses. (Some do, of course, so it’s worth your while to download your manuscript to an electronic reader — my agent uses a Kindle — to see how your pages look on it.) The major literary contests for aspiring writers have been quite slow to switch over to purely electronic entries, probably because regular mail submissions are very handy for sending the admission fee.

But enough theory. Let’s apply some of this to a practical example. As always, if you’re having trouble reading individual words, try holding down the COMMAND key and pressing + to enlarge the image.

a-sample-page

See how your eye tries to leap from one J to the next? Sing along with me now, campers: the skimming eye is automatically attracted to capital letters in a text.

That’s why, in case you were wondering, not-especially-literate people tend to Capitalize Words for Emphasis. (When they’re not placing words that no one has ever said aloud inside quotation marks to indicate that those words are somehow “special” — another widespread professional readers’ pet peeve.) It’s almost always grammatically incorrect, but it definitely does the job of eliciting attention.

That’s not always a good thing, as far as Millicent is concerned. I can show you why in 14 words.

The West Wind whipped through the screen door as if it were not there.

Clearly, the writer intends the reader to respond to this statement with a comment like, “My, but that’s a forceful wind.” An ordinarily critical reader might ask, “Um, isn’t the whole point of a screen door that it allows air to travel through it unobstructed?” Every Millicent currently treading the earth’s surface, however, would produce precisely the same response.

“Why,” they will demand, “is west windcapitalized? Is it someone’s name?”

The practice is, in short, distracting. As a general rule of thumb, anything that causes Millicent to wonder why the writer chose to include it — rather than, say, why the protagonist did or what’s going to happen next — is worth removing from a submission.

That doesn’t mean, of course, that it’s in your best interest to avoid capitalized words altogether. Due to proper nouns’ completely legitimate use of capitals, they jump off the page at the reader — which can be a good thing, if a manuscript is crammed to the gills with action, unnamed characters, and other literary titivations that do not involve the major characters. The reader’s eye will be drawn to the major players when they show up. Problem solved, right?

Not in most manuscripts, no. Since most novels and pretty much all memoirs deal with their respective protagonists on virtually every page, it isn’t precisely necessary to keep calling attention to the protagonist by referring to him by name. Constantly.

Or is it, John? John? Are you listening, John?

Frequent repetition of the protagonist’s name is seldom necessary, especially in scenes where only he appears — and it can become downright irritating over the course the dialogue of a two-character scene. Unless the one of the characters happens to have multiple personalities, it’s generally assumed that the names of the conversants will not alter substantially within the course of a few pages of dialogue.

“So why,” Millicent wants to know, “do so many writers keep labeling the participants every few lines, even in scenes where there’s little probability of confusing the reader by reverting entirely to pronouns?”

An excellent question, Millie. That’s why professional editors so often excise tag lines (he said, she said), rather than having the narrative identify every speaker ever time s/he opens his or her pretty mouth: with only two possible speakers and alternating dialogue, any reasonably intelligent reader may safely be relied upon to follow which lines of dialogue are being spoken by which character. And, let’s face it, this:

John peered through the grimy window. “Is that you, Arlene?”

“Who else would it be?” She pushed the door open with her hip. “Mind helping me with these grocery bags?”

“Oh, of course.”

“Thanks.” As soon as she dropped her burden on the counter, she tossed her car keys in his general direction. “There are twelve more in the trunk.”

moves a heck of a lot faster on the page than this:

“Is that you, Arlene?” John asked, peering through the grimy window.

“Who else would it be?” Arlene asked rhetorically, pushing the door open with her hip. “Mind helping me with these grocery bags?” Arlene added.

“Oh, of course,” John replied.

“Thanks,” Arlene said. As soon as she dropped her burden on the counter, Arlene tossed her car keys in his general direction. “There are twelve more in the trunk,” Arlene said.

Rather pedantic by comparison, no? In published writing, it’s actually considered a trifle insulting to the reader’s intelligence to keep reminding her that the guy who was speaking two lines ago is speaking again now.

What was his name again? Could it possibly have been John?

That reasonably intelligent reader we were discussing a while ago is also more than capable of remembering what both of those people are called by their kith and kin, once the narrative has established proper names. But you’d never know that by the number of times some manuscripts have their discussants call one another by name — and how often the narrative refers to them by name.

John doesn’t think it’s in John’s best interest to do that. John would like to believe that Millicent would remember who he is for more than a sentence or paragraph at a time, even if the narrative did not keep barking his name like a trained seal: “John! John! John!”

In many manuscripts, simply reducing the number of tag lines in a dialogue scene will cut out a startlingly high percentage of the name repetition. In dialogue where the use of tag lines has not been minimized, proper names can pop up so frequently that it’s like a drumbeat in the reader’s ear. Let’s take a gander at a slightly less obvious example.

“I don’t think that’s fair of you, Susan,” Louisa snapped.

“Why ever not?” Sue asked.

“Oh, don’t be disingenuous with me, Sue. I’ve known you too long.”

Susan played with a nearby paperweight. Was she testing its weight for throwing? “Honestly, Lou, I haven’t the slightest idea what you’re talking about. Unless this is about John?”

“Of course it’s about John,” Louisa huffed. “How many husbands do you think I have?”

“Just one,” Susan said, smiling. “It’s been just John since the seventh grade.”

Louisa’s eyes stung for a moment. Susan always had known how to push her buttons. “Don’t change the subject, Susan. Next, you’ll be reminiscing about that time we hacked our classmate Elaine to death with sharpened rulers when we were in the fourth grade.”

Susan sighed. “Those were the days, eh, Lou?”

“I’ll say,” Louisa said, edging out of paperweight-tossing range. “She should have known better than to beat you at tetherball.”

Yes, speakers in the real world do call one another by name this much sometimes, but — feel free to sing along; you know the words by now — like so much of real-life dialogue, that level of repetition would be snore-inducing, if not downright hypnotic, on the page. Especially when name-bearing tag lines are featured in the text, even dialogue between just a couple of characters can convey the sense of a very crowded room.

And that’s more than a little puzzling to professional readers. “Why,” Millicent wonders, hastily taking a sip of her too-hot latte, “would a writer go to such lengths to label people the reader already knows?”

Even when both characters share the same sex, and thus the same personal pronoun, constant name repetition is rarely necessary for maintaining clarity. Yet over-labeling is so common that after reading a few hundred — or a few thousand — manuscripts, Millicent would have to be pretty darned unobservant not to have begun to suspect that many writers simply harbor a prejudice against the innocent-but-effectual pronouns he and she.

Seriously, a lot of submitters seem to go out of their way to eschew pronouns, even in narrative paragraphs. To take not an unusually proper noun-ridden example:

Eve slapped her laptop shut with a bang and glanced around, annoyed, for her waitress. Naturally, Tanya was nowhere in sight. Eve ostentatiously drained her drink to its dregs, but when Tanya did not come running, Eve filched a straw from the table next to her. The guy tapping away on his laptop never even noticed. Eve made slurping sounds on the bottom of her glass with it.

Still no sign of Tanya. For good measure, Eve upended the glass, scattering swiftly melting ice cubes messily all over the starched white tablecloth, and began banging the now-empty vessel upon the now-sodden linen. “Service!” Eve bellowed. “Tanya!”

Quietly, Tanya retrieved Eve’s glass from Eve’s waving hand. “Don’t you think you’ve had enough?”

Eve looked up at Tanya with that my-daddy-is-someone-important air that always worked with bank tellers, hot dog vendors, and waitresses who lived primarily upon their tips. “I’ve been drinking Perrier all night. As you would know if you had been paying attention, Tanya. May I have another?”

Come on, admit it — that was kind of annoying to read, wasn’t it? Until you’ve seen this phenomenon in action, it seems a trifle counter-intuitive that reusing a single word within two consecutive lines might be irritating to a reader, but as we’ve just observed, it can be, even if the word in question is not a proper noun. The capitalization of a name makes it stand out more, however.

Of course, if for some reason the writer of that last piece of sterling prose wanted for some reason best known to himself to render it infinitely more annoying to Millicent, we already know how he might manage that, don’t we? All he needs to do is rechristen Eve and Tanya with names beginning with the same capital letter.

Eve slapped her laptop shut with a bang and glanced around, annoyed, for her waitress. Naturally, Edna was nowhere in sight. Eve ostentatiously drained her drink to its dregs, but when Edna did not come running, Eve filched a straw from the table next to her. The guy tapping away on his laptop never even noticed. Eve made slurping sounds on the bottom of her glass with it.

Still no sign of Edna. For good measure, Eve upended the glass, scattering swiftly melting ice cubes messily all over the starched white tablecloth, and began banging the now-empty vessel upon the now-sodden linen. “Service!” Eve bellowed. “Edna!”

Quietly, Edna retrieved Eve’s glass from Eve’s waving hand. “Don’t you think you’ve had enough?”

Eve looked up at Edna with that my-daddy-is-someone-important air that always worked with bank tellers, hot dog vendors, and waitresses who lived primarily upon their tips. “I’ve been drinking Perrier all night. As you would know if you had been paying attention, Edna. May I have another?”

Remarkable how much more difficult that was to read, isn’t it? To get an even better sense of how repetitious it would seem on a printed page, take a few steps back from your computer (if you can manage that logistically) and take a gander at the pattern all of those capital Es make in the text.

Now, admittedly, the writer of this exceptional excerpt may merely have been trying to clarify matters by repeating the names so often: there are in fact two women in this scene. If both were only called she every time, naturally, the narrative might conceivably become confusing. (If you have any doubts about how confusing a narrative can be when no proper names are used at all, get a 4-year-old to tell you the plot of a movie she’s just seen.)

However, like many proper name-heavy manuscripts, the writer here (who was me, obviously, so I guess it’s not all that productive to speculate about her motivation) has constructed the narrative to make opportunities for name repetition where it isn’t logically necessary. Here’s the same scene again, streamlined to minimize the necessity of naming the players:

She slapped her laptop shut with a bang and glanced around, annoyed, for her waitress. Naturally, Tanya nowhere in sight. Eve ostentatiously drained her drink to its dregs, but when no one came running, she filched a straw from the table next to her — the guy tapping away on his computer never even noticed — and made slurping sounds on the bottom of her glass with it.

Still no sign of life. For good measure, she upended the glass, scattering swiftly melting ice cubes messily all over the starched white tablecloth, and began banging the now-empty vessel upon the now-sodden linen. “Service!” she bellowed.

Quietly, Tanya retrieved the now-airborne glass before it could crash to the floor. “Don’t you think you’ve had enough?”

Eve looked up at her with that my-daddy-is-someone-important air that always worked with bank tellers, hot dog vendors, and waitresses. “I’ve been drinking Perrier all night, as you would have known had you been paying attention. May I have another?”

Anybody confused? I thought not. As you may see, proper nouns were not necessary very often in this passage.

Before any of you proper noun-huggers out there start grumbling about the care required to figure out when a pronoun is appropriate and when a proper noun, that was not a very time-consuming revision. All it really required to alert the reader to which she was which was a clear narrative line, a well-presented situation — and a willingness to name names when necessary.

That, and an awareness that repeating names even as far apart as three or four lines just doesn’t look good on a printed page; it’s distracting to the eye, and therefore a detriment to the reader’s enjoyment of the text. A proper noun repeated more than once per sentence — or, heaven help us — within a single line of text — is almost always a sign that sentence is in need of serious revision.

Ready to accept the general principle, but unsure how you might apply it to your manuscript? Never fear — next time, I shall run you through so many practical examples that you’ll be excising proper nouns in your sleep. You might enjoy some variation from the IN ITS ENTIRETY, IN HARD COPY, and OUT LOUD song.

Night-night, John-John, and keep up the good work!

Pet Peeves on Parade, part XXIX, and Structural Repetition, part VI, and bears, oh my! And other run-on sentences of note. And anything else that might occur to me to include.

Sick of structural repetition yet, campers? Excellent: you’re starting to gain a sense of how Millicent the agency screener and the rest of us who read for a living feel about it.

Oh, you think I’m kidding? Those of use who have been at the manuscript game for a while tend to have negative reaction to it that borders on the visceral. At the end of a long, hard day — or week, or month, or lifetime — of watching manuscripts get caught up in the insidious allure of and to make even the simplest run of short sentences sound interconnected and chatty, just like the run-ons that plague everyday speech, most of us would be perfectly happy never to see a conjunction again.

Okay, so we tend to get over it by the next day. Then what do you think happens? We’re greeted by another manuscript penned by some well-meaning and probably talented soul laboring under the misconception that a narrative voice must sound like somebody who’s had eight cups of coffee by 9 a.m.

Make that someone rude who’s had eight cups of coffee by 9 a.m. There’s just no getting that pushy narrator to pause for breath — or a period. Perhaps unsurprisingly, this run-on dominated style is especially common in first-person narratives:

I was walking down the street, and I saw a car drive by. Not just any car, mind you, but a red, white, and blue car with magenta trim and violet and gold rims. And then, just when I thought my eyeballs could take no more searing, a truck drove up and I looked at it: a two-ton mauve beauty with chartreuse bucket seats, a scarlet grill, and neon yellow racing stripes.

I stopped and stared. Who wouldn’t?

Makes some sense, right? The character narrating the piece is a non-stop talker; the constant forward impulse of all of those ands conveys that. Clearly, what we see on the page is what the narrator would sound like in real life.

A rather literal interpretation of narrative voice — and, perhaps because so many people are hyper-literal, a radically overused device — but justifiable. You’d be astonished, though, at how often third-person narratives — which, although they may follow a single character closely, are seldom attempts to echo an individual’s speech pattern — fall into a similar cadence.

Why is that a problem? Let’s allow those cars to take another pass by our hero.

George was walking down the street, and he saw a car drive by. Not just any car, but a red, white, and blue car with magenta trim and violet and gold rims. And then, just when he thought his eyeballs could take no more searing, a truck drove up and he looked at it: a two-ton mauve beauty with chartreuse bucket seats, a scarlet grill, and neon yellow racing stripes.

George stopped and stared. Who wouldn’t?

Doesn’t work as well, does it? In this version, those run-ons come across as precisely what they are: not a reflection of an individual’s speech patterns, but rather repetitively-structured writing. And, unfortunately for the writer responsible for these immortal words, repetitive in a manner that our old pal, Millicent the agency screener, is likely not only to find repetitive on this page, but across half of the manuscripts she screens today.

Given the unfortunate ubiquity of this structure, a reasonable submitter might conclude that Millicent’s sensibilities would get blunted after a while, but in practice, quite the opposite is true. If anything, most professional readers become more sensitive to word, phrase, and structural repetition over time. So if the ands in question have rampaged all over page 1 of a submission — or even, heaven help us, a query letter — we shouldn’t be tremendously surprised if Millicent reverts to the most over-used word in her vocabulary?

That’s right, campers: “Next!”

Honestly, it’s hard to blame her. Seeing the same phenomenon rampage across submission after submission, one does start to wonder if every sentence structure other than this happened and that happened and then we did this, that, and the other thing was wiped off the face of the earth by an evil wizard. And (see, even I’m doing it now) those of us prone to sympathizing with good writers everywhere can easily become depressed about that, because the ubiquitous use of run-ons can make otherwise quite polished writing seem in a submission like, well, the rest of what we see.

“Oh, talented writer who appears not to read his or her own work very often in hard copy,” we moan, startling onlookers and fellow coffee shop habitués, “why are you handicapping your voice so? It would be understandable — if a bit predictable — if you were writing a first-person narrative, especially if it is YA, but in this close third-person narrative, why cram so many disparate elements into a single sentence? If only you would give the ands a rest and vary your sentence structures more, your voice would be much more enjoyable to read.”

I’m telling you: it’s a tragedy — all the more so because so many aspiring writers are not even aware that this plague afflicts their manuscripts. For every voice-constructor makes a conscious authorial choice to incorporate conversational run-ons to ramp up the narrative’s chatty verisimilitude, there seem to be ten who just don’t notice the ands piling up .

Purposeful or not, the results still aren’t pretty, as far as Millicent is concerned. Any reasonably busy professional reader sees and in print so often that she might as well have that WANTED poster above plastered on her cubicle wall.

And‘s crime? Accessory to structurally repetitive prose. As we have seen close up and personal in my last few posts, too great an affection for this multi-purpose word can lead to run-on sentences, dull action sequences, and contracting nasty warts all over one’s kneecaps.

Well, perhaps not the last, but let’s face it: no other individual word is as single-handedly responsible for text that distracts the eye, enervates the mind, and wearies the soul by saying different things in more or less the same way over and over and over again on the page. Yet on the individual sentence level, the problem may not be at all apparent.

Don’t believe me? Okay, let’s take a look at the issue both in isolation and at the paragraph level.

Bernadette had her cake and ate it, too.

Standing alone, there’s nothing inherently wrong with this sentence, right? Most self-editors would not even consider excising it. Solitude, however, tends not to be this structure’s writer-preferred state. A perennial favorite in both submissions and contest entries, the X happened and Y happened sentence structure all too often travels in packs.

Yes, like wolves. Here’s what the mob tends to look like in its natural habitat:

Bernadette had her cake and ate it, too. Jorge ate what was left of her cake and then went out and baked his own. He believed it to be good, tasty, and yummy. After having tried his cake and found it untoothsome, unpalatable, and generally inedible, Frankenstein’s monster broke into his apartment and destroyed his oven.

“I’m stopping him,” the monster told reporters, “before he bakes again.”

See the problem? No? Okay, let’s look at that first paragraph again as Millicent might:

Bernadette had her cake AND ate it, too. Jorge ate what was left of her cake AND then went out AND baked his own. He believed it to be good, tasty, AND yummy. After having tried his cake AND found it untoothsome, unpalatable, AND generally inedible, Frankenstein’s monster broke into his apartment AND destroyed his oven.

Like any sentence structure that appears too often within a short run of text, this type of sentence to bore the reader after a while, even if the subject matter is inherently interesting — and yes, Virginia, even if every sentence in the passage isn’t put together in precisely the same way. That’s and‘s fault, you know; when too many of them appear on a page, even the untrained eye starts unconsciously counting them up.

Seven, by the way. And two in the last paragraph of explanation — which also boasted two evens, in case you’re interested.

That’s not to say, naturally, that the X happened and Y happened sentence structure doesn’t have some legitimate uses. Let’s face it, it’s darned useful, providing a quick way to inform the reader of quite a bit of action in a short amount of text. Instead of having to write a brand-new sentence for each verb with the same subject, all of the action can be presented as a list, essentially. That can be especially handy if the individual activities mentioned are necessary to plot, characterization, or clarity, but not especially interesting in and of themselves.

Weary from a long day at work, Ambrose sat down and removed his heavy steel-toed boots.

Nothing wrong with that, right? The reader doesn’t need to spend two sentences mulling over Ambrose’s rather predictable post-workday actions. Now, while we’ve got our revision spectacles on, we could debate from now until next Tuesday whether the reader actually needs to be told that Ambrose sat down — not exactly a character-revealing move, is it? — but that’s a matter of style, not proper presentation. Technically, this is a perfectly legitimate way to convey what’s going on.

You’d be astonished, though, how often aspiring writers will treat even quite a thrilling string of events in this manner, purely in the interest of telling a tale rapidly. This tactic is particularly popular amongst synopsis-writers trying to compress a complex plot into just a page or two. Like so:

AMBROSE MERCUROCROME, JR. (27) comes home from work one day, removes his steel-toed boots, and discovers that the third toe on his left foot has transformed into a gecko. He cuts it off in a panic and takes it to a veterinarian, DR. LAO (193). Dr. Lao examines the gecko-toe and determines it has the capacity to knit exquisite sweaters. He and the gecko kill AMBROSE, go into business together, and soon take the skiwear market by storm.

Not the most scintillating way of describing the plot, is it? The repetitive structure gives the impression that none of these potentially quite exciting plot developments is important enough to the story to rate its own sentence. Obviously, that’s a problem in a synopsis, where the goal is to present the story you’re telling as interesting and exciting.

Perhaps less obviously — brace yourself, and-lovers; you’re not going to like this — this structure can create a similarly dismissive impression on a manuscript page. Not to be telling stories out of school, but skimming eye like You-Know-Who’s will has been known note only the first verb in a sentence and skip the rest.

Before any and-hugger out there takes umbrage at the idea of every sentence in his submission or contest entry’s not getting read in full, let’s take a moment to think about verb-listing sentences from Millicent’s perspective — or, indeed, any reader’s. If an action is not crucial enough to what’s going on for the writer to devote an entire sentence to it, why should we assume that it’s important to the scene?

I sense some squirming out there. “But Anne,” some of you and partisans hasten to point out, “while I admit that sometimes I lump a bunch of activity together in a few short, list-like sentences in order to speed things up a bit, that’s not the primary way I use and in my prose. As you yourself have mentioned, and not all that long ago, stringing together sentences beginning with but or yet, it creates the impression conversation-like flow. Isn’t that essential for a convincing first-person narrative?”

At the risk of repeating myself, partisans, echoing recognizable speech patterns is only one technique for constructing a plausibly realistic first-person narrative voice. There are others; this is simply the easiest. It would be hard to deny that

I woke up the next morning and poisoned my husband’s cornflakes.

is chatty, casual, echoing the way your local spouse-poisoner is likely to describe her activities to her next-door neighbor. True, it doesn’t quite match the arid eloquence of Ambrose Bierce’s

Early one June morning in 1872, I murdered my father — an act which made a deep impression on me at the time.

But then, what does?

You would not be alone, then, if you feel that the heavy use of and is downright indispensable in constructing dialogue or a first-person narrative. (Just ask Millicent how often she sees it on any given day of submission-screening.) Many a living, breathing, conversation-producing person does incorporate the X happened and Y happened structure into her speech with great regularity.

In many cases, with monotonous regularity. Certainly, it can feel awfully darned monotonous to the reader, if it appears on the printed page with anywhere near the frequency that it tumbles out of the average person’s mouth.

Don’t believe me? Okay, try walking into any public place with an abacus and moving a bead every time you hear somebody use and. Better get some training on how to use that abacus quickly, though; your total is going to be up in the thousands before you know it.

Yes? Do those of you who have been following this series have anything you’d like to add here? Perhaps the observation that no matter why a word, phrase, sentence structure, and/or narrative device appears over and over again within a short span of text, it’s likely to strike a professional reader as repetitive?

No? Were you perhaps thinking of my oft-repeated axiom that just because something happens in the real world doesn’t necessarily mean that a transcript of it will make compelling reading?

Despite the sad fact that both of these observations are undoubtedly true, few real-world patterns are as consistently reproduced with fidelity in writing as everyday, mundane verbal patterns. Sociological movements come and go unsung, jargon passes through the language literarily unnoted, entire financial systems melt down without generating so much as a mention in a novel — but heaven forfend that everyday redundant or pause-riddled speech should not be reproduced mercilessly down to the last spouted cliché.

And don’t even get me started on the practically court-reporter levels of realism writers tend to lavish on characters who stutter or — how to put this gracefully? — do not cling tenaciously to the rules of grammar when they speak. In some manuscripts, it seems that if there’s an ain’t uttered within a five-mile radius, the writer is going to risk life and limb to track it down, stun it, and pin it to the page with quotation marks.

Again, I’m not saying that there aren’t some pretty good reasons underlying this impulse. Many aspiring writers consciously strive for prose that echoes the kind of conversational rhythms and structures one hears every day, particularly when they are penning first-person or present-tense narratives.

“I want it to sound real,” they say with engaging earnestness. “My goal is to hold, as ’twere, the mirror up to nature.”

Unfortunately, from Millicent’s perspective, most of these writers don’t realize just how widespread this particular goal is — or that much real-life conversation would be either deadly dull, logically incoherent, or at minimum not literarily interesting transferred directly to the printed page. Real-life speakers repeat both words and sentence structures to an extent that would make even the most patient reader rip her hair out at the roots in frustration.

And I’m talking arm hair here, people. If you doubt the intensity of this reaction, here’s a little experiment:

(1) Sit in a crowded café for two hours, jotting down the conversations around you verbatim.

No fair picking and choosing only the interesting ones; you’re striving for realistic dialogue, right?

(2) Go home and type up those conversations as scenes, using only the dialogue that you actually overheard.

No cheating: reproduce ALL of it.

(3) Wait a week.

(4) Seat yourself in a comfy chair and read the result in its entirety.

If you can peruse the result without falling into a profound slumber, congratulations! You have an unusually high threshold for boredom; perhaps you have a future as an agency screener. Or maybe you have cultivated an affection for the mundane that far outstrips that of the average reader.

How can you tell if you have roughly the same redundancy tolerance as most reader? Did you find yourself reaching for the nearest ice pick with the intention of self-destruction within five pages?

And if your fingers start itching not for that ice pick, but for a pen to write some acidic commentary on the subject of the inadvisability of boring one’s audience with gratuitous word repetition, have you considered a career in publishing? Millicent was reaching for that pen before she graduated from middle school.

I was reaching for it before I could walk. One of the most beloved Mini family anecdotes concerns my correcting a dinner guest’s grammar from my high chair. His spoken grammar.

But enough about me. Let’s get back to that test.

(5) Ask yourself honestly: does the dialogue you overheard have any entertainment value at all when reproduced in its entirety? Or are only selected lines worth preserving — if, indeed, any lines deserve to be passed down to posterity at all?

Even if you are lucky enough to stumble upon an unusually witty group of café denizens, it’s highly unlikely that you would be able to get the result past Millicent, either as dialogue or as narrative. In professional writing, merely sounding real is not enough; a manuscript must also be entertaining enough to hold a reader’s interest.

Yes, Virginia, even if the manuscript in question happens to be literary fiction, if it’s book-length. Most of what goes on in the real world, and nearly everything that’s said, doesn’t rise to the standards of literature.

Not of good literature, anyway. And that’s as it should be, as far as I’m concerned.

There’s more to being a writer than having adequate transcription skills, after all; merely reproducing the real isn’t particularly ambitious, artistically speaking. Think about it: wouldn’t you rather apply your unique worldview and scintillating ability with words to create something better than reality?

In that spirit, let’s revisit that sentence structure beloved of the real-life speaker, X happened and Y happened and see if we can’t improve upon it. Why, here’s an example of it wandering by now.

Ghislaine blanched and placed her lily-white hand upon her swiftly-beating heart. Roland nodded with satisfaction and strode toward her, grinning. She grabbed a poker from next to the fire and glanced around for an escape. He chortled villainously and continued to move closer.

Did it bug you that time? Each of these sentences is in fact grammatically correct, and this structure reads as though it is merely echoing common spoken English. It’s also pretty much the least interesting way to present the two acts in each sentence: the and is, after all, simply replacing the period that could logically separate each of these actions.

By contrast, take a look at how varying the sentence structure and adding the odd gerund livens things up:

Ghislaine blanched, her lily-white hand clutching her swiftly-beating heart. Roland strode toward her, grinning. She grabbed a poker from next to the fire and glanced around for an escape. He chortled villainously, moving closer every second.

Easier to read, isn’t it? Admittedly, the prose is still pretty purple — or at least a blushing lilac — but the paragraph is no longer jumping up and down, crying, “My author knows only one way to structure a sentence! Run, Millicent, run, or you’ll be driven mad by page 42!”

Good advice, bellowing paragraph, but your assessment is rather generous: most pros would be driven mad within a page, particularly if that page happens to be page 1. We tend to have a very low tolerance for over-use of this particular sentence structure. Seriously, I’ve seen pens poked through manuscripts at the third instance of this kind of sentence within half a page. Screaming has been known to ensue after the sixteenth use within the same space.

If that seems like an over-reaction, consider this: most professional readers go into the job because they like to read. Adore it. Can’t get enough of lovely prose. Lest we forget, people who work at agencies are individuals with personal preferences, rather than the set of automatons sharing a single brain that many aspiring writers presume them to be. I can guarantee, however, that they all share one characteristic: they love the language and the many ways in which it can be used.

What does that mean in practice, you ask? Millicent screens manuscripts all day at work, pulls a battered paperback out of her bag on the subway home, and reads herself to sleep at night; her boss totes submissions back and forth on that same subway because he’s so devoted to his job that he does half of his new client consideration at home. And no matter how many manuscripts they reject in a given week, both wake up each and every day hoping that today, at last, will bring an amazing manuscript into the agency, one to believe in and shepherd toward other lovers of good literature.

With such an orientation, it’s genuinely frustrating to see a great story poorly presented, or an exciting new voice dimly discernible through a Frankenstein manuscript. Or — and this happens more often than any of us might care to think — when a talented writer was apparently in such a hurry to get a scene down on paper that a series of potentially fascinating actions degenerated into a mere list that barely hints at the marvelous passage that might have been.

“But Anne,” and-huggers everywhere cry, “I just love the charge-ahead rhythm all of those ands impart to a passage! If the writing is strong enough, the story gripping enough, surely a literature-lover like Millicent would be able to put her repetition reservations aside?”

I see that it’s time to get ruthless: I’m going to have to show you just how much damage an injudicious application of ands can inflict upon even the best writing. To make the lesson sting as much as possible, let’s resurrect an example I used a week or two ago, the exceptionally beautiful and oft-cited ending of F. Scott Fitzgerald’s THE GREAT GATSBY. To refresh your memory:

And as I sat there brooding on the old, unknown world, I thought of Gatsby’s wonder when he first picked out the green light at the end of Daisy’s dock. He had come a long way to this blue lawn, and his dream must have seemed so close that he could hardly fail to grasp it. He did not know that it was already behind him, somewhere back in that vast obscurity beyond the city, where the dark fields of the republic rolled on under the night.

Gatsby believed in the green light, the orgiastic future that year by year recedes before us. It eluded us then, but that’s no matter — tomorrow we will run faster, stretch out our arms farther… And one fine morning–

So we beat on, boats against the current, borne back ceaselessly into the past.

Even before I finished typing this, I could sense hands shooting up all over the ether. “Aha, Anne! He began two sentences with and! And he used the very X happened and Y happened structure you’ve been complaining about. So I may use both with impunity, right?”

No, actually — I selected this passage precisely because he does incorporate them; he also, you will notice, uses the passive voice in one sentence. He does both sparingly, selectively.

Look at the horror that might have resulted had he been less variable in his structural choices. (I apologize in advance for this, Uncle Scott, but I’m making a vital point here.)

And I sat there brooding on the old, unknown world, and I thought of Gatsby’s wonder when he first picked out the green light at the end of Daisy’s dock. He had come a long way to this blue lawn, and his dream must have seemed so close that he could hardly fail to grasp it. He did not know that it was already behind him, and that it was somewhere back in that vast obscurity beyond the city, and it was where the dark fields of the republic rolled on under the night.

Gatsby believed in the green light, and in the orgiastic future that year by year recedes before us. And it eluded us then, but that’s no matter — tomorrow we will run faster and we will stretch out our arms farther… And one fine morning–

So we beat on, boats against the current, borne back ceaselessly into the past.

The moral: even when the writing is very good indeed, structural repetition can be distracting. (Take that, writers who believe that they’re too talented for their work ever to require revision.)

Where might one start to weed out the ands, you ask? Glance over your pages for sentences in which and appears more than once. Chances are high that such a sentence will be a run-on — or a too heavily burdened list.

Not sure that you’ll be able to spot them in the wild? Here is a classic run-on — too much information crammed into a single sentence, facilitated by those pesky conjunctions.

In avoiding the police, Babette ran down the Metro stairs and out onto the platform and into the nearest train.

And here is a description crammed into list form:

Zorro scanned the house, admiring its inventive decorative scheme. Its attractive red lintels, inviting purple door, and Robin Hood green roof demanded the attention of passers-by, while its white-and-orange checked kitchen curtains seemed to promise that pies would be cooling beneath them soon and sultry sheers wafted from the bedrooms on the second floor, offering (in the chaste realm of thought, at least) the imaginative onlooker a suggestion for what to do until the pies cooled. Not that the view from the street gave an impression of relaxation: the lawn was manicured and the hedges were clipped and shorn; even the small and compact doghouse was shipshape and freshly painted.

Interesting use of detail, but why on earth stuff so much description into so few sentences? What’s the narrator’s hurry? And is it really a good idea to preface such a hastily thrown-together image with an announcement to Millicent that what is about to be described is inventive?

She’s like to make up her own mind about that, thank you very much. But trust me, by the middle of the second sentence, she will already be asking herself, “Wasn’t there another, more interesting way the writer could have conveyed this information? If not, is are all of these details even necessary?”

Some writers, of course, elect to include run-on sentences deliberately in their work, for specific effect: to make the narrator sound less literate, for instance, or more childlike, or to emphasize the length of a list of actions the protagonist has to take to achieve a goal. Or sometimes, the point is to increase the comic value of a scene by the speed with which it is described, as in this excerpt from Stella Gibbons’ immortal comedy, COLD COMFORT FARM:

He had told Flora all about his slim, expensive mistress, Lily, who made boring scenes and took up the time and energy which he would much sooner have spent with his wife, but he had to have Lily, because in Beverly Hills, if you did not have a mistress, people thought you were rather queer, and if, on the other hand, you spent all your time with your wife, and were quite firm about it, and said that you liked your wife, and, anyway, why the hell shouldn’t you, the papers came out with repulsive articles headed “Hollywood Czar’s Domestic Bliss,” and you had to supply them with pictures of your wife pouring your morning chocolate and watering the ferns.

So there was no way out of it, Mr. Neck said.

Quite the sentence, eh? (Not the second, silly — the first.) I’m going to part company with pretty much every other editor in the world for a moment and say that I think that a writer can get away with this sort of run-on every once in a while, under three very strict conditions:

(1) if — and only if — it serves a very specific narrative purpose that could not be achieved in any other manner (in this example, to convey the impression that Mr. Neck is in the habit of launching into such diatribes on intimate topics with relative strangers at the drop of the proverbial hat),

(2) if — and only if — it achieves that purpose entirely successfully (not a foregone conclusion, by any means), and

(3) if — and only if — the writer chooses to do this at a crucial point in the manuscript, s/he doesn’t use it elsewhere, or at least reserves the repetition of this choice for those few instances where it will have the greatest effect.

Why minimize it elsewhere? As we saw in that last example, this device tends to create run-on sentences with and…and…and constructions, technical no-nos. You may be doing it deliberately, but as with any grammatical rule, many writers who do not share your acumen with language include them accidentally.

Why might that prove problematic at submission time? Well, Let me ask you this: how is a speed-reading Millicent to tell the difference between a literate submitter pushing a grammatical boundary on purpose and some under-read yahoo who simply doesn’t know that run-ons are incorrect?

Usually, by noticing whether the device appears only infrequently, which implies deliberate use, or every few lines, which implies an ingrained writing habit. Drawing either conclusion would require our Millie to read a significant chunk of the text.

Obviously, that would take quite a bit more time than shouting, “Next!”

I’ve been sensing disgruntled rumblings out there since point #3. “But Anne, I read a great deal, and I see published literary fiction authors break this rule all the time. Doesn’t that mean that the language has changed, and people like you who go on and on about the rules of grammar are just fuddy-duddies who will be first up against the wall come the literary revolution?”

Whoa there, rumblers — as I believe I may have pointed out before, I invented neither the rules of grammar nor the norms of submission evaluation. If I had, every agency and publishing house would post a clear, well-explained list of standard format expectations on its website, along with explanations of any personal reading preferences and pet peeves its staff might happen to be cherishing. Millicent would be a well-paid, under-worked reader who could spend all the time she wanted with any given submission in order to give it a full and thoughtful perusal; the agent for whom she works would be able to afford to take on a difficult-to-market book project every month or so, just because he happens to like the writing, and the government would issue delightful little checks to compensate writers for all of the time they must now spend marketing their own work.

As simple observation will tell you that these matters are not under my personal control, kindly take me off your literary hit lists. Thank you.

No, but seriously, folks, even in literary fiction, it’s dangerous to include grammatically incorrect sentences in a submission — to someone who hasn’t read more of your work than the first few pages of your manuscript, it’s impossible to tell whether you are breaking the normal rules of grammar in order to create a specific effect, or because you just don’t know the rule. If an agency screener concludes that it’s the latter, she’s going to reject the manuscript, almost invariably.

Then, too, the X happened and Y happened structure is just not considered very literary in the business. So the automatic assumption if it shows up too much is that the material covered by it is to be read for content, rather than beauty of prose.

To quote Millicent’s real-life dialogue: “Next!”

Unless you are getting an extremely valuable effect out of a foray into the ungrammatical — and an effect that would impress Millicent with its efficacy at first glance — it’s best to save them for when it serves you best. At the very least, make sure that two such sentences NEVER appear back-to-back.

Why? To avoid that passage appearing to Millicent as the work of — horrors! — a habitual runner-on or — sacre bleu! — someone who does not know the rules of grammar. Or even — avert your eyes, children — as the rushed first draft of a writer who has become bored by what’s going on in the scene and just wants to get that darned set of actions or description onto the page as quickly as humanly possible.

Oh, that diagnosis didn’t occur to you in the midst of that description of the house? Millicent would have thought of it by the second and.

None of these may be a fair assessment of any given sentence in your manuscript, of course. But when you do find patches of ands in your text, step back and ask yourself honestly: “Do I really NEED to tell the reader this so tersely — or all within a single sentence? Or, indeed, at all?”

“Perhaps,” (you’re still speaking to yourself here, in case you were wondering) “I could find a way that I could make the telling more intriguing or unusual by adding more detail? I notice by reading back over the relevant paragraphs that my X happened and Y happened sentences tend to be light on specifics.”

My, you’re starting to think like an editor, reader. A Frankenstein manuscript just isn’t safe anymore when you’re in the room. But would you mind not wielding that ice pick so close to the computer screen?

Since your eye is becoming so sophisticated, take another look at paragraphs where ands abound and consider the opposite possibility: do all of those ands indicate that the narrative is rushing through the action of the scene too quickly for the reader to enjoy it? Are some of those overloaded sentences cramming four or five genuinely exciting actions together — and don’t some of these actions deserve their own sentences?

Or, to put it a bit more bluntly, is the repeated use of and in fact your manuscript’s way of saying COME BACK AND FLESH THIS OUT LATER?

You thought you were the only one who did this, didn’t you? Almost every writer has resorted to this device at the end of a long writing day. Or when we have a necessary-but-dull piece of business that we want to gloss over in a hurry. When the point is just to get lines down on a page — or to get a storyline down before the inspiration fades — X happened and Y happened and Z happened is arguably the speediest way to do it. It’s a perfectly acceptable time-saving strategy for a first draft — as long as you remember to go back later and vary the sentence structure.

Oh, and to make sure that you’re showing in that passage, not telling. Millicent has an ice pick, too.

When time-strapped writers forget to rework these flash-written paragraphs, the results may be a bit grim. Relying heavily on the and construction tends to flatten the highs and lows of a story. When actions come across as parts of a list, rather than as a sequence in which all the parts are important, the reader tends to gloss over them quickly, under the mistaken impression that these events are being presented in list form because they are necessary to the plot, but none is interesting enough to sustain an entire sentence.

Which, I’m guessing, is not precisely the response you want your sentences to evoke from Millicent, right?

Does revising for this tendency require an impeccable attention to detail? You bet it does. But honestly, isn’t there more to your literary voice than a sense of consecutive speech? Doesn’t that inventively-decorated house in your mind deserve a full description? And isn’t there more to constructing a powerful scene than simply getting it on the page before you have to run out the door to work?

Doesn’t, in short, your writing deserve this level of scrutiny? Keep up the good work!

Pet Peeves on Parade, part XXVIII and Structural Repetition, part V: wait — there’s a forest out there? How can I possibly be expected to see it through all of these trees?

The other day, an author who had established her literary credentials some decades ago — let’s call her Martha, because it’s nothing like her name — came over to my house for tea and a vigorous discussion of the ever-changing literary market. I love chatting with well-read, highly opinionated people on this particular subject, and Martha did not disappoint. She is, to put it mildly, no fan of what she calls “the recent vampire/werewolf/zombie craze,” nor does she entirely improve of this golden age of YA.

“I keep meeting wonderful writers,” she says, “who have just given up on writing for adults. Or about anyone with a pulse.”

I do, too, but actually, I find this view a trifle outdated: when I walk into, say, a Barnes & Noble today, what strikes me is not the size of the YA section (I think the expansion of this particular book category has yielded some great things) or how few novel protagonists boast pulses (for me, a little contact with the undead goes a long way), but what a high percentage of the books currently available for sale were written by those who no longer have pulses at all. I’m as fond of Mark Twain, Edgar Allen Poe, and Mary Wollstonecraft Shelley as the next person, but do they really need to take up half the summer reading table AND an entire shelf of the sale books? Might an enterprising publisher not shell out for some display space for a few more living authors?

And while we’re at it, is there a particular reason that so many bookstores stock only FRANKENSTEIN, but not any of Shelley’s other novels? Again, I’m as fond of, etc., etc., but the lady was prolific. For my money, VALPURGA, her fictional account of the Inquisition, dances circles around FRANKENSTEIN. But perhaps that’s merely another manifestation of my preference for living protagonists, rather than revivified ones.

As so often happens, I ended up defending publishing trends I do not necessarily applaud, simply because Martha seemed so very determined to ring the death knell for the industry — because, she said, “All publishers think about now is cash.”

That’s a very popular complaint amongst those who landed their agents back when it was considered a trifle gauche for writers to admit that they wanted to make a living at it. My kith and kin has been involved in producing books since the 1920s, and I can’t say that I’ve ever heard of a time when publishing was purely a charitable enterprise. It is true, however, that both agents and publishers routinely used to nurse promising authors through half a dozen books, despite anemic sales, in the hope that someday, he (and it was almost always he) would gain a larger audience. Now, if a new author’s book does not sell well, she (and it often is she these days) and her agent may well have trouble convincing even an editor absolutely besotted with her prose stylings to take a chance with her next.

Hey, the bookstore needs that shelf space for its fifth copy of FRANKENSTEIN.

To be fair, though, readers also have quite different expectations than they did when Shelley’s debut novel hit the shelves — or, for that matter, when Martha’s did. Pacing is considerably faster these days; the passive voice so popular prior to World War II is considered stylistically rather weak, and in deference to that type of browser who habitually grabs books off the shelves and reads page 1 before purchasing, action tends to appear much earlier in plots than in years past.

Yes, even in literary fiction — do some comparative reading. Martha didn’t want to believe it, either.

Because I am, as you may have noticed, a big fan of concrete examples, I reached over to my fiction bookshelves for an example of good, solid literary writing that might have trouble getting published, or even landing an agent, today. I didn’t have to run my fingertips past more than half a dozen spines before I found a great page 1: William Styron’s breakthrough 1951 novel, LIE DOWN IN DARKNESS.

I would urge all of you to read this lyrical, moving book in its entirety (after you polish off VALPURGA, perhaps). For our purposes, though, I’m going to show you only what I read to Martha. Try to absorb it on two levels: for the quality of the writing, and as our old pal, Millicent the agency screener, might respond to it if it landed on her desk as a submission from an unknown writer today. To aid in that imaginative feat, I’ll even show it to you as she would see it.

“Wow, he was a wonderful writer,” Martha said. “Why did you stop there?”

“Because,” I said, bracing myself for the inevitable outcry of the literary-minded, “an agency screener wouldn’t have read any farther.”

Any guesses why? How about that paragraph-long, 118-word opening sentence? Or the two subordinate clauses beginning with which and the one with where? Or the piling-up of prepositions? Or the abrupt shift from the third person to the second on line 6?

None of this, of course, mars the inherent loveliness of the writing; hearing it read out loud, Martha was quite right to be impressed. As seen on the submission page, though, how likely to you think Millicent is to exclaim, as my guest did, “Wow, this is a wonderful writer,” rather than “Wow, that’s quite a run-on sentence?” And having emitted the second, how likely is she not to follow it with, “Next!”

Darned right, that would be a pity; this is a beautifully-written, incisive novel. But Millicent is in fact justified in believing that a browser picking up this page 1 is likely to set the book back on the shelf again halfway through that gargantuan opening sentence.

What would make her so sure of that? Because the difference between the literary market of 1951 and the literary market of 2011 lies not merely in how quickly professional readers make up their minds about submissions, but also in non-professional readers’ expectations for what constitutes good writing.

I know, I know. After I made that argument to Martha, she kept feeling my head to see if I had developed a fever.

Why might a browser not be able to see past the length of that opening sentence? Memory, partially: the browser’s high school English teacher would have marked her down for producing a run-on of this magnitude. Besides, subordinate clauses are simply not as highly regarded as they used to be. Back in the day, literature was rife with these; now, most Millicents are trained to consider them, well, a bit awkward. In fact, chances are very good that she was specifically trained to zero in on relative pronouns like which and subordinate conjunctions like where with the intent of ferreting out run-ons.

That, I suspect, is going to come as surprise to those of you who love 19th-century novels. We could quibble for hours about whether literary tastes have changed for better or worse. Since they have undoubtedly changed, though, it’s vital for aspiring writers who prefer more old-fashioned structures to realize that what was hailed by critics in 1951 might well give Millicent pause on page 1 today.

Or even give her an excuse to stop reading. But that does not necessarily mean that if the late lamented Mssr. Styron were trying to break into the literary fiction market today, I would advise him to lose all of the subordinate clauses.

Oh, I would certainly recommend some tinkering; that semicolon, for instance, could be replaced by a period at no great loss to the passage. Because the writing is so pretty here, however, I’m reluctant to impose the necessary cuts and changes on this passage, even for the purposes of an instructive example. As an editor, all I can justifiably do is point out the problems; it’s the writer’s job to rewrite.

That, too, often comes as a surprise to those harboring old-fashioned views of publishing. I meet aspiring writers all the time who greet any and all revision suggestions with an airy and dismissive, “Oh, I’m sure the acquiring editor/the agent of my dreams/some luckless proofreader will take care of that. All that matters at the submission stage is the quality of the writing.”

To a professional reader, sentence-level difficulties are not external to the writing; they’re integral parts of it. How a writer revises — or doesn’t — is as important to the ultimate quality of the book as the initial composition. Contrary to popular belief, though, there is no such thing as a single best way to revise a narrative, any more than there is a single best way to tell a story.

That being the case, how could an editor justifiably perform all necessary revisions to a manuscript? Or an agent, for that matter? And why wouldn’t a savvy writer prefer to make those changes herself, so she can control the voice?

Part of the charm of individual authorial voice is that it is, in fact, individual — but you’d never glean that from how writers (and writing teachers) tend to talk about revision. All too often, we speak amongst ourselves as though the revision process involved no more than either (a) identifying and removing all of the objectively-observable mistakes in a manuscript, or (b) changing our minds about some specific plot point or matter of characterization, then implementing it throughout the manuscript.

These are two perfectly reasonable self-editing goals, of course, but they are not the only conceivable ones. When dealing with what I call, with apologies to Madame Shelley, a Frankenstein manuscript — a text that, while perhaps prettily written, has not yet been revised to the level of professional polish — a conscientious self-editor might well perform a read-through for voice consistency, another for grammatical problems, a third for logic leaps, a fourth because the protagonist’s husband is no longer a plumber but the member of Congress representing Washington’s 7th District…

And so forth. Revision can come in many, many flavors, variable by specificity, level of focus, the type of feedback to which the writer is responding, and even the point in publication history at which the manuscript is being revised.

Does that all sound dandy in theory, but perplexing in practice? Don’t worry; I am queen of the concrete example, remember?

To help you gain a solid sense of how diverse different of levels of revision can be, I’m going to treat you to a page from one of my favorite fluffy novels of yore, Noël Coward’s POMP AND CIRCUMSTANCE, a lighthearted romp set in a tropical British colony on the eve of a royal visit.

I chose this piece not merely because it retains a surprisingly high level of Frankenstein manuscript characteristics for a work by a well-established writer (possibly because it was Coward’s only published novel), or even because it deserves another generation of readers. (As it does; his comic timing is unparalleled.) I think it’s an interesting study in how literary conventions change: even at the time of its release in 1960, some critics considered it a bit outdated. Coward’s heyday had been several decades before, they argued, so the type of sex comedy that used to shock in the 1920s was a bit passé, and wasn’t it a bit late in the literary day to steer so firmly away from sociopolitical commentary?

Now, sociopolitical commentary has largely fallen out of style, at least in first novels, and sex, as Coward himself was fond of observing, seems to be here to stay. Here is a page from the end of the book, where our narrator, a harried British matron living on a South Sea island, finds herself entertaining Droopy, the husband of her best friend Bunny’s would-be mistress.

P&C sample

Amusing, certainly, but a bit Frankensteinish on the page is it not? At first glance, how would you suggest Noël revise it? Would your revision goals be different if this were page 5, rather than page 272?

Before you give your final answers, here’s that page again, after it has been subjected to just the kind of repetition-spotting mark-up I’ve been asking you to perform of late. (Sorry about the dark image; I honestly didn’t take the photograph in a particularly gloomy room. If you’re having trouble reading the specifics, try pressing command +.)

P&C edit 1

Replete with structural redundancy, is it not? By today’s book publication standards, as Millicent would no doubt be overjoyed to tell you, it would deserve instant rejection on that basis alone.

But would you agree? Or is the very repetition an inherent part of this comic voice?

Arguments could be made in both directions, you know. After all, this narrative voice is not all too far from the kind of writing we all see every day online, or even in the chattier varieties of journalism. We can all see why some writers would favor this kind of voice, right? Read out loud, this kind of first-person narration can sound very natural, akin to actual speech.

That’s not to say, though, that Millicent would not cringe at the very sight of it in a novel submission. And why? Feel free to chant it with me: the level of repetition that works in everyday speech is often hard to take on the printed page.

As you can see for yourself in the example above, I suspect. Now that you see all of those ands and other word repetition marked on the page, you must admit that they are mighty distracting to the eye. By repeating the same sentence structures over and over, our buddy Noël is practically begging Millicent to skip lines while skimming.

Nor is all of the redundancy here literal; there’s a certain amount of conceptual repetition as well. Take note of all of those visually-based verbs: not only do people look a great deal, but our heroine envisages AND tries to imagine how she might appear in his eyes.

And did you catch the over-use of subordinate clauses, all of those whiches in yellow? While a tolerant Millie might be inclined to glide past one every ten or fifteen pages, even a screener noted for her restraint would begin to get restless with a quarter as many as appear on that single page above.

That almost certainly would not have been a major objection raised by Millicent’s forebears in 1960, though, right? The literary gatekeepers would have concentrated on quite different parts of this page — the grammatically-necessary missing commas, for instance, and the back-to-back prepositions.

Longing to see how Millicent’s grandmother would have commented on this page? Well, you’re in luck; I just happen to have her feedback handy.

P&Eedit2

Let’s linger a moment in order to consider Grandma M’s primary quibbles. First, as she points out so politely in red at the top of the page, it takes at least two sentences to form a narrative paragraph. In dialogue, a single-line paragraph is acceptable, but in standard narrative prose, it is technically incorrect.

Was that gigantic clunk I just heard the sound of jaws belonging to anyone who has picked up a newspaper or magazine within the last decade hitting the floor?

In theory, Grandma M is quite right on this point — and more of her present-day descendants would side with her than you might suppose. Millie’s grandmother did not bring her up to regard setting grammar at naught lightly, after all. But does that necessarily mean it would be a good idea for you to sit down today and excise every single-sentence narrative paragraph in your manuscript?

Perhaps not: the convention of occasionally inserting a single-line paragraph for emphasis has become quite accepted in nonfiction. The practice has crept deeply enough into most stripes of genre fiction that it probably would not raise Millicent’s eyebrows much.

How can you tell if the convention is safe to use in your submission? As always, the best way of assessing the acceptability of a non-standard sentence structure in a particular book category is to become conversant with what’s been published in that category within the last few years. Not just what the leading lights of the field have been writing lately, mind you; what an established author can get away with doing to a sentence is not always acceptable in a submission by someone trying to break into the field.

Pay attention to what kinds of sentences first-time authors of your kind of book are writing these days, and you needn’t fear going too far afield. As a general rule of thumb, even first-time novelists can usually get the occasional use of the single-sentence paragraph device past Millicent — provided that the content of the sentence in question is sufficiently startling to justify standing alone. As in:

The sky was perfectly clear as I walked home from school that day, the kind of vivid blue first-graders choose from the crayon box as a background for a smiling yellow sun. The philosopher Hegel would have loved it: the external world mirroring the clean, happy order of my well-regulated mind.

That is, until I tripped over the werewolf lying prone across my doorstep.

Didn’t see that last bit coming, did you? The paragraph break emphasizes the jaggedness of the narrative leap — and, perhaps equally important from a submission perspective, renders the plot twist easier for a skimming eye to catch.

Grandma M would growl at this construction (“My, Granny, what big teeth you have!”), and rightly so. Why? Well, it violates the two-sentences-or-more rule, for starters. In the second place, this problem could have been avoided entirely by eschewing the RETURN key. In a slower world, one where readers lived sufficiently leisurely lives that they might be safely relied upon to glance at every sentence on a page, all of this information could have fit perfectly happily into a single paragraph. Like so:

The sky was perfectly clear as I walked home from school that day, the kind of vivid blue first-graders choose from the crayon box as a background for a smiling yellow sun. The philosopher Hegel would have loved it: the external world mirroring the clean, happy order of my well-regulated mind. That is, until I tripped over the werewolf lying prone across my doorstep.

I bring this up not only to appease Grandma M’s restless spirit, currently haunting an agency or publishing house somewhere in Manhattan, but so that those of you addicted to single-line paragraphs will know what to do with hanging sentences: tuck ‘em back into the paragraph from whence they came. Ruthlessly.

At least a few of them. Please?

Really, it’s in your submission’s best interest to use the single-line paragraph trick infrequently, reserving it for those times when it will have the most effect. That will at least give your narrative the advantage of novelty.

How so? Well, amongst aspiring writers who favor this structure, moderation is practically unheard-of. Many, if not most, novelists and memoirists who favor this device do not use the convention sparingly, nor do they reserve its use for divulging information that might legitimately come as a surprise to a reasonably intelligent reader.

As a result, Millie tends to tense up a bit at the very sight of a single-sentence paragraph — yes, even ones that are dramatically justifiable. Hard to blame her, really, considering how mundane some of the revelations she sees in submissions turn out to be. A fairly typical example:

The sky was perfectly clear as I walked home from school that day, the kind of vivid blue first-graders choose from the crayon box as a background for a smiling yellow sun. The philosopher Hegel would have loved it: the external world mirroring the clean, happy order of my well-regulated mind.

Beside the sidewalk, a daffodil bloomed.

Not exactly a stop-the-presses moment, is it?

Often, too, aspiring writers will use a single-line paragraph to highlight a punch line. This can work rather well, if it doesn’t occur very often in the text — any literary trick will lose its efficacy if it’s over-used — AND if the joke is genuinely funny. Much of the time in manuscripts, alas, it isn’t.

At least not hilarious enough to risk enraging Grandma M’s spirit by stopping the narrative short to highlight the quip. See for yourself:

The sky was perfectly clear as I walked home from school that day, the kind of vivid blue first-graders choose from the crayon box as a background for a smiling yellow sun. The philosopher Hegel would have loved it: the external world mirroring the clean, happy order of my well-regulated mind.

My Algebra II teacher would have fallen over dead with astonishment.

Gentle irony does not often a guffaw make, after all. And think about it: if the reader must be notified by a grammatically-questionable paragraph break that a particular line is meant to be funny, doesn’t that very choice indicate a certain authorial doubt that the reader will catch the joke? Or that it’s funny in the first place?

Grandma M’s other big objection to Noël’s page 272 — and this pet peeve, too, she is likely to have passed down the generations — would be to, you guessed it, the many, many run-on sentences. The run-ons here, however, are not the result of the driving rhythmic pattern or descriptive complexity that made ol’ William go overboard on his opening; clearly, Noël was just trying to sound chatty.

That should sound familiar by this point in the series, right? Like so many aspiring novelists, our Noël favors an anecdotal-style narrative voice, one that echoes the consecutiveness of everyday speech. That can work beautifully in dialogue, where part of the point is for the words captured within the quotation marks to sound like something an actual human being might really say, but in narration, this type of sentence structure gets old fast.

Why might that be, dear readers? Sing along with me now: structural repetition reads as redundant. Varying the narrative’s sentence structure will render it easier, not to mention more pleasant, to read.

Are some of you former jaw-droppers waving your arms frantically, trying to get my attention? “Okay, Anne,” these sore-jawed folk point out, “I get it: Millicents have disliked textual repetition for decades now. No need to exhume Grandma M’s grandmother to hammer home that point. But I’d had the distinct impression that Millie is a greater stickler for bigger-picture problems than her forebears. Don’t I have more important things to worry about than grammatical perfection when I’m getting ready to slide my manuscript under her nose?”

Well, grammatical perfection is always an asset in a manuscript, ex-jaw-droppers, so a completely clean manuscript is not at all an unreasonable goal for your pre-submission text scan. You are right, however, that present-day Millicents do tend to be weighing a great many more factors than their grandmothers did when deciding whether the manuscript in front of them has publication potential. But not all of those factors involve large-scale questions of marketability and audience-appropriateness; Millicent is also charged with going over the writing with the proverbial fine-toothed comb. Using, of course, today’s standards as a guide.

What kinds of manuscript problems might catch on her comb that Grandma M’s would have missed, you ask with fear and trembling? See for yourself — here’s Millie’s response on the page we’ve been examining:

P&E edit 3

I sincerely hope that your first thought upon seeing her much, much higher expectations was not to wish that you’d had the foresight to try to land an agent back in 1960, rather than now. (Although I would not blame you at all if you kicked yourself for not launching your work back in the 1980s, when the home computer was available but not yet ubiquitous, astronomically increasing the number of both queries and submissions Millicent would see in a given week.) True, the competition to land an agent is substantially fiercer now, but it’s also true that a much, much broader range of voices are getting published than in Grandma M’s time.

Back then, if you weren’t a straight, white man from a solid upper-middle class home, Granny expected you at least to have the courtesy to write like one. (Styron’s father worked in a shipyard, so he had to fudge it a little; so did his contemporary Gore Vidal, for other reasons.) If you did happen to be a SWMFaSUMCH, you were, of course, perfectly welcome to try to imagine what it was like not to be one, although on the whole, your work would probably be more happily received if you stuck to writing what you knew. And if there was a typo in your manuscript, well, next time, don’t have your wife type it for you.

You think I’m making that up, don’t you? That’s a quote, something an agent told a rather well-known writer of my acquaintance in the mid-1960s. The latter kept quiet about the fact that he was unmarried at the time and composed his books on a typewriter.

Let’s return from that rather interesting flashback, though, and concentrate upon the now. It’s not enough to recognize that literary standards — and thus professional expectations for self-editing — have changed radically over time. It’s not even sufficient to accept, although I hope it’s occurred to you, that what constituted good writing in your favorite book from 1937 — or 1951, or 1960 — might not be able to make it past Millicent today. If you’re going to use authors from the past as your role models — a practice both Grandma M and I would encourage — you owe it to your career as a writer also to familiarize yourself with the current writing in your book category.

Just for today, what I would like you to take away from these examples is that each of the editorial viewpoints would prompt quite different revisions — and in some instances, mutually contradictory ones. This is one reason the pros tend not to consider the revision process definitively ended until a book is published and sitting on a shelf: since reading can take place on many levels, so can revision.

Don’t believe me? Okay, clap on your reading glasses and peruse the three widely disparate results conscientious reviser Noël might have produced in response to each of the marked-up pages above. For the first, the one that merely noted the structural, word, and concept repetition, the changes might be as simple as this:

P&C basic edit

“Hey, Anne!” the sharper-eyed among you burble excitedly. “Despite the fact that Noël has added a couple of paragraph breaks, presumably to make it easier for the reader to differentiate between speech and thought, the text ends up being shorter. He snuck another line of text at the bottom of the page!”

Well-caught, eagle-eyed burblers. A thoughtfully-executed revision to minimize structural redundancy can often both clarify meaning and lop off extraneous text.

I hope you also noticed that while that very specifically-focused revision was quite helpful to the manuscript, it didn’t take care of some of the grammatical gaffes — or, indeed, most of the other problems that would have troubled Grandma M. Let’s take a peek at what our Noël might have done to page 272 after that august lady had applied her red pen to it. (Hint: you might want to take a magnifying glass to the punctuation.)

P&C revision 2

Quite different from the first revision, is it not? This time around, the punctuation’s impeccable, but the narration retains some of the redundancy that a modern-day Millicent might deplore.

Millie might also roll her eyes at her grandmother’s winking at instances of the passive voice and the retention of unnecessary tag lines. Indeed, for Noël to revise this page to her specifications, he’s going to have to invest quite a bit more time. Shall we see how he fared?

P&C final edit

Remember, not every close-up examination of a single tree will result in a pruning plan that will yield the same forest. A savvy self-editor will bear that in mind, rather than expecting that any single pass at revision, however sensible, will result in a manuscript that will please every reader.

By apprising yourself of the current norms in your chosen book category, you can maximize the probability that your self-editing eye will coincide with Millicent’s expectations. Keep up the good work!

Pet Peeves on Parade, part XXVII: plausibility, realism, and the wildly variable potentials of plot

I return to you an injured warrior, campers: for the past few days, my keyboard has lain idle while I have been recovering from a viciously broken fingernail. I’ve been lolling around with my left hand elevated, muttering ruefully.

Were those giant guffaws I just heard rolling about the ether an indication that some of you would not consider this a debilitating injury? I defy anyone to type successfully while a significant part of the nail bed on the pointer finger so dear to those who use the hunt-and-peck method is protected from the elements by nothing but the largest Band-Aid currently available to the medical community. Or to touch-type with any accuracy whilst said Band-Aid extends that finger to clownish lengths. Should any writer out there not care if his intended Fs are 5s and his Ps plus signs, I have yet to meet him.

In the course of all of that enforced lolling, however, I had leisure to contemplate once again the burning issue of plausibility on the page. Now that I’m back, I’m going to fling it into your consciousness, too: honestly, if you encountered the story above on page 57 of a novel, would it seem remotely realistic to you?

To a reader either unfamiliar with the torrid history of my long, accident-prone nails or happily inexperienced in having their own nails violently bent back, I’m guessing it would not. I’m also guessing that would come as a surprise to some of you, because as anyone who reads manuscripts for a living can tell you, the single most common response to an editorial, “Wow, that doesn’t seem particularly plausible,” is an anguished writer’s cry of, “But it really happened!”

I can tell you now that to a pro like Millicent the agency screener, this argument will be completely unconvincing — and not merely because she has, if she’s been at it a while, heard it applied to scenes ranging from cleverly survived grizzly bear maulings to life-threatening hangnail removals to couples who actually split the domestic chores fifty-fifty, rather than just claiming that they do. (Oh, like I was going to do laundry with a bent-back fingernail.) Any guesses why that cri de coeur about the inherently not-very-believable nature of reality will leave her cold?

Long-time readers, chant it with me now: just because something has occurred in real life does not necessarily mean it will be plausible written as fiction. Nor does the fact that a human being might actually have uttered a particular phrase render it automatically effective dialogue. For that reason, it’s the writer’s responsibility not simply to provide snapshots and transcripts of real life on the page, but to write about it in such a way to make it seem plausible to the reader.

Let’s face it, plenty of real-life shenanigans are completely absurd; plenty of what tumbles out of people’s mouths is at least equally so. The world as we know it does not labor under the novelist’s imperative to render actions dramatically satisfying, or even interesting. None of us is empowered to walk up to someone who does something astonishing and say, “Hey, that’s completely out of character for you. Editing! Cut what this man just did.” (Although, admittedly, it would be an interesting approach to winning friends and influencing people.) And don’t even get me started about how a good editor could improve the dialogue all of us overhear in the movie ticket line, at the grocery store, or at your garden-variety garden party.

Besides, as a novelist, isn’t your job to improve upon reality? Isn’t it, in fact, your art and your pleasure to take the real and dress it up in pretty language, garnishing it with trenchant insights?

So you can’t really blame Millicent and her cronies for preferring fiction writing to have more to recommend it than its resemblance to something that might have happened on this terrestrial sphere. I suspect all of us who love good writing harbor a similar preference.

But I ask you as a reader: would you have felt differently if the tale at the opening of this post had turned up on page 143 of a memoir?

Most readers would; based on a true story is not ubiquitous in book and movie marketing simply because folks in those industries happen to like the sound of the phrase, after all. It’s human nature to like to be in the know.

That does not mean, however, that any truthful memoir — which, as the series of scandals that have rocked the publishing world in recent years have made all of us aware, are not necessarily synonymous terms — is automatically and inherently plausible. Yes, the reader picks up a memoir with the expectation that it will provide a fact-based portrayal of reality, but once again, it’s not just the accuracy of the facts that makes them seem true-to-life on the page.

What might the decisive factor be, campers? Could it be how the writer conveys those facts on the page?

As the pros like to say, it all depends on the writing. Just as many a ho-hum real-life event has been punched up by a gifted prose stylist into an unforgettable scene on the page, many an inherently fascinating occurrence has been rendered downright turgid by a dull telling.

Don’t believe me? Okay, try this little experiment: the next time you find yourself at a gathering that contains both interesting and uninteresting people, pick a few of each at random. Ask these people to describe their first really vivid memories — or, if you have ears of iron, their first memories of how their parents responded to a major public event like men walking on the moon, the shooting of President Reagan and James Brady, or a celebrity couple’s breaking up. (Hey, one person’s intriguing public event is another person’s snoozefest.) Listen attentively to each account without interrupting.

Then ask yourself afterward: “Did all of those stories seem equally true?”

If it’s not apparent to you a few sentences into the first poorly-told account why the storyteller’s skill makes all the difference to the audience’s perception of the story, well, I shall be very surprised. What might be less apparent — and thus require more careful listening to detect — is that you’re probably going to care less whether what the speaker is saying is true if she happens to tell the tale well.

And that, my friends, sums up the private reactions of many, many denizens of the publishing world in the wake of the A MILLION LITTLE PIECES scandal. For months afterward, while people in the outside world were asking, “But is this accurate?”, folks who dealt with books for a living — and, I suspect, most habitual readers of memoir — kept saying, “But was it well-written?”

Frankly, for a memoir to work, it needs to be both. Unless the memoirist in question is already a celebrity — in which case he’s probably not going to be the sole writer, anyway — a simple recital of the facts, however titillating they may be in and of themselves, will not necessarily grab Millicent. Nor will a beautifully-told collection of purely imaginary events fly in the memoir market.

You know where gorgeous writing that doesn’t confine itself rigidly to what actually happens in the real world works really well, though? In a novel. Provided, of course, that the writer presents those fictional — or fictionalized — events in such a manner that they are both a pleasure to read and seem plausible within the context of the world of the book.

Do I spot some timidly-raised hands out there? “But Anne,” those of you who specifically do not write about the real point out shyly, “I don’t think this applies to my work. I create storylines out of whole cloth, creating plots where vampires roam freely, werewolves earn master’s degrees, and denizens of other planets lecture in political science departments. Of course, my stories aren’t plausible; that’s part of their point.”

Actually, to work on the page, any storyline needs to be plausible. That is, the narrative must be sufficiently self-conscious about its own premise that any reader who has accepted its underlying logic that everything in the story could have happened that way.

You would be amazed at how often paranormal, science fiction, and fantasy manuscripts do not adhere to this basic precept of storytelling. Implausible fantasies are perennially among Millicent’s pet peeves.

That got a few goats, did it not? “What part of fantasy don’t you understand, Millie?” I hear some of you mutter under your respective breaths. “It’s not intended to be realistic.”

No, but it does need to be plausible — which is not necessarily synonymous with realism. In fact, in a completely fantastic story, remaining plausible might actually require being anti-realistic.

How so? Well, for the reader to be carried along with a story, its internal logic must make sense, right? A narrative that deliberately eschews the laws of physics of our world can’t just ignore physical properties and motion altogether; the writer must come up with a new set of rules governing the world of the story. The less like the real world that fantasy world is, the more vital to the reader’s willing suspension of disbelief maintaining the reader’s sense of plausibility is.

That means, in effect, that while a fantastic plot allows the writer to play with reality, in order to be plausible, the narrative must be respectful of the fictional reality. So when, say, the three-toed sloth protagonist first sets a digit upon the Planet Targ, a place the reader was informed 138 pages ago was exempt from both gravity and dirt, and ol’ Three-Toe leaves a footprint, that’s going to jar a reader who has been paying attention. And the negative effects of even minor inconsistencies can pile up awfully fast: when T-T appears with his designer jeans covered in mud thirty pages after the footprint faux pas, the reader is obviously going to be less accepting than the first time the writer broke the rules.

What is the cumulative effect likely to be? For a lay reader, being knocked out of the story altogether. To a professional reader, however, the results are usually more dire — and are likely to be triggered by the first plausibility lapse, not the third or fourth.

“Oh, no,” Millicent sighs over The Saga of the Sloth. “This writer has set up a really interesting set of rules for this world, and now she’s violated one of them. That’s too bad; I was buying the premise here, and now I have to question it. Next!”

From Millicent’s perspective, the inconsistent detail about the footprint, while not necessarily a rejection-worthy problem in itself, represented a symptom of a plot-level plausibility issue, one that she does not necessarily feel compelled to read on to see confirmed thirty pages later in the muddy jeans. It was the writer’s job to make Three-Toe’s trip to Targ believable within the context of the book’s logic, after all. Since the narrative has already demonstrated a lax approach toward internal plausibility, an experienced Millie would expect to see more lapses later on in the manuscript.

And most of the time, she would be quite right about that. If you really want to set your fantastic world apart from 99% of the others she sees, make its attributes perfectly consistent.

That should be a piece of cake, right?

I’m kidding, of course; editing one’s own work for consistency is one of the most difficult self-editing tasks there is. That’s true, incidentally, no matter where your story might fall on the fantastic-realistic scale. In fact, proofing a hyper-realistic text can be even more challenging than a completely fictional one: even if it’s vitally important to the story that the broom is always kept behind the china cabinet, not the ottoman, the very mundanity of the detail may render it harder to keep in mind.

But you don’t want your heroine to expend her last gasp of breath futilely flailing behind the wrong piece of furniture, would you?

Naturally, from the reader’s perspective, the less predictable a detail is, the more memorable it is likely to be. Case in point: what kind of animal is visiting the Planet Targ? Would you have been able to answer so quickly if the story had just been about some guy named Bart?

Does that gasp of frustration mean that those of you who write reality-based fiction and memoir are already familiar with the problem of how to make the real memorable while still maintaining a sense of realism? Let’s face it: most of real-life details are likely to be on the unmemorable side. While a fantasy writer has the option — nay, the responsibility — to transform that perfectly ordinary mailbox on the corner into a flying monkey that happens to deliver mail for a living, a writer painting a picture against a backdrop of this world can’t.

(At least not until I have finished organizing my secret Chimps-on-Wings postal service. Mum’s the word until I put the finishing touches on that promising enterprise.)

But details need not strain the credulity in order to capture the reader’s imagination. Allow me to tell you a little story to illustrate — or, rather a series of little stories. But first, let me prime the creative pump by showing you a couple of literal illustrations.

fortune side onefortune side two

These are the two sides of the single fortune I found tucked into an end-of-the-meal cookie last year, right around census time: a tactfully-phrased prediction of my future happiness — by mail, no less! — accompanied by a terse statement about my general standing in the world. Now, had I been a less secure person, I might have taken umbrage at my dessert’s presuming to judge whether I counted or not, but since I had already sent back my census form, I found the symmetry very pleasing: clearly, Somebody Up There (or at any rate, Somebody Working in a Cookie Factory) was planning to reward the civic virtue of my outgoing mail with something fabulous in my incoming mail.

Imagine how dismayed I would have been, though, had I not yet popped my census form into the mail — or, even worse, if I had not yet received my census form. As I rearranged vegetables and yogurt containers in preparation for fitting my leftover asparagus in black bean sauce and Hunan pork into my overstuffed refrigerator, I would have kept wondering: is the census form the mail I’m supposed to find so darned pleasant? I mean, I understand the Constitutional obligation to be counted every ten years, but who is this fortune cookie to order me to enjoy filling it out?”

Admittedly, in a real-life fortune cookie-consumption situation, this might have been a bit of an overreaction. (Although what’s next, I wonder? Miranda warnings printed on Mars bars, for easy distribution at crime scenes? The First Amendment immortalized in marzipan, lest bakery patrons temporarily forget about their right to freedom of assembly whilst purchasing fresh macaroons?) Had the protagonist in a novel or memoir stumbled upon this chatty piece of paper, however — and less probable things turn up on the manuscript page all the time — it would have seemed pretty significant, wouldn’t it?

Any thoughts on why that might be the case? Could it be that this bizarre means of communication is one of those vivid details I keep urging all of you to work into the opening pages of your manuscripts, as well as the descriptive paragraph in your queries, synopses, verbal pitches, and contest entries? Could the paragraphs above be crammed with the kind of fresh, unexpected little tidbits intended to make Millicent suddenly sit bolt upright, exclaiming, “My word — I’ve never seen anything like that before,” at the top of her lungs?

Or, to put it in terms the whole English class can understand, in choosing to incorporate that wacky fortune cookie into the narrative, am I showing, rather than telling, something about the situation and character?

How can a savvy self-editing writer tell whether a detail is vivid or unusual enough to be memorable? Here’s a pretty reliable test: if the same anecdote were told without that particular detail, or with it described in (ugh) general terms, would the story would be inherently less interesting?

Don’t believe that so simple a change could have such a dramatic subjective effect? Okay, let me tell that story again with the telling details minimized. To make it a fair test, I’m going to keep the subject matter of the fortunes the same. Because I always like to show you examples of correctly-formatted manuscript pages, however, this time, I’m going to present it to you as a screening Millicent might see it. As always, if you’re having trouble reading the individual words, try enlarging the image by holding down the COMMAND key and pressing +.

It’s not as funny, is it, or as interesting? I haven’t made very deep cuts here — mostly, I’ve trimmed the adjectives — and the voice is still essentially the same. But I ask you: is the story as memorable without those telling details? I think not.

Some of you are still not convinced, I can tell. Okay, let’s take a more radical approach to cutting text, something more like what most aspiring writers do to the descriptive paragraphs in their query letters, the story overviews in their verbal pitches, and/or the entirety of their synopses, to make them fit within the required quite short parameters. Take a peek at the same tale, told in the generic terms that writers adopt in the interests of brevity:

Not nearly as much of a grabber as the original version, is it? Or the second, for that matter. No one could dispute that it’s a shorter version of the same story, but notice how in this rendition, the narrator seems to assume that the reader will spontaneously picture the incident so clearly that no details are necessary. Apparently, it’s the reader’s job to fill in the details, not the writer’s.

Except it isn’t. As far as Millicent is concerned, it’s the writer’s responsibility to tell the story in a way that provokes the intended reaction in the reader, not the reader’s to guess what the writer meant. Or to figure out what details might fit plausibly into the scene.

I hate to be the one to break it to you, but professional reading is seldom anywhere near as charitable as the average submitter or contest entrant hopes it will be. Blame it on the intensity of competition created by literally millions of aspiring writers seeking to get published: Millicent knows that if the well-written submission in front of her does not provide her with the reading experience her boss the agent believes will sell right now, chances are good that one of the next thousand submissions will.

According to her, then, it’s your job to draw her into your story so completely that she forgets about all of that. It’s your job to wow her with your storytelling — and without relying upon her sense that you might be writing about something that really happened to supply the plausibility strong, tangible details would provide.

So it honestly is in your best interest to assume that the reader is only going to picture the details you actually provide on the page. Since you cannot be sure that every reader will fill in the specifics you want, make darned sure that what you want the reader to take from the scene is not left to his imagination. If the detail is important, take the page space to include it.

This is particularly good advice if you happen either to be writing memoir or a novel with scenes based upon your personal experience. All too often, reality-based narrators rely upon the fact that something really happened to render it interesting to a reader, regardless of how skillfully that story may be told. All that’s really necessary is a clear telling, right? Or that the kind of terse narrative that works so well in a verbal anecdote will inspire the same reaction if reproduced verbatim on the page?

How well does either of these extremely common theories work out in practice? Well, let me ask you: did you prefer the first version of the fortune cookie story, the second, or the third? More importantly for submission purposes, which do you think would grab Millicent the most as the opening of a manuscript?

Uh-huh. The difference between those three renditions was not the voice (although a case could be made that part of the voice of the first was created through the selection of the details) or even the writing quality (although the last version did get a mite word-repetitive), but the narrative’s willingness to include telling details — and unusual ones at that.

What if the entertainment differential between the three lay not in an authorial failure of imagination in composing the last version, but in a failure to recognize that the point of including this anecdote is presumably to entertain and inform the reader? In telling the story as quickly as possible, can a writer sometimes defeat the purpose of including it at all?

“But Anne!” memoirists and reality-based novelists protest nervously. “When I’m writing about the real, I can’t just make up pithy little details to enliven the narrative, can I? I have to stick to what happened!”

True enough, anxious truth-tellers: if you are writing the real, you cannot control the facts. What you can control, however, and what any writer must control, is how you present them to the reader.

No matter what you write, the success of your narrative is going to depend largely upon your storytelling skills — they’re what separates your account of a particular incident from anybody else’s, right? Frankly, this isn’t an easy task, even if dear self doesn’t happen to be the protagonist; it’s genuinely hard to represent the real world well on the page. Let’s face it, reality is sometimes a lousy storyteller.

Oh, your life has never been trite or obvious or just plain perplexing, even for a minute? Okay, all of you English and Literature majors, tell me, please, how the following 100% true anecdote rates on the symbolism front.

A couple of years ago, I was scheduled to give a eulogy for a dead friend of mine — a writer of great promise, as the pros used to say — at our college reunion. Because several of my classmates had, unfortunately, passed away since our last get-together, eight of us were to give our eulogies at the same event. Because I am, for better of worse, known to my long-time acquaintances as a teller of jokes, I was under substantial pressure to…how shall I put this?…clean up the narrative of my late friend’s life a little. Or at least tell a version that might not offend the folks who didn’t happen to know him.

No, that’s not the symbolic part; that’s all backstory. Here’s the symbolism: my throat was annoyingly, scratchily sore for the entire week that I was editing the eulogy.

Now, if I saw a parallel that obvious in a novel I was editing, I would probably advise cutting it. “No need to hit the reader over the head with it,” I’d scrawl in the margins. “Yes, it’s showing, not telling, but please. Couldn’t you come up with something a bit more original?”

(And yes, now that you mention it, I am known for the length of my marginalia. Brevity may be the soul of wit, but explanation is often the soul of clarity.)

Now, if my life were a short story written for an English class, the voice loss in that anecdote might pass for legitimate symbolism — or even irony, in a pinch. A bit heavy-handed, true, but certainly situationally appropriate: outsiders move to silence protagonist’s voice through censorship = protagonist’s sore throat. Both New Age the-body-is-telling-you-something types and postmodern the-body-is-a-text theorists would undoubtedly be pleased.

But the fact is, in a novel or memoir, this cause-and-effect dynamic would seem forced, or even trite. Certainly, it’s unlikely to make Millicent drop her latte and exclaim, “Wow, I never saw that coming!”

As I believe I may have already mentioned, just because something happens in real life doesn’t necessarily mean that it will make convincing fiction. My sore throat is precisely the type of symbolism that comes across as ham-handed in a novel. It’s too immediate, for one thing, too quid pro quo. Dramatically, the situation should have taken time to build — over the years since my friend’s death, perhaps — so the reader could have felt clever for figuring out why the throat problem happened. Maybe even anticipated it.

How much better would it have been, in storytelling terms, if our protagonist had dealt with all the different input with aplomb, not coming down with strep throat until scant minutes before she was to speak? That way, in fine melodramatic style, she would have to croak her way through her speech, while her doctor stood by anxiously with antibiotics.

The possibilities make the writerly heart swoon, do they not?

Just think how long it would extend a funeral scene if a eulogizer were unable to speak more than a few emotion-charged words before her voice disappeared with a mouse-like squeak. Imagine the deceased’s secret admirer creeping closer and closer, to catch the muttered words.

Heck, just think of the dramatic impact of any high-stakes interpersonal battle where one of the arguers cannot speak above a whisper. Or the comic value of the persecuted protagonist’s being able to infect her tormenters with strep, so they, too, are speechless by the end of the story.

Great stuff, eh? Much, much better than protagonist feels silenced, protagonist IS silenced. That’s just so…literal.

Besides, readers like to see a complex array of factors as causes for an event, and an equally complex array of effects. Perhaps if our protagonist had been not spoken about her friend since he passed away (which, in a sense, is quite true: I was unable to make it across the country for his memorial service; that could be transformed into an interesting flashback), then she would be fictionally justified in developing speech-inhibiting throat problems now. Or if he and she had shared deep, dark secrets she had sworn never to reveal (no comment), how telling a slight sore throat might be on the eve of spilling the proverbial beans, eh?

But a single event’s sparking a severe head cold? Dramatically unsatisfying. Not to mention implausible.

Taken too far, it might even make the protagonist seem like a wimp. Readers, like moviegoers, like to see protagonists take a few hits and bounce up again. Even better is when the protagonist is beaten to a bloody pulp, but comes back to win anyway.

One of the great truisms of the American novel is don’t let your protagonist feel sorry for himself for too long — at least, not if his problems rise to the level of requiring action to fix. Simply put, most readers would rather see a protagonist at least make an attempt to solve his problems than spend 50 pages resenting them.

I can feel authors of novels and memoirs where characters sit around and think about their troubles for chapters on end blanching. Frankly, you should, at least if you intend to write for the U.S. market. Domestic agents and editors expect first-time authors’ plots to move along at a pretty good clip — and few characteristics slow a plot down like a protagonist’s tendency to mull. Especially in a first-person narrative, where by definition, the reader must stay within the worldview of the narrator.

Some of you blanching souls have your hands raised, I see. “But Anne,” these pale folks exclaim, “I’ve always heard that the real key to keeping a reader’s interest is to introduce conflict on every page. Well, most of my protagonist’s conflict is internal — she can’t make up her mind where to turn. Surely,” the pallor deepens, “a professional reader like Millicent wouldn’t dismiss this kind of thinking as whining, right?”

That’s a good question, blanchers, and one that fully deserves an answer. The short one is that it all depends on how long the equivocation goes on, how plausible the conflict is, and how repetitive the mulling ends up being. That, and whether the protagonist (or the plot, for that matter) is doing anything else whilst the wheels in her brain churn.

The long answer, of course, is that in order to formulate a really good answer to that particular question, you would need to go out and read a hefty proportion of the tomes released in your book category within the last couple of years. Not EVERY book, mind you: those by first-time authors, because the already-established have to impress fewer people to get a new book into print.

In recent years, most fiction categories have moved pretty firmly toward the action end of the continuum. As opposed to, say, virtually any novel written in English prior to 1900, most of which hugged the other, pages-of-mulling end of the continuum.

This preference isn’t limited to the literary realm, either — we often see this philosophy in movies, too. Don’t believe me? Okay, think about any domestic film with where an accident confines the protagonist to a wheelchair.

No examples springing to mind? Okay, how about if the protagonist is the victim of gratuitous discrimination, or even just simple bad luck? I’m talking about serious drawbacks here, not just everyday annoyances, of course. ( For some reason, whining about trivial problems — “But I don’t have the right shoes to wear with a mauve bridesmaid’s dress!” — seems to be tolerated better by most readers and audience members, provided that the whine-producer doesn’t bring the plot to a screeching halt until she finds those shoes.)

Got a film firmly in mind? Now tell me: doesn’t the film include one or more of the following scenes:

(a) some hale and hearty soul urging the mangled/unemployed/otherwise unhappy protagonist to stop feeling sorry for himself,

(b) a vibrantly healthy physical therapist (job counselor/spouse/friend) telling the protagonist that the REAL reason he can’t move as well as he once did is not the casts on his legs/total paralysis/missing chunks of torso/total lack of resources/loss of the love of his life, but his lousy ATTITUDE, and/or

(c) the protagonist’s lecturing someone else on his/her need to stop feeling sorry for himself and move on with his/her life?

In fact, don’t filmmakers — yes, and writers of books, too — routinely expect their characters to become better, stronger people as the result of undergoing life-shattering trauma?

Now, we all know that this is seldom true in real life, right? As someone who has spent quite a bit of time in physical therapy clinics over the last year, I’m here to tell you that pain does not automatically make people better human beings; it makes them small and scared and peevish. That sudden, crisis-evoked burst of adrenaline that enables 110-pound mothers to move Volkswagens off their trapped toddlers aside, few of us are valiantly heroic in the face of more than a minute or two of living with a heart attack or third-degree burns.

Or ten months of physical therapy. And had I mentioned that my nail had a boo-boo?

Heck, even the average head cold — with or without a concomitant voice loss — tends to make most of us pretty cranky. Yet dramatically, we as readers accept that the little irritations of life might seem like a big deal at the time, even in fiction, because these seemingly trivial incidents may be Fraught with Significance.

Which often yields the odd result, in books and movies, of protagonists who bear the loss of a limb, spouse, or job with admirable stoicism, but fly into uncontrollable spasms of self-pity at the first missed bus connection or hot dog that comes without onions WHEN I ORDERED ONIONS.

Why oh why does God let things like this happen to good people?

One of my favorite examples of this phenomenon comes in that silly American remake of the charming Japanese film, SHALL WE DANCE? After someone spills a sauce-laden foodstuff on the Jennifer Lopez character’s suede jacket, she not only sulks for two full scenes about it, but is later seen to be crying so hard over the stain that the protagonist feels constrained to offer her his handkerchief.

Meanwhile, the death of her dancing career, the loss of her life partner, and a depression so debilitating that she barely lifts her head for the first half of the movie receive only a few seconds’ worth of exposition. Why? Because dwelling on the ruin of her dreams would be wallowing; dwelling on minor annoyances is Symbolic of Deeper Feelings.

So where does that leave us on the vivid detail front — or the plausibility front, for that matter? Should we all shy away from giving our protagonists big problems, in favor of more easily-presented small ones?

Well, I’m not going to lie to you: there are plenty of writing gurus out there who would advise you to do precisely that. Edith Wharton remarked in her excellent autobiography (which details, among other things, how terribly embarrassed everybody her social circle was when she and Theodore Roosevelt achieved national recognition for their achievements, rather than for their respective standings in the NYC social register; how trying.) that the American public wants tragedies with happy endings. It still seems to be true.

So why, you may be wondering, am I about to advise you not only to depict your protagonists (fictional and real both) with many and varied problems, as well as significant, realistic barriers to achieving their goals? Have I merely gone detail-mad?

Not by a long shot. I have heard many, many agents and editors complain in recent years about too-simple protagonists with too-easily-resolved problems. In conference presentation after conference presentation, they’ve been advising that writers should give their protagonists more quirks.

It’s an excellent way to make your characters memorable, after all — and it enables the inclusion of lots and lots of luscious telling details. Give ‘em backstory. If you want to make them sympathetic, a hard childhood, dead parent, or unsympathetic boss is a great tool for encouraging empathy.

Not to mention being plausibly survivable traumas. Do you have any idea how many Americans have experienced one of those things? Or all three?

Feel free to heap your protagonist (and love interest, and villain) with knotty, real-life problems — provided, of course, that none of these hardships actually prevent the protagonist from achieving his or her ultimate goal. Interesting delay creates dramatic conflict; resignation in the face of an insuperable barrier, however, is hard to make entertaining for very long. Make sure that the protagonist fights the good fight with as much vim and resources as someone who did not have those problems — or show her coming up with clever ways to make those liabilities work for her.

Again, this is not the way we typically notice people with severe problems acting in real life, but we’re talking writing that people read for pleasure here. We’re talking drama.

We’re talking, to put it bluntly, about moving a protagonist through a story in a compelling way, and as such, as readers and viewers, we have been trained to regard the well-meaning soul who criticizes the recently-bereaved protagonist by saying, “Gee, Monique, I don’t think you’ve gotten over your mother’s death yet,” as a caring, loving friend, rather than as a callous monster incapable of reading a calendar with sufficient accuracy to note that Monique buried her beloved mother only a couple of weeks before.

While a sympathetic soul might reasonably ask, “Um, why should she have gotten over it already, if she’s not completely heartless?”, strategically, even the deepest mourning should not cause the plot to stop moving altogether.

Don’t get me wrong: I don’t think that professional readers who resent characters who linger in their grief are inherently unsympathetic human beings. They just see far, far too much wallowing on the page.

While that’s undoubtedly realistic, it doesn’t really work in a manuscript. Fictional characters who feel sorry for themselves (or who even possess the rational skills to think at length over the practical ramifications of obstacles in their paths) tend to be passive, from the reader’s point of view. They don’t do much, and while they’re not doing much, the plot grinds to a screaming halt. Yawn.

Or to express it in Millicent’s parlance: next!

Yes, people do this in real life. All the time. But I’m relatively positive that someone told you very, very recently, just because something really happened doesn’t mean it will work on the page.

My, we’ve covered a lot of ground today. I’m going to leave all of this to germinate in your fertile minds for the nonce, campers, while I turn our attention back to nit-picky issues for the next few posts. (Oh, you thought I hadn’t noticed that I’d digressed from structural repetition?) Trust me, you’ll want to have your eye well accustomed to focusing on sentence-level details before we leap back up to plot-level planning.

A good self-editor has to be able to bear all levels of the narrative in mind simultaneously, after all. This is complicated stuff, but then, so is reality, right? Keep up the good work!

Part XXVI of Pet Peeves on Parade, and part IV of Structural Repetition, and other excuses stockpile a whole lot of ands. Because you wouldn’t want to run out or anything.

Are your fingers stained with highlighter ink, campers? I hope they are: last time, I urged you to scan your submission pages — in particular, the first five, the opening chapter, or all of a contest entry — for over-use of the words and, but, and then; the average manuscript submission is positively peppered with ‘em. Since our old pal, Millicent the agency screener, sees these words so very often, I suggested that you print out these pages and highlight these words throughout, so that you might get a sense of just how often you tend to utilize them.

As I hope you have seen for yourselves, once you started marking, it was pretty darned astonishing just how often those conjunctions leapt off the page, wasn’t it? Or they would have, had you flung yourself into this nit-picky task wholeheartedly — as opposed to, say, devoting yourselves the activities of normal people.

The typical writerly reaction, though, is somewhere in between: glancing over those pages with an initially willing mind, but throwing up one’s hands in despair three buts in. “What was Anne thinking,” I sensed some of you muttering yesterday, “to advise such a time-consuming (and potentially ink-consuming) exercise? Doesn’t she realize that most of us have to fight in order to carve out time to write — and even if I happened to be one of the happy few who don’t, sunny days relatively rare in the Pacific Northwest?”

Well, in the first place, summer in Seattle is frequently beautiful; the popular belief that it rains here non-stop is a myth. In the second place, I do realize just how important your time is to you — which is precisely why I’m advising you to invest a little time now in exchange for not having scads of your time wasted later in the submission process.

Think of it this way: as those of you who have submitted to an agency or entered a contest lately are already well aware, preparing your pages and sending them off is quite time-consuming, and, if you’re like most aspiring writers, even more energy-consuming. We also all know, I hope, that the cleaner your manuscript — that’s industry-speak for pages free of basic spelling, grammar, formatting, and logic problems, in case anyone was wondering — the less likely it is to push Millicent’s rejection buttons. The same holds true for her pet peeves: the better revision job you do, the less likely your pages are to come winging back in your SASE, accompanied by a form-letter rejection. Or, as is increasingly common, for them not to come back at all.

Sense where I’m heading with this? Getting caught in a submission-rejection cycle generally ends up eating far, far more of a writer’s valuable time than an intensive revision aimed at weeding out rejection triggers would take.

Or, to put it more bluntly, aspiring writers who routinely send out first drafts, especially — sacre bleu! — ones that have neither been proofread or spell- and grammar-checked — because they are impatient to get their books published generally have a harder time landing an agent, winning a contest, and/or pleasing an editor than writers patient enough to polish their work prior to submitting it.

Given such a noble goal, concentrating upon something as basic as whether your narrative relies too heavily upon and, but, and then may not seem as if it would make a big difference, but actually, out of all the potential problems a self-editor might discover in a Frankenstein manuscript, overused conjunctions are some of the easiest to catch and fix. And the pay-off can be tremendous: quick-reading agency screeners, editorial assistants (who screen submissions for editors) and contest judges are routinely ordered to subtract points (Brownie in the case of the former two, literal in the case of the contest submission) for grammatical errors — and word repetition is always high on their penalty list.

As is that habitual roommate of conjunctions, the run-on sentence. Not sure what one looks like? Here’s a lulu, presented for your reading pleasure in its natural habitat, the manuscript page.

Laugh if you like, but would it astonish you to learn that this is shorter than some of the sentences my aged eyes have beheld in manuscripts and contest entries? I’ve seen sentences that have dragged on for more than a page; I once spotted one that expected the reader to follow its twists and turns for almost three.

Although I have apparently lived to tell about it, there can be no legitimate justification for dragging the reader through such an epic. The best possible outcome — which the author does not deserve — is that perhaps no one will notice that there was only a single period in those 21 lines of text, but that’s not what’s likely to happen at submission time. Since text like this simply shouts at Millicent, “Hey, this writer didn’t bother to reread this paragraph in hard copy after writing or revising it; clearly, these pages are not ready for professional perusal,” including such a lengthy run-on produces prose that is in effect self-rejecting.

I sense that those of you fond of the occasional multiply compound sentence longing to equivocate. “But Anne,” run-on huggers point out, “couldn’t embracing this sort of conversational-style sentence be a daring authorial choice? Could it not, in fact, be a characteristic of a distinctive voice?”

Well, it could, if it were handled skillfully — but in 99.99% of cases, extended run-ons are not interesting enough to be honored with the name of style. Run-on sentences, much like the repetition of a favorite word or phrase, virtually never strike Millicent as the result of well-thought-out and purposeful writerly strategy. Or, if a pro does think it is purposeful it’s poor strategy: “I know! I’ll bore my reader and annoy Millicent by making her read the sentence twice in order to understand it!”

Seem like a harsh assessment? It isn’t, particularly, if you consider that from an agent or editor’s perspective, it’s the writer’s job to write not only clearly, but beautifully, adhering to the basic rules of grammar. Expressing a sentiment well and without gaffes is, after all, the minimum requirement for professional writing, not an optional extra.

To Millicent, then, a run-on sentence tends to look like an instance of the writer’s just being in too much of a hurry to write well — and in practice, she’s frequently right about that. It’s not at all uncommon for an aspiring writer to whip out a scene or paragraph in a rush, fully intending to come back and flesh out those not-especially-stirring sentences when he has more time. Astonishingly often, though, that mythical day with 27 hours — 24 for normal life, plus an extra 3 for revision — never manages to roll around. The writer forgets all about those original noble intentions and moves on.

Multiply that by a few hundred times, and you’ll end up with the type of submission that makes Millicent shake her head over a good premise gone awry: a typo-filled, run-on laden series of scenes dimly indicating what an intriguing story this might be four or five drafts down the line. A half-century ago, an agent or editor might have taken on a project like this, seeing that with proper professional guidance, the writer might polish it up into something genuinely fine. Today, however, our Millie sees just too many technically perfect submissions to worry much about rejecting those that still need work.

You’d be surprised, I suspect, at just how clearly a page featuring a couple of run-ons telegraphs to the pros that this manuscript could use more revision. Run-ons are usually hodgepodges of several distinct sentences’ worth of material, rubber-cemented together with our old pals and, but, and then. Look how obvious it is that the writer was in a rush:

Eighteen thousand citizens rushed as one to the city’s walls and stared over the side, but they could not possibly have anticipated what they would find there and gasped accordingly, then began to shout.

Essentially, this is a summary, not a description. We can see where and how this hefty hunk of prose could be chopped up into interesting, specific detail-filled individual sentences, but for reasons best known to herself, the writer has elected not to do so.

Once a reader has developed the editorial eye to see what could have been, other types of compound sentence also seem ripe for closer scrutiny. Take, for instance, the 19th century prose practice of stringing clause after clause together with whiches and whos and wheres:

Petunia, who was desperate, ran along the docks where Ambrose had vanished. She turned right every time she came to a curve, which was easier than making a new decision each time, but which left her wondering after about fifteen minutes if the awnings she was passing were the same ones she had passed earlier.

Modern style cries out for fewer of those clunky asides. And don’t even get Millicent started on the species of run-on that’s simply the result of a writer’s apparently being unsure whether it’s okay to replace a period with a comma in order to speed up the reader’s sense of what’s going on.

Sebastian hesitated before marching through the doorway, the scent of gunpowder coming through it was so strong.

The answer, Millie would like me to tell you, is no: it’s never correct to slap two complete sentences together with a comma. That last example should have been cut in half with a period:

Sebastian hesitated before marching through the doorway. The scent of gunpowder coming through it was so strong.

Or a semicolon:

Sebastian hesitated before marching through the doorway; the scent of gunpowder coming through it was so strong.

Even with the punctuation corrected, these sentences still might raise Millicent’s ire. Any guesses why?

Give yourself a gold star with almond clusters if you instantly leapt to your feet, shouting, “So is comparative! It must take a modifier!” A so statement logically requires a that follow-up. Voilà:

Sebastian hesitated before marching through the doorway. The scent of gunpowder coming through it was so strong that it made him gag.

Why, yes, I did add some extra information to this sentence that might not have been part of the author’s original intention; editors are notorious for doing that, in the interests of rendering the prose clearer. I could also have revised these sentences without changing the meaning. What the author probably meant (“And should have taken the time to say,” sniffs Millie) was this:

The scent of gunpowder wafting through the doorway was so strong that Sebastian hesitated before marching through it.

This version also, I am glad to report, neatly side-steps the other professional readers’ pet peeve in the original, presenting cause and effect out of chronological order. Think about it: how likely is it that Sebastian would have hesitated before he smelled the gunpowder? Isn’t it far more plausible that he paused because it wafted toward him and he drew a conclusion from it about what probably lay beyond that doorway?

I hate to be the one to break the sad news, but the writer of the first version probably thought she had said precisely that. She was just in too much of a hurry to go back and make sure a reader would take that meaning from it.

Starting to get the hang of reading a run-on for clarity and grammar? Good. Now — and only now — are we ready to talk about style.

Let’s face it, none of these are particularly pretty sentences. The word choice is not especially interesting; they reveal little about the physical environment, Sebastian’s character, or even the danger into which he is almost certainly walking. As such, the phrasing takes a potentially suspenseful moment and squashes the reader’s sense of anticipation.

So I ask you: as a writer, how likely would you be to do any of those things on purpose, in the name of delightful literature or compelling storytelling?

Millicent doesn’t think it’s likely, either. No professional reader would mistake any of these examples for a daring stylistic experiment; they are not polished or interesting enough to prompt the reader to try to figure out if the writer had some clever reason for presenting these facts in this manner.

Nor — dare I say it? — are these sentences original enough to set off the High Literary Stylings siren in Millicent’s brainpan. That may well come as something of a surprise to creators of the variety of first-person narration whose primary stylistic recommendation is that it reads like everyday speech. The most popular means of pulling that off, as we have discussed earlier in the Pet Peeves on Parade series, is to replace grammatically-necessary periods with the ands, buts, and thens that grant a false consecutiveness to verbal storytelling.

My name is Louisa, and I am seven years old — and already, I see your eyes glazing over, dismissing anything I might have to say as the mere ramblings of a child. But I was there when the schoolhouse caught fire, there when the mayor decamped with the last dime of the town’s funds, there when the crocodiles began to squirm up from the riverbed to dine on the dear departed that no one was around anymore to bury. Then the vultures came, and still, I was there.

It’s not an uncompelling voice — although of the scores of professional readers’ pet peeves, few will cause the average Millicent to mutter, “Next!” faster than the grade-school storytelling expedient of having the narrator say right off the bat My name is X and I am # years old — but honestly, any originality the reader might spot in it comes from the details, not the echo of run-on filled normal speech. (“And even if it did,” Millicent adds, “this is a far cry from a seven-year-old’s voice.”)

Don’t believe me? Okay, here is the same passage, stripped of run-ons and reworked to minimize conjunctions.

My name is Louisa. I am seven years old. Already, I see your eyes glazing over, dismissing anything I might have to say as the mere ramblings of a child, but I was there when the schoolhouse caught fire. I was there when the mayor decamped with the last dime of the town’s funds. I was there when the crocodiles began to squirm up from the riverbed to dine on the dear departed that no one was around anymore to bury. When the vultures came, I was still there.

A forest of hands sprouted throughout the course of that last paragraph; I couldn’t be more delighted. “But Anne,” shout those of you who have been paying attention in recent weeks, “isn’t this opening a prime example of the oh-so-common invocatory rhythm achieved through word and phrase repetition that we have already identified as one of Millie’s pet peeves? I can’t believe that you edited the original without addressing that problem.”

Hey, it’s not the editor’s job to rewrite the author’s voice choices; all we do is flag what’s not working and suggest how to kick-start that story’s engine. It’s the writer’s job to decide how the words should appear on the page, right?

Admit it: you’re happy that’s the case. You wouldn’t really like somebody else to set your literary voice for you, would you?

So I leave to you the meaty creative challenge of making your prose sound like you at your best. For the moment, my goal is far less lofty: I want to help you be able to spot a run-on when you encounter it in the wild.

Here’s a good preliminary rule of thumb: if you can’t say any given sentence within a single breath, it might be a run-on. (Yet another great reason to read your manuscript OUT LOUD, IN HARD COPY, and IN THEIR ENTIRETY before you submit, eh?) Another classic tip-off: where run-ons gather, there will be ands aplenty also, typically.

So whip out your marked pages from last time, please, and let’s observe the reproduction habits of and. If you’re like most writers, your marking project probably revealed four major patterns of andusage:

(1) In lists.

Remember, not all lists take the form of Kamala had three novels, two memoirs, and a dictionary in her backpack. Keep an eye out for lists consisting of named emotions, which often appear in groups (Kamala felt angry, betrayed, and hurt), too-hurried accounts of activity (Kamala went to the store, searched fruitlessly for spumoni ice cream, ran down the block to her favorite trattoria, and begged them to sell her a couple of scoops on the sly.), as well as lists inadvertently formed by the use of and for emphasis (Kamala felt angry and betrayed and hurt and, consequently, ravenous for spumoni ice cream.).

Don’t think of all of those types of sentence as lists? Millicent does, believe me — and are lists really the most interesting way to present your protagonist’s activities? Ever?

(2) In the immensely popular X happened and (then) Y happened sentence structure.

We’re all familiar with this one, right? Edward ate his pizza and drank his Coke. The sky turned brown, and all of the birds stopped singing. I could go on like this all night, and if my guests were not flipping impatiently through magazines, I would.

There’s nothing wrong with this structure per se — but used too often, or too close together, all of those ands can start to feel quite repetitious quite fast. As can…

(3) In the almost-as-popular trilogy structure: Someone did X, Y, and Z. Alternatively, it may appear as Someone did X and Y, then Z.

Yes, either of these structures could be considered a list (as in, Christos cried, rolled over, and bawled some more.), but since most aspiring writers simply like the three-beat rhythm, I prefer to talk about it as a separate sentence type. Again, there’s nothing wrong with this structure if used sparingly, but all too often, the three-beat descriptive sentence becomes the default in the manuscript.

The resulting repetition can feel quite percussive to a reader, even if the actual sentence structure varies:

Christos felt betrayed, confused, and, oddly enough, desperate for some spumoni ice cream. Puzzled, he wandered into his kitchen, yanked open the freezer door, and pondered his ice cream supply. Wait — what had happened to his long-hoarded supply? Suddenly, it came to him: he’d heard Kamala rooting about in here in the wee hours, rattling bowls and clattering spoons. He felt angry and betrayed and hurt.

See how predictable those threesomes became, even in the space of one short paragraph? Imagine how Millicent feels when confronted with pages upon pages of them — which happens more than any of us would like to think.

(4) In complex descriptions.

Descriptions with multiple elements almost always contain at least one and, particularly if the sentence is passive: Germaine was tall and lanky. Again, this is technically a list (albeit a short one), but few writers would think of it as one.

Pay close attention to descriptive passages for another common and bugbear: sentences containing more than one of them. A multiple-and sentence is to most professional readers what a red flag is to a bull, and yet they are so easy to produce almost inadvertently if a writer is trying to cram too much description into a single sentence. As in:

Germaine was tall and lanky, with long, straight hair that came down to her lean and boyish hips. She liked to dress in black-and-white dresses, the kind that confused the eye if she walked past a strobe light, and skin-tight leather boots. She also favored tight jeans and tank tops, except of course for days she knew she would be running into Kamala and joining her on a spumoni ice cream run.

Quite a lot of ands, isn’t it? As strange as it may seem, most writers have an infinitely easier time spotting this kind of repetition in other people’s work; in their own, they tend to concentrate on the description, not the repetitive structure.

Complicating matters is the fact that often, two or more of these four types of and usage will appear within a single paragraph — or even a single sentence. Not sure what that might look like in practice? Okay, see if you can ferret out instances of all four kinds in this sterling piece of prose:

Abe took a deep breath and ran his palms over his face. He yanked his handkerchief from his pocket and mopped the red and black tattoo over his left eyebrow, folded it twice, and stuffed it back into his coat. A motley assortment of trash caused his hand to recoil: cast-off candy bar wrappers, half-sucked lollipops hastily stuck back into their wrappers, waiting for later, and both red and black licorice whips. Sure, he was a sane and sober adult now. Outwardly composed, he twisted his face into a smile, swallowed a groan, and extended his hand to Emile.

How did you do? Admittedly, we’re looking for something a bit subtle here. Although the types of repetition used in this example may sound merely chatty when read out loud, they would come across as structurally redundant on the page. Even minor word repetition can set editorial teeth on edge, because editors — like other professional readers — are trained to zero in on redundancy.

To see how this orientation might affect how one reads, let’s look at this same paragraph with a screener’s heightened antennae:

Abe took a deep breath and ran his palms over his face. He yanked his handkerchief from his pocket and mopped the red and black tattoo over his left eyebrow, folded it twice, and stuffed it back into his coat. A motley assortment of trash caused his hand to recoil: cast-off candy bar wrappers, half-sucked lollipops hastily stuck back into their wrappers, waiting for later, and both red and black licorice whips. Sure, he was a sane and sober adult now. Outwardly composed, he twisted his face into a smile, swallowed a groan, and extended his hand to Emile.

See? The repetition of all those ands can be downright hypnotic — the percussive repetition lulls the reader, even if the action being described on either end of the and is very exciting indeed.

There’s a reason for that, you know, and if you’ve been paying attention throughout this series, it has probably already occurred to you. The swiftly-scanning eye’s automatic tendency is to jump between repeated words on a page, in very much the manner that a CLUE player might move his piece from the study to the kitchen via the secret passage about which everyone in the game is evidently quite well-informed. (Hey, it’s an editor’s job to demand precise word usage.)

The result: Miss Scarlet did it in the kitchen with the revolver.

Oops, wrong chain of events: the result relevant for our purposes is a submission page read far, far more quickly than the average submitter might wish. Not only by Millicent and her ilk, but by the average reader as well.

The best way to avoid triggering this skimming reaction is to vary your sentence structure. A great place to start: scanning your manuscript for any sentence in which the word and appears more than once. Take a gander:

Ezekiel put on his cocked hat, his coat of many colors, and his pink and black checked pantaloons. And he dusted himself out before heading toward the big top, clown shoes a-flopping.

Did your eye catch the subtle problem here? No? Let’s take a second look, this time as Millicent would see it:

Ezekiel put on his cocked hat, his coat of many colors, and his pink and black checked pantaloons. And he dusted himself out before heading toward the big top, clown shoes a-flopping.

All of the ands are serving slightly different functions here, two of which would be perfectly valid if they stood alone: the first is connecting the second and third items in a list; the second is connecting two characteristics in a shorter list. And the third — as in this sentence — is the kind of usage we discussed last time, where a conjunction gives a false sense of chatty consecutiveness between the first sentence and the second.

When I first began writing that last paragraph, I didn’t intend it to be an illustration of just how visually confusing word repetition may be on the page — but as I seemed to be succeeding brilliantly at doing just that, I figured I’d just run with it.

You’re welcome. Let’s highlight the repetition here, to determine precisely why a skimming reader might find it confusing:

All of the ands are serving slightly different functions here, two of which would be perfectly legitimate if they stood alone: the first is connecting the second and third items in a list; the second is connecting two characteristics in a shorter list. And the third — as in this sentence — is the kind of usage we discussed yesterday, where a conjunction gives a false sense of chatty consecutiveness between the first sentence and the second.

Is your brain in a twist after all of that percussive redundancy? Never fear — the twin revising morals are actually quite simple to remember:

(1) Every writer, no matter how experienced, will occasionally write a poorly-constructed sentence or paragraph, so there will never be a point where any of us can legitimately assume that our first drafts require no revision whatsoever, and

(2) Just because a given word may carry more than one meaning — or, as here, refer to distinct categories of things — that fact doesn’t nullify the effects of repetition upon the reader.

Because we writers tend to think of words according to their respective functions within any given sentence, rather than as images on a page, these kinds of repetition often flies under our self-editing radars. Unless one is looking for it specifically, it’s easy to, well, overlook. Thus my urging you to whip out the highlighting pens, in case you were wondering. I’m just trying to make repetition jump out at you as garishly as it does to those of us who read for a living.

Incidentally, words that sound alike but are spelled differently — there, they’re, and their, for instance — often strike readers as repetitious if they are used in too close proximity to one another. For example:

“They’re going to look for their zithers in there,” Thierry pointed out.

Why might this sentence give a reader pause? Because many pronounce words silently in their heads while they scan. Yet another great incentive to read your manuscript IN ITS ENTIRETY, IN HARD COPY, and OUT LOUD, eh? It’s the best way to replicate the silent reader’s mental experience.

Next time, I shall delve into some other problems that commonly arise from an over-reliance upon ands. In the meantime, in between time, try to minimize word and sentence structure repetition, and keep up the good work!