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!

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!

Pet peeves on parade, part XXV, structural repetition, part III, and the role of pretzels in a well-rounded breakfast

This morning, I was puzzled into wakefulness by my fiancé’s waving a soy latte and a freshly-baked pretzel under my nose. A new German bakery has opened in our neighborhood, and he’s terrified that it will go out of business without our daily support. A reliable source for Black Forest cake is not to be taken for granted, after all.

Now, I’m as fond of a good pretzel as the next person, but at 8 a.m., I must confess, mustard-laden food options are generally not the first to pop to mind. Nor is rock salt my favorite pillow covering, given my druthers.

Rick, however, subscribes to the surprisingly pervasive school of thought that holds what a person has said she liked once, ever, will come as a pleasant surprise to receive at any randomly-selected moment for the rest of her life. Or so I surmise from the fact that he could not resist pointing out that I had apparently enjoyed a remarkably similar pretzel only two afternoons before.

Which, of course, would render it even less likely that I would want another one now. The pretzel was turning out to be pretty tasty, though, so rather than take the time to explain at length that piling on more of a good thing does not necessarily improve, well, anything, I decided it would be the better part of valor to thank him graciously and bear my usual breakfast into a more appropriate environment for consuming something warm and squishy. As I fled, I marveled at how, once again, the muses had tumbled all over themselves to provide me with a delightfully apt metaphor for a craft issue you and I were already discussing.

Oh, hadn’t the pretzel-paragraph construction parallel hit you instantly? Allow me to recast it as a self-editing aphorism for the ages, then: what might read beautifully as a stand-alone sentence may not work as well within the context of a page of text. Varying word choice and sentence structure will usually provide the reader with a more pleasurable reading experience than a narrative’s insisting that if something looked good on the page once, it will necessarily look great if it’s repeated.

For the last couple of posts, I’ve been talking about how professional readers tend to respond to repetition in submissions. (To summarize their reaction for those of you joining us mid-series: not at all well.) I cannot in good conscience round off my lobbying for reduced repetition in your manuscripts, though, without discussing those ever-popular transients passing through Conjunction Junction: and, but, and then.

Positive legions of hands shoot into the air. Yes, grammar mavens? “But Anne,” you point out, and rightly so, “then isn’t a conjunction! Why, then, would you include it in your discussion of conjunctions, when there are so many legitimate conjunctions — yet, for instance — deserving of your august scrutiny?”

Quite right, hand-wavers: when used properly, then isn’t strictly speaking a conjunction. However, enough writers are using it these days as if it were a synonym for and in a list of actions (as in The Little Red Hen kneaded the bread, baked it, then fed it to her forty-seven children.) that I feel justified in — nay, compelled to — treat it as such for the purposes of our ongoing discussion of repetitive sentence structures and their predictably negative effect on Millicent the agency screener’s weary peepers.

Language does grow and change, of course. Back in the bad old days, when dinosaurs roamed the earth Roosevelts were presidents Dorothy Parker was still speaking to Ernest Hemingway editors like Maxwell Perkins called the shots in the publishing world, it was considered hugely improper to begin any sentence with and, but, or then; amongst the literate, these words were purely intra-sentence phenomena. As my Uncle Alex (a fairly well-known SF short story writer in the 1950s, an editor at the LA Free Press, and a stickler for grammar for his entire life) used to scrawl in the margins of letters I had written when he returned them to me, a conjunction, by definition, connects one part of a sentence to another.

“Therefore,” he would ink in large letters, “a conjunction may not begin a sentence. How’s your mother?”

There are easier things than growing up in a family of writers and editors. Toward the end of his long, colorful, and occasionally scurrilous life, Uncle Alex was even known to shout grammatical advice at the TV screen when newscasters –sacre bleu! — began their sentences with conjunctions. And really, who could blame him?

(I couldn’t resist. Hey, a pretzel is not exactly the breakfast of champions.)

Time and the language have been marching merrily onward, however, and at this point in North American history, it’s considered quite acceptable to begin the occasional sentence with a conjunction. I do it here all the time. So do most bloggers, journalists, and columnists: it’s a recognized technique for establishing an informal, chatty narrative voice.

That mournful crashing sound you just heard was Uncle Alex stomping his feet on the floor of heaven, trying to get all of us to cut it out, already, but there can be perfectly legitimate stylistic reasons to open a sentence with a conjunction. They can, for instance, be very valuable for maintaining an ongoing rhythm in a paragraph. Like so:

Ghislaine spotted the train pulling into the station. But would Arbogast be on it? He would — he had to be. And if he wasn’t, well, she was just going to have to call him to find out why. Or not. Anyway, she wasn’t going to waste her energy speculating on what would be a moot point the second Arbogast stepped off that train and caught her in his arms.

As Uncle Alex would undoubtedly have been the first (and last, and middle) to tell you, classic English grammar has an elegant means of preventing those conjunctions from hanging out at the beginnings of those sentences: by eliminating the periods and replacing them with commas. The result would look a little something like this:

Ghislaine spotted the train pulling into the station, but would Arbogast be on it? He would — he had to be, and if he wasn’t, well, she was just going to have to call him to find out why — or not. Anyway, she wasn’t going to waste her energy speculating on what would be a moot point the second he stepped off that train and caught her in his arms.

To old-fashioned eyes, this paragraph’s meaning is identical to the first; it is merely cleaner grammatically. However, I suspect that most current readers of English prose would recognize a substantial difference in the rhythm. A period is, as the English like to call it, a full stop; a comma, on the other hand, indicates a pause. A dash indicates a slightly longer and more pointed pause. To this millennium’s sensibilities, the first example has a choppiness, a breathless quality that conveys the subtle impression that Ghislaine’s breathing is shallow, her pulse racing.

The periods my uncle would have forbidden, then, could be regarded as subtle narrative indicators of protagonist stress. At least to those in the habit of breaking paragraphs down into their constituent parts to see what their functions are. Like, say, most of us who read manuscripts for a living.

Before we leave that last set of examples, did you happen to notice any other editorial pet peeves in that first? No? Okay, let me whip out my editorial machete pen and remove a couple of Millicent’s pet peeves. Rather than merely noticing that this third version reads better, why not challenge your revision skills by trying to figure out why?

Ghislaine spotted the train pulling into the station, but would Arbogast be on it? He would — he had to be, and if he wasn’t, well, she was just going to have to call him to find out why. Right now, she wasn’t going to waste her energy speculating on what would be a moot point the second he stepped off that train and caught her in his arms.

How did you do? Take a nice, shiny gold star from petty cash if you immediately cried, “Why, word repetition is word repetition, Anne — which is why you removed the second Jason in the paragraph.” Stack another star on top of the first if you added, “Anyway is often how speakers inform hearers that they’ve digressed from their point. Is there a reason the narrative should go out of its way to inform readers that it has digressed?” And give yourself three more stars if you have gotten in touch with your inner Millicent sufficiently to have mused, “You know, to find out why — or not is conceptually unnecessary. And would the paragraph lose any actual meaning if I cut or not?”

I hear those of you who did not shout any of those three observations muttering under your collective breath, and you’re quite right: this is nit-picky stuff. Both good writing and professional presentation are made up of lots and lots of nit-picky stuff. Your point?

While you’re trying to come up with a sufficiently scathing comeback for that one, let’s tie the anyway revelation (i.e., that what’s considered acceptable in everyday speech may not work so well in a narrative voice on paper, even if it happens to be in the first person), back to our ongoing discussion of and and but. Since conjunction-opened sentences can sometimes mirror actual speech better than more strictly grammatical ones, the former can be a positive boon to dialogue.

Seem paradoxical? Okay, contrast this sterling exchange:

“And I tell you, Spencer, it was eerie. I’m never going back into that deserted house again. And that’s final.”

“But Yvette, you’re backing recklessly away from the conventions of our chosen genre! You’re a scantily-clad, unattached female who screams easily, often while tossing your dreamy long red (or blonde) hair. You are fleet of foot in the face of danger. Yet you are astonishingly prone to tripping over easily-avoidable bits of bracken your surer-footed male counterparts and non-ingénue sidekicks never seem to twist their ankles navigating. And, naturally, you are entirely unarmed. Therefore, you must return to face the danger that any sane person would take extreme measures to avoid!”

“Or what? Or you’re going to turn me in to the Stereotype Enforcement Police?”

“Or else, that’s all.”

“Fine. Then give me the key to the tool shed.”

“If you insist. But don’t come crying to me when an axe comes crashing through your door at the closed-for-the-season hotel.”

with the same dialogue after the conjunctions have been tucked into the middle of the sentences:

“I tell you, Spencer, it was eerie. I’m never going back into that deserted house again. That’s final.”

“Yvette, you’re backing recklessly away from the conventions of our chosen genre! You’re a scantily-clad, unattached female who screams easily, often while tossing your dreamy long red (or blonde) hair. You are fleet of foot in the face of danger, yet surprisingly prone to tripping over easily-avoidable bits of bracken your surer-footed male counterparts and non-ingénue sidekicks never seem to twist their ankles navigating. Naturally, you are entirely unarmed. Therefore, you must return to face the danger that any sane person would take extreme measures to avoid!”

“Is there some penalty attached to my refusal? Are you going to turn me in to the Stereotype Enforcement Police?”

“You must, that’s all.”

“Fine. Give me the key to the tool shed.”

“If you insist, but don’t come crying to me when an axe comes crashing through your door at the closed-for-the-season hotel.”

The difference is subtle, but to a professional reader, it would be quite evident: the second version sounds more formal. Partially, this is a function of the verbal gymnastics required to avoid the colloquial Or what? Or else.

But these are not the only ways aspiring writers utilize sentence-beginning conjunctions in narrative prose, are they? As anyone who has ever been trapped in a conversation with a non-stop talker can tell you, beginning sentences with conjunctions gives an impression of consecutiveness of logic or storyline. (As was the case with the first sentence of this paragraph, as it happens.) Even when no such link actually exists, the conjunctions give the hearer the impression that there is no polite place to interrupt, to turn the soliloquy-in-progress into a dialogue.

We all encounter this phenomenon so often in everyday life that giving a concrete example seems a tad, well, repetitive. If you feel that your life lacks such monologues, though, try this experiment the next time you’re at a boring cocktail party. (They’re coming back, I hear.)

(1) Walk up to another guest, preferably a stranger or someone you do not like very much. (It will soon become apparent why that last trait is desirable.)

(2) Tell a lengthy anecdote, beginning every sentence with either and, but or then. Take as few breaths as possible throughout your speech.

(3) Time how long it takes a reasonably courteous person to get a word in edgewise.

Personally, I’ve kept this game going for over 15 minutes at a stretch. The imminent threat of fainting due to shortness of breath alone stopped me.

Which is, in case you happen to be writing a book about such things, why panhandlers and telemarketers so often speak for minutes at a time in what seems to the hearer to be one long sentence: run-on sentences discourage interruption. Almost invariably, this phenomenon is brought to you by the heavy lifting skills of and, but and then.

Perhaps for this reason, aspiring writers just love to tuck conjunctions in all over the place: it can create the impression of swift forward movement in the narrative. Or, even more often, to establish that chatty-sounding first-person narrative voice I mentioned above. Sometimes, this can work beautifully, but as with any repeated stylistic trick, there’s a fine line between effective and over-the-top.

Also, had I mentioned that aspiring writers just love to overload their manuscripts with conjunctions? And that they use the device a lot? Or that by the time Millicent picks up your submission, she’s probably already read hundreds of conjunctions that day?

In case I’m being too subtle here: since false consecutiveness is a narrative that professional readers see so very much, you might want to screen your submission for its frequency. Particularly, if you’ll forgive my being a bit pushy and marketing-minded here, in the early pages of your manuscript. And absolutely on the first page.

Why especially the opening? Long-time readers, chant it with me now: agents, editors, and contest judges tend to assume that the writing on pages 1-5 is an accurate representation of the style throughout the entire manuscript. That presumption enables them to stop reading as soon as they decide that the writing is weak.

Or, to cast it in terms of our running analogy: Millicent didn’t like the second pretzel of the day, she takes it as given that she’s not going to like the 145th. She does not feel the need to gobble up pretzels 3-144 to confirm that.

Was that sudden blinding flash an indication that light bulbs just went off over some of your heads? That’s right: this often-unwarranted assumption, renders rejection on page 1 not only logically possible, but reasonable. It certainly underlies the average Millicent’s practice of not reading past any problems that might turn up on page 1 of a submission: once you’ve seen a modicum of this author’s writing, she reasons, you’ve seen enough.

Feel free to pause here to punch the nearest pillow, sofa cushion, or other relatively soft object seventeen or eighteen times. I’ll wait.

Got all of that frustration out of your system? Excellent. Let’s shift our energies to what a writer can control in this situation. Narrative structure and voice are not merely matters of style; to a market-savvy writer, they are also matters of strategy.

And, frankly, the oh-so-common practice of conjunction overuse is not particularly good strategy. If you over-use any single narrative tool in your writer’s kit in those early pages, Millicent and her ilk are not going to stick around to see whether you’ve mended your ways by page 25, alas. They’re going to stop reading, so they may move on to the next submission.

Do I hear some moaning out there that’s not attributable to any of my late relatives? “But Anne,” these disembodied voices moan, bravely beginning their protest with a conjunction, thereby risking a thunderbolt flung by Uncle Alex and whatever minor deities he may have managed to befriend in his time in the choir eternal; he always did throw great parties, “not every book’s best writing falls on its first page, or even within its first chapter. Many, many writers take a chapter or two to warm up to their topics. So doesn’t this practice give an unfair advantage to those writers who do front-load their work?”

In a word, yes. Next question? In fact, I would highly recommend front-loading your submission or contest entry with your best writing, because I want your work to succeed.

Again, we could waste a lot of energy complaining about the necessity for this (which I’m sure all of us could, at great length), but I would rather we concentrate instead upon heading the problem off at the proverbial pass. Whip out your trusty highlighter pens, and let’s get to work.

(1) Print out at least the first 5 pages of your submission. If you want to be very thorough, print the entire first chapter, as well a random page from each subsequent chapter.

And before anybody asks: no, reading through those pages on your computer’s screen is not an adequate substitute here. Nor is simply doing a Word search for those particular words. The goal here is not to come up with a simple accounting of how often you are using these words, but to spot patterns in how and where you are habitually including them.

(2) Pick a color for and, another for but (go ahead and use it for the howevers and yets, too), and a third for then.

Why these words and no others? Well, these particular ones tend to get a real workout in the average manuscript: when writers are trying to cover material rapidly, for instance, and, but, and then often appear many times per page. Or per paragraph.

Or even per sentence. Yes, really.

(3) Mark every single time each of those words appears on your pages.

Not just where these words open a sentence, mind you, but every instance.

(4) After you have finished inking, go back and re-examine every use of then, asking yourself: could I revise that sentence to cut the word entirely? If it begins a sentence, is that the most effective opening?

(5) If you were even tempted to skip Step 4, does then appear more than once within those first 5 pages? More than once on page 1?

At the risk of seeming draconian, you should seriously consider excising every single use of then in those opening pages — and at least toy with getting rid of most thereafter. Sound drastic? Believe me, I have an excellent reason for suggesting it: some professional readers’ visceral negative reaction to repetitive use of then borders on the physically painful.

Why? Well, it’s one of the first words any professional editor would cut from a text — and with good reason. In written English, pretty much any event that is described after any other event is assumed to have happened later than the first described, unless the text specifies otherwise. For instance:

Jean-Marc poached the eggs in a little butter, slid them onto the plate, then served them.

Ostensibly, there’s nothing wrong with this sentence, right? Perhaps not, but given the average reader’s belief that time is linear, it is logically identical to:

Jean-Marc poached the eggs in a little butter, slid them onto the plate, and served them.

Technically, then is unnecessary here. In fact, then is almost always omittable as a purely temporal marker.

“Pardon my asking,” Millicent says, wondering why I have a latte at my elbow and she doesn’t, “but why is do submissions so often include it repeatedly, as if it were stylish? Or, if appears frequently enough, as a characteristic of authorial voice? It’s seldom necessary, and it’s hardly original.”

That would be hard for anyone who has read more than a handful of manuscripts or contest entries to dispute. To professional eyes, this percussive use of then is logically redundant, at best. At worst, it’s a sign that the writer is getting a bit tired of writing interestingly about a series of events and so crammed them all into a list.

Is this really the reaction you want to elicit to your narrative voice within the first few pages of your book?

Actually, it’s not a bad idea to omit temporal thens altogether in your writing unless the event described after them is a genuine surprise or occurred so abruptly that it would have been so to onlookers. Here’s an instance where the use is undoubtedly justified:

Jean-Marc poached the eggs in a little butter, slid them onto the plate — then flung their steaming runniness into Anselmo’s astonished face.

Now that’s a then that signals a change in sentence direction, isn’t it? Reserving the device for this use will render your thens substantially more powerful.

(6) Turn now to the buts, howevers, and yets on your marked-up pages. Each time they appear, ask yourself: is the clause that immediately follows the word ACTUALLY a shift in meaning from what has come immediately before it? If not, consider excising the words altogether.

I hear more squawking from the non-celestial peanut gallery. “But Anne,” they cry, bravely persisting in their long-term habit of opening every protest hurled my way with a conjunction, “you can’t seriously mean that! Don’t you mean that I should carefully rewrite the sentence, substituting another word that means precisely the same as but, however, or yet? The whole point of my introducing however and yet was to give my but a periodic rest, after all.”

Good question, but-resters, but I did mean what I said. But, however, and yet logically imply contradiction to what has already been stated. Many aspiring writers use these words simply as transitions, a way to make the sentence before seem to flow naturally — that is, in a way that sounds like conversation — into the next.

What I’m suggesting here is not that you remove every legitimate negation, but rather that you should remove the negative conjunctions that are misused. Let’s take a gander at what a savvy reviser might spare.

Bartholomew wanted to answer, but his tongue seemed to be swelling in his mouth. Was it an allergic reaction, stress, or had Josette poisoned him? He felt panic rising within him. However, his epi pen was in the pocket of his fetching dressing gown, so he need not panic. Yet now that he began to search for it, his personal first-aid kit seemed to have vanished from its usual resting-place.

“Cat got your tongue?” Josette asked sweetly, adding another lump of strangely-colored sugar to his tea.

I would vote for keeping all of buts, howevers, and yets in this passage. Each is serving its proper function: they are introducing new facts that are genuinely opposed to those that came just before the conjunction.

That is not always the case, alas. Take a look at a version of the same scene where none of these words is ushering in a twist related to the last information before it:

Bartholomew settled his fetching dressing gown around him irritably, but his tongue seemed to be swelling in his mouth. Was it an allergic reaction, stress, or had Josette poisoned him? He felt panic rising within him. However, he could not breathe. Yet his asthma seemed to be kicking in full force.

“Cat got your tongue?” Josette asked sweetly, adding another lump of strangely-colored sugar to his tea.

See the difference? By including conjunctions that imply an opposition is to follow, but not delivering upon it, the transitional buts, howevers, and yets ring false.

Yes, this level of textual analysis IS a heck of a lot of work, now that you mention it. Strategically, it’s worth it, for this device is so popular amongst aspiring writers that the transitional but has become, you guessed it, a common screeners’ pet peeve.

Harrumphs all round from my questioners, earth-bound and otherwise. “No big surprise there,” they huff. “To hear you tell it, it doesn’t take much for a writerly preference to graduate to industry pet peeve.”

Actually, it does take much — much repetition. It just doesn’t take very long manning the screening desk to discover that out of any 100 submissions, a good 92 will all share this narrative device.

And yes, Virginia, the transitional but IS that common. As is the unnecessary then. Trust me, agents and editors alike will bless you if your manuscript is relatively light on these overworked words.

Or if you don’t overuse favorite words in general. English is a marvelous language for prose because contains so very many different words; it enables great precision of description.

“So why on earth,” Millicent wonders, rejoining us after a coffee run, “do these submissions keep leaning so heavily on to be, to have, to think, to walk, to see, to say, and to take? If it happened in, say, one submission out of fifty, I could cope with it, but every other one?”

Good question, Millie. Varying word choice almost always makes a better impression upon professional readers than leaning too heavily on the basics.

Yes, I brought this up a few days ago, but it’s a fact that I wish more first-time submitters knew, but usually, US writers have been taught just the opposite: all throughout their school years, teachers kept quoting either Mark Twain or Somerset Maugham’s (depending upon how old the teachers were, and what examples their teachers had used) overworked axioms about never using a complex word when a simple word would do.

The reason that your teachers told you this is not that simple, straightforward words are inherently better than polysyllabic ones, but because they were trying to prevent you from making the opposite mistake: a narrative that sounds as if it has swallowed a thesaurus whole, dragging in pretentious or obsolete words inappropriate to the book category or target market. For most manuscripts, this is still pretty good advice.

Now, however, it’s considered less a matter of style than of marketing. Remember, the standard vocabulary expectation for adult fiction is a 10th-grade reading level; in many genres, it’s even lower. Doing a bit of reading in your chosen category can help you figure out where to pitch your word choices — and how broad a vocabulary Millicent is likely to expect in your manuscript.

Why is this a good idea? Not only is the gratuitous induction of polysyllabic terminology into a tome formulated for a less erudite audience not liable to galvanize a professional reader into spontaneous cries of “Huzzah!” (see how silly it looks on the page?) — it can also stick out like the proverbial sore thumb, knocking the reader out of the story.

The much-hyped 2007 movie JUNO contained such an excellent example of this that you might want to consider renting it just to see this phenomenon in action. After spending fully two-thirds of the film establishing the protagonist’s father as a Working Man with a Heart of Gold, living in a house that apparently contains no books, repeatedly telling better-heeled folk that he’s just a plain man, and who never once mentions to his pregnant 16-year-old daughter that her condition might conceivably (so to speak) affect any future college plans she might have, he says to his daughter, “You look morose.”

At which, naturally, half of my fellow theatergoers laughed, believing this line to be a joke. Morose didn’t seem to be a word that this character would ever use. Yet from context, it wasn’t intended humorously: evidently, the screenwriter simply liked the word.

Nothing wrong with that, of course — but authorial affection is not always sufficient justification to include a pet word or phrase. If a word is not book-category appropriate, think seriously about finding a substitute. That’s not compromising your artistic vision; that’s gearing your voice to your audience.

It’s also a necessary step towards individualizing your authorial voice. Just as a matter of practicality, if Millicent has already seen several conjunction-heavy narratives within the last hour, it’s going to be significantly more difficult to impress her with the originality of a manuscript that’s embraced a similar narrative strategy.

Speaking of developing a sensitivity to repetition across manuscripts, as well as within them, did anyone happen to catch the too-close similarity of Yvette and Josette in the two of today’s examples? “What’s going on?” Millicent shouts immediately after burning her lip on her too-hot latte. “A plague of -ettes? Did a bestseller from a year ago feature a heroine with an -ette name, and are the writers of these two passages copying that?”

Well caught, Millicent: I didn’t catch that one myself until about ten minutes after I wrote the second example. Clearly, I should have had a more balanced breakfast.

Don’t toss out those marked-up pages, please: we shall be talking more about overused conjunctions in the days to come. Next time, it’s on to the ands. Keep up the good work!

Pet peeves on parade, part XXIV, structural repetition, part II, or, are these concurrent series starting to get out of hand?

No, that image isn’t doctored — that’s a quick snapshot I took today of my garden’s first summer poppy. Eat your heart out, Georgia O’Keeffe.

I wasn’t playing hooky in the garden, honest; I was prowling my flowerbeds for bright, arresting color to illustrate our topic du jour. 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 a flower that might attract a passing motorist’s attention from half a block away?

“But Anne,” metaphor enthusiasts throughout the writing world protest, “I don’t get it. How are these two apparently unrelated things akin?”

That’s a perfectly legitimate question from a writerly point of view, metaphor-huggers, but from an editorial perspective, the connection is self-evident: both seem to leap out at the observer. 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. Ready, set — observe!

All of those Js and Ps were the first thing you saw on your return trip, were they not? A sharp-eyed pro like Millicent the agency screener would have that reaction scanning the page at a normal reading distance.

Now let’s take a gander at how the visual 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.

Quite a bit less amusing to read, isn’t it? I wouldn’t be at all astonished if you were tempted not to read it all the way to the end — 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?

A trained eye would be drawn immediately toward those repeated patterns — and thus away from other aspects of the text a savvy writer might want a professional reader like our old pal Millicent to notice instead, such as the compelling storyline, the interesting characters, and/or the overall beauty of the writing. 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 — you’re sitting down, I hope? — weak writing.

On the off chance that I’m being too subtle here: 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.

To put it rather less gently: 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 vary 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.

Did my reuse of the that’s true + adverb structure bug you more in that last paragraph, or the recycling of even? By this point, I would hope that neither escaped your attention.

Back to the principle at hand: 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.

Obviously, no one 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 into the state dinner, but he could not resist cursing under his breath.

Something tells me that a scene with stakes this high could have been written about in a slightly more compelling manner. There’s more to good storytelling, after all, than just getting all of the facts down on the page. To see why this is true, 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. 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? 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 an angry 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 she 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 while 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 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 so, you’re certainly not 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 it — 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 her 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? 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. “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, or to utilize a favorite complex sentence form twice 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 last post’s foray into A TALE OF TWO CITIES was so obvious, let’s try a comparatively subtle one on for size.

Rubbing his sides for warmth, Stephen 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 Brian, who had told him to wear nylons under them on this near-freezing night? – he wondered if Tammy 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.

The sad thing is, most of the time, writers don’t even realize that they’re repeating patterns, because unless the repetition bug has really bitten them, the redundancy isn’t in every sentence. Or if it is, the 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:

Arnold 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? 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, of course, 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 a couple of times, she will simply assume — feel free to sing along; you should know the words by now — that the pattern will recur throughout the manuscript.

How does s/he 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?

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.)

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 them, 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 removed 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.

But 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, or even 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 Harold’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 Harold, 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.

My, but our examples are violent today. To most self-editors, this paragraph would not seem especially problematic. However, to a professional reader, 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. To a professional reader, this is how the paragraph above would scan:

As the car door opened, Beatrice swallowed a horrified gasp. It was Harold’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 Harold, 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 her 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 is most unlikely to be so forgiving.

Do you honestly want to gamble on Millicent’s possible saintliness at the submission stage?

Because 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; 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 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. Keep up the good work!

Pet peeves on parade, part XXIII: the monster always returns…returns…returns…

I’m having a good day, campers: today, I got to delve back into an editing project I’d had to put aside for a while. It’s something that requires my full energy; digging one’s arms up to the elbow in a complex manuscript takes more out of a conscientious editor than writers tend to believe.

You’d be surprised at how deeply those of us who read for a living can bond with the manuscripts we handle. It’s not as though an editor (or an agent, or an agency screener) can plop himself down and read a book like any other reader; it’s our job to be alive to every detail. I like to think of myself as the book’s advocate, trying to figure out all of the little ways to make it as beautiful and marketable as humanly possible.

And no, in response to what a good third of you just thought very loudly, beautiful writing is not always marketable, any more than marketable writing is always beautiful. Ideally, a manuscript should be both. It should also, if I can possibly manage to nudge it in this direction, be written in a voice and vocabulary appropriately challenging for its target readership.

Bringing out any of these laudable traits is not only a matter of critiquing what could be improved; quite a lot of what I do involves helping the author see what is already good and could be made better. Part of being a thoughtful freelance editor — as opposed to a careful copyeditor, the nit-picky soul who concentrates on making sure that the manuscript is clear and the sentences grammatically correct, the minimum standard for professional writing — involves not only checking for possible red lights that might lead to rejection, but also figuring out what a manuscript’s strengths are, as well as why it will appeal to its target audience.

Again, those are not necessarily the same thing, right?

Most aspiring writers do need to be reminded, I’ve noticed, what is good about their work. Or even told what the selling points for their books are.

There’s a pretty good reason for this, actually. Throughout the writing process, it’s awfully easy to start to think of the effort you’ve put into a book as its most important characteristic. But realistically, publishing houses do not acquire books simply because someone went to the trouble to write them. Nor, contrary to popular opinion amongst aspiring writers, will readers — ones who do not already know the author personally, at any rate — pick up a book simply because somebody happened to write it.

Why does prompt publishers to acquire manuscripts and readers to buy books, you ask? Would I sound like a broken record if I suggested that both sell because of their strengths?

In fact, the length of time it took to write a book is precisely the wrong thing to mention in a query letter or pitch; it’s widely considered unprofessional. Millicent the agency screener is apt to regard queries that include statements like I have spent seven years writing NOVEL, GREAT AMERICAN as not only a waste of page space, but as a studied appeal for her sympathy.

“Why on earth would I care how long this manuscript took to write?” Millicent murmurs into her omnipresent latte. “And why would I be more favorably impressed by a seven-year effort than one that took only six? What matters is on the page, not what Herculean efforts it took to get there.”

Let me repeat that, as it’s awfully important: at the submission stage, manuscripts are evaluated based upon what actually appears on their pages, not the writer’s intentions, effort, or even what the book might look like after a conscientious editor’s had a few rounds with it. Many, many aspiring writers seem to have a hard time accepting this, judging by how often justifications and explanations seem to find their way into queries and pitches. From a professional point of view, this information just isn’t relevant.

But that’s not the only reason that including it could hurt you. Because it’s quite standard for both agents and editors to request revisions after taking on a book project — see my earlier observation about how involved professional readers can get with manuscripts they like — it’s prudent to assume that the pros in your future will expect you to be able to incorporate feedback in a timely and reasonable manner. So if the agent of your dreams’ reaction to a detailed account of the five years you invested in producing the manuscript is less likely to be, “Gee, this book must be worthwhile,” but “Heavens — if a single draft took five years, how long will any revisions I want take?” is it truly in your interests to mention it?

Save the probably quite interesting story of how you churned out that 400-page novel in the scant ten-minute increments you managed to snatch between your day job and your night job for future interviews. Trust me, your reading public will eat it up.

In your queries and pitches, stick to the information that Millicent actually needs in order to decide whether to request pages. As submitting writers are all too prone to forget, publishing is a business, not an art form — agents and editors acquire books they believe are marketable, not just ones they believe are well-written. And, as I believe I have mentioned several hundred times before, they do not — contrary to the hope of most submitting writers — read the entire submission before making up their minds on either point.

Anyone care to tell the class at what point in the average submission Millicent stops reading? Think on it, and I shall give you the answer at the end of this post.

Hint: it doesn’t necessarily correlate to the number of pages her agent boss asked you to send. Not at all.

How does this relate to the revision process, you ask? Well, swift judgments mean that if you have limited revision time at your disposal, it’s smart strategy to concentrate on the first 50 pages of your manuscript — the usual first request from an agent — or, in a pinch, the first 5. (If you are planning to head to a writers’ conference anytime soon, burnishing the first 5 until they shine is imperative: the first five pages of the manuscript are the standard writing sample, the most anyone is at all likely to ask to see within the context of a pitch meeting. But I digress.)

Do I sense an undercurrent of amusement out there? “Are you seriously taking the time to justify doing any revision at all, Anne?” those of you who have followed the Pet Peeves on Parade series closely ask, chuckling. “Isn’t it a bit late in the series for that? We all know what a stickler Millicent can — and indeed, should — be. Or are you once again leading us down the primrose path to some well-concealed eventual point?”

Well, the importance of revision bears repeating, chucklers, but you’re right: my little peroration was warming you up for a pet peeve that I suspect not all of you will agree is problematic on the page. Or so professional readers like yours truly surmise from how pervasive the problem I’m about to mention is in submissions — particularly in openings.

I’m speaking, of course, to invocatory rhythms that don’t quite work. And you thought this post wasn’t going to be a continuation of our discussion on voice!

Invocatory rhythms are one of the most popular tools aspiring writers use to beautify their narratives, a kind of sing-song rhythm that alerts the reader that Something Literary is Going on Here. One of the easiest ways to add this music to a text is through word and phrase repetition. Take a gander at a fairly representative sample:

Musette ran through the corridor, ran like the wind, ran as though lions were behind her and the open arms of a knight in shining armor in front. Didn’t she deserve her freedom, after all this time? Didn’t she deserve a life free of the incessant demands of boss, husband, co-worker, photocopy machine, cat? Didn’t she, in fact, deserve to breathe the fresh air of autonomy, unfettered by any limitations whatsoever?

See the problem? No? Okay, let’s take a peek at it through Millicent’s experience-sharpened peepers.

Musette ran through the corridor, ran like the wind, ran as though lions were behind her and the open arms of a knight in shining armor in front. Didn’t she deserve her freedom, after all this time? Didn’t she deserve a life free of the incessant demands of boss, husband, co-worker, photocopy machine, cat? Didn’t she, in fact, deserve to breathe the fresh air of autonomy, unfettered by any limitations whatsoever?

The problem is clearer now, right? Not only does this innocent-looking paragraph harbor a heck of a lot of word and phrase repetition — enough that our Millie may murmur under her breath, “Wow — doesn’t this writer know any other words?” — but that eye-confusing reiteration is encased in identical sentence structures. The result is a little something we professional readers like to call structural repetition: a percussive repetition of similarly-structured sentences (or sentence fragments) intended to make a rhythmic point.

Why bring this up as a voice and revision problem, in addition to a notorious Millicents’ pet peeve? Because part of the issue here is editorial: merely broadening the vocabulary, the usual fix for word repetition, would not solve this problem. Lookee:

Musette ran through the corridor, sped like the wind, fled as though lions were behind her and the open arms of a knight in shining armor in front. Didn’t she deserve her liberty, after all this time? Didn’t she merit a life free of the incessant demands of boss, husband, co-worker, photocopy machine, cat? Didn’t she, in fact, have an inherent right to breathe the fresh air of autonomy, unfettered by any limitations whatsoever?

Better already, is it not? To a professional reader, though, this passage would still read as structurally repetitious, despite the wording being more varied (and thus more interesting) this time around. And that reaction is apt to confuse self-editors, who would tend to see the nice, pulsing rhythm pushing the paragraph forward, rather than the probability that the too-similar sentence structures will cause the reader to zone out a bit as the paragraph goes on.

Not to mention the virtual certainty that Millicent will murmur, “There’s nothing inherently wrong with this narrative trick, but why must this writer foist it on us twice in a single paragraph?”

You’ve got an excellent point there, Millie. Like every other narrative device, structural repetition works best when it is used sparingly.

How sparingly, you ask with fear and trepidation? Two or three times, say, in the course of a manuscript, to draw the reader’s attention to particularly important passages. Even within the context of this short excerpt, see how much more effective the first use of structural repetition is if we remove the second.

Musette ran through the corridor, sped like the wind, fled as though lions were behind her and the open arms of a knight in shining armor in front. Didn’t she deserve her liberty, after all this time? She longed with the urgency of a sneeze for a life free of the incessant demands of boss, husband, co-worker, photocopy machine, cat. Clearly, she had an inherent right to breathe the fresh air of autonomy, unfettered by any limitations whatsoever.

Didn’t like it that way? Okay, let’s switch where the structural repetition falls — and while we’re at it, take out the cliché about the wind.

Musette sped through the corridor as though lions were behind her and the open arms of a knight in shining armor in front. Didn’t she deserve her liberty, after all this time? Didn’t she merit a life free of the incessant demands of boss, husband, co-worker, photocopy machine, cat? Didn’t she, in fact, have an inherent right to breathe the fresh air of autonomy, unfettered by any limitations whatsoever?

Was that a sudden gust of non-clichéd wind that just made my cat topple over, or did a significant minority of you just sigh gustily?
“I see that there are repeated words in the original version, Anne,” some of you point out, “but frankly, I liked it best. Surely the choice to incorporate structural repetition is a stylistic choice, rather than a matter best left up to an editor. Unless you have just inadvertently proven your point about not every reader’s liking every well-written narrative voice, and you are demonstrating yourself to be the kind of knuckle-dragging troglodyte who eschews the joys of literary fiction in favor of novels that — ugh — feature a plot?”

Actually, I’ve been known to read and enjoy both, oh ye quick to judge. What’s more, I’ve read plenty of literary fiction with strong plots and genre fiction that features beautiful language. So there.

But you are obliquely correct, oh sighers, that the original version above was more likely to have dropped from the fingertips of a writer with specifically literary aspirations than one who was aiming for a more mainstream readership. Since invocatory rhythms are quite common in poetry, this style turns up very frequently in novel and memoir submissions, particularly in those that are either literary fiction or are other types of manuscript written with a literary tone. It just sounds pretty, right?

“If the writing’s pretty on an individual sentence level,” sighers everywhere argue, “how could that be problematic in a submission?”

In several ways, actually. Rather than telling you why, let’s look at the single most famous example of invocatory prose in English literature, the opening to Charles Dickens’ A TALE OF TWO CITIES. Yes, I use this particular example fairly frequently, but humor me here: Dickens, bless his now-still heart, has provided us with a lulu of an example of why structural repetition is problematic in print.

Just for kicks, pretend that you have never seen it before, and try to read like an agency screener. To facilitate that laudable endeavor — and to give you the opportunity to judge for yourself whether all of this textual repetition provides a compelling entrée into the story that follows, here is not just the well-known opening, but the next page as well. As always, if you find you are having trouble making out the individual words, try holding down the COMMAND key and pressing + to enlarge the images.

Now, this voice is certainly distinctive, isn’t it? Hard to conceive of a more memorable opening, rhythmically speaking. But it’s also true that if these were the first two pages of a submission, virtually any modern-day Millicent would have rejected it by line three. Any guesses why?

If your hand instantly shot into the air, alerting me to your trenchant observation that it was because the first paragraph is one interminable run-on sentence — 119 words, connected incorrectly by commas, rather than semicolons, sacre bleu! — give yourself a gold star for the day.

Ditto if you zeroed in upon the apparently random capitalization of nouns, the criminal punctuation choices, the ubiquitous logical contradictions (yes, I know it’s meant to be ironic; think like a screener here and look for reasons to shout, “Next!”), the second paragraph written entirely in the passive voice, and the fact that two paragraphs into the piece, the reader still has absolutely no idea who the protagonist is or what’s going on.

And can’t you just picture an editor furiously scribbling in the margins: “Which was it — the best of times or the worst of times? It could hardly have been both. Commit to one or the other!”

Although any one of those perfectly valid objections might have prompted that cry of “Next!”, the structural repetition is what most pros would have noticed first. To see why, you stand up right now and take two steps backward from your computer monitor.

Notice the visual pattern? Millicent would have spotted it as soon as she pulled the first page of ol’ Charles’ manuscript out of the envelope.

Actually, if you’ve been revising for a while, you might have caught that the structural repetition problem without backing off. A solid tip-off: the verb to be appears 14 times within the first sentence.

It was the best of times, it was the worst of times, it was the age of wisdom, it was the age of foolishness, it was the epoch of belief, it was the epoch of incredulity, it was the season of Light, it was the season of Darkness, it was the spring of hope, it was the winter of despair, we had everything before us, we had nothing before us, we were all going direct to Heaven, we were all going direct the other way — in short, the period was so far like the present period, that some of its noisiest authorities insisted on its being received, for good or for evil, in the superlative degree of comparison only.

Yes, this is a level of verb variation that would make Millicent long for the comparatively challenging vocabulary choices of See Dick run, Jane. Run, Jane, run. Remember, though, it’s not just the repeated words and phrases that would raise professional readers’ weary eyebrows here: it’s the phenomenon of consecutive sentences being set up in the same way. No matter how great your high school English teacher told you this particular opening was, it’s dull for the reader to read the same It was X, it was Y sentence structure over and over again.

Or, indeed, any given sentence structure, if it is repeated often enough within too few lines of text.

Unfortunately, a lot of writers just adore structural repetition: it reads a bit like a prayer. It can provide a driving, almost galloping rhythm to a page. Many aspiring writers see that rhythm in the work of authors they admire and say, “By gum, I’m going to make my paragraphs read like that!”

And they do. Sometimes, they make their paragraphs read like that several times per page.

Don’t mind that loud rapping. It’s merely Millicent pounding her head against a wall, moaning, “Make it stop! Make it stop!”

That’s what happens when perfectly legitimate voice choices run amok. Like any magic trick,, repetitive structure loses its ability to charm when the reader sees it too often. After a surprisingly short while, it can start to come across less as an interesting stylistic choice than as a sort of narrative tic.

Don’t believe me? Okay, let me ask you: how many iterations of It was… did Dickens put you through before you first thought Oh, come on, Chuck; get on with it?

“But Anne,” lovers of percussive repetition beg piteously, “I just love my structurally repetitious opening page/paragraph/chapter. If I’m careful not to use this trick again anywhere in the manuscript, I can keep it, can’t I?”

I have a news flash from Millicentville: she sees a LOT of structurally repetitious openings; as with anything else she sees a dozen times a week, it’s probably going to be more difficult to impress her by this method. She’s also not particularly likely to believe that an opening redolent with repetition is a one-time narrative choice.

More often than not, when a manuscript opens with repetitive structure, it will continue with repetitive structure. That, alas, renders structural repetition dangerous to use in the first pages of a submission. Or book proposal. Agents and editors are just so used to this tendency that they’re all too likely — fairly or not — to conclude that to read on would be to be treated to the same type of sentence over and over, ad infinitum.

And that, my friends, is not invocatory; it’s soporific. Next time, I shall talk about ways to tell which is which in your writing, to figure out when invocatory rhythms will help your work.

Remember, Millicent seldom makes it all the way to the bottom of page one. That’s not a whole lot of lines in which to establish the originality and power of your voice.

Too bad our pal Chuckles blew his chance by repeating himself so much, eh? Keep up the good work!

Pet peeves on parade, part XXII: a stay of execution for some of those oft-doomed darlings, or, how can I tell which of this array of beauties to keep?

Because we have been concentrating quite heavily on craft issues of late — and very satisfying it has been, too — I had planned to devote Memorial Day weekend entirely to book promotion skills: author interviews, book trailers, guest blogs, and similar increasingly essential but seldom discussed wrenches for the first-time author’s toolkit. I do plan on getting to that material tomorrow. I realized this morning, however, that due to a heavily-booked last couple of days, I had left those of you in the throes of revision without a meaty homework assignment for the long weekend.

That will never do, will it? You might have to resort to sending out a few more queries, writing fresh pages, spending time with your kith and/or kin, or some other non-revision-related activity.

Practice is essential for building up the revision portion of that toolkit — and not just experience correcting one’s own manuscript on a sentence level. Being able to produce and polish a lovely sentence is, after all, the best-known part of an author’s job description. It often comes as a surprise to first-time novelists and memoirists, though, that most of the feedback agents, contest judges, and yes, even many editors give is not line-specific, but general requests to change precisely the type of patterns we’ve been discussing throughout this series: ramping up the showing, rather than the telling; tinkering with the pacing to keep the reader turning pages; revealing more character complexity in the dialogue, and so forth.

You didn’t think I’d been going on and on about these matters just to get your work past Millicent the agency screener, did you? Once you’ve landed the agent of your dreams, you will need to be able to translate sometimes rather vague revision requests (which can run the full gamut from cut out all of the semicolons to more should happen in the first 50 pages to does your protagonist’s brother absolutely have to be gay?) into concrete changes on the manuscript page. Sometimes very quickly.

How quickly, you ask with fear and trembling? Well, let me put it this way: my agent once called me on Thanksgiving to ask if I could rewrite the last third of a novel to an editor’s specifications before Christmas. I had it on her desk in three weeks.

Well may you react with horror — but if you’re not afraid of having your hair turn white on the spot, think about how much more difficult that would have been to pull off if I hadn’t already amassed a pretty hefty array of tools already honed in my writer’s toolkit.

That hellscape you just envisioned is a fairly standard experience for first-time novelists and memoirists, by the way. See why I am constantly badgering you to improve your revision skills, even if you happen to have a brilliant manuscript already in hand? You never know when you’re going to need ‘em.

Want to know what the most challenging part of revising on a deadline? Maintaining consistency of voice. It’s terribly easy to become so fixated on details — or on a certain part of the text — that one ends up with the requested changes, true, but also with a Frankenstein manuscript.

For those of you new to Author! Author!, a Frankenstein manuscript meanders in voice, tone, perspective, structure, and/or style; like the body parts of Dr. Frankenstein’s creature, the text may create the illusion of a whole entity, but it lacks the spark, the true-to-life continuity of a story told from beginning to end by a consistent authorial voice. Often, FM tendencies are the result of multiple or partial revision; even more often, they spring from a writer’s learning the tricks of the trade while writing a book.

How do I know? You’d be surprised how frequently the voice is quite different at the end of the manuscript than at the beginning. Or polished in parts, but rough in others.

Part of the point of this series has been to help you identify these FM tendencies in your own work. To that end, we’ve been talking a great deal about what to take out of a manuscript. Today, I would like to discuss what to leave in, or even what you might want to add.

And the masses rejoice! “Oh, that’s such a relief, Anne,” burnt-out revisers shout from every corner of the globe. “I’ve been working my fingers to the elbow, excising redundant text, spicing up my dialogue, and, of course, getting rid of all of those ands, all the while steeling myself for the inevitable moment when you would talk me into axing my favorite sentences and phrases. Because, after all, we’ve all been told time and time again to kill your darlings. But may I, kind lady, dare hope that you’re going to tell me to keep a couple of my favorites?”

Oh, you poor dears — no wonder you’ve been quivering in your boots. How could you not be, when writing teachers all over North America have been shouting at their students to axe their favorite bits of prose since practically the moment the classic piece of advice fell out of Dorothy Parker’s well-rouged lips sometime during Prohibition?

Well, I’m not going to do it. While a willingness to consider cutting even one’s pet bits is indeed useful, in my experience, most talented writers — published and as-yet-to-be-published alike — actually have a pretty good sense of the little things that shine in their manuscripts. They may not be right that all of the pretty bits are indispensable to the story they are telling, but they usually know which sentences sing and which merely croak.

Especially if the writer in question has been honing her craft, her pet parts of the text are likely to be telling little details, original, fresh, surprising specifics that bring joy to the eyes of agents, editors, and contest judges when they appear nestled in a manuscript — particularly on the first page of the text, where they act like miniature neon signs reading, “Hello? This one can WRITE!” causing Millicent to sit up straight for perhaps the first time that screening day and cry, “By gum, maybe I should not toss this one into the rejection pile.”

As lovely as eliciting this reaction is, there is more to catching a professional reader’s attention than a charming and detailed first page, I’m afraid. Of course, it’s a necessary first step to that reader’s moving on eagerly to the second, and the third, and so forth. Yet an initial good impression is not enough, however much writing teachers emphasize the importance of including an opening hook: as I believe I may have mentioned before in this series, in order to wow an agent into asking to see the entire manuscript, or into reading the entirety of the one you’ve already sent, the impressive writing needs to continue consistently throughout.

Ah, some of you formerly joyous revisers have wilted a bit, haven’t you, under the realization that keeping your favorite writing may require more work than cutting it wholesale? “But Anne,” you whimper, “how can a revising writer tell if the proportion of telling little details falls off throughout a manuscript enough to harm the narrative? More importantly for submission purposes, what density of telling details is enough to continue pleasing a professional reader’s eye?”

Excellent questions both, revisers: we’re all aware that the answer to the first is not necessarily the answer to the second, right? The first is largely a matter of personal style, after all, as well as the narrative expectations of a particular book category. Some writers wrangle generalizations better than others, after all. Generally speaking, though, the higher the proportion of exquisite detail to generalization, the more literary the writing; the more summary statements predominate, the lower the expected reading level of the audience.

And if the three repetitions of general in those last two paragraphs drove you crazy, I’m proud of you. You’ve been doing your editing homework.

In answer to the indignant collective gasp I hear echoing about the cosmos, literary is not simply a synonym for high-quality when we’re talking about writing. Let’s face it, there is plenty of good fiction writing that isn’t literary fiction — and plenty of excellent writing that isn’t literary. Just as the various striations of YA presume specific reading levels, literary fiction assumes a college-educated audience, or at any rate readers with a college-level vocabulary.

Thus, literary fiction is a book category, not a value judgment. It is quite possible, however, to bring a literary voice to other book categories — one sees literary-voiced memoir (like, for instance, Barbara Robinette Moss’ extraordinary CHANGE ME INTO ZEUS’ DAUGHTER from time to time, and many breakout novels are literary-voiced genre works.

That doesn’t mean, however, that a highly literary voice would be appropriate to every book category — or indeed, to every story. Only you, as author, can decide the best voice for your story, but in order to figure out the detail/generalization level appropriate to your book category, you can pick up some external clues.

How? By keeping up with the market in your chosen field, of course. I’ve said it before, and I’ll say it again: unless you are willing to read recent releases in your chosen book category — as opposed to what was coming out 5, 10, or 50 years ago — you’re going to have a much harder time querying, submitting, and yes, revising your own work.

Why? Because you won’t know what the current expectations and conventions are. Case in point: detail vs. summary statements.

Think about it: could you really get away with a summary sentence like, “She had legs that stretched all the way from here to Kalamazoo,” in a genre other than hardboiled mystery, bless its abstraction-loving fan base? (All right, I’ll admit it: one of the all-time best compliments I have ever received came from a writer of hardboiled; he commented on a dress I was wearing by telling me, “You look like trouble in a B movie.” I shall continue to cherish that to my grave.)

That’s one of the many, many reasons agents and editors tend to expect aspiring and published writers alike to read a whole lot of recently-published books within the category they write, in case any of you conference-goers out there had been wondering: to gain a working sense of the abstract/concrete statement ratio habitual readers of that type of book will expect to see. Some other reasons for keeping up with the latest releases: learning what that particular readership likes, figuring out what is and isn’t appropriate vocabulary for that specific readership, gaining currency with what’s being published right now, rather than in, say, 1858, and other practical benefits.

Some of you are sniffing disdainfully, aren’t you? “But Anne, none of this can possibly apply to me or my manuscript. My book is ART, you see: it is totally original. It cannot be forced into an artificial category.”

I can understand why you might feel that way, oh sniffers, but I have a news flash for you: there’s no such thing as a published book that doesn’t fall into a particular book category, no matter how genre-busting it may be. It’s simply how agents, publishers, and booksellers think of books. (If that is indeed news to you, and for some tips on figuring out which conceptual container might best house your manuscript for marketing purposes, please see the HOW TO FIGURE OUT YOUR BOOK’S CATEGORY posts on the archive list at right.)

Because that’s the case, the pros’ eyes tend to glaze over whenever an aspiring writer refuses — or even hesitates — to say to which category his manuscript belongs. To them, that just sounds like, you guessed it, a lack of familiarity with the current book market.

It’s not enough, though, to have a general (there’s that word again!) sense of what kind of writing is currently highly regarded in your chosen category. You also need to get a feel for your own personal style. Before you can decide where you want to pitch your manuscript on the detail scale, you need to figure out where the telling details already tend congregate in your work — and where they do not, so you may work toward overall voice consistency.

Which brings us right back to close textual analysis, doesn’t it? Funny how that worked out. Whip out your trusty marking pens, campers, and try this experiment:

1. Print out three chapters of your manuscript: the first, one from the middle, and one toward the end of the book.

Don’t use the final chapter; most writers polish that one automatically, doubtless the effect of our high school English teachers making us read the final pages of THE GREAT GATSBY so often. Second or third from the end will give you a better idea of your voice when you’re trying to wind things up.

Do print out Chapter 1, though, because if Millicent reads any of them at all, she will start there.

2. Make yourself comfy someplace where you will not be disturbed for a few hours, and start reading.

Easier said than done, of course, especially for those of you with young children gladdening your daily lives, but this isn’t relaxation: this is work. So don’t you dare feel guilty about taking the time to pore over your prose.

Yes, I know: your three-year-old will not be all that impressed that I said so. But you owe it to your writing to get to know your own voice.

3. While you are reading, highlight in nice, bright yellow every time the narrative gives information about a character in summary form.

Yes, this will be a phenomenal amount of work, but trust me: it will be worth it. Mark everything from Angelique felt envious to Maxine was a shop welder of immense proportions to Zeb was a compassionate soul, drawn to injured children, limping dogs, and soup kitchens.

4. Now use a different color of pen — red is nice — to underline any character-revealing information that the narrative conveys indirectly, through specific detail or speeches that demonstrate a characteristic or an environment that is reflective of a character’s internal mood.

Remember, you are not judging the quality of the sentences here — you are looking for passages that encourage the reader to draw his or her own conclusions about what the character is like, rather than simply stating it as a fact. To revisit the trio from above, red-marked sentences might include:

Unable to contain herself, Angelique surreptitiously poked her rival with a pin, or

Maxine’s broad shoulders barely fit through the doors to her metal shop, or even

Zeb was late for work again, having been sidetracked by a child’s scraped knee, a search for the same little girl’s lost cocker spaniel, and the absolute necessity to track down and fund the homeless person he had been forced to overlook yesterday because he’d already given away the last dollar in his pocket.

Beginning to spot some patterns? Good. Now that your manuscript is color-coded to tell you at a glance what your summary statement/telling detail ratio is, how consistent is your narrative being about preserving those proportions?

That’s a big concept to get your mind around, I know. While you’re pondering, let’s get back to that colorful text.

5. Now that you’ve identified these different species of sentences, double-check immediately before and after the indirect indicators in red for summary statements telling the reader precisely how these dandy little details should be interpreted. Circle bottom-lining conclusion statements in a third color — let’s say green, and complete the Rastafarian triumvirate.

Such summaries tend to lurk in the environs of telling details — usually unnecessarily, as vivid details by definition speak for themselves. You may find them elsewhere, naturally, but these will be the easiest to spot.

6. For each green-marked sentence, ask yourself, “Self, is this summary absolutely necessary here, or does the indirect statement cover what I wanted to say? Could it in fact be cut, and would the manuscript be both shorter and better for it?”

Applied consistently, this question can strip a lot of unnecessary verbiage from a manuscript relatively painlessly. It’s a good strategy to know, because it’s often difficult for a writer to notice redundancy on a page he has written himself — from a writerly perspective, saying something in two different ways often just looks like creative emphasis.

Or — and this is more common — the writer may not trust the reader to draw the correct conclusion from the more delicate indirect clues, and so rush to provide the logical extrapolation. But readers are pretty smart, especially those lovers of good writing (in every sense) who dote on marvelously revealing details.

Again, that’s not to say that specifics should trump generalities every time. Abstract statements that bottom-line a character’s ever-changing array of feelings, thoughts, and actions (Eileen was morose, Teddy was sexy, Elvira was a tall, cool hunk of woman, etc.) can save a lot of time in a narrative, quickly providing the reader a sense of what’s going on and who is doing it.

Sometimes, that can come in very handy. In a scene where the action is pretty mundane, a swift summary statement like Bernadette spent the next fifteen hours yawning her way through book shelving can act like a fast-forward button for the narration.

The effect can be even greater when there is a lot going on. When an action scene suddenly requires fifteen thugs to jump Our Hero, describing each one individually and in a nuanced manner would slow the scene down to a crawl — which, inevitably, would convey the impression that O.H. is being beaten up in slow motion.

Fast-paced action deserves fast-paced narration, short, tense sentences that get the blood pumping. Short, to-the-point summary statements like Edmund ducked sideways. The anvil thudded into the wall behind him. may well serve the scene better than long, lyrical, detail-rich ones that go on for line after line.

Oh, you wanted a second example? Okay: As Edmund veered sideways, the rush of air by his ear, percussive and harsh, reminded him of that long-ago summer of fireflies and BB guns, unwashed berry juice climbing up to his elbows after braving the bees for an afternoon’s blackberrying. Funny, how something as dangerous as an anvil flung at his head could awaken such long-dormant memories.

Yes, the second set was prettier — but which would work best for this SPECIFIC action scene in this SPECIFIC story, told in this SPECIFIC voice?

By contrast, concrete characterization statements depict what a character is saying, doing, feeling, and so forth in a particular moment. In a story told primarily through concrete statements — and again, writing with a high concrete/abstract ratio is considered more stylistically sophisticated — the narrative expects the reader to draw conclusions about what characters are like based upon an array of specific actions, feelings, words, and so forth, rather than simply providing a summary statement.

Does that distinction sound at all familiar? It should: this is yet another manifestation of everyone’s favorite writing bugbear, the difference between showing and telling.

Yet constructing an effective narrative is not as simple as eschewing the latter and embracing the former. Obviously, every manuscript ever produced needs both abstract and concrete statements. Because, let’s face it, there’s no such thing as a chapter, paragraph, or even sentence that’s appropriate for every book in which the creative mind might choose to have it appear.

Context matters — and so does book category.

Avoiding summary statements wherever possible may serve a high-end women’s fiction writer very well, for example, but actually harm certain types of genre novel. The rash of semicolons that might make an academic book look learned is unlikely to fly in a Western — but you’d be surprised how much more acceptable it would be in a science fiction novel. And while those of us devoted to literary fiction do occasionally marvel at a story intended exclusively for a college-educated readership written in very simple language, the vocabulary range of most literary fiction is quite different from that of well-written YA.

But you knew that already, right?

And don’t even get me started on how much more acceptable rampant summary statements are in most types of nonfiction than in fiction. Memoirs in particular tend to rely upon them pretty heavily.

Why? Well, as a reader, how eager are you to hear every detail of what happened to even a very interesting real-life narrator over a two-year period? If a memoirist steers too clear of abstract statements like Auntie Mame’s famous My puberty was bleak, she’s going to end up expending quite a bit of precious page space on illustrating just how bleak it was, right?

So much for my carefully non-judgmental speech on the subject of abstract vs. concrete statements. It is worth noting, though, that on any given day of manuscript-screening, your garden-variety Millicent sees a whole lot more summary sentences than concrete ones.

Which, obviously, can render a genuinely original detail quite a refreshment for weary professional eyes. So, generally speaking (ooh, there’s that pesky word again), if you can increase the frequency with which such concrete details appear, you’ll be better off.

Ready to take gander at the ratio in the manuscript you’ve been submitting — or are planning to submit to professional scrutiny anytime soon? Fantastic. Let’s revisit those yellow, red, and green pages from above. But this time, grab a fourth color of pen –- how would you feel about embracing something in the purple family?

7. Mark all the sentences where your protagonist (or any other character whose thoughts are audible to the reader) thinks a response to something that has just happened, instead of saying it aloud or the narrative’s demonstrating the reaction indirectly.

Remember, you’re not judging the quality of writing by determining what to highlight, or sentencing any given observation to the chopping block by marking it. You are simply making patterns in the text more visible.

These kinds of sentences are hard to show out of context, so let me mark up a bit of text for you. The sentences destined for purple overcoats are in caps:

I CAN’T BELIEVE SHE SAID THAT, ZACHARY THOUGHT.

WHY WASN’T HE ANSWERING? “What’s wrong?” Nanette asked, rubbing her tennis-sore ankles. “Are you feeling sick to your stomach again?”

OH, WOULD ONLY THAT HIS ONGOING DISSATISFACTION WITH THEIR MARRIAGE STEMMED FROM A SOURCE AS SIMPLE AS NAUSEA. WAS HIS WIFE HONESTLY SO SOULLESS THAT SHE COULDN’T FEEL THEIR WELL-MANICURED LAWN CREEPING UP THE DOORSTEP TO SMOTHER THEM IN SEDUCTIVE NORMALCY? “No, I just had a long day at work.”

Everyone clear on the distinction I’m making here? Excellent. Now humor me a little and dig up a fifth color of pen — blue, anyone?

8. Mark any sentence where your protagonist’s reactions are conveyed through bodily sensation of some sort. Or depicted by the world surrounding him, or through some other concrete detail.

You’re probably going to find yourself re-marking some of the red sentences from #4, but plow ahead nevertheless, please. Starting to notice some narrative patterns? Expressing character reaction via physicality or projection is a great way to raise the telling little detail quota in your manuscripts.

Does this advice seem familiar? It should, for those of you who regularly attend writing workshops or have worked with an editor. It is generally expressed by the terse marginal admonition, “Get out of your character’s head!”

I wish feedback-givers would explain this advice more often; too many writers read it as an order to prevent their characters from thinking at all, ever. But that’s not what get out of your character’s head! means, at least not most of the time. Generally (ooh!), it’s an editor’s way of TELLING the writer to stop telling the reader about the character’s emotional responses through dialogue-like thought. Instead, (these feedback-givers suggest) SHOW the emotion through details like bodily sensation, noticing a significant detail in the environment that highlights the mood, or…

Well, you get the picture. It’s yet another way that editors bark at writers, “Hey, you — show, don’t tell!”

What will happen to your manuscript if you take this advice to heart? Well, among other things, it will probably be more appealing to Millicent — because, believe me, protagonists who think rather than feel the vast majority of the time disproportionately people the novels submitted to agencies and publishing houses.

And when I say vast majority of the time, I mean in practically every submission they receive. To put it bluntly, a novel or memoir that conveys protagonist response in ways other than thought a significant proportion of the time will at very least enjoy the advantage of surprise.

Why are characters who think their responses — essentially summarizing what they might have said or done in response instead of saying or doing it — so very common, especially in memoir? One theory is that we writers are so often rather quiet people, more given to thinking great comebacks than saying them out loud.

A girl’s best friend is her murmur, as Dorothy Parker used to say.

Or maybe we just think our protagonists will be more likable if they think nasty things about their fellow characters, rather than saying them out loud. That, or there are a whole lot of writers out there whose English teachers made them read HAMLET one too many times, causing them to contract Chronic Soliloquization Disorder.

Whichever it is, Millicent would be happier about most submissions in practically every book category if they exhibited this type of writing less. Done with care, avoiding long swathes of thought need not stifle creative expression.

Don’t believe me? Okay, let’s revisit our little scene of domestic tranquility from above, this time grounding the characters’ reactions in the flesh and the room:

By the time Nanette was midway through her enthusiastic account of the office party, Zachary’s stomach had tied itself into the Gordian knot. The collected swords of every samurai in the history of Japan would have been helpless against it.

“Zach!” Nanette’s back snapped into even greater perpendicularity to her hard chair. “You’re not listening. Upset tummy again?”

He could barely hear her over the ringing of his ears. He could swear he heard their well-manicured lawn creeping up the doorstep to smother them in seductive normalcy. The very wallpaper seemed to be gasping in horror at the prospect of having to live here a second longer. “I just had a long day at work.”

See the difference? The essentials are still here, just expressed in a less obviously thought-based manner. The narrative’s gotten out of the characters’ heads — and stepped right into their bodies.

Go back and take another look at your marked-up manuscript. How blue is it? How heavily purple is that prose? (Sorry; I couldn’t resist setting you up for that one.)

No, but seriously, it’s a good question: all of the types of sentence you just identified are in fact necessary to a successful narrative, so ideally, you have ended up with a very colorful sheaf of paper. Using too many of one type or another, believe it or not, can be boring for the reader, just as using the same sentence structure over and over lulls the eye into skimming.

If you doubt this, try reading a government report sometime. One declarative sentence after another can be stultifying for the reader.

The telling details of your manuscript will be nestled in those red- and blue-marked sentences, Note how frequently they appear in your chapters. If you find more than half a page of yellow and/or purple between patches of darker colors, you might want to go back and mix up your abstract/concrete ratio more.

If you find any pages that are entirely yellow and/or purple, I would suggest running, not walking, to the nearest used bookstore, buying three or four battered paperback editions of books that sell well in your chosen genre, and carting them home to perform the five-marker experiment on them. Could you revise your manuscript so that the color ratio in it replicates that in those books?

Yes, this is a time-consuming exercise, now that you mention it. A test like this is rather nerve-wracking to apply to your own work, but it’s a great way to start getting in the habit of being able to see your pages as someone who does not know you might. (If you want to get a REALLY clear sense of it, trade chapters with a writer you trust, and apply the same experiment.)

At the end of it all, however, you will have a much, much clearer idea of what your narrative voice sounds like — not only at its best and worst, but when it is just trying to do its job. You’ll gain a sense of what it sounds like when you’re tired or excited, trying desperately to get a thought down before it vanishes or having the time to allow your words to revel in their own beauty.

Once you gain that working sense of your own voice, editing your own work will become easier, I promise. You’ll be able to spot the telltale signs that the narrative has slipped away from it; you may even come to feel the drift before the words hit the page.

It sounds like magic, but it isn’t: it’s narrative consistency.

What does all of this have to do with saving your darlings? Plenty. How wonderful would it be if your best writing did not jump out at the reader because the entire manuscript was that good?

A lovely thought, isn’t it? Your darlings will be comfortably housed in a strong, sure narrative; they may — and this happens more than one might think — be your pets because they are already written in your personal narrative voice.

But you won’t know that for sure until you know your voice inside out, will you? Keep up the good work!

The Short Road Home, part V, in which we have apparently all died and gone to Concrete Example Heaven

On and off for the last couple of weeks, we’ve been talking about that graveyard of literary tension and promoter of telling rather than showing, the Short Road Home. The SRH haunts novel and memoir submissions in a variety of disguises. Oh, it’s a versatile narrative trick, easily applied to a broad range of manuscript environments; it is as proficient at strangling burgeoning character development as it is at draining the tension out of a scene.

Most often, of course, it manifests as a scene or plot that resolves conflict practically the nanosecond it appears — astonishingly often without any effort whatsoever on the part of the protagonist. Indeed, conflict-avoidance is so popular amongst fictional characters that protagonists tend to favor resisting the status quo even in their minds.

Oh, you may laugh, but you’d be surprised how often those of us who read for a living will watch, stunned, as a protagonist briefly considers perhaps maybe eventually doing or saying something — only to be interrupted by another character rushing in to prevent even the thought of discord from developing into something that might be interesting for the reader to watch. The swiftness with which these tension-averse white knights dispatch nascent conflict is sometimes downright eerie, begging the question: is this character a participant in this story, or is he reading it?

You’d like a concrete example, wouldn’t you? We aim to please.

If only I had the courage to speak up, Tyrone thought, seething. I’ve put up with my repressive boss’ arbitrary pronouncements for years. Maybe today is the day I should stop being a doormat. Maybe today is the day I shall start speaking up for myself. Maybe today is…

“Oh, and before we end the meeting,” Artie said, smoothing his notes, “I’ve been sensing some disgruntlement in the face of our recent reorganization. Perhaps I’ve been a trifle, well, if not insensitive, then at least myopic. I’d like to hear your concerns, though.” He turned to Tyrone. “I’ve always valued your opinion, Ty. How do you think we could improve our beloved department?”

Beaming, Tyrone wrestled a binder stuffed with suggestions from his backpack. “I thought you’d never ask!”

Ah, but the reader wishes you hadn’t asked, Artie. Characters who read one another’s minds are notorious tension-deflaters.

They are also prone to cutting off plot possibilities before they have a chance to do more than poke their wary heads above ground. Had Artie not magically deduced his employees’ irritation from some clue that the narrative has not elected to share with the reader — if, in other words, the conflict were shown by any means other than Tyrone’s thoughts telling us about them — maybe then Tyrone would have had to take the longer, more arduous road of addressing the problem by — wait for it — addressing the problem. As in out loud, in a manner that might have provoked an interesting, true-to-life scene.

We met another favorite guise of the Short Road Homes in my last post: telling a story out of chronological order, drowning any possible suspense about the outcome of a conflict by revealing it at the beginning of the scene, rather than the end. Even if foreshadowing is vague, it can sap the reader’s impetus to wonder what is going to happen next — a pity, really, as its purpose is ostensibly to raise suspense.

All too soon, our happy mood vanished, ruining the rest of the day. If I’d known what was going to happen next, I would have grabbed the oars and rowed like mad for the shore.

“Where’s the sun gone?” Barbara asked suddenly.

Meg’s hat blew off before she could reply. “The sky looks mighty ominous. I’d always thought that the clouds spelled DOOM was just an expression.”

I pointed a shaking finger over the side. “Are those sharks?”

Even minor chronology-surfing can lead to confusion. Since — chant it with me now, long-term readers — unless the narrative specifically states otherwise, events are presumed to occur in the order they appear on the page, what may appear to the writer as just a little creative sentence restructuring may genuinely muddy the reader’s conception what’s going on.

How? By inverting cause and effect temporally. Compare, for instance, this inadvertently time-traveling piece of prose:

Horrified, James jumped backward as Fred took a swing at him. He narrowly avoided being grabbed by George’s flailing hands. Wincing at the pain, he managed to spot and catch Bob’s crowbar before it connected with the side of his head.

With this more straightforward narration, in which cause precedes effect and our hero does not react before he perceives a threat:

Abruptly, Fred took a swing at him. Horrified, James jumped backward, practically into George’s flailing hands. As he veered under the large man’s arm, he spotted Bob wielding a crowbar. He managed to catch it just before it connected with the side of his head. His palm exploded with pain.

Much clearer, is it not? It’s also less of a Short Road Home: the reader is not told up front that something that has not yet occurred on the page will cause our hero to wince with pain.

Sometimes, though, a writer’s effort to make a series of actions clear can also send the narrative sliding down the Short Road Home. The pros like to call this over-explaining, for reasons I hope the next example will render obvious.

Darlene took a deep breath, so she could speak at length. This was taking a surprising amount of explanation. “It’s over, honey.”

Morgan’s eyes filled with tears. Confusion suffused his soul as he struggled to plumb her meaning. “But I don’t understand!”

He honestly didn’t. His perplexity continued even after Darlene’s quiet, “How is that possible, after the last hour and a half of conversation?” He just couldn’t wrap his mind around what she was trying to say. Was there a subtext here? Was it a subtle joke? Why was she telling him this now? Had there been a series of clues he had not caught, and if so, would she merely get angrier if he asked her for an itemized list?

He reached for his notebook, so he could consult his notes from the previous hour. “You’ll have to explain this to me again. What is it you’re trying to say?”

A tad redundant, is it not? Again, over-explanation is typically a show, don’t tell problem: by swamping the character-revealing and plot-resolving action with a welter of extraneous explanation, not only is the pacing slowed, but the central point of the scene (in this case, Morgan’s refusal to accept a painful rejection) gets a bit lost. So while all of that repetitive bottom-lining of his emotional state may have seemed to the author like necessary clarification, naming those emotions rather than showing them renders the scene less effective.

Too-heavy explanations are also, as we discussed in this series, rather insulting to Millicent’s intelligence. I’ve wrested a bit of comedy from Morgan’s cluelessness in order to make this scene more fun to read, so the distrust of the reader’s ability to draw quite obvious conclusions about a fairly straightforward situation may not have leapt out at you. It’s not as though this scene deals with unfamiliar concepts, however; for most readers, confusion — and, by extension, denial — don’t really require much introduction.

Don’t believe me? Okay, here’s that same scene again, allowing the characters’ actions and feelings to speak for themselves.

Darlene took a deep breath. “It’s over, honey.”

Morgan’s eyes filled with tears. “But I don’t understand!”

Her grip tightened on the back of the chair so much that her knuckles grew white, but she held her voice quiet. “How is that possible, after the last hour and a half of conversation?”

Every inch of his intestines quivering, we reached for his notebook, so he could consult his notes from the previous hour. There had to be a way to talk her out of this, but how?

“I just want to make sure I get your reasoning.” He measured the time between his words with care: long enough to buy him some time, not long enough to make her want to leap into his mouth with pliers to drag the reluctant syllables out. “You know, so I can explain your departure to our friends.”

Axing all of that extraneous explanation certainly bought some room for character development, didn’t it? That would come as a surprise to most Short Road Home-wielders, I suspect: the urge to summarize tends to be a side effect of the impulse to speed things up. Or, as is often the case in these decadent days of relatively low word counts — can you imagine, say, THE WORLD ACCORDING TO GARP, if it had to be cut down to under 100,000 words before it could be marketed? — of a clawing, terrified need to slash fifty pages from an over-long manuscript.

Besides, as we have just seen, summarizing emotional turmoil, that oh-so-common manifestation of the Short Road Home, just isn’t as effective on the page as demonstrating it through specific feelings, actions, and thoughts. Not merely labeling the emotion in question. mind you — Jack was sad is not, after all, a particularly evocative description — but by showing it in detail and trusting the reader to draw the correct conclusion about Jack’s emotional state.

He roved listlessly around the living room, straightening a grinning china dwarf here, making sure a magazine’s edge was exactly parallel to the edge of a table there. Calla might not be alive to notice anymore, but that was no reason to relax her standards. Someday, a guest might stop by, as they did in the old days.

You wouldn’t want to convey the impression that Millicent is intellectually incapable of extrapolating as self-evident a conclusion as Jack was sad from that little gem, would you?

The SRH’s almost magical ability to minimize the emotional impact of a moment is not limited to tragedy, either; as we saw in the Pet Peeves on Parade series, over-explanation’s ability to declare a joke dead on arrival is legendary. Less discussed amongst writers but equally pernicious, skating too quickly past the comic constituent parts of a potentially funny scene can also be fatal to humor.

Just as suspense is more effective if the reader has time to absorb the ambient threat and imagine a negative outcome before something bad happens — Alfred Hitchcock was apparently fond of saying that the best way to render a scene that will end with an explosion was not to show the participants running around in terror of the imminent bang, but to let the audience a bomb was concealed under a table, then let them squirm while a couple of characters who have no idea they’re dining atop a bomb chat about something else entirely — a funny build-up tends to have more impact if the reader has a chance to appreciate a series of amusing details.

Premises in particular are susceptible to death by Short Road Home. Take a gander:

Surely, nobody would care if she took just one apricot from that beautiful pile. Gerri reached out, grabbed a small one near the bottom — and then the entire pyramid disintegrated, sending fruit flying everywhere.

Now, this might have been funny, had it been fleshed out a bit more. Indeed, it wouldn’t be particularly difficult for a comedy-minded reader to picture what probably happened here in hilarious detail, based upon this scant description. But it’s not the reader’s job to contribute material to a book’s humorous scenes; it’s the writer’s job to write them so that they are funny.

Surprisingly often, simply drawing out the suspense will make a SRH scene funnier. Let’s apply the Hitchcock principle to poor Gerri’s plight.

The largest pile of fruit she had ever seen loomed before her, five feet high if it was an inch and nearly as broad at the base. Each perfectly ripe apricot selflessly offered a flawless furry cheek to the public, an arc of delicious roundness identical to its neighbor. She leaned forward to examine it more closely, convinced that the fruit must be fake.

A slap of immistakable sweetness assured her nose that her brain was dead wrong. She had to force herself not to plunge her face into the wall of fruit.

She circled the display, running her fingers as close to the base as she dared. The Great Pyramid of Giza could hardly have been arranged with greater care, but Gerri felt this was an even greater human achievement: presumably, the ancient wonder had taken years; judging by the heady aroma, this must have been the work of a single breathless hour. She could not even begin to imagine the bravery it must have taken to place that last crowning apricot, the cherry on the top of the world’s most precariously-constructed sundae.

Her mouth was watering; clearly, it had been a mistake to swoop in for a sniff. A reasonable adult would simply have accepted that the pyramid was what the sign next to it said it was — the Arabella County 4-H Club’s summer project, an attempt to beat a three-decade-old youth timed fruit-piling record — and moved on. A reasonable adult, however, would not have been forcibly deprived of stone fruit for the last two years by a husband who wouldn’t have known a vegetable had it leapt into his mouth of its own accord, screaming, “Eat me, Harold!”

She slipped around back, where theft would be least likely to be noticed and selected her prey. A smallish one, with a dent in it so minuscule that Sherlock Holmes might have missed it. Millimeter by millimeter, she edged it out of its space in the middle of the tenth row.

She slipped it into her pocket, cool and damp, just before a fresh group of State Fair-goers stampeded into the room. “Isn’t it magnificent, Ma?” a little girl with pigtails gushed.

Palpitating but proud, Gerri wove her way through the crowd. “Oh, excuse me,” she told a gawker. “I didn’t mean to step on your shoe.”

He waved away her concern a little too hard; Gerri had to duck to avoid his elbow. Her elbow knocked into something soft and prickly.

The Zucchini Through the Ages display went crashing to the ground, its hand-lettered signage squashing thirty squash into pulp in an instant. Small zucchini rolled under bystanders’ feet, sending strangers careening into one another. The first-place entry, a monster of eighteen pounds, flew straight into the stomach of a passing Girl Scout, forcing a stream of fairground goodies out of her astonished mouth. In the ensuing stampede, every single entry in the legume category was trampled beyond recognition.

Only the apricot mountain was spared. “I knew they must have glued it together,” Gerri muttered, slipping form the tent.

Oh, hadn’t I mentioned that comedy also benefits from a healthy dose of surprise?

No, but seriously, folks, after a lifetime of reading and a couple of decades of reading professionally, it’s my considered opinion that the overwhelming majority of aspiring writers don’t have a clear idea just how much the average reader enjoys savoring conflict — or how much more trivial an easily-solved problem appears on the page than one with which the protagonist must struggle for pages or chapters on end. Just as an Idiot Plot that is resolved the instant someone thinks to ask Aunt Joyce her ring size is less than dramatically satisfying, a plot resolved by a Short Road Home tends to leave readers feeling a trifle underfed.

They came for a full meal, you know, with many succulent courses. How could they not be disappointed when a narrative merely gives them a glimpse of a nicely-fried brook trout, then whisks it away untasted? Or when the waiter spends the whole meal boasting of the spectacular dessert, then brings out a single dry cookie for the entire table to share?

And that’s non-professional readers’ reaction; the pros are even more ravenous for luscious, richly-depicted narrative tension. Just because Millicent spends her days grazing upon query letters and munching on synopses doesn’t mean she wouldn’t be thrilled to have a feast come submission-reading time.

Please say you’ve grasped the concept, because this metaphor is beginning to whimper under its explanatory load.

An excellent place to start sniffing around for instances of the Short Road Home: when a narrative begins to stray close to stereotype territory. Why? Well, stereotypes thrive upon generalization, so when they rear their ugly heads, they tend to nudge the narrative toward summary statements, conclusions, and the like. Grounding a scene or argument in the specific has the opposite tendency.

Straying toward the general is particularly likely too occur in memoirs and novels where writer is working overtime to make a character likeable — or always right. A character that is never wrong is, among other things, predictable; when predictability has pulled up a chair and seated itself in a scene, tension tends to take a flying leap out the nearest window.

Too theoretical? Okay, let’s take a peek at the offspring one of the more common marriages of stereotype and Short Road Home: the troubled child of the protagonist, particularly if it’s a teenager.

At the very mention, Millicent has already started cringing in her cubicle in New York, I assure you. The TCoP crosses her desk so frequently in adult fiction and memoir that she can scarcely see a character in the 13-19 age range without instinctively flinching and crying out, “Don’t tell me — she’s going to be sullen.”

You’re quite right, Millicent — 99% of the time, she will be. And rebellious. Not to mention disrespectful, sighing, and eye-rolling.

Yes, troubled kids and teenagers across the land have been known to do these things from time to time — but remember what I said a few paragraphs back about predictability? When Millicent encounters the rare non-stereotypical teenager in a submission, it’s a red-letter day.

Do I sense some shifting in chairs out there? “Yeah, yeah,” I hear a few seasoned self-editors piping, “I already know to avoid stereotypes, because Millicent sees them so often and because the whole point of writing a book is to show my view of the world, not a bunch of clichés. What does this have to do with the Short Road Home?”

In practice, quite a bit: it’s very, very common for a narrative featuring a TCoP to expend considerable (and usually disproportionate) time explaining the kid’s behavior — and, often, justifying how the protagonist responds to it. Unfortunately, this rush to interpret not infrequently begins as early as the first scene in which the TCoP is introduced.

What might this look like on the first page of a manuscript, you ask? A little something like this — and see if you can catch the subtle narrative bias that often colors this stripe of the Short Road Home:

When hard-working Tom Carver opened his front door, arriving home late from work at the stuffed animal plant yet again, his daughter, Malia, was once again refusing to speak to him. Glaring at him silently with all of the dastardly sneer her fifteen-year-old face could muster, she played with her spiky, three-toned hair until the third time he had considerately asked her how her school’s field trip to the State Fair had gone.

“Like you care!” she exclaimed, rolling her eyes dramatically. She rushed from the room. Small chunks of what appeared to be zucchini flew from her hair onto the beautifully-swept floor.

The now-familiar sound of her slammed bedroom door ringing in his ears, he wandered into the kitchen to kiss his adored wife on her long-suffering cheek. “Criminy, I’m tired of that, Alice. Someday, all of that slamming is going to bring the house tumbling down on our heads. I’ll bet she hasn’t done even one of her very reasonable load of daily chores, either. Why did good people like us end up with such a rotten kid? I try to be a good father.”

Alice shook her head good-humoredly as she dried her wet hands on a dishtowel, slipped an apple pie in the oven, settled the home-make brownies more comfortably on their plate, and adjusted the schedule book in which she juggled her forty-seven different weekly volunteer commitments. “Well, Tom, she’s not a bad kid; she just acts like one. Malia’s felt abandoned since her mother, your ex-wife, stopped taking her bipolar medication and ran off with that bullfighter three months ago, totally ignoring the custody schedule we invested so many lawyers’ bills in setting up. She doesn’t have any safe outlet for her anger, so she is focusing it on you, the parent she barely knew until you gained the full custody you’d been seeking for years because you loved her so much. All you can do is be patient and consistent, earning her trust over time.”

Tom helped himself to a large scoop of the dinner he had known would be waiting for him. “You’re always right, Alice. I’m so lucky to have you.”

Well, I’m glad that’s settled. No need to read the rest of the novel, is there?

That’s a shame, because this story contains elements of a good character-driven novel. There’s a wealth of raw material here: a new custody situation; a teenager dealing with her mother’s madness and affection for matadors; a father suddenly thrust into being the primary caretaker for a child who had been living with his unstable ex; a stepmother torn between her loyalty to her husband and her resentment about abruptly being asked to parent a child in trouble full-time.

But when instant therapy sends us veering down the Short Road Home, all of that juicy conflict just becomes another case study, rather than gas to fuel the rest of the book. The result: what might have been an interesting scene that either showed the conflict (instead of telling the reader about it), provided interesting character development, or moved the plot along.

In other words, it becomes a scene that the writer should consider cutting.

Effectively, the narrative’s eagerness to demonstrate the protagonist’s (or other wise adult’s) complete understanding of the situation stops the story cold while the analysis is going on. Not for a second is the reader permitted to speculate whether Malia’s father or stepmother had done something to provoke her response; we hardly have time even to consider whether Tom’s apparently habitual lateness is legitimate ground for resentment.

Again, that’s a pity. If only Tom had said, “You know, instead of avoiding conflict, I’m going to maximize it, to make things more interesting for the reader,” and gone to knock on Malia’s door instead of strolling into the kitchen for coffee and soporific analysis, we might have had all the narrative tension we could eat.

Heck, had the narrative just gone ahead and shown Tom and Alice being patient and consistent, earning Malia’s trust over the next 200 pages, the reader MIGHT have figured out, I think, that being patient and consistent is a good way to deal with a troubled teenager. But no: the subtle Short Road Home demands that the reader be told what to conclude early and often.

Whenever you notice one of your characters rationalizing in order to sidestep a conflict, ask yourself: am I cheating my readers of an interesting scene here? And if you find you have a Jiminy Cricket character, for heaven’s sake, write a second version of every important scene, a draft where he doesn’t show up and explain everything in a trice, and see if it isn’t more dynamic. Do this even if your book’s Jiminy Cricket is the protagonist’s therapist.

Especially if it’s the therapist. Millicent sees a lot of those.

If you are writing a book where the protagonist spends a significant amount of time in therapy, make sure that you are balancing two-people-sitting-in-a-room-talking scenes with scenes of realization outside the office. And make sure to do some solid character development for the therapist as well, to keep these scenes tense and vibrant.

If you are in doubt about how to structure this, take a gander at Judith Guest’s excellent ORDINARY PEOPLE, where most of the protagonist-in-therapy’s breakthroughs occur outside of the analyst’s office. The therapist appears from time to time, punctuating young Conrad’s progress toward rebuilding his life after a particularly grisly suicide attempt with pithy questions, not sum-it-all-up answers.

Hey, here’s a radical thought for revising a Short Road Home scene: what if you tinkered with it so your protagonist learns his lessons primarily through direct personal experience — or through learning about someone else’s direct personal experience told in vivid, tension-filled flashbacks?

Sound familiar? It should: it’s a pretty solid prescription for a narrative that shows, rather than tells.

Which, at the risk of wearing out some pretty time-honored writing advice, you should strive to do as often as possible — at least in your first book, where you really need to wow the pros. After you make it big, I give you permission to construct a plot entirely about a couple of characters sitting around talking, motionless.

But for heaven’s sake, leave that pyramid of apricots alone; it’s not as solid as it appears to be. Keep up the good work!

The Short Road Home, part IV: Tommy! Watch out for that bear lurking at the end of this post! Tommy!

I can’t quite decide whether I am profoundly sorry or oddly pleased that I’ve been digressing from our series-within-a-series on the Short Road Home, my pet name for a storyline that introduces a conflict only to resolve it immediately, sometimes before the reader has a chance to register that the problem raised is at all serious. Yes, too-swift fixes make it harder for the reader to root for the protagonist — or, when faced with a truly galloping case of SRH, to perceive any build-up of narrative tension at all — but since authorial distrust in readers’ attention spans often underlie these apparently self-solving problems, perhaps jumping around between topics has been appropriate.

Those of us who read for a living, however, may be trusted to have attention spans longer than a third grader hopped up on a quart of cola and half a dozen brownies. Oh, our old pal, Millicent the agency screener, may be conditioned to reject most manuscript submissions on page 1, but once she gets into a story, she, like any other reader, wants to see it played out in a satisfying manner.

That seems to be news to an awful lot of submitters, however. You’d be amazed at how often not small, potentially character-revealing conflicts are resolved practically as soon as they appear on the page, but major ones. In book openings, it’s not even all that uncommon to use one of these near-momentary crises as a clumsy means of introducing necessary backstory, as the following sterling piece of dialogue illustrates.

“It’s gone!” Marvin scrabbled around frantically in the dry grass next to his sleeping back, careless of the rattlesnake producing marimba rhythms on its tail a scant yard away. “My beloved late great-great-grandfather’s pocket watch!”

Antoinette gasped. “Not the one traditionally passed from dying father to eldest son for a century and a half, and entrusted to you by your father on his deathbed not four weeks ago?”

“The same.” A silver disk flew through the air at his head, glinting in the firelight. “Why, here it is! Where did it come from?”

The sleeping bag on the far side of the fire jackknifed. Jesse’s red face peered out of the opening. “You dropped it three hours ago. I was waiting for you to notice.”

Marvin flung his arms around Antoinette. “My legacy is safe!”

“What kind of idiot brings an heirloom mountain climbing?” Jesse muttered, trying to regain a comfortable position.

Yes, this is Hollywood narration — all three characters are already aware of the significance of the watch, so the only conceivable motivation for Antoinette and Marvin to explain it to each other is so the reader can hear what they say, right? — but you must admit, it is a darned efficient means of shoehorning the watch’s importance to Marvin into the story. It might not even come across as heavy-handed, if the reader had time to absorb the loss, understand its significance through Marvin’s reaction, and gain a sense of what might happen if the watch were never found.

But here, the darned thing reappears practically the instant Antoinette finishes filling the reader in about it, killing any possible suspense before it’s had time to build. Does that strike you as a narrative strategy likely to entrance a professional reader? Or is it likely to seem like the Short Road Home to anyone with an attention span longer than a drunken gnat’s?

Leaving aside for the moment the burning question of whether a gnat could be trained to hold its liquor, let’s consider how much more annoying this narrative strategy would be if (a) it were used frequently throughout the story, (b) it were in fact the primary tactic for introducing conflict into the story, and/or (c) the conflict in question were one that had been hyped throughout the book as central to the protagonist’s personal journey.

Yes, you did read that last bit correctly, campers. You would be stunned at how frequently Millicent sees a manuscript’s central conflict diverted to the Short Road Home. Often in the last chapter — or on the next-to-last page.

“Oh, Marv,” Antoinette moaned, cradling his bloody head, “you are so close to learning the truth about your family. Before you die, let’s look at that watch one more time.”

With effort, he fished it out of his pocket. The last rays of the sun illuminated its broad face. “Wait — I’ve never noticed that notch before. Maybe it has a false back.”

After the third time he dropped the watch, she put her deft fingers to work for him. “Why, you’re right. There’s been a piece of paper hidden back here all the time.”

She spread the paper two inches from his eyes. With difficulty, he made out the words. “Dear descendent: you will have heard all your life about a family curse. There really isn’t one; I just made it up to scare off competition from my gold mine. Please find attached the true map to your inheritance. Love, Marvin Bellamy the First.”

Suddenly, Marvin felt life once again suffusing his limbs. “Why, that’s the answer I’ve been seeking since we began this long, strange trek!”

Antoinette struggled to contain her annoyance. “And to think, if you’d only given that watch more than a passing glance after your father gave it to you, we wouldn’t have had to spend fifteen months hiking these mountains barefoot.”

“Oh, stop your moaning.” He sprang to his feet. “Your shoes didn’t wear out until month three. Let’s go find the gold mine — it’s only a few hundred yards away.”

“Um, excuse me?” Millicent asks politely. “Is there a reason that I had to read the 312 pages prior to this one? The entire plot has just been sewn up in seven paragraphs.”

Ah, but you should be grateful, Millie: at least this protagonist had to do something in order to send us careening down the Short Road Home. Granted, it wasn’t much; he simply had to manhandle his main prop a little to find his long-sought truth. As you know from experience, many a passive protagonist simply has another character hand the key to the plot to him on a silver platter.

The shadowy figure was closer now, bending over him. If this was Death, he certainly wore nice cologne.

Wait — he knew that scent. Hurriedly, Marvin wiped the dust from his eyes, but he still didn’t believe what they told him. “Dad? I thought you were…”

“Dead?” Marvin the Fifth chuckled ruefully. “No, not quite, son. That was merely the necessary push to aim you toward your legacy. Still got that watch?”

Marvin dug it out of his pocket. Snatching it, the old man cracked it in half.

“My inheritance!” Marvin screamed, horrified.

“Oh, it’s just a cheap knock-off.” Dad poked around in the shards. “But it contained this key to a safe-deposit box located twenty-two feet from this very spot. Come on, kid, let’s go claim your real inheritance. On the way, I’ll tell you all about your great-great grandfather’s plan for making his descendents rich.”

“Do I have to walk?” Marvin whined. “I’m tired from all of that mountain-climbing.”

“Hello?” Antoinette shouted after the pair. “Remember me? The lady who has been carrying your backpack for the last 100 pages?”

Come on, admit it: Marvin, Jr. is not the only one who seems a trifle lazy here. This writer appears to have dropped a deus ex machina into this plot, having a new character waltz into the story at the last minute to explain away all of the remaining mystery, rather than engaging in the hard, meticulous work of setting up sufficient clues throughout the story for the protagonist to be able to solve it himself.

Like other forms of the Short Road Home, the external explainer is a tension-killer. It could have been worse, though: ol’ Dad could have popped up periodically throughout the story, making it clear to all and sundry that he could have filled Marvin in at any time, if so chose he. What a pity that Marvin was just too darned lazy — or dim-witted, or determined that this story would take 324 pages to tell — to ask the obvious question.

Oh, you laugh, but narrators effectively tease the reader in this manner all the time in both novel and memoir submissions, through the use of the historical future tense. The openings of chapters are particularly fertile ground for this sort of suspense-killing narration. Often mistaken for subtle foreshadowing, transitional statements like I was happy — but my illusions were about to be shattered forever. actually minimize the tension to come.

How? Well, before the conflict even begins, the reader already knows the outcome: the narrator’s illusions will be shattered. She may not yet know the details, but you can hardly expect her to begin reading the next scene hoping for the best, can you?

Section-opening paragraphs that tell the reader how the scene how it’s going to end before the scene begins are alarmingly ubiquitous. Sometimes, such foreshadowing is subtle:

Although I didn’t know it at the time, my days of wine and roses were soon to come to an end — and in a way that I could never have anticipated in a thousand years of constant guessing. How was I to know that every child only has so many circuses in him before he snaps?

When my great-uncle Cornelius came down to breakfast waving the circus tickets that Saturday in May, I couldn’t have been happier…

Sometimes, though, foreshadowing is so detailed that it more or less operates as a synopsis of the scene to follow:

My hard-won sense of independence was not to last long, however. All too soon, the police would march back into my life again, using my innocuous string of 127 unpaid parking tickets (hey, everyone is forgetful from time to time, right?) as an excuse to grab me off the street, throw me in the back of a paddy wagon, and drag me off to three nights’ worth of trying to sleep in a cell so crowded that the Black Hole of Calcutta would have seemed positively roomy by contrast.

It all began as I was minding my own business, driving to work on an ordinary Tuesday…

In both cases, the narrative is telling, not showing — and, even more troubling to writing rule-mongers, telling the story out of chronological order. The latter is generally a risky choice, because, let’s face it, unless you’re writing a book that features time travel, most readers will expect events to unfold in chronological order — or if not, for flashbacks to be well-marked enough that the reader never needs to ask, “Wait, when is this happening?”

For the sake of clarity, beginning a scene at the beginning and proceeding to the end without extensive temporal detours is the established norm. That’s why, in case any of you had been wondering, the frequent use of and then tends to annoy your garden-variety Millicent: unless a narrative specifically indicates otherwise, actions are assumed to have occurred in the order they appear on the page. I lost my footing and plunged into the water. And then the bear ate me, therefore, does not convey any more information to the reader than I lost my footing and plunged into the water. The bear ate me.

I hear some of you giggling. “Oh, come on, Anne,” lovers of conversational-style narration and/or run-on sentences protest. “I can see that and then might have been logically unnecessary here, but what’s the big deal about adding a couple of extra words?”

If they appear only once or twice in the course of a manuscript, they might not be a big deal. Given the extreme popularity of chatty-voiced narration, however, and the common conception that first-person narration peppered with conversational conjunctions is a valid reflection of everyday speech, Millicent sees an awful lot of and thens in a work day. Often, more than once on a single page. Or within a single paragraph.

You might want to give it a rest. I’m just saying.

Back to the benefits of telling a story in chronological order, rather than skipping around in time. Showing events in the order they occurred renders maintaining narrative tension easier, particularly in first-person narration: the reader may be safely left in the dark about surprising developments until they’re sprung upon the narrator, right?

Let’s face it, though, if the reader already knows what is going to happen before a scene begins, the temptation to skim or even skip the recap can be considerable. Particularly, say, if the reader in question happens to be a Millicent trying to get through a hundred submissions in an afternoon. Maybe she should run out and grab a latte to perk herself up a little…

All of which is to say: if you were looking for a good place to start trimming a manuscript, running a quick scan for the historical future tense might be a dandy place to start. Often, such opening paragraphs may be cut wholesale with little loss to the overall story. Ditto with premature analysis.

Oh, wait: I’m foreshadowing — and to render it even more confusing, I’m doing it by jumping backwards in time. The last time I addressed this topic, a reader wrote in to ask:

I’m assuming that it’s still okay to occasionally employ the historical future (foreshadowing) comments, as long as we don’t prematurely spill the beans…or choke on them…in our rush to analyze, yes?

That’s an interesting question. So much so that I strongly suspect that if this reader had asked it at a literary conference, agents and editors would glance at one another sheepishly, not wanting to generalize away the possibility that a writer in the audience could wow ‘em with foreshadowing, and then fall back on that time-worn industry truism, it all depends upon the writing.

Which would be precisely true, yet not really answer the question. But did you notice how gratuitous that and then was?

To address it head-on, let’s take another gander at our last two examples. In a novel or a memoir, a writer could probably get away with using the first, provided that the story that followed was presented in an entertaining and active manner.

Yes, Example #1 does provide analysis of action that has not yet happened, from the reader’s point of view — and doesn’t it make a difference to think of a foreshadowing paragraph that way, campers, instead of as a transition between one scene and other? — but it does not, as our questioner puts it, spill the beans. The reader knows that something traumatic is going to happen, and where, but not enough about either the event or the outcome to spoil the tension of the upcoming scene.

In Example #2, by contrast, not only does the narrative announce to the reader the specifics of what is about to occur — told, not shown, so the reader cannot readily picture the scene, so revisiting it seems dramatically necessary — but shoves the reader toward an interpretation of the events to come. After such a preamble, we expect to be outraged.

Which, too, is dangerous strategy in a submission: such an introduction raises the bar for the scene that follows pretty high, doesn’t it? If a text promises Millicent thrills and doesn’t deliver them, she’s not going to be happy. Or impressed. Frankly, though, if she’s already in a touchy mood — how many times must the woman burn her lip on a latte before she learns to let it cool before she takes a sip? — the mere sight of the historical future might set Millicent’s teeth on edge, causing her to read the scene that follows with a jaundiced eye.

Why, you ask? The insidious long-term result of repetition — because writers, unlike pretty much everybody else currently roaming the planet, just LOVE foreshadowing. The historical future makes most of us giggle like schoolgirls tickled by 5000 feathers.

As with any device that writers as a group overuse, it’s really, really easy to annoy Millicent with the historical future. Especially if she happens to work at an agency that handles a lot of memoir, where it’s unusual to see a submission that doesn’t use the device several times within the first 50 pages alone.

Heck, it’s not all that uncommon to see it used more than once within the first five. By the end of any given week of screening, poor Millie has seen enough variations on but little did I know that my entire world was about to crumble to generate some serious doubt in her mind about whether there’s something about writing memoir that causes an author to become unstuck in the space-time continuum on a habitual basis.

Which, in a way, we do. Since memoirs by definition are the story of one’s past, really getting into the writing process can often feel a bit like time-travel. After all, how else is a memoirist going to recall all of those wonderfully evocative telling details that enlivened the day a bear ate her brother?

Tell me honestly: as a reader, would you rather see that bear jump out of the underbrush and devour bratty little Tommy twice — once before the scene begins, and once at its culmination — or only once?

Or, to put it another way, would you prefer to know that Tommy is going to be a carnivore’s dinner, so you may brace yourself for it? Or would you like it better if the scene appeared to be entirely about the narrator and Tommy bickering until the moment when the bear appears — and then have it devour him?

If you’re like most readers — and virtually all professional ones — nine times out of ten, you would pick the latter. And for good reason: genuine suspense arises organically from conflict between the characters as the story chugs along. A surprise that you’ve known was coming for two pages is obviously going to startle you less than one that appears out of nowhere.

Foreshadowing is the opposite tactic: it tells the reader what to expect, dampening the surprise. It’s hard to do without spoiling future fun. All too often, what the writer considers a subtle hint informs the reader that a shock is to come in such explicit terms that when the shock actually occurs, the reader yawns and says, “So?”

That’s a pretty high price to pay for a transitional sentence or two that sounds cool, isn’t it?

Not all foreshadowing utilizes the historical future tense, of course, but it’s not a bad idea to get into the habit of revisiting any point in the manuscript where the story deviates from chronological order for so much as a sentence. Or even — and revising writers almost universally miss this when scanning their own works — for half a sentence.

Why? Well, from a reader’s perspective, even that brief a Short Road Home can substantially reduce a scene’s tension. Take, for example, this fairly common species of scene-introducing prose:

On the day my brother Jacques shocked us all by running away from home, I woke with a stomachache, as if my intestines had decided to unravel themselves to follow him on his uncertain road, leaving the rest of my body behind.

Assuming that the reader had gleaned no previous inkling that Jacques might be contemplating going AWOL, what does the narrative gain from opening with the scene’s big shocker? Yes, announcing it this way might well evoke a certain curiosity about why Frère Jacques departed, perhaps, but why not let the reader experience the surprise along with the family?

Taking the latter tack would not even necessarily entail losing the dramatic effect of foreshadowing. Take a look at the same scene opener without the spoiler at the beginning of the first sentence:

I awoke with a stomachache, as if my intestines had decided to unravel themselves to follow an uncertain road behind the Pied Piper, leaving the rest of my body behind. If this was what summer vacation felt like, give me six more weeks of school.

Mom burst into the room with such violence that I cringed instinctively, anticipating the obviously unhinged door’s flying across the room at me. “Have you seen Jacques? He’s not in his room.”

More dramatic, isn’t it? Starting off with a description of a normal day and letting the events unfold naturally is a more sophisticated form of foreshadowing than just blurting out the twist up front.

Not to mention closer to the way people tend to experience surprises in real life– as a manifestation of the unexpected.

That may seem self-evident, but as Millicent would have been the first to tell you had not I beaten her to the punch, few manuscript submissions contain twists that actually surprise professional readers. Partially, as we discussed earlier in this series, this is the fault of the pervasiveness of the Idiot Plot in TV and film, of course, but it also seems that many aspiring writers confuse an eventuality that would come out of the blue from the point of view of the character experiencing it with a twist that would stun a reader.

Again, it all depends upon the writing. (Hmm, where have I heard that before?) At the risk of espousing a radical new form of manuscript critique, I’m a big fan of allowing the reader to draw her own conclusions — and of trusting her to gasp when the story throws her an unanticipated curve ball. After all, it’s not as though she has the attention span of a gnat, drunken or otherwise.

Unfortunately, many aspiring writers apparently don’t trust the reader to catch subtle foreshadowing; they would rather hangs up a great big sign that says, HEY, YOU — GET READY TO BE ASTONISHED. That in and of itself renders whatever happens next less astonishing than if it came out of the proverbial clear blue sky.

I’m sensing some disgruntlement out there. “But Anne,” some of you inveterate foreshadowers call out, “what you say about real-life surprises isn’t always true. Plenty of people experience premonitions.”

That’s quite true, disgruntled mutterers: many folks do feel genuine advance foreboding from time to time. Others cultivate chronic worry, and still others apply their reasoning skills to the available data in order to come up with a prediction about what is likely to occur.

Do such people exist in real life? Absolutely. Should one or more of them be tromping around your manuscript, bellowing their premonitions at the tops of their gifted lungs? Perhaps occasionally, as necessary and appropriate, if — and only if — their presence doesn’t relieve the reader of the opportunity to speculate on her own.

In fact, a great way to increase plot tension in a story featuring a psychic character is to show him being wrong occasionally. Mixes things up a bit for the reader. But — correct me if I’m wrong — in real life, most of us don’t hear giant voices from the sky telling anyone who might happen to be following our personal story arcs what is going to happen to us twenty minutes hence.

To those of you who do habitually hear such a voice: you might want to consult a reputable psychiatrist, because the rest of us don’t lead externally-narrated lives. There’s an excellent chance that six-foot rabbit who has been giving you orders is lying to you, honey.

If we were all subject to omniscient third-person narration at the most startling moments of our lives, Tommy wouldn’t have let that bear get the drop on him, would he? Unfortunately for his future prospects, as handy as it would have been had a talking vulture been available to warn him about the nearby hungry beast, that doesn’t happen much in real life.

But that doesn’t mean that if you do find that your life starts being narrated on the spot by a talking vulture, you shouldn’t seek some professional help.

Speaking of professional help: from a professional reader’s point of view, heavy-handed foreshadowing on the page is rather like having a tone-deaf deity bellow driving instructions from a low-hanging cloud bank. Yes, that constant nagging might well cause Millicent to avoid driving into that rock five miles down the road — but, time-strapped as she is, I’m betting that the warning is more likely to convince her to stop driving on that road altogether, rather than hanging on for the now-predictable ride.

Okay, so that wasn’t one of my better metaphors; darn that pesky vulture for distracting me. Keep up the good work!

The Short Road Home, Part III: always let your conscience be your guide — except when you shouldn’t

Did you miss me, campers? I’ve been hiding under the covers of both a good book and my bed for the past few days. Why, you ask? Well, I can take a hint: the last time I poked my nose outside my front door, I sprained my ankle and caught a cold.

Clearly, Somebody Up There is harboring a preference for my staying put. With my foot in the air and a mug of hot tea clutched to my chest.

I am venturing forth this evening, however, to reignite our discussion of the Short Road Home, my pet term for a scene that introduces a potential conflict, only to resolve it so quickly that the reader barely has time to notice an increase in ambient conflict. Short Roads Home have been the downfall of many a submitted novel, for a small handful of exceedingly simple reasons: such scenes almost invariably tell rather than show, minimize inter-character conflict, and let the tension of the story lag.

So why, you might well have spent last week wondering, do Short Roads Home remain immensely popular in manuscript submissions? Much of the time, the writers who construct such shortcuts are not even aware that they are doing it.

That, I think, is both unfortunate and unnecessary. Today, I’m going to show you how to recognize the subtle form of Short Road Home, so you may see this common mega-problem in action and learn how to fix it.

As in right now. Or at least before you send your baby out again.

Why the urgency? Because the Short Road Home is so very common, an experienced pro might not even have to read more than a couple of lines of a scene to identify it — and shove the submission into the rejection pile. In fact, it’s in the interest of a time-strapped Millicent the agency screener, Maury the editorial assistant, or Mehitabel the veteran contest judge to be on the lookout for this phenomenon: it’s a pretty good indicator that a manuscript has not seen very many critical first readers.

As such, M, M, and M tend to assume, the book is probably at least one revision away from being polished. Or, to put it as they would, “Next!”

Long-time readers of this blog, did a light bulb appear above your heads somewhere in the course of those last two paragraphs? Did it occur to you as if archangels suddenly appeared and shouted the news into your awed ears that, as with nonstandard formatting, the appearance of an ultra-frequent megaproblem in a manuscript might actually be a welcome sight to an agent, editor, or contest judge, because it means that the work can be rejected without further ado — or, more to the point, without investing further reading time?

If so, congratulations — you now have a much, much firmer grasp of how submissions work than a good 95% of the writers currently slapping stamps on SASEs across the English-speaking world. It’s one of the great paradoxes of being in a position to discover new writers: in order to unearth that great undiscovered talent, they have to read a lot of, well, everything else. So the faster they can sift through the rest and reject the bulk of what they receive, the more time and energy they have to devote to that elusive perfect book.

Which is great, if your manuscript happens to be that needle in a haystack. It’s substantially less great if your project is a pin that merely needs a bit more sharpening and an eye installed before M, M, and/or M will recognize it as what they have been seeking.

Was the refreshing breeze that just wafted across my elevated foot the collective result of all of you agent-seekers sighing gustily? I’m not surprised: polishing a manuscript to professional standards is hard work, and not something that is going to happen all by itself. As much as the artist in all of us would like to believe that each and every sentence to fall off our fingertips onto a keyboard is camera-ready, more than talent is typically necessary to bring a wonderful story to publication. It takes inspiration, yes, but it also takes craft and an acquired knowledge of how the publishing industry expects good writing to be presented.

And half of you sighed again. But honestly, if you were setting out to be a professional baseball player, would you expect to hit the ball out of the park the first time you tried? Even a natural benefits from training.

But as M, M, and M can tell you to their cost, that’s not the prevailing notion of how books get published. Quite the opposite: most aspiring writers new to the business leap to the unwarranted conclusion that an agent or editor will be so delighted by a fresh voice that s/he is automatically going to be willing to ignore other problems in the manuscript until after the contract is signed.

In practice, this doesn’t happen much, even for manuscripts with minor problems. Certainly not for those with pacing or storytelling problems.

Out comes the broken record again: when submitting your writing in any professional context, it is not safe to assume that it will meet with readers eager to give it the benefit of the doubt. Seldom does one hear a professional reader say, “Well, this manuscript certainly needs work, but I think it’s going to be worth my while to expend my energy on helping the author fix it.”

And never, alas, does one hear, “This author seems to have trouble moving the plot along and maintaining tension, but that’s nothing that a good writing class couldn’t fix. Let’s sign this writer now, and help her grow as an artist for the three or four years it will take her to learn to correct these problems.”

As delightful as it would be if they did habitually express such sentiments — better still, if they routinely acted upon them — this just doesn’t happen for writers who don’t already have a solid platform (i.e., a special expertise or celebrity status to lend credibility to a book). As a non-celebrity writer, you can safely assume that the first reader at an agency, publishing house, or contest is looking for reasons to weed your work out, rather than reasons to accept it. At least for the first half of the book or so. Millicent and her ilk don’t worry too much about too quickly rejecting the next great American novel — since writers are resilient creatures who improve their skills on their own time (and dime), the publishing industry is fairly confident that the great ones will keep coming back.

Until then, they’re hoping that those great ones will take a hint, stop submitting, and polish their manuscripts before approaching the pros again. Oh, and becoming a celebrity in the meantime would be a selling point, too.

For some reason, people in the writing community — especially those who write for writers’ publications and teach seminars, I notice — don’t like to talk much about this hope. Maybe it’s so they can put a positive spin on the process, to concentrate on the aspects of this honestly hugely difficult climb to publication that are within the writer’s control.

As far as I’m concerned, megaproblems are very much within the writer’s control, as are the other rejection triggers we’ve been discussing over the last few months– but only if the writer knows about them in advance of submission. So let’s get down to the proverbial brass tacks and see about clearing up the subtle Short Road Home.

The subtle flavor of Short Road Home crops up frequently in the work of authors who have themselves spent quite a bit of time in therapy, 12 Step programs, or watching Oprah: the second an interpersonal conflict pops up, some well-informed watchdog of a character — or, even more often, the protagonist’s internal Jiminy Cricket — will deftly analyze the underlying motivations of the players at length. Case closed!

Not sure what I’m talking about? Okay, here’s a common example: when a protagonist apparently shows up to a scene purely in order to comment upon it as an outside observer, rather than participating actively in it.

“I did not press the panic button!” James insisted.

Barnaby pointed to the city skyline melting into a fluorescent puddle in the distance. “The warhead didn’t launch itself!”

Etienne listened to the argument swirling around him, knowing it wasn’t really about who bombed what when. Anybody could see that the rapidly-disintegrating city was just an excuse for James and Barnaby to snipe at each other, a transparent mask laid delicately over the face of their unadmitted mutual passion. He wished that they would just rent a motel room and get on with it, so he wouldn’t have to listen to their bickering — assuming, that is, that James’ little slip of the finger had left any motels standing.

See the problem? Essentially, the protagonist is acting as the reader’s translator here: no need to draw one’s own conclusions while Etienne is on the job. No messy loose ends left to complicate the plot here — or to keep the reader turning pages.

Even when these helpful characters are not therapists by trade (although M, M, and M have seen a LOT of manuscripts where they are), they are so full of insight that they basically perform instant, on-the-spot relationship diagnosis: “I realize that you’re upset, Cheryl, but aren’t you displacing your underlying dissatisfaction at being laid off at the lumberyard onto your boyfriend? After all, it’s not his fault that pastry chefs remain in such high demand. If you were not envious of his job security, would you really have minded his torrid affair with those Siamese twins?

Ta da! Situation understood! Conflict eliminated!

“But Anne,” I hear many an amateur Jiminy Cricket protest, “I don’t understand. Don’t my explanations move the plot along? Don’t they provide necessary character development? And isn’t my spouting them a fabulous way of making sure that the reader doesn’t miss any critical nuances?”

Why, yes, Jiminy, your running commentary can indeed perform all of those functions — but by definition, your pointing them out to the reader is telling, not showing.

I’m not just bringing that up to sound like your 10th grade composition teacher, either. While no one minds the occasional foray into summation, both characters and situations tend to be more intriguing if the narrative allows the reader to be the primary drawer of conclusions based upon what the various characters do, say, and think.

It makes for a more involving narrative. Hyper-analytical protagonists seldom surprise; they’re too thoroughly explaining what’s already gone on, what’s going on now, and what is likely to be going on in future to allow a twist to sneak up on the reader.

Also, when the instant-analysis device is overused, the reader can become jaded to it pretty quickly. After the third or fourth instance — or after the first, if the reader happens to be a professional manuscript-scanner — the reader is apt to become convinced that that there is absolutely no point in trying to second-guess the protagonist.

Why bother, if the author is going to tell her right away what to conclude from what has just passed? Which, correct me if I am wrong, completely prevents the reader from enjoying one of the great joys of getting into a novel, trying to figure out what is going to happen next.

Besides, as we saw last week, instant analysis can relieves the conflicting characters of any urgency they might have felt in resolving their interpersonal issues. Since Jiminy Cricket hops on in and spells out everyone’s underlying motivations, the hard work of figuring one’s own way out of a jam is rendered unnecessary.

If this seems like an exaggeration to you, take a good look at your manuscript — or, indeed, any book where the protagonist and/or another character habitually analyzes what is going on while it is going on, or immediately thereafter. Does the protagonist leap into action immediately after the analysis is through, or wait for new developments?

In the vast majority of manuscripts, it is the latter — which means that the analytical sections tend to put the plot on hold for their duration. Where analysis replaces action, momentum lulls are practically inevitable.

Memoirs are particularly susceptible to this type of stalling, incidentally. Memoirists just adore foreshadowing — because, obviously, they are telling about their past through the lens of the present. In the course of foreshadowing (often identifiable by the historical future tense: “It was not to turn out as I hoped…”), the narrator will all too often analyze a scene for the reader before showing it, thus killing any significant suspense the reader might have felt about how the scene will be resolved.

Yes, you know the story you are telling very well, but remember, your reader doesn’t. Just because something really occurred does not relieve the writer of the obligation to make its telling vibrant and dynamic. You may be excited to share insights gleaned over the course of a lifetime, but if they are not presented as the stories unfold in the memoir, the reader may have a hard time tying the lessons to the anecdotes.

A great structural rule of thumb for memoirs: show first, conclude later.

But what’s that you say, Great Hinter in the Sky? That burgeoning swelling in my ankle means I should stop for now? Thanks for telling me — I wouldn’t want to risk drawing the wrong conclusion from the evidence, after all.

I shall continue to wax poetic on this subject tomorrow. In the meantime, make sure those protagonists stay active, concentrate on giving the reader enough information so s/he may draw the correct inferences about what’s going on, and keep up the good work!

The Short Road Home, Part II: establishing and preserving narrative intensity, or, why not let those characters roll around on the tiger skin for a while?

Quite the author photo, is it not? That’s the jacket picture for the first edition of Elinor Glyn‘s 1927 bestseller, IT, incidentally — and in response to what those of you familiar with silent film just thought, yes, Madame Glyn was in fact the person who coined the phrase the It Girl for Clara Bow. She also discovered Rudolf Valentino, bullied early Hollywood set dressers out of depicting the stately homes of England with suits of armor in every corner, and convinced the reading public that kissing a lady on the inside of the wrist was far, far sexier than smooching the back of her hand.

She was crucial in establishing many of the long-standing conventions of the romance genre, in short. No great prose stylist, she nevertheless managed to establish her own particular brand of smoldering, setting the standard for passion-on-the-page for decades.

Getting the word out about a writer to that extent was no mean achievement, back in the long-ago days before the Internet — and she pulled it off before telephones were common in private homes. Yet by the time IT was published, Madame Glyn had been THE name in potboiler romance for a decade. Her breakthrough novel, Three Weeks, was considered so scandalous when it came out that it inspired a popular song:

Would you like to sin
With Elinor Glyn
On a tiger skin?
Or would you prefer
To err with her
On some other fur?

Catchy, no? Even today, most authors would have happily cut off a toe or two in exchange for that kind of free publicity.

Why bring up Madame Glyn in the middle of a discussion of narrative shortcuts and too-quick resolutions of major plot conflicts? Ah, I could tell you up front, but if I have learned anything from studying her work, it’s to draw out the mystery.

To our muttons, then, Last time, I broached the monumental twin subjects of tension and conflict in novels and memoirs. While lack of either is a frequent rejection trigger, there are as many individual underlying causes for flabby tension and minimal conflict as there are manuscripts — or, indeed, as there are pages in individual manuscripts. But that’s not going to stop me from talking about how to attack some of the more common culprits.

Yesterday, I introduced the Short Road Home, the all-too-common narrative practice of resolving a conflict practically as soon as it is introduced — or the first time the protagonist really puts his mind to it. Whether it’s stamping out a fallen match before the reader’s had a chance to see it be even the vaguest threat to the drapes or a protagonist so distracted by subplots that she doesn’t get a chance to devote serious thought to the book’s central problem until Chapter 32 in a 33-chapter novel, professional and non-professional readers alike tend to find cutting to the chase dramatically unsatisfying.

Surprisingly, the intention underlying most Short Roads Home is less often a matter of a writer’s trying to pick up a story’s pace than an attempt to skip over a series of events the writer just doesn’t find very interesting. Oh, the provoking event may be interesting, as may the eventual resolution; it’s all of the action needed to get the reader from Point A to Point B that tends to get omitted. SRH solutions may be very attractive to writers not eager to deal with scenes necessary to resolve a conflict and/or the solution’s messy and page-consuming results.

“What’s that, Lassie? Timmy’s fallen into the well?”

It’s so much easier, the logic runs, just to summarize what happened, telling rather than showing the reader what is going on. SRH solutions are, in a word, shortcuts — and in the vast majority of manuscripts, shortcuts that both minimize conflict and reduce tension.

The good news is that the Short Road Home is exceptionally easy to spot in a manuscript, once a writer knows to be looking for it. While a bit time-consuming to fix — often, SRH are small shortcuts, rather than extensive plot detours, so it may require some pretty close reading to spot ‘em — the benefits in added character development tend to be substantial.

Okay, so good news is relative. I never promised you that revision would be a breeze, did I?

Not all too-quick resolutions of a major problem in the plot fall under the SRH rubric, however. Last time, for the sake of discussion, I brewed it for you in its full-bodied version. Today, I am going to deal with the subtle flavor, scenes where character development or conflict is curtailed by too-quick narrative analysis. Like the full-bodied version, this mega-problem is not limited to works of fiction, but runs rampant through narrative nonfiction and memoir as well.

The subtle flavor of the Short Road Home is easy for the author to overlook, particularly in a first novel or memoir. Writers new to the craft tend to be so pleased when they develop the skill to pin down an emotional moment with precision that they go wild with it for a little while. First-person and tight third-person narratives are particularly susceptible to over-analysis: since these point of view choices allow the reader to see the protagonist’s every thought and feeling, it’s pretty easy to get carried away.

The result, alas, is often text in which the conclusions drawn from even the least significant event positively swamp the event itself. In the face of such apparent narrative overreaction, the poor reader is left to guess what is significant and what is merely a passing annoyance.

The border guard eyed him with suspicion. “Your passport, sir?”

Why on earth had the man asked that? Gregory wondered. Was the contraband bulging under his winter coat? Was it too odd that he was wearing a winter coat at all in July?

But what could he do but comply? “Of course. Would you mind holding my monumentally heavy valise while I dig it out?”

The guard accepted the load. “What have you got in here, sir? Gold bars?”

What did the man mean by that? Could he possibly know just by hoisting the bag what was within? Or did the clank give the gold bars away?

As Gregory pulled the necessary papers from his inside coat pocket, a matchbook from the Kit Kat Klub tumbled to the tiled floor. He was too fearful of dropping anything else to pick it up. He lamented the inconvenience. What if he needed to light someone’s cigar on the boat? What if the generator went out, and he was forced to light a candle? Where would he get a candle in that contingency, and did the power go out on steamers very often?

“Here, you are, sir.” The guard returned his passport with a curt smile. “Enjoy your trip.”

Just what did that sinister little smile portend? Gregory wondered uncomfortably. Had he actually gotten away with smuggling, or was the guard merely toying with him?

Exhausting, isn’t it? The instant a solidly conflictual moment peeps its poor little head above ground, narrative eager beavers stop the plot cold to devote themselves to analyzing it, sometimes for pages on end. If a nuance tries to escape unpinned-down, perhaps in order to grace a later scene, the narrative leaps upon it like a vicious wildcat, worrying it to bits.

Frequently, this analysis takes the form of what could be an interestingly subtle conversational conflict’s being presented purely in the form of the protagonist’s mulling over the provocation without responding overtly at all — creating a scene in which all of the conflict takes place in a character’s mind. As we saw above, rhetorical questions are just dandy for achieving this effect.

Oh, what the heck. Let’s see speculation run wild again.

“No more cake for me,” Moira said with a sigh. “I’m stuffed.”

“Oh, have some more, Moira,” Cheyenne wheedled. “You could use to pack on a few pounds.”

Moira’s hand froze in mid-air, crumb-bedusted dessert plate trembling aloft. What did Cheyenne mean by that? Was he just being polite — or was this a backhanded way of reminding her that she was supposed to be on a perpetual diet, with the Miss America pageant only three months away? Or was he afraid that if the guests didn’t consume every last morsel, he would revert to his habits from before, from those torrid days at the emergency reduction boot camp where they’d met, and snort up all of the remaining calories like a Hoover?

She had to smile at the thought: he had been adorable chubby. But that’s not the kind of person who should be seen on a beauty queen’s arm.

She decided to change the subject, as well as her conversational partner. “So, Barbara, how are you enjoying wombat farming?”

See what the narrative has done here? The long internal monologue provides both backstory and character development, but it has also deprived the reader of what could have been a meaningful exchange between Moira and Cheyenne. Instead of allowing the reader to derive impressions of their attitudes toward each other through action and dialogue, the narrative simply summarizes the facts the reader needs to know. To depress the tension of the scene even further, once the logical possibilities for Cheyenne’s motivation have been disposed of in this silent, non-confrontational manner, the scene proceeds as if no conflict had ever reared its ugly head.

Why is this a problem? Well, when a text over-explains situations and motivations, the reader does not have to do any thinking; it’s like a murder mystery where the murderer is identified and we are told how he will be caught on page one. Where’s the suspense? Why keep turning pages?

I see you scowling, but honestly, given how many manuscripts she has to read in a day, this is a completely understandable reaction. Most aspiring writers tend to forget this — or never knew it in the first place — but professional readers do not, as a rule, devour an entire chapter, or even an entire page, before making up their minds about whether they think the submission is marketable. They read line by line, extrapolating patterns.

How might this affect a submission in practice? Let’s assume that Millicent has the first 50 pages of the manuscript containing that last example. If it appears on page 1, she is likely to stop there, because a subtle Short Road Home has already appeared. Because this is her first contact with the writer’s work, she left to speculate whether this is a writing habit, or a one-time fluke. Depending upon which way she decides, she may choose to take a chance that it is a one-time gaffe and keep reading — or, and this is by far the more popular choice, she may pass with thanks.

If the SRH doesn’t appear until page 43, however, she might well continue. She already has some reason to believe that SRHs are not this writer’s go-to solution for conflict. Generally speaking, though, the sooner a writing problem occurs in a manuscript, the more likely she is to diagnose it as inherent to the writer in question’s style, and score the piece accordingly. Even if the overall writing style is strong, a reliance on the SRH is likely to get the writer labeled as promising, but needing a more experience in moving the plot along.

Or, to put it in the parlance of the business, “Next!”

Subtle Short Roads Home often trigger the feedback, “Show — don’t tell!” But frankly, I think that admonition does not give the writer enough guidance. There are a lot of ways that a writer could be telling the reader what is going on; a subtle SRH is only one of many, and I don’t think it’s fair to leave an aspiring writer to guess which rule she has transgressed.

But then, as I believe I have pointed out before, I don’t rule the universe. If I did, though, every writer who was told “Show — don’t tell!” would also receive specific feedback on where and how his manuscript has slipped onto the primrose path of the Short Road Home. In addition, I would provide them with three weeks of paid holiday every six months just for writing (child care provided gratis, of course), a pet monkey, a freezer full of ice cream, and a leather-bound set of the complete writings of Madame de Staël.

Because, frankly, subtle Short Roads Home bug me. I feel that they should be stopped in our lifetime, by federal statute, if necessary.

The way a subtle Short Road Home halts the flow of a wonderful story reminds me of the fate of the migratory birds that used to visit my house when I was a child. Each spring, lovely, swooping swallows would return to their permanent nests, firmly affixed under the eaves of my house, invariably arriving four days after their much-publicized return to Mission San Juan Capistrano, much farther south. For me, it was an annual festival, watching the happy birds frolic over the vineyard, evidently delighted to be home.

Then, one dark year, the nasty little boy who lived half a mile from us took a great big stick and knocked their nests down. The swallows never returned again. Little Georgie had disrupted their narrative, you see.

A subtle SRH disrupts an ongoing narrative, too, smashing imaginative possibilities to the ground with a single blow. Once an overly-enthusiastic analysis has laid the underlying emotional rubric of a relationship completely bare, the rhythm of a story generally has a hard time recovering momentum.

When a text over-analyzes, how can the reader draw any conclusions? That’s not a bad definition of telling, rather than showing, come to think of it: showing the reader what is going on and allowing her to draw her own conclusions tends to produce a richer reading experience than simply stating the facts.

Readers of good writing don’t want to be passive; they want to get emotionally involved with the characters, so they can inhabit, for a time, the world of the book. They want to care about the characters. to keep turning page after page, to find out what happens to them.

Essentially, subtle Short Roads Home are about not trusting the reader to draw the right conclusions about a scene, a character, or a plot twist. They’re about being afraid that the reader might stop liking a character who has ugly thoughts, or who seems not to be handling a situation well. They’re about, I think, a writer’s being afraid that he may not have presented his story well enough to prove the point of his book.

And, sometimes, they’re just about following the lead of television and movies, which show us over and over emotions analyzed to the nth degree. We’ve gotten accustomed to being told immediately why any given character has acted in a particular manner. The various LAW & ORDER franchises excel at this, particularly L&O SVU: in practically every episode, one of the police officers will, in the interests of drama and character development, lose an apparently tenuous grasp on his or her emotions/underlying hostility/grasp of constitutional law and police procedure and let loose upon a suspect.

Or a witness. Or a coworker. The point is, they yell at somebody.

Then, practically the nanosecond after the heat of emotion has passed, another member of the squad will turn up to explain why the character blew up. Helpfully, they often direct this explanation to the person who has just finished bellowing. Whew — just when the audience member thought s/he might have to draw a conclusion based upon what s/he had seen occur.

Or — and this one’s my personal favorite — one of the police officers (or forensic pathologist, or administrator, or someone else entitled by billing to a series of close-ups of an anguished face) does or says something well-intentioned at the beginning of the episode that triggers (however indirectly) someone else to do something stupid. An actual example: “If I hadn’t bought my nephew that computer, he would never have met that online predator!”

Hard to argue with that one, isn’t it? It’s also hard to imagine the next line of dialogue’s not being a cliché, because an assertion like this isn’t precisely conducive to any response but, “Oh, Mrs. Miniver, you mustn’t blame yourself.”

But I digress. With both of these structures, the character in question exhibits his remorse, naturally, by repeating this sentiment at crucial points throughout the episode, looking tortured. Then he bends some pesky police regulation/federal statute/commandment because (and in the interests of brevity, I’m going to cut to the essentials of the argument here) the ends of catching that creep justify the means.

Cue recap of feeling guilty — often punctuated by a co-worker’s patient explanation that capturing the creep du jour didn’t REALLY change the underlying emotional situation, raise the dead, get the nephew un-molested, etc. — and leave those emotional threads hanging for next week’s episode. Wash, rise, repeat.

What identifies this series of events as a Short Road Home is not so much that the villain is pretty much always caught and convicted, but that complex human emotions that talented actors would surely be delighted to play are simply summarized in the plot. Or, to put it as an editor might, the turmoil is told, rather than shown.

To be fair, TV and movie scripts are technically limited to the sensations of sight and sound: they cannot tell their stories any other way. A novelist or memoirist, on the other hand, can draw upon the full range of sensations — and show thoughts. A book writer who restricts himself to using only the tools of TV and movies is like a pianist who insists upon playing only the black keys.

Live a little. You have a lot of ways to show character development and motivation; use them.

Don’t see how this might apply to your revision? Okay, consider your manuscript for a moment: does it contain scenes where, instead of interaction between characters showing the reader what the conflicts are and how the protagonist works through them, the protagonist instead:

(a) sits around (often while driving in a car) and thinks through the problem to its logical conclusion, ruling out possible actions instead of testing them through doing? A species example, so you may recognize it in the wild: Should I go to my boss and confess? No, he’ll never understand. Maybe I should just return the money quietly, hoping no one will notice. But whom am I kidding? Or perhaps I should…

(b) sits around drinking coffee/tea/another beverage with her friends while they come up with analysis and solution? As in: “What do you think, Angela and Trieste? Should I try to save my relationship with Bertie, who might be an axe murderer, or should I leave him? Compare and contrast the possibilities, please, while I score us some more of this luscious chocolate cake.”

Or — and this one often surprises writers when I bring it up:

(c) sits around with her therapist/his significant other, dissecting the problem and coming up with a solution? As in: “Oh, stop kicking yourself, George. You’ve done the best you can for your daughter. It’s not your fault that her mother died in that hideous lacrosse accident when she was only six, and has hated netting ever since.” “I know you’re right, Martha, but by Jove! I can’t help feeling responsible.”

If you can answer yes to any of these questions, sit down right away and read your book straight through, beginning to end. Afterward, ask yourself: would the plot have suffered tremendously if those scenes were omitted entirely? Are there other ways you could convey the same points, through action rather than thought or discussion?

Just a suggestion. (“And just what does she mean by that?” Gregory worried, gnawing his fingernails down to the elbow.)

Speaking of elbows, do I see a few waving in the air? “But Anne,” lovers of the classics protest, “Some of my favorite 19th-century novels spend chapters on end wallowing in the type of intensive introspection you describe. Since good writing is good writing, regardless of the era in which it was produced, Millicent couldn’t possibly regard this orientation as slow pacing.”

Actually, she is fully capable of doing so — in fact, she’s trained to do it. Readers today expect more action on even the literary fiction page than they did back in the days when the next train through town might not show up for a week. That’s why, incidentally, novels (or memoirs) published more than 20 years ago would not be the best role model choices for pacing a book a writer planned to submit today.

Yes, even if the book in question is a recognized classic. I love JANE EYRE as much as the next person, but there’s a reason that all of the film adaptations have simply omitted the huge section of text dealing with the heroine’s conflict over whether to become a missionary or not. As interesting and character-revealing as it is, it’s not as dramatic as the rest of the story.

Do all of those averted eyes mean that some of you don’t want to believe that reading tastes have changed since the Civil War? Believe me, I understand the impulse: it’s tempting, isn’t it, to blame agents for this, since over that particular period they have become the weeders-out of what editors at the major US publishing houses see? (In case you didn’t know, all of the major American publishers currently have policies specifically forbidding considering unagented work; the much-vaunted slush pile no longer exists.) But the fact that pacing standards have sped to near-breakneck rates in recent years really isn’t the agents’ fault: it’s genuinely difficult for them to sell more moderately-paced books. Ditto with long ones.

Why? The price of paper has risen astronomically in recent years, as has the cost of binding. This, in case you are curious, is the primary reason that Millicent tends to have a knee-jerk negative reaction to a first novel much over 100,000 words (400 pages in standard format; if what I just said sounded like Urdu to you, run, don’t walk to check out the HOW TO FORMAT A BOOK MANUSCRIPT and WORD COUNT categories on the archive list at right). At 120,000 words — around 500 pages — the cost of binding shoots up.

Bad news for all of us who grew up wanting to emulate John Irving’s pacing, certainly. Or John Steinbeck’s. Or, if we’re honest about it, the protagonist introspection levels of pretty much any meganovelist who wrote prior to the Second World War.

For reasons of history, then, as well as practicality, Millicent starts to tense up when a submission’s tension begins to wilt. But that doesn’t mean that it’s in a writer’s interest to skim over interesting conflict too quickly with a Short Road Home.

I’ve gleaned a lulu of an example from our cover girl of the day’s best-known novel, IT. The impoverished society-girl heroine, Ava Cleveland, is desperate for money to maintain her lifestyle in the face of her brother’s bordering-on-criminal gambling debts. When the following scene begins, she’s just told her friends that she is spending a season in the country to hide the fact that she is going to be asking her admirer, John Gaunt, to give her a — gasp! — job:

So she shut up the Park Avenue flat and dodged her creditors and disappeared to “Virginia” — which happened on the map to be her old nurse’s abode in an ancient house in the old-fashioned poorer quarter of Brooklyn. Close, if she had known it, to one of John Gaunt’s hospitals for children.

Something made her restless, even from the first day of her arrival — so at last she looked at John Gaunt’s card again — and rang Hanover 09410 — once more.

Admit it: you’re already a trifle bored, aren’t you? That’s probably because you’re so used to the current standards of writing that even this much summary strikes you as skirting the edge of show-don’t-tell comfort. Don’t feel bad, if that was your reaction. Actually, Millicent probably wouldn’t have made it beyond the first sentence of this excerpt — and for a reason that is very common in present-day submissions.

Any idea why? Hint: go back and take a gander at that first sentence.

Quite a few ands in it, aren’t there? And technically, quotation marks should not be used to indicate so-called; italics would have been the preferred choice here.

But let’s be charitable: this was published 1927, when submission standards were a considerably more lax. Moving on:

Miss Shrimper answered and was as insulting as she could be, when she heard a refined female voice…No, Mr. Gaunt could not come to the phone — he never came to the phone! The idea!

Ava’s voice sharpened. “Be good enough to tell him that the lady he met at Mrs. Meriton’s is speaking.”

It is doubtful that even this would have succeeded, had not John Gaunt himself chanced to come out from his inner shrine and seen Miss Shrimper’s acid face — something told him instantly that it was Ava trying to get through to him.

John Gaunt turned to re-enter his private room. “Put her through,” was all he said.

And as she did so, Miss Shrimper’s eyes filled with apprehensive tears.

Did you catch the Short Road Home? The narrative had gotten a legitimate conflict going between Ava and Miss Shrimper (albeit through having chosen to summarize the latter’s indignation rather than showing it through dialogue and tone) — when along comes stupid old John (called by both names each time he appears, please note, a rookie narrative mistake) to intuit what’s going on by some mysterious, doubtless magical means.

Presto! Conflict killed.

Not content with abruptly cutting off the hostility between the two women, Glyn went on to minimize Ava’s difficulties in asking for what she wants — another perennially popular version of the Short Road Home. To top it off, her characters take refuge in that most boring of dialogue forms, the ultra-polite. See for yourself.

“Good morning, Miss Cleveland.” His voice was deep, and Ava, at the other end, quivered strangely. “What can I do for you?”

“I want to — work.”

“You had better come and see me tomorrow at eleven, then — I am altering some posts in my office. You may wish to give the name of Miss Clover, perhaps?” The tones were cold as steel and entirely businesslike.

Ava experienced a chill — but “Miss Clover!” That was an idea! “Very well, she answered, and put down the phone.

John Gaunt lay back in his chair and smiled.

“How surprised she will be,” he said to himself. Then he went out and had his rather long hair trimmed slightly so that its thick, deep waves lay close against his Napoleonic head. His nails, which Ava had thought too brilliantly polished, were given a still brighter luster too. Then he went to his Club and was sphinx-like and almost surly with one or two business friends he met.

I could have stopped earlier, but who was I to deny you that Napoleonic head? Hard to imagine that less than a century ago, that description would have been considered inherently attractive, isn’t it?

I could run through a laundry list of all the reasons Millicent might give for not making it all the way through this excerpt — the repeated two-part name, the telling rather than showing, the paragraph containing only a single sentence, the mysterious capitalization of club, the burning question of how exactly may one be sphinx-like without either posing riddles or having a cat’s head — but that’s not what I want you to focus upon here. Instead, concentrate on just how effectively the use of the Short Road Home in this last bit smothered all of the following:

(a) the tension that the narrative seems to be assuring the reader exists, yet doesn’t actually show;

(b) the sense that Ava was having to overcome any scruples in going to work, since she just blurted out the request with no preamble or hesitation, beyond the moment indicated by the dash;

(c) any indication that Ava was going to have to beg for the job, since John Gaunt agrees instantly, and

(d) any anticipation the reader might have felt prior to this scene about difficulties Ava might encounter at her first job, since John Gaunt has very kindly handed her a simple alternative to having to be honest about who she is — and in case we were in any doubt about this suggestion’s utility, Ava considerately just tells the reader that it’s a good idea.

A pretty efficient page’s work — and that’s not even counting the significant achievement of impressing the reader with Ava’s apparent inability to hold still for more than a paragraph without quivering for reasons she doesn’t understand. (Nor do we, as it happens.) By handling potentially conflict-ridden material in this manner, Madame Glyn effectively killed the tension of what should have been a harrowing scene.

That’s unfortunate, because this super-quick resolution is not even representative of the rest of the book. Oh, Madame Glyn does favor the Short Road Home from time to time — but given the exchange above, would you be expecting Ava to try to sell herself to John in order to save her brother? Or John to use the solicitation of same as a complex ruse to propose marriage? Or for businesslike John to express his burgeoning feelings to Ava through (I kid you not) the delicate art of interior decoration?

The moral: just because a storyline is full of conflict doesn’t necessarily mean that the book will be a page-turner. How a writer chooses to present that conflict is crucial.

Frankly, Millicent would be a less cynical woman if more aspiring writers realized this. Beware of inexplicable quavering, everybody, and keep up the good work!

A detour from the pet peeve parade: the short road home

Throughout our rather sprawling Pet Peeves on Parade series, I have been chattering blithely about narrative conflict and tension, as though every aspiring writer out there were already hard at work, trying to ratchet up the quotas of both in their manuscripts. As, indeed, those of us who read for a living so frequently advise: make sure there is conflict on every single page is, after all, one of the most commonly-given pieces of how-to-please-the-agent-of-your-dreams revision advice.

But if you’ll pardon my asking, what does it mean?

Seriously, how would a conscientious self-editor apply this advice to the manuscript page? Insert a sword fight every eight paragraphs or so? Have the nearest gas station should spring a leak just because the protagonist happens to be strolling by? Force the lovers in your romance cease stop billing and cooing in favor of snarling at one another?

Of course not — but you would be surprised how often aspiring writers stumble into the harsh daylight at the end of a writers’ conference muttering to themselves, “Must ramp up conflict. Tension on every page!” without being certain what that means on a practical level. There’s a pretty good reason for that: colloquially, conflict and tension are often used interchangeably, but amongst professional writers and those who edit them, they mean two different but interrelated things.

So let’s take a moment to define our literary terms, shall we?

Narrative conflict is when a character (usually the protagonist, but not always) is prevented from meeting his or her goal (either a momentary one or the ultimate conclusion of the plot) by some antagonistic force. The thwarting influence may be external to the character experiencing it (as when the villain punches our hero in the nose for asking too many pesky questions), emerge from within her psyche (as when our heroine wants to jump onto the stage at the county fair and declare that the goat-judging was rigged, but can’t overcome that fear of public speaking that she has had since that first traumatic operatic recital at the age of 10), or even be subconscious (as when our hero and heroine meet each other quite accidentally during the liquor store hold-up, feeling mysteriously drawn to each other but not yet realizing that they were twins separated at birth).

Narrative tension, on the other hand, is when the pacing, plot, and characterization at any given point of the book are tight enough that the reader remains engaged in what is going on — and wondering what is going to happen next — rather than, say, idly wondering whether it is time to check in again with a 24-hour news network. A scene or page may be interesting without maintaining tension, and a predictable storyline may never create any tension at all.

Or, to put it so simply that a sophisticated reader would howl in protest, conflict is character-based, whereas tension typically relates to plot.

Because conflict and tension are related, a manuscript that suffers from a lack of one often suffers from a paucity of the other as well. First-time novelists and memoirists are particularly prone to falling prey to both, enough so that the professional readers’ stereotype of a first submission is — are you sitting down? — a story that meanders episodically from event to unrelated event, just like real life.

“And just like real life,” our old pal, Millicent the agency screener, has been known to murmur over manuscripts, “any randomly-chosen scene will not appear to a bystander to be going anywhere in particular. Is there a point to all of this slice-of-life activity?”

Why might first books be more likely to fall prey to this pervasive problem than others? Keeping both conflict and tension high for an entire manuscript is darned difficult; it’s a learned skill, and many quite talented writers have been known to write a practice book or two before they learn it.

Oh, should I have checked again that you were sitting down before I broached that one?

The other major reason first books tend to drag is that writers new to the biz are far less likely to sit down and read their manuscripts front to back before submitting them than those who’ve been hanging around the industry longer. Long enough, say, to have heard the old saw about a novel or memoir’s needing to have conflict on every page, or the one about the desirability of keeping the tension consistently high in the first fifty pages, to keep Millicent turning those submission pages.

Yet another reason that I keep yammering at all of you to — sing along with me now, long-time readers — read your manuscript IN ITS ENTIRETY, IN HARD COPY, and OUT LOUD before submitting it. Lack of conflict and tension become far, far more apparent when a manuscript is read this way.

Actually, pretty much every manuscript mega-problem is more likely to leap off the page at the reviser reading this way, rather then the more common piecemeal scene-by-scene or on-the-screen approaches. This is particularly true when a writer is revising on a deadline — or has just received a request for pages from a real, live agent.

Which is, of course, precisely when it’s most tempting not to give your work a thorough read-through. Especially in the second case: if you’re like the overwhelming majority of aspiring writers, you’ll be so excited by a positive response to your query that you’ll want to pop those pages in the mail or hit the SEND button within 24 hours or so. You know, before that nice agent changes his mind.

If you read that last paragraph and cried, “By gum, that’s me!” relax. Requests for pages don’t expire for a year or so, typically. Even if the request came as the result of a successful pitch — and if so, kudos on your bravery — an aspiring writer does not, contrary to popular panicked opinion, need to get the requested materials onto the agent’s desk before s/he forgets the pitch. If one pitched at a reasonably busy conference, it’s safe to assume that s/he will forget your pitch — but that s/he will have taken good notes.

Translation: you have time to proofread before sending all or part of your manuscript. In fact, it’s only professional to take the time to do so.

Unfortunately, those whose writing would most benefit from a good, hard, critical reading tend to be those less likely to perform it. While many aspiring writers develop strong enough self-editing skills to rid their entries of micro-problems — grammatical errors, clarity snafus, and other gaffes on the sentence and paragraph level — when they’re skidding toward a deadline, they often do not make time to catch the mega-problems.

So let’s all chant the mantra together again for good measure: before you submit so much as a paragraph of your writing to a professional reader, it would behoove you to read it IN ITS ENTIRETY, IN HARD COPY, and OUT LOUD.

I know, I know: it has too many syllables to be a proper mantra. Chant it anyway, so it doesn’t slip your mind the night before that contest deadline.

Many a hand has been in the air for many a paragraph now, hasn’t it? “But Anne,” anguished middle-of-the-night manuscript contemplators everywhere wail, “how can I tell if my manuscript does indeed lack conflict and/or tension? I’ve read some of the individual passages so often now that they seem set in stone to me.”

Excellent question, anguished self-editors. While there are as many individual causes of sagging tension and conflict minimization as there are plotlines, certain types of narrative choices are more conducive to producing them. In the interest of keeping all of you revisers’ spirits up as you approach the often-daunting task of revision, I’m going to begin with the easiest to spot — and one of the simpler to fix.

I like to call this extremely common manuscript phenomenon the Short Road Home, and it comes in two flavors, full-bodied and subtle. Today, I shall focus on the full-bodied version.

The Short Road Home crops up when a problem in a plot is solved too easily for either its continuance or its resolution to provide significant dramatic tension to the story — or to reveal heretofore unrevealed character nuances. Most often, this takes the form of a conflict resolved before the reader has had time to perceive it as difficult to solve — or understand what the stakes are.

What might the SRH look like on the page? Well, in its full-bodied form, characters may worry about a problem for a hundred pages –- and then resolve it in three.

We’ve all seen this in action, right? A character’s internal conflict is depicted as insurmountable — and then it turns out that all he needed to do all along was admit that he was wrong, and everything is fine. The first outsider who walks into town and asks a few pointed questions solves a decade-old mystery. The protagonist has traveled halfway around the world in order to confront the father who deserted him years before — and apparently, every road in Madagascar leads directly to him.

Ta da! Crisis resolved. No roadblocks here.

The thing is, though, blocked roads tend to be quite a bit more interesting to read about than unblocked ones. So you can hardly blame Millicent for becoming impatient when pages at a time pass without conflict — and then, when the long-anticipated conflict does arise, the narrative swiftly reaches out and squashes it like a troublesome bug.

Wham! Splat! All gone, never to be heard from again. Perhaps like so:

Percy rumpled his hair for what must have been the fifteenth time that day. How on earth was he going to find his long-lost relative in a city of half a million people, armed with only a ten-year-old photograph and a dim memory that Uncle Gerard adored hazelnut gelato?

Perhaps that was the best place to start; he nipped around the corner to Gelato Galleria. After all, sensory memories were always the strongest.

“Hazelnut?” The man behind the counter seemed thunderstruck. “Only one customer has ever ordered hazelnut here. Mr. Gerard’s my best customer.”

Percy reached across the counter to grasp him by his striped lapels. “When was he last in? Be quick, man — it may be a matter of life and death.”

“Th-this morning. He ordered seven pints for a party this evening. I’m supposed to deliver it.”

“Allow me.” Percy’s tone dispensed with the possibility of further discussion. “I would be delighted to deliver it for you.”

Or maybe like this:

Irene mopped her sopping brow, staring after the departing train. Her last chance for redemption chugged away from her. If only she hadn’t been so stubborn! Or so true: Mother had been wrong to extract that promise on her deathbed, the one about never revealing her true identity. Now, the only sister she would ever have was gone from her life forever.

She was wiping her eyes furtively when someone tapped her on the shoulder. Really, strangers were so pushy these days. She wheeled around.

“I missed my train,” Eileen said sheepishly. “Would you mind putting me up for another night?”

“Another night?” Irene threw her arms around her sibling. “You can stay with me forever. You are my identical twin!”

“Well,” Eileen murmured into her sister’s curls, “that would explain why meeting you three hundred pages ago was so like gazing into a mirror. How strange that nobody else noticed the resemblance, eh?”

Or, even more common, the too-quickly-resolved conflict on the scene level:

“I had that paper a minute ago,” Archibald said, beginning to contemplate perhaps thinking about maybe starting to contemplate looking for it. “Where can it be? Without it, I cannot walk into that meeting.”

“Is this it?” Grace held up the wastepaper basket, angled so he could see within its shallow depths.

Relieved, he fished it out. “Thanks, I would have been lost without it.”

It drives Millicent nuts. “If a conflict so unimportant to the plot and/or character development that it can be disposed of this quickly,” she murmurs, “why include it in the manuscript at all?”

Good question, Millie — often, a problem’s being too easy to solve is an indicator that it could be cut with no cost to the story. Or that the problem was not set up in sufficient detail in the first place. Slice-of-life scenes are, alas, particularly susceptible to too-quick resolution, as are scenes where, heaven help us, everyone is polite.

Yes, you read that correctly. Few traits kill conflict on a page as effectively as a protagonist who is unfailingly polite. Contrary to popular belief amongst writers, a monotonously courteous protagonist is almost never more likeable than one who isn’t — and even everyday polite statements tend to make professional readers start glancing at their watches.

Why? Well, as delightful as courtesy is in real life, polite dialogue is by its very definition generic; it reveals nothing about the speaker except a propensity toward good manners.

Don’t believe me? Here’s an exchange that crops up in a good 90% of submitted manuscripts.

“Why, hello, Betty,” Marjorie said.

“Hello, Margie. How are you today?”

“Fine, thanks. And you?”

“Fine. How are the kids?”

“Fine. How is your mother doing?”

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

“Oh, yes. It seems to be spring at last.”

“Yes. Yes, it does.”

Put down that revolver, Millicent. I assure you, life is still worth living.

But you see the problem, right? On the page, good manners are predictable — and thus inherently tension-reducing.

Or, to put it as Millicent would, “Next!”

Take care, however, not to pursue the opposite route from Short Road Home by creating false suspense; Millicent doesn’t like that much, either. False suspense is the common tension-increasing technique of withholding information from the protagonist that a fairly simple and logical action would have revealed earlier in the plot, or even in the scene — or by denying the reader information that the protagonist already knows.

Trust me: if the clue is in plain sight, most professional readers will resent it if the narrative doesn’t point it out the first time it appears; if the protagonist has traveled five hundred miles to ask his grandmother about her past, Millicent is going to get angry if he just sits there passively and waits for her to blurt out the long-hidden information, rather than asking her about it.

Ditto if the protagonist sees his late cousin’s face appear in a window, confronts some hideous monster in the closet, and/or recognizes that the French ambassador is actually his long-lost brother — but the reader is not filled in on what he knows, or even sees, for six more chapters. Amongst the pros, it’s considered a cheap form of tension-building.

Not sure why? Okay — my God, what’s that creeping up behind your desk chair? Oh, it’s…horrible. Too horrible to describe…

Not a very satisfying plot twist, is it? And it should look familiar from last time: it’s a variation on the she ran through the woods opening.

In its most extreme form, false suspense can become what the fine film critic Roger Ebert calls an Idiot Plot, one where the fundamental problem of a story could have been solved if just one character had asked just one obvious question early in the plot. (“Wait — how will our wandering unarmed into the murder’s lair lay a trap for him?”)

We’re all familiar with Idiot Plots, right? Sitcom episodes very, very frequently feature them, presumably so any given issue can be resolved within 22 minutes. A zany crew of misfits is hardly likely to solve the world hunger problem in that amount of time, after all. But a trumped-up conflict based upon Janie’s being afraid Fred will find out that she lied about something really, really unimportant? You can probably write the last scene right now, based upon that last sentence alone.

“Wait a gosh darned minute,” I can hear some of you say. “The very fact that Mssr. Ebert has a pet name for it reflects the fact that Idiot Plots are widely accepted in the entertainment industry. Since the reading public also watches television and movies, wouldn’t they just accept quick resolutions of conflict as the current storytelling norm? If the writing in the scene is good enough, can’t I get away with a few shortcuts?”

Well, it depends: does taking any one of those shortcuts reduce the tension? Would fleshing out a conflict increase it at a crucial point? Would, in short, the manuscript exhibit both conflict and tension on every page if you DIDN’T take those shortcuts?

Before you answer that, bear in mind that a story does not have to be inherently stupid or poorly written to feature an Idiot Plot — or a Short Road Home, for that matter. In the classic comic novel TOM JONES, the heroine, Sophia, spends half the book angry with Tom because she heard a single rumor that he had spoken of her freely in public — and so, although she has braved considerable dangers to follow him on his journey, she stomps off without bothering to ask him if the rumor were true.

And why does Sophia do this, you ask? I’d bet a nickel that Henry Fielding would have said, “Because the plot required it, silly. If she’d stuck around at the inn to ask him, the romantic conflict would have been resolved in thirty seconds flat!”

That may have been sufficient reason to satisfy an editor in the 18th century, but let me assure you that the folks working in agencies and publishing houses are made of sterner stuff these days. They’ve seen the same movies and sitcoms you have: they’re tired of Idiot Plots and Short Roads Home.

“Show me something fresh,” Millicent cries at the stacks and stacks of manuscripts on her desk, “something I haven’t seen before!”

So here’s a special message to those of you who have deliberately held your respective noses and produced Idiot Plots because you thought the market preferred them: don’t. Try adding legitimate conflict to every page instead and seeing what happens.

Well, that was easy. I guess my work here is done.

Or does a certain amount of disgruntlement linger in the air? “Well, you may not like it, Anne,” some of you mutter, “but I have seen the Short Road Home used countless times in books. How can a trait knock my manuscript out of consideration when so many prominent writers do it routinely? Clearly, someone is selling stories with these kinds of devices.”

I can easily believe that you’ve seen the Short Road Home a million times in published books, and a million and twelve times in movies — so often, in fact, that you may not have identified it as a storytelling problem per se. Allow me to suggest that the main producers of Short Roads Home, like Idiot Plots are not typically first-time screenwriters and novelists, though, but ones with already-established track records.

In other words, it would not necessarily behoove you to emulate their step-skipping ways. As a general rule, the longer ago the writer broke in and/or the more successful he has been, the greater latitude he enjoys. There’s even an industry truism about it: to break into the business, a first book has to be significantly better than what is already on the market.

To be blunt, as good is not necessarily good enough. Sorry to have to be the one to tell you that, but it’s just a fact of the literary market.

That inconvenient reality can create some tension (hooray for drama!) in a critique group made up of a mix of published and unpublished writers. Years ago, a genuinely fine writer of many published books brought my critique group a chapter in which her protagonist escaped from a choking situation by kneeing her attacker (who happened to be her boyfriend) in the groin. The attacker slunk off almost immediately, never to return; conflict resolved.

Naturally, three aspects of this scene immediately set off Short Road Home alarm bells for me. First, reflexes tend to kick in pretty darned quickly. My self-defense teacher taught me that a man will instinctively move to protect what she liked to call “his delicates,” so that area is not a good first-strike target when you were defending yourself. So why didn’t the bad guy automatically block the blow?

Second, the attacker was able to walk out of the room right away after being battered in the groin, with no recovery time. Simple playground observation tells us is seldom true in these instances.

Third — and what marked this exchange as a SRH rather than merely physically improbable — this scene ended a relationship that had been going on for two-thirds of the book. One swift jab, and both sides spontaneously agreed to call it a day.

Is it just me, or are most relationships, abusive or otherwise, just a touch harder to terminate permanently? I’ve had dentists’ offices try harder to keep in touch with me. By this story’s standards, everyone who works at my college alumni magazine is a dedicated stalker.

But because my colleague was an established author, she was able to get this SRH past her agent, although her editor did subsequently flag it. However, it’s the kind of logical problem reviewers do tend to catch, even in the work of well-known writers — and thus, it should be avoided.

But that’s not the only reason I brought up this example. I wanted you to have a vivid image in your mind the next time you are reading through your own manuscript or contest entry: if your villain doesn’t need recovery time after being kneed in the groin or the equivalent, perhaps you need to reexamine just how quickly you’re backing your protagonist out of the scene.

One true test of a SRH is if a reader is left wondering, “Gee, wouldn’t there have been consequences for what just happened? Wasn’t that resolved awfully easily?” If you are rushing your protagonist away from conflict — which, after all, is the stuff of dramatic writing — you might want to sit down and think about why.

Another good test: does the first effort the protagonist makes solve the problem? Not her first thought about it, mind you — the first time she takes an active step. If your heroine is seeking answers to a deep, dark secret buried in her past, does the very first person she asks in her hometown know the whole story — and tell her immediately? Or, still better, does a minor character volunteer his piece of her puzzle BEFORE she asks?

You think I’m kidding about that, don’t you? You don’t read many manuscripts, I take it. All too often, mystery-solving protagonists come across as pretty lousy detectives, because evidence has to fall right into their laps, clearly labeled, before they recognize it.

“Funny,” such a protagonist is prone to say, evidently looking around the house where he spent most of his formative years and raised his seventeen children for the very first time, “I never noticed that gigantic safe behind the portrait of Grandmamma before.”

Seriously, professional readers see this kind of premise all the time. An astoundingly high percentage of novels feature seekers who apparently give off some sort of pheromone that causes:

a) People who are hiding tremendous secrets to blurt them out spontaneously to someone they have never seen before;

b) Long-lost parents/siblings/children/lovers whose residence has remained a source of conjecture to even the most dedicated police detectives to turn up in an instantly-fathomable disguise toward the end of the book;

c) Flawlessly accurate local historians to appear as if by magic to fill the protagonist in on necessary backstory at precisely the point that the plot requires it;

d) Characters who have based their entire self-esteem upon suffering in silence for the past 27 years suddenly to feel the need to share their pain extremely articulately with total strangers;

e) Living or dead Native American, East Indian, and/or Asian wise persons to appear to share deep spiritual wisdom with the protagonist;

f) Diaries and photographs that have been scrupulously hidden for years, decades, or even centuries to leap out of their hiding places at exactly the right moment for the protagonist to find them, and/or

g) Birds/dogs/horses/clouds/small children/crones of various descriptions to begin to act in odd ways, nudging Our Hero/ine toward the necessary next puzzle piece as surely as if they had arranged themselves into a gigantic arrow.

Here’s a good rule of thumb for whether your story is taking the Short Road Home: at every revelation, ask yourself, “Why did that just happen?”

If your answer is, “So the story could move from Point A to Point B,” and you can’t give any solid character-driven reason beyond that, then chances are close to 100% that you have a SRH on your hands.

What should you do when you find one? Well, clear away the too-easy plot devices first, then try throwing a few metaphorical barrels in your protagonist’s path. Give him a couple of unrelated problems, for instance. Make the locals a shade more hostile, or a cohort a touch less competent. Add a subplot about a school board election. Have the old lady who has spent the last fifty years proudly clinging to letters from her long-lost love burn them ten minutes before she dies, instead of handing them over to the protagonist with an injunction to publish them with all possible speed.

Make your protagonist’s life more difficult any way you can, in short. Go ahead; s/he’ll forgive you.

On the plot level, having your protagonist track down a false lead or two is often a great place to start making his life a more interesting hell. Trial and error can be a fantastic plotting device, as well as giving you room for character development.

For some fabulous examples of this, take a gander at almost any film from the first decade of Jackie Chan’s career. In many of them, Our Hero is almost always beaten to a pulp by the villain early in the story — often more or less simultaneously with the murderer’s gloating over having killed the hero’s father/mother/teacher/best friend. (In Western action films, the same array of emotions tends to be evoked by killing the hero’s beautiful wife, who not infrequently is clutching their adorable toddler at the time.) Then we see him painfully acquiring the skills, allies, and/or resources he will need in order to defeat the villain at the end of the film.

Or check out the early HARRY POTTER books. When Harry and his friends encounter new threats, they don’t really have the life experience to differentiate between a teacher who dislikes them and someone who wants Britain to be overrun by soul-sucking wraiths. Yet miraculously, by responding to the smaller threats throughout the school year, Harry et alia learn precisely the skills they will need to battle the major threat at the end of the book.

Oh, you hadn’t noticed that the plots of the first three books were essentially identical? Nice guy, that Voldemort, carefully calibrating his yearly threat to wizardkind so it tests Harry’s skills-at-that-age to the limit without ever exceeding them.

Now, strictly speaking, quite a bit of that pulp-beating and lesson-learning is extraneous to the primary conflict of the story’s ultimate goal of pitting Good Guy vs. Bad Guy. Jackie Chan and Harry could have simply marched out to meet the enemy in the first scene of the movie or book. We all know that he’s going to be taking that tromp eventually.

But half of the fun for the audience is watching the hero get to the point where he can take on the enemy successfully, isn’t it?

Remember, the goal of storytelling is not to get your protagonist from the beginning to the end of the plot as fast as possible, but to take your readers through an enjoyable, twisted journey en route. Short Roads Home are the superhighways of the literary world: a byway might not get you there as quickly, but I guarantee you, the scenery is going to be better.

Try taking your characters down the side roads every once in awhile; have ‘em learn some lessons along the way. Stretch wires along the path in front of them, so they may develop the skills not to trip. And let ‘em fail from time to time — or succeed occasionally, if your protagonist is disaster-prone. Varied outcomes are usually interesting for the reader than continual triumph or perpetual defeat.

Next time, I’m going to tackle a harder-to-spot version of the Short Road Home — because yes, Virginia, today’s was the easy one to fix. Keep up the good work!

Pet peeves on parade, part XIX: there was something about his eyes, something indescribable…



I could not allow another week to end, campers, without filling you in on yet another common professional readers’ pet peeve. Specifically, one that drives your humble servant up the wall, not only because it is ubiquitous in manuscript submissions, but because when it does appear, its context usually makes it pretty obvious that the writer who penned it considers it (a) original, (b) philosophical-sounding, or even profound, and (c) pretty darned good writing, rather than what it actually is: (a) a hackneyed phrase, (b) descriptively vague, and (c) see (a) and (b)

What is this pervasive descriptive shortcut, you cry, famous for causing gentle souls like me — and our old pal, Millicent the agency screener — to rend our garments and wail when good writers foist it upon us? Let’s see if you can spot it in its natural habitat.

Here are five sterling examples of it, ripped from five different manuscripts. Let the garment-rending begin!

“If that’s really the way you feel, I have nothing more to say.”

Something in his eyes made Aileen pause, reconsider, turn back. “What is it you’re not saying, Jeremiah?”

He smiled, slowly, cruelly. “Ah, that would spoil the horrible surprise, wouldn’t it?”

Did anything in that exchange strike you as odd? If you are shaking your head at the computer screen, you’re not alone — most aspiring writers would see nothing wrong with it.

Millicent, to put it mildly, would. To gain a sense of why, let’s examine the phenomenon in another incarnation.

A feeling washed over Emily, strong and powerful. She couldn’t have put it into words, even to her closest friends, but it shook her to the core of her being.

“Yes!” she cried, startling everyone in the courtroom. “I shot the sheriff!” She turned to her incredulous husband. “But I swear to you, Archibald, I did not shoot the deputy.”

See any similarity between those last two examples? Millicent would. She’d also spot a definite familial resemblance between both of them and this:

Oliver walked her forward, keeping his hands over her eyes. Some ten feet of awkward stumbling later, he gently removed them. “Look.”

Perdita gasped. A vista of indescribable beauty spread out before her. “Oh, my! Why hadn’t I noticed this before?”

“Beats me.” Oliver returned to his game of solitaire. “I would have thought the Grand Canyon was kind of hard to miss.”

Starting to feel an inkling of Millicent’s well-justified irritation? One more time, maestro, please.

The audience swayed on its feet, blasted by the power of Mervin’s voice. It was not what he said, precisely, or even the words he chose to express it that moved them so strongly: it was an indefinable manner, a confidence that told them as surely as if he had shouted it that this man was telling the truth.

It’s begun to feel redundant, hasn’t it, even though I assured you at the outset that each of these examples came from a different source? Welcome to the world of the agency screener: if 35 out of the 127 first pages Millicent reads today contain the same descriptive shortcut — certainly within the bounds of possibility, with a trope this popular — Instance No. 34 is going to seem as repetitious as if it had appeared on the same page as Instances Nos. 28-33.

“Not this again!” she mutters, rending her aforementioned garments. “Show me something original, I beg you!”

We could feel smug, of course, that Millicent has just fallen into precisely the same phrasing trap to which she is objecting: the writer would be entirely justified in inquiring what precisely she had in mind. We could also point out that it isn’t particularly fair to the writer of Instance No. 30 that a professional reader might well have been more annoyed by the sight of this descriptive shortcut than she was by Instance No. 2. And who could fail to feel for the aspiring writer who decided that Instance No. 34 is just what his page 1 needed but did not call upon the descriptive device again for another 273 pages being treated as precisely as repetitious as the writer who elected to place Instances Nos. 5-9 all on the same page?

Oh, you don’t think that really happens? Au contraire, mes amis. I can beat that record in two sentences flat.

There it was again, that odd, vague sensation. It told Erminia without words that something, somewhere, somehow, was wrong.

What sensation?” Millicent demands, ripping her cuffs to shreds. “What is Erminia feeling, precisely? What does she think is wrong, and for what possible narrative reason has the writer chosen to hide the content of her fears from the reader?”

You must admit, these are perfectly reasonable questions. After all, it’s the writer’s job to describe what’s going on in sufficient detail for the reader to be able to picture it, not the reader’s job to fill in the details when the writer prefers to remain vague.

You wouldn’t know it, though, from a hefty minority of the submissions that cross Millicent’s desk on a daily basis. Apparently, there are a whole lot of aspiring writers who believe — wrongly, according to the overwhelming majority of professional readers — that leaving crucial sensations, thoughts, intuitions, and even physical descriptions to the reader’s imagination is not only permissible, but stylish. It’s hard to blame them, really: unless one happened to have had the privilege of reading many manuscripts or contest entries back to back, one wouldn’t have any idea just how common this descriptive shortcut is.

Trust me, it decorates many, many first pages. And contest entries. And dialogue. You’d be astonished at how many novels (and memoirs, actually) open with this well-worn trope — it’s an extremely popular (and thus Millicent-annoying) means of establishing suspense from line 1.

A noise came from behind her, causing Jemima to jump. Silly to be so nervous, when she had been through these woods more times than she could count. Admittedly, she had never been carrying quite this heavy a load of goodies for her grandmother, bread and sausage and pears and three whole roasted chickens.

There it was again. Something was following her; she was sure of it now.

Already, Millicent’s collar is in tatters. “What noise?” she wails, beginning on her right sleeve. “What did it sound like? What does she think is following her, and upon what auditory clues is she basing that conclusion. Also, what do three ands in a row add to this description that would not be adequately conveyed by the grammatically correct bread, sausage, pears, and three whole roasted chickens?”

Does the general pallor that just spread over half my readership’s faces indicate that some of you were under the impression that featuring this kind of and repetition within a single sentence was (a) stylish, (b) technically correct, (c) a narrative choice unlikely to annoy Millicent if done more than once every 50 pages or so, (d) a narrative choice unlikely to annoy Millicent if done more than every 50 lines or so, (e) a narrative choice unlikely to annoy Millicent if done more than once per paragraph, or (f) all of the above? I’m afraid I have some bad news for you, then.

It’s even worse news if you happen to subscribe to the rather pervasive school of thought that holds that regardless of whether the point of view is in the first, second, or third person — heck, even if it is from the omniscient perspective of Somebody Up There who can pry into every character’s mind — it is always an effective writing technique to make the narrative voice sound like someone speaking out loud in casual conversation in the year in which the manuscript was written. While this can work beautifully for novels and memoirs set in the recent past and written in the first person, chatty contemporary spoken word styles will not fit comfortably with every storyline.

It’s especially jarring in stories set in eras of the past when people spoke more formally — which is to say pretty much anytime prior to the last decade. Every era has its own slang, of course, but there’s no denying that the vagueness of modern conversation would have puzzled Jane Austen exceedingly, either in dialogue or narration.

Everybody knows that a single man who happens to be rich must be looking to get married. Or something.

Whatever you do or don’t know about his feelings or beliefs, no sooner does he set foot in a neighborhood than everyone decides he belongs to one of their daughters. Whatever!

“May one inquire,” Miss Austen demands, ripping her delicate handkerchief in long, clean lines, “to what this author is referring? Why has he elected to dispense with subject-object agreement, that well-belovèd and inflexible rule denoting that the subject of a sentence — in this case, everyone — should agree in number with its object. I would lay it down as a general principle, then, that everyone and his daughter would always be preferred by right-thinking readers to everyone and their daughters. And what, if I may be so bold as to ask, is the significance of whatever in this context?”

Search me, Aunt Jane. Millicent and I have been wondering about that, too.

Another popular species of vagueness in openings — also frequently born, I suspect, out of a desire to create suspense by omission, rather than via a detailed depiction of an inherently tense situation — is a little something we pros like to call the unnamed protagonist cliché. Tellingly, it is also known by another moniker: she ran through the forest…

Oh, you may laugh, but you wouldn’t believe how many manuscripts begin rather like this:

She fled through the forest, her long, red hair whipping against the bundle she hid ineffectually under her cloak in an attempt to shield it from the driving sleet. All she knew was that something was pursuing her, something terrible, something violent. Something that had forced her to leave behind everything she had ever known. Something that had changed her life forever.

Suddenly, a noise came from behind her…

By this point in the afternoon’s reading, poor Millicent’s wardrobe is in tatters. “Who is this woman, and why should I care that her life has changed forever when the narrative hasn’t yet told me anything about her previous life? From what is she fleeing? Am I supposed to think that the bundle is a baby, or am I only thinking that because it was a baby in 15 out of the last 37 similar openings? And why oh why not just tell me what’s chasing her?”

Again, perfectly legitimate questions — but not, it’s probably safe to assume, reactions the author would prefer this opening to elicit from a screener. Or indeed, any reader. Presumably, the writer is hoping that lay reader would read the opening above and murmur, “Heavens, will she get away? What is pursing her? Is the baby alive?” — and be spurred by those questions to keep reading.

Millicent, however, is unlikely to scan even one more line; had I mentioned how frequently she is treated to this kind of false suspense? “Is there any particular reason that I’m being kept in the dark about this broad’s name?” she murmurs, the frayed edges of her garments wafting gently in the air conditioned breeze. “Is it a state secret? Is it really my job to read on until the narrative deigns to tell me something that basic? Or maybe this writer has seen too many movies; in a book written in the third person, you don’t need to wait until someone addresses the protagonist to find out her name.”

Trust me, you’re better off identifying your characters right away.

A few valiant specificity-haters have had their hands in the air for paragraphs on end. “But Anne,” they point out, “in that last example, the writer was obviously just trying to start the story with a bang. You must admit that there’s no shortage of action in that opening, nor is there any serious question about what the book is about: the story that follows is obviously going to concern this woman, her bundle, and all of that red hair in their collective attempt to reach safety from the unnamed threat. Millicent can’t deny that it is exciting!”

Actually, she could — you would be astonished how efficacious sheer repetition can be in sapping the thrill from an exciting-but-common opening scene. And let’s face it, the long, red hair cliché and the everything she had ever known exaggeration would not exactly stun Millicent with their originality, either. Fleeing maidens habitually forget to tie back their long red or blonde hair while they are leaving everything behind, burning their bridges and changing their lives forever, whilst fleeing unnamed pursuers.

Those of us born brunette and/or bob our hair should be deeply grateful, evidently. An alien from the Planet Targ dropped into Millicent’s desk chair to form opinions of life on earth from manuscript submissions would undoubtedly conclude that we dark-haired females alone remain safe at home, rather than being chased by noises offstage into some conveniently nearby woods.

One more omnipresent variety of rend-inducing narrative vagueness, then I shall sign off for an evening of peaceful brunette serenity. See if anything in the following little gem strikes you as a potential Millicent-irritant.

As smoke curled up Blair’s nostrils, the irreality of the situation smote his consciousness head-on. It was like a movie: he simply observed his nearest and dearest go up in flames. As much as he longed to change the channel, he couldn’t.

Actually, there were two classic pet peeves cunningly concealed in that compact paragraph; did you catch them? First, the it was just like a movie trope has been so widely used in submissions since the 1920s that even the most recently hired Millicent is likely to regard it as a cliché at this late date. A more experienced Millicent might also regard it as the narrative shorthand it is: rather than showing readers precisely how and why Blair experienced the situation as divorced from his real life, the narrative not only chooses to tell us in just a few words what it was like — the writer is presuming that every reader will know precisely what she means by it was like a movie.

In essence, then, the writer is expecting the reader to guess in what specific ways Blair’s experience was filmic. And we all know how Millicent feels about that species of narrative expectation, right?

“Is it my job to provide the necessary description?” she fumes, taking a stapler to her hitherto undamaged skirt. “Isn’t it the writer’s responsibility to, well, write?”

Come on, admit it: she has a point. She would also be well within her rights to call out the narrative for its other professional reader-piquer, the mixed metaphor.

Oh, you didn’t catch it? Although we are told that Blair’s current situation is like a movie, he longs to change the channel as if he were watching television.

Someone didn’t reread this submission IN ITS ENTIRETY, IN HARD COPY, and OUT LOUD, clearly.

What’s the cumulative moral here? Select your words with care — remember, all Millicent, or any reader, actually knows about the scene you are presenting is what you describe on the page. Yes, it’s undoubtedly quicker and more convenient to allow the reader to fill in the minutiae, but if you resort to vagueness or shorthand, how can you be sure that every reader will come up with the specifics you intend?

Or to put it another way: isn’t your creative vision worth conveying in detail?

And for heaven’s sake, tempestuous redheads and blondes-in-peril, grab a barrette or a baseball cap on your way out the door. Perhaps without all of that hair flying about in your eyes, you can finally get a good look at who or what is pursuing you.

Maybe then you could describe it to us. Keep up the good work!

Pet peeves on parade, part XVIII: Ivan who?

Hello, campers –
As those of you who have been hanging around the Author! Author! community for a while are, I hope, aware, I seldom rerun a former post wholesale. Oh, I’m not above taking an old post, dressing it in a new gown, switching out some jewelry, and sending onto the runway again, blinking at the bright lights, but it’s rare that I don’t add at least 5 or 6 pages of new material.

Today, I’m bringing you a post from last year’s Frankenstein manuscript series. It’s quite apt for our ongoing discussion of perennial professional readers’ pet peeves, but perhaps equally important today, I can post it with a minimum of keyboard time. I took a tumble earlier today, and I’m under doctors’ orders to take it easy.

This is as easy as I ever take it, apparently: I punched up today’s version only minimally. Enjoy!

Have you noticed a running pattern in the last week or two of posts on self-editing, campers? Have you dimly sensed that no matter where my suggestion du jour may begin, my narratives always end up taking a scenic detour through the joys of keeping the pacing tight in your manuscript? Has your significant other been shaking you awake, demanding that you cease muttering, “But does it have conflict on every page? EVERY page?” over and over again in the night? Have you found yourself clapping your hands loudly in boring work meetings, exclaiming, “Where’s the tension? Let’s get things moving here, people!” At family gatherings? At church? While waiting in line to vote?

Glad to hear it. My subtle indoctrination technique is working!

In case I haven’t yet dumped enough cold water on those of you intending to submit your writing to professional scrutiny any time in the foreseeable future: manuscripts or book proposal that drag their feet even a little tend to get rejected. Especially, as we discussed yesterday, those that meander within the first few pages. And while we’ve all read dozens of published books that have rocked us gently to sleep by page 4, and it truly isn’t fair that your manuscript is being held to a higher standard than THOSE evidently were, sitting around resenting the differential isn’t going to help you get your work published so effectively as making sure that YOUR manuscript is as tight as a drum.

I’m aware that the very notion makes half of you want to curl up into a protective ball around your manuscript, whimpering, “NO! You can’t cut ANY of it!” I know perfectly well that many, if not most, aspiring writers beard the heavens with bootless cries against the strange reality dictating that a manuscript should be publication-ready before it has an agent, who will probably ask the writer to change it significantly before sending it out to editors, anyway. I am even fully cognizant of the fact that from a writerly perspective, we love your writing — give us less of it doesn’t make much sense at all.

Yet a sober recognition of the extreme competitiveness of the literary market and the ability to self-edit in order to render one’s work more marketable within its ever-changing landscape are species characteristics of the professional working writer; while it’s not completely unheard-of for a first draft to be what ends up on the published page, by and large, producing a book-length manuscript purely from inspiration, without revision or even close subsequent reads by the author prior to an editor’s involvement, is roughly as rare amongst the successful author population as qualifying for the Olympics is amongst the world population.

I know you have it in you to approach this like a pro. Let’s talk conflict.

As I may have mentioned once or twice throughout this series, it’s an industry truism that a novel should have conflict — or still better, tension — on every page. While anybody who has had a half-hour conversation with me about the current state of the industry knows that I feel this standard should not be applied arbitrarily to every book in every genre, you should be aware of this axiom — because, I assure you, every agency screener is. In my ruminations on the subject, the word arbitrary tends to come up, as do the phrases knee-jerk reaction, radical oversimplification of a complex array of literary factors, and power run mad. I’ve been known to question whether, for instance, BREAKFAST AT TIFFANY’S, CATCH-22, or OF HUMAN BONDAGE could find a publisher today as new books, much less an agent.

Or, indeed, virtually any of the bestsellers of the 18th or 19th centuries. Don’t believe me? Okay, here is the opening page of the absolutely last word in exciting dramatic novels in 1819, IVANHOE:

Ivanhoe first page

“What is this?” a modern-day Millicent mutters under her breath, reading for the SASE that, being a conscientious submitter, Sir Walter Scott had included with his submission. “A book about furniture? A manual on room decor? Where is the conflict? And what’s the deal with the punctuation? Next!”

But that’s rich array of rejection reasons would not be what Sir Walter would hear, right? No, his only clue about why his submission was rejected would be this:

Dear Scott:

I read your submission with great interest, but I’m afraid your manuscript does not meet our needs at this time. I just didn’t fall in love with the story.

Another agent may well feel differently, and I wish you every success finding a home for this book.

Sincerely,

Millicent’s boss
Great Big Agency

I’m making light of it, but honestly, I have sat up many a midnight, worrying about all of the talented aspiring writers out there currently relying upon, say, Charles Dickens or Jane Austen as pacing role models, only to have their hearts broken by rejection by agents, editors, and contest judges who, rationally enough, base their assessments about whether a book is marketable upon what has been selling within the last five years, rather than upon the kind of abstract notion of Good Literature that most of us encountered in our English classes. To say nothing of writers who chose as their lodestar books released a decade ago, or even, in some especially fast-changing genres, just a few years back.

If you doubt that, I invite you to round up all of the agents who were trawling writers’ conferences for chick lit in, say, 2002, at the height of the post-BRIDGET JONES enthusiasm, and ask them whether they still rabidly seeking chick lit today. Those genuinely enamored of the genre have stuck with it, of course, but a good two-thirds of them subsequently spent a couple of years pursing the next big YA vampire classic. (2011 Anne here: or are currently as busy tumbling over backwards to avoid being affiliated with the next THREE CUPS OF TEA as they were a year ago trying to find it.)

My point is, publishing is driven as much by fads as by an appreciation for the beauty of a well-crafted sentence; in the mid-1980s, for instance, a novel’s being over 100,000 words was considered completely acceptable. Yet interestingly, the truism about conflict on every page has endured for a couple of decades now. There are plenty of agents and editors out there, and good ones, who do apply this standard to submissions, so you’re better off if you think about the pacing issue before you send your baby out the door, rather than later puzzling over a form-letter rejection, wondering if the pacing could possibly have been the problem.

Much of the time, it is. So much so that I feel a checklist coming on:

(1) If you’re editing for length, seeking out comparatively slow bits to shorten — or, dare I say it, cut altogether — should be at the top of your to-do list.

Actually, a search-and-minimize technique isn’t a bad idea even if length isn’t your particular bugbear, either, but it’s absolutely essential when editing for length.

What should go in the place of the trimmed bits? Conflict, of course.

(2) If you want to keep a slow scene, ramp up the conflict within it.

“But Anne,” those of you who write introspective books cry, “what can I do if my plot is, in fact, rather sedate? I can hardly make the supermarket down the block spontaneously combust in order to add spice to my domestic drama, can I? It would look so odd.”

This is a good question, and prompts me to ask another: what does tension on every page mean?

Should every character be fighting with every other constantly? Do you have to show things exploding at least once every 33 lines? Should the librarian in Chapter 2 pull a switchblade on your protagonist when he tries to check out a book on gardening?

No, on all counts. But how about these tension-increasers?

Some character could want something and not get it on every page, right, without gunpowder being involved.

A character could say one thing and do another.

Every conversation could contain some seed of disagreement.

That’s all realistic, isn’t it? After all, no two human beings are ever in absolute agreement on every point. At least no two I have ever known.

(3) Consider having allies disagree, harbor different motivations — or having the protagonist be less sure of her own.

Trust me, your protagonist’s relationship with her best buddy will come across to the reader as stronger– not to mention more true-to-life — if they have the occasional tiff. A person has to care more about a friend to maintain a relationship through a conflict than through periods of sunny agreement.

So make your characters fight a little for their friendships from time to time. They’ll seem more valuable.

Where overt disagreement is not feasible, then how about a differential between what your protagonist is saying and what she is thinking? The protagonist could habitually bite her tongue, while her angry thoughts run rampant. Internal conflict is definitely interesting.

(4) Seek out dialogue-only scenes and inspect them for lack of tension.

I’m talking about ALL scenes where the dialogue is uninterrupted by narrative text for more than, say, half a page. Reach for your manuscript, scan it for dialogue-only scenes, and check to see whether those scenes are sufficiently conflictual to maintain Millicent’s interest. Most of the time, they don’t.

Did I just hear the battle cry of all of those writers out there who were taught since their infancies that dialogue should speak for itself, and that it is inherently bad writing EVER to include a character’s thoughts in the midst of dialogue? Am I about to be on the receiving end of a body blow from those stalwart souls who have doomed readers to two or three pages on end of pure dialogue, devoid of other activity, or even markers of who is speaking when?

Oh, dear. How shall I put this gently?

If you are so gifted a dialogue-writer that you can convey every nuance of a relationship between two characters at a particular moment in time purely through dialogue, do so with my blessings. But honestly, if you have that particular talent, you might want to go into writing stage or screenplays. Novels, I believe, are places to show complex characters with interesting motivations, people who think and act as well as speak.

Personally, if I want to read transcripted conversations, a novel or memoir is not the first place I look. That’s what trial transcripts are for, after all.

I am aware, though, that there are plenty of writers — and writing teachers — out there who would disagree with me. (Look, Ma: conflict on this page!) If you prefer to follow their precepts, fine. But do be aware that it’s hard to maintain a sense of forward motion throughout pages of dialogue-only text, particularly if one of the speakers is a character the reader does not know particularly well.

(5) Consider the dramatic appeal of duplicity.

This is a great way to liven up those dialogue-only scenes. Few of us say everything that is on our minds at any given moment. Anyone who has ever been a teenager being lectured by a parent, for instance, or an employee shouted at by a boss, has direct personal knowledge of a situation where what is said out loud and what is thought is WILDLY different, where reproducing merely the dialogue would not give an accurate picture of what is really going on between these two people.

Almost everyone holds something back when talking to others — out of politeness sometimes, out of fear others, out of strategy, out of love. The struggle to express oneself without giving away the whole candy store is one of the great human problems, isn’t it? So why not let that struggle manifest on the page?

(6) Double-check all dialogue-based scenes for tension.

Is there enough conflict in them? If no emotion is being generated on either side of a discussion, there probably isn’t.

The conflict need not be large; an argument certainly isn’t appropriate to every scene. Are there a couple of small tweaks you could make to increase the tension between these characters, or the tension within the character’s own mind?

(7) Excise dialogue that doesn’t advance the storyline or provide memorable character development.

Is the conversation providing new information, or just rehashing what the reader already knows? If the latter, could the line be cut without the reader losing a sense of what is going on?

You’d be stunned by how often the answer is yes. Remember, repetition bogs down pace considerably. Trim as much of it as possible — yes, even if real-life characters would say precisely what you already have on the page.

(8) Scrutinize fill-in-the-friend scenes for conceptual redundancy.

Pay particular attention to scenes where the protagonist is telling another character what just happened; such dialogue is notoriously redundant. In fact, know a very prominent agent, one who gives classes and writes books to give advice to aspiring writers, who insists that any scene where characters are talking over ANYTHING that has already occurred in the book should be cut outright. However, since he also counsels removing any scene where the protagonist drinks tea, sips coffee, drives anywhere alone, or thinks about what is going on, I’m not sure I would advise taking his admonitions as revealed gospel.

But the next time you find your characters sitting in a coffee shop, chatting about what has happened in the previous scene, you might want to ask yourself: would the reader be able to follow what is going on in the book if this scene were cut?

(9) Check the beginnings of scenes (and chapters) for over-long set-ups.

Heck, check them for extra verbiage in general. The writing is often sparer at the end of a scene or chapter than at the beginning.

Why? Well, writers tend to compose in bursts, lavishing more time and detail upon the opening, hitting a groove in the middle — and rushing to get the rest of the scene on paper before that parent-teacher conference ten minutes hence. Openings also tend to be the most revised portions of text: if a writer comes up with a bon mot down the line, she will often insert it near the beginning of a scene or chapter.

(10) Generally speaking, a manuscript that has ups and downs will be perceived by the reader as more exciting than one that does not.

Consider changing the running order of the scenes. Alternating action scenes with processing scenes, or fast-paced scenes with slower ones, will give more movement to the plot.

(11) Experiment with varied sentence structure.

If you find yourself perplexed about the drooping energy of a scene whose action would seem to dictate tight pacing, try this trick o’ the trade: at exciting moments, make the sentences shorter than at more meditative times in your plot. That way, the rhythm of the punctuation echoes the increased heart rate of your protagonist. Your reader will automatically find himself reading faster — which, in turn, will make the suspense of the scene seem greater.

Good trick, eh? You can perform a similar feat with dialogue, to give the impression of greater underlying hostility between the speakers.

(12) Let the dialogue reflect the speakers’ breathing patterns.

We’ve talked about this one before, right? People breathe less deeply when they are upset; breathing shallowly, they speak in shorter bursts than when they are relaxed. Also, agitated people are more likely to throw the rules of etiquette to the four winds and interrupt others. It is not a time for long speeches.

Dialogue that reflects these two phenomena usually comes across to readers as more exciting than exchanges of hefty chunks of speech. If you are trying to make a dialogue-based scene read faster, try breaking up the individual speeches, providing interruptions; the resulting dialogue will seem more conflict-ridden, even if the actual conversation is not about something inherently conflict-inducing.

Seriously, it works. Consider this tame little piece of dialogue:

“We’re having apple pie for dessert?” Albert asked. “I thought we were having cherry cobbler, the kind I like. The kids would love it; it would mean so much to them. Don’t you remember how much time and energy they put into picking those cherries last summer?”

Janie chuckled ruefully. “I certainly do. I was the one who ended up pitting them all. Even from preserves, though, the cherry cobbler you like takes a terribly long time to make. I never deviate from Aunt Gloria’s pie recipe, the one she learned from that traveling pie pan salesman during the Great Depression. Infusing the cherries with cinnamon alone takes an entire afternoon. I can throw together an apple pie in an hour.”

“And the result is divine, honey, with both: your Aunt Gloria certainly learned her lesson from that salesman well. But I’m sure that the kids would like to see the fruits of their labor, so to speak, show up on the dinner table before they’ve forgotten all about summer picking season.”

“Well,” Janie said, sighing, “you have a point, but I simply don’t have time to make another dessert before the Graysons come over for dinner.”

Not exactly a conflict-fest, is it? Now take a gander at the same scene with Albert and Janie taking shorter breaths — and some editorial rearrangement with an eye toward maximizing conflict. To make it an even higher dive, let’s maintain it as a dialogue-only scene:

“We’re having apple pie for dessert?” Albert asked.

“I simply don’t have time,” Janie replied, “to make another dessert before the Graysons come over for dinner.”

“I thought we were having cherry cobbler, the kind I like.”

“Even from preserves, the cobbler you like takes a long time to make.”

“The kids would love it. Don’t you remember how much time and energy they put into picking those cherries last summer?”

“I certainly do. I was the one who ended up pitting them all.”

“I’m sure the kids would like to see the fruits of their labor show up on the dinner table before they’ve forgotten all about summer picking season.”

Janie sighed. “Look, I never deviate from Aunt Gloria’s Great Depression cherry pie recipe…”

“Yeah, your Aunt Gloria certainly learned something from that traveling pie pan salesman.”

“…And infusing the cherries with cinnamon alone takes an entire afternoon. I can throw together an apple pie in an hour.”

“And the result is divine, honey,” Albert sneered.

Quite a different scene, isn’t it, even though the dialogue is almost identical? Hardly divorce-court material, even now, but now the scene isn’t about pie v. cobbler at all: it’s about clashing expectations within a marriage — and what does Albert have against Aunt Gloria, anyway?

If you really get stumped about where to break the speeches, try running around the block, then coming back and seeing how much of each character’s speech you can say out loud before you have to gasp for breath — thus allowing another party opportunity to speak up.

I swear that this really works.

(13) Consider the possibility that you may be able to convey the necessary tension by showing only part of the scene — or winnowing down a conversation to a quick exchange.

Sometimes, less honestly is more. If the goal is to put tension into this particular scene, do you really need more than the beginning and end of the Janie-Albert exchange?

“We’re having apple pie for dessert?” Albert asked.

“I simply don’t have time,” Janie replied, ‘to make another dessert before the Graysons come over for dinner. Your favorite cobbler takes an entire afternoon of my time, but I can throw together a pie in an hour.”

“And the result is divine, honey,” Albert sneered.

Sufficient, isn’t it? That’s four lines of pure interpersonal conflict that could be dropped into any kitchen conversation between spouses of a certain age.

To coin a phrase, sometimes less is more. Keep up the good work!

Pet peeves on parade, part XVII: once more — and this time with feeling!

All finished with your income taxes, campers? Since the 15th was a holiday in Washington D.C., giving us a whole extra weekend to gnaw on our erasers and scratch our heads, I figured that the end of last week was a good time to take a short break from blogging. Call me zany, but I suspect that a fairly hefty percentage of the Author! Author! community is more word-oriented than number-obsessed.

Hey, my high school calculus teacher didn’t call me Liberal Arts Annie for nothing. He had worked his way through college playing poker (or so he claimed); I edited other students’ term papers. It takes all types to make a world.

Which renders it surprising, does it not, that wildly different sorts of people say such similar things in real-life dialogue? Admittedly, I may be more sensitive to verbal repetition than usual at the moment– you wouldn’t believe how often someone recovering from car crash injuries is asked the same questions. Not only by different practitioners, but by the same practitioner at each visit.

I realize that these well-meaning, healing-mongering individuals have forms to fill out and file, but since presumably one is not not their only patient on any given day, or even in the course of any given hour, I can’t imagine that they, too, are not bored to death by the sheer repetition. Quoth the parrots:

“So how are you feeling today? Better? Worse? The same? How is that {fill in body part here} doing? How would you rate your pain on a scale of one to ten, with one being none and ten the worst pain you have ever experienced?

Naturally, as a fully-vested member of the storytellers’ guild, one would try to vary one’s answers each time, to spice up the collective dialogue. What they want, of course, is not for the patient to respond in a manner that might conceivably be interesting to another human being (or to me) to hear or read, but in an extremely limited vocabulary and in the brevity permitted on their forms. They want our dialogue, in short, to resemble their dialogues with every other patient so closely that the only thing that differentiates us is the answer to those questions.

No personalities, please: just the facts, ma’am. Preferably delivered in so clipped and uncommunicative a manner that a Bertolt Brecht drama would seem positively chatty by contrast:

“So how are you feeling today?” Dr. Synonym asked brightly.

“Okay,” Patient No. 8276494/14A replied.

“Better?”

“No.”

“Worse?”

“No.”

“The same?”

Patient No. 8276494/14A sighed. Had s/he not already implicitly answered this question? “Yes.”

“How is that…” Dr. Synonym glanced down at the chart. “Knee doing? Better? Worse? The same?”

“About the same.”

“How would you rate your pain on a scale of one to ten, with one being none and ten the worst pain you can imagine?”

Patient No. 8276494/14A pictured being ripped to pieces by dingoes. “Five.”

On the manuscript page, this exchange would be pretty dull, even the first time around — in fact, unless the point were to show how dull and repetitious this round of questions was, most professional readers would probably advise the author to cut it. And we should all hope that this was the point of the submission from which our example was borrowed, because it appeared more than once throughout the course of a narrative, it would be stultifying.

Don’t believe me? Okay, I dare you: read it again.

The problem here isn’t merely that this is generic dialogue, a question-and-answer session so generic that neither question nor answer reveal much about either of the speakers. Or, indeed, about the situation both parties are ostensibly concerned with discussing.

So I ask you, manuscript revisers: is this dialogue, although unquestionably lifted from real life, worth preserving on the page for posterity? If not, how would you go about rendering more character- and/or plot-revealing?

The most obvious fix would be to have Dr. Synonym ask less generic questions — or at least ones that a good third of the patients currently scurrying around clinics in those fiendishly-designed little smocks that invariably leave half of one’s body exposed to the elements have answered within the last 20 minutes. Throwing even one curve ball into the mix would render the scene less predictable. Let’s try two.

“So how are you feeling today?” Dr. Synonym asked brightly. “Better?”

“No.”

“Worse?”

“No.”

Was he even listening? “Experiencing any difficulty climbing the giant rock candy mountain to snatch the magic beans from the resident ogre?”

“No.”

The doctor noted on the chart: sprained sense of humor. “Been eaten by crocodiles, lately?”

“No.”

“How is that knee doing?” She decided to make it multiple choice this time. “Better? Worse? The same?”

“About the same.”

“You’re tired.” She snapped her notebook closed with a strained smile. “Let’s see if we can do better tomorrow.”

Quite a different dynamic, isn’t it? Now, there’s conflict in the scene: the doctor is trying to elicit an individuated response, but the patient insists upon being minimally communicative. By playing with the expected, we end up with more tension on the page.

I’m sensing some of you lovers of slice-of-life literature just itching to jump into the fray. “But Anne,” reality-huggers protest, “I don’t believe a doctor would say that in real life. What I like in dialogue is seeing actual speech mirrored precisely on the page. Yes, it’s occasionally boring, but aren’t most readers prepared to put up with a little dullness if the scene rings true?”

Some readers, yes. Professional readers, seldom. And our old pal, Millicent the agency screener, when she’s in the throes of reading a stack of submissions between now and her long-delayed lunch? Very rarely indeed.

Besides, who is to say that a real-life doctor wouldn’t ask a couple of funny questions in this situation? You really should get out more, slice-of-lifers.

Let’s assume for the sake of argument, though, that it’s necessary to the plot or characterization to depict the doctor’s asking precisely the questions the reader will expect him to ask. (Yes, I changed Dr. Synonym’s sex this time around. Had I mentioned that I like variety on the page?) A savvy reviser could embrace the strategy that has not worked so well in my myriad medical appointments: beefing up the answers. Or even allowing a question or two to go unanswered.

Dr. Synonym leaned over her battened-down body, apparently addressing her chin. “So how are you feeling today?”

“Like some idiots have tied me to a hospital bed,” Jenna spat. “How else would a sane person feel?”

His expression did not alter. “Better?”

“Better than what?”

“Worse?”

She closed her eyes wearily. “Untie me, and maybe I’ll tell you.”

“The same, then?”

She could hear his fountain pen scratching. Clearly, that last question had been rhetorical.

“How is that knee doing? Better? Worse? The same?”

Jenna had not seen her legs in three weeks. “You tell me. I don’t have eyes on my toes.”

“How would you rate your pain on a scale of one to ten, with one being none and ten the worst pain you can imagine?”

“Eighty-seven. Fourteen hundred. Five thousand and twelve.”

“You’re tired.” He snapped his notebook closed with a strained smile. “Let’s see if we can do better tomorrow.”

Much more interesting than all of those nos, isn’t it? This is an old, old professional writer’s trick: avoid having your characters answer yes-or-no questions with either a yes or a no, since they add so little new information to the scene. Or an I don’t know, which typically adds even less.

Why avoid these three in particular? They often shut down a conversation, rather than moving it in an unexpected direction. Besides, yes,no, and I don’t know are usually the least interesting ways to answer a question;. We live in a full and fascinating universe, after all: neither fiction nor reality — complex fiction and reality, anyway — lend themselves to simple, dismissive answers.

Besides, if they come at the beginning of a fuller response to a yes/no question, the actual yes/no response is often not necessary. It’s implied in the rest of the statement.

“Is your leg feeling better today?”

“No, I feel as though it were about to fall off.”

Yes, a patient might actually say it this way, but on the page, this means essentially the same thing, doesn’t it?

“Is your leg feeling better today?”

“I feel as though it were about to fall off.”

It’s every bit as realistic, too. But it works better on the page: real-life dialogue tends to be rife with both phrase, idea, and even fact repetition.

Unfortunately, so does a hefty percentage of the dialogue in manuscript submissions. Rather than improving upon real-life speech by minimizing redundancy, sticking to the topic at hand, avoiding clichés, and varying phrasing — to name but a few of the many, many benefits of only selectively mirroring the way people actually talk — or using it to develop character, many aspiring writers don’t give much thought to how interesting the dialogue on their pages might be for someone else to read.

Seem perverse, in a population characterized by a clawing, desperate desire to have others read their writing? Strange to say, it seems to be true, judging by what turns up on the submission page. It’s as though dialogue were magically exempt from the thou shalt not bore thy reader rule applicable to the narrative portions of the manuscript.

Stop rolling your eyes. Even in manuscripts that have obviously been put together with care and revised meticulously, the dialogue is often repetitious in both phrasing and content. Add to that the simple truth that since it can take a heck of a long time to write a book, a writer does not always remember where — or even if — a character has made a particular point before, and even if he does, he may not be confident that the reader will remember it from 200 pages ago, and Millicent ends up grinding her teeth and muttering, “You TOLD us that already, Francine!” a great deal more than any of us might like.

Yes, do take a moment to admire that last epic sentence. I doubt we’ll see its like again.

What’s the solution for repetitive dialogue on the whole manuscript level? Well, it depends upon the type of repetition a writer tends to favor. If a character’s dialogue is redundant because she likes to spout a catchphrase — please tell me she doesn’t — the fix is downright easy: a quick confab with Word’s FIND function, a few creative substitutions, and voilà! Problem solved.

If the problem is more complex than that, I’m afraid I must be redundant and suggest reading though every line of dialogue in your manuscript IN HARD COPY and OUT LOUD. Why not silently and on your computer screen? The eye reads much faster on a backlit screen, rendering any sort of proofreading more difficult, and your ear may catch what your eyes do not.

Conceptual redundancy, however, is substantially more difficult for a self-editor to catch — it both time for close reading of the entire manuscript and a retentive memory. Even if that reviser happens to have been blessed with both, after slaving over a manuscript for months or years on end, repeated or largely similar snippets of dialogue, explanations, and even relatively important plot points can seem…well, if not precisely fresh, at least not memorable from earlier in the latest draft.

Unfortunately, this quite predictable byproduct of revision burnout does not always fill professional readers with sympathy for the writer’s dilemma. Quite the opposite, in fact.

“Great jumping Jehoshaphat!” Millicent groans over many a submission. “Didn’t this writer bother to read this manuscript before sending it to us? Couldn’t she see that she told us this already!”

Would you believe me if I told you she is not only likely to formulate this complaint if she finds the same line of dialogue or repeated explanations three lines apart or three chapters? Or that it’s not unheard-of for a professional reader to notice reused phrasing or concepts if there are only two iterations hundreds of pages apart?

How is this possible, you ask? It’s an editor’s job to be that preternaturally observant of manuscript details; we’re trained to respond to it as if it were the sound of fingernails scraping across a blackboard. Because editors are so sensitive to repetition, agents learn to keep an eye out for it, too. So when the agent of your dreams was teaching her Millicents what red flags were deal-breakers, guess what was high on the list?

Every time we discuss this issue, I am transported back to the dim reaches of my past. I was six years old, standing in line for the Peter Pan ride at Disneyland, back in the days when the quality and popularity of the ride was easily discernable by the level of ticket required to board it. E was the best; I believe this particular ride was somewhere in the B- range.

My tepid-to-begin-with enthusiasm had begun to fade practically as soon as I stepped into a queue of inexplicable length to cruise around an ersatz London with Peter, Wendy, and the gang. All brown eyes and braids, I had already spent several hours holding my mother’s hand while my father took my older brother on D and E ticket rides. And I was not particularly enamored of PETER PAN as a story: even at that tender age, the business of telling children that if they only wish hard enough, their dead loved ones will come back from the dead struck me as rather mean.

Honestly, what does that story about the motivations of all of those kids whose late relatives persistently remain dead?

Alas, the Peter Pan ride was one of the few the guidebook deemed appropriate to literary critics of my tender age. But the longer we stood in line, the more difficult I found it to muster even the appearance of childish joie de vivre.

Why was I feeling so oppressed, the six-year-old in all of us cries? Because as each ship-shaped car took a new crew of tourists whirring into the bowels of the ride, Peter’s voice cried out, “Come on, everybody, raring to go-o-o-o!”

After about five minutes of listening to that annoying howl while inching toward the front of line, I started counting the repetitions. By the time it was our turn to step into a flying ship, Peter had barked that inane phrase at me 103 times.

It’s all I remember about the ride. Newly alive to the necessity of editing dialogue, I told the smiling park employee who liberated us from our ship at the end of the ride that it would have been far, far better without all of that phrase repetition at the beginning.

He patted me on the back as he hurried me toward the exit. “I know,” he whispered. “By the end of the day, I want to strangle someone.”

And that, my friends, is how little girls with braids grow up to be editors. While most of the population comes to accept the conceptual and phrase repetition that is constantly flung at all of us, all the time, in both everyday conversations and on TV, we remain painfully alive to it.

We think it should go-o-o-o.

Wait — some of you tuned out that anecdote, didn’t you? You remembered it from last year’s discussion of conceptual repetition, I’m guessing. Well, I have just one thing to say to those of you who skimmed past it: that’s exactly how Millicent feels when she sees a snippet of conversation from Chapter 3 turn up again in Chapter 17.

Actually, your reaction was almost certainly more charitable than hers, and with good reason. Most of us become inured through years of, well, repetition to the film habit of repeating facts and lines that the screenwriter wants to make sure the viewer remembers, information integral to either the plot (“I know we’ve been over this before, Trevor, but I must reiterate: cut the RED cord hanging from that bomb, not the yellow one!”), character development (“Just because you’re a left-handed cellist and the provost of this college, Yvette, doesn’t mean you’re always right!”), or both (“You may be the best antiques appraiser in the British Isles, Mr. Lovejoy, but you are a cad!”)

My all-time favorite example of this phenomenon — again, this may seem a tad familiar to some of you, but I’m trying to sensitize you — came in the cult TV series Strangers With Candy, a parody of those 1970s Afterschool Specials that let young folks like me into esoteric truths like Peer Pressure Exists, Drugs are Bad, and You Should Have Self-Esteem.

In case, you know, the average kid might not have picked up on any of that from the 1,247 times he had heard adults tell him these things before. Stand up straight.

The writers and producers of the Afterschool Specials seemed to be operating upon the assumption that either young viewers’ memories or our general level of intelligence was inherently suspect. It was rare that these shows ever made any major point only once — or that the fate of the Good Kid Who Made One Mistake was not obvious from roughly minute five of the program.

True to this storytelling tradition, Strangers With Candy’s heroine, Jerri Blank, often telegraphed upcoming plot twists by saying things like, “I would just like to reiterate, Shelly, that I would just die if anything happened to you.” Moments later, of course, Shelly is toast.

Oh, you may smile, but this species of heavy-handed foreshadowing is substantially less funny to encounter in a manuscript, particularly to someone attuned to catching repetition. You would be astonished by how often characters say things like, “But Ernest, have you forgotten that I learned how to tie sailors’ knots when I was kidnapped by pirates three years ago?”

Because that’s the kind of thing that’s likely to slip one’s mind. I’ll bet hardly a week goes by without your uttering a sentence like that.

Or so one might conclude from the frequency with which such statements turn up in submissions — even when the first 50 pages of the manuscript dealt with that very pirate kidnapping. And every time such a reference is repeated, another little girl with braids vows to grow up to devote her life to excising all of that ambient redundancy.

Hey, someone’s got to make the library safe for readers with retentive memories. Keep up the good work!

Pet peeves on parade, part XVI: but I don’t want to give away the whole candy store!

Have you noticed a theme running through the last few posts, campers? Yes, we’ve ostensibly been talking about dialogue, but in that fine tradition of narrative where there’s more going on than what’s going on, as Millicent the agency screener might put it, I’ve been sneaking in some other lessons as well. Many of them, as some of you may have noticed, have related to reducing the passivity of one’s protagonist(s).

On the off chance that I’ve been too subtle: a protagonist who merely observes the plot, rather than being a force — or, ideally, the primary force — driving it forward can bring an otherwise exciting story to a grinding halt while s/he ruminates. (Confidential to Elizabeth: you’re welcome.) Similarly, a protagonist who contributes minimally to a scene, remains silent, or does not respond to stimuli that would cause the calmest herd of elephants to stampede for the nearest exit can sap tension.

So it’s not entirely surprising, is it, that a protagonist who is purely reactive on page 1 might cause Millicent to worry about how exciting s/he will be to follow for the rest of the book? Let’s face it, even if the opening scene is chock full of unexpected conflict, seeing it through the eyes and psyche of a protagonist seemingly determined not to get involved, or even one who just doesn’t ask particularly incisive questions, may make it seem, well, less exciting.

Not to mention making the protagonist come across as less intelligent than the author probably intended. Last time, we saw how a character’s repeating what has just been said to him can markedly lowers his apparent I.Q. by a few dozen points. When a protagonist stops the story in its tracks to draw conclusions that would cause a reasonably intelligent eight-year-old to exclaim, “Well, duh!”, it can have a similar effect. Imagine, for instance, having to follow Pauline through a 380-page novel.

Pauline struggled against her bonds, but it was no use. Her tormentor must have been an Eagle Scout with a specialty in knotting, to tie her to the railroad track this firmly. “You don’t mean to…hurt me, do you?”

“Of course not.” Edgar sneered, twirling his mustache. “It’s the oncoming train that’s going to hurt you. Quite a lot, I should think.”

Her eyes widened to the circumference of her Aunt Bettina’s favorite teacups, the ones with the wee lilacs painted upon them. “Are you trying to kill me? Why? What have I ever done to you?”

“Oh, I don’t know.” Depressed, he flopped onto a nearby pile of burlap sacks. “I just have this thing for tying pretty women to railroad tracks. You happened to be here.” He buried his head in his elegant hands. “God, I really need to establish some standards.”

Was he weakening? Over the roar of the engine, it was so hard to be sure. “Edgar? If you don’t do something, I shall be squashed flatter than the proverbial pancake.”

He did not even lift his head. “I doubt it. With my luck, a handsome stranger will suddenly appear to rescue you.”

A shadow crossed her face. “Why, hello there, little lady,” a stranger blessed with undeniable good looks said. “You look like you could use some help.”

She had to shout to be heard over the wheels. “Yes, I could. You see, Edgar’s tied me to the train tracks, and there’s a train coming.”

Miffed at me for ending the scene before we found out it Pauline survived? Come on, admit it — you were tempted to shout, “Well, duh!” in response to some of Pauline’s statements, were you not? Who could blame you, when apparently her only role in the scene is to point out the obvious?

Millicent would have stopped reading, too, but she would have diagnosed the problem here differently. “Why doesn’t this writer trust my intelligence?” she would mutter, reaching for the nearest form-letter rejection. “Why does s/he assume that I’m too stupid to be able to follow this series of events — and a cliché-ridden series of events at that — without continual explanations of what’s going on?”

That’s a question for the ages, Millicent. In this case, the writer may have considered Pauline’s affection for the obvious funny. Or those frequent unnecessary statements may be Hollywood narration: instead of the narrative’s showing what’s happening, the dialogue’s carries the burden, even though the situation must be clear to the two characters to whom Pauline is speaking.

Or — and this is a possibility we have not yet considered in this series — this scene is lifted from a book category where the imperiled protagonist is expected to be purely reactive.

Didn’t see that one coming, did you? All too often, those of us who teach writing to writers speak as though good writing were good writing, independent of genre, but that’s not always the case. Every book category has its own conventions; what would be considered normal in one may seem downright poky in another.

Case in point: our Pauline. Her tendency to lie there and wait for someone to untie her would be a drawback in a mainstream fiction or high-end women’s fiction manuscript, but for a rather wide segment of the WIP (Women in Peril) romance market, a certain amount of passivity is a positive boon. Heck, if this example were WIP, Pauline might not only be tied to a train track — she might be menaced by a lion wielding a Tommy gun.

As opposed to, say, a bulletproof lady too quick to be lashed down with large steaks in her capacious pockets in case of lion attack. The latter would make a great heroine of an Action/Adventure — and the last thing Millicent would expect her to be is passive.

Unless, of course, Pauline is the love interest in a thriller. Starting to see how this works?

Even if she were a passive protagonist in a genre more accepting of passivity (usually in females; in the U.S., genuinely passive male protagonists tend to be limited to YA or literary fiction), it would dangerous to depict the old girl being purely reactive on page 1: the Millicent who reads WIP at the agency of your dreams may also be screening fantasy, science fiction, mystery, or any of the other genres that tend to feature active female protagonists. As a general rule, then, it’s better strategy to show your protagonist being active and smart on page 1.

Which is to say: place your protagonist in an exciting situation, not just next to it.

Also, you might want to make it clear from the first line of page 1 who your protagonist is. Not who in the philosophical sense, or even in the demographic sense, but which character the reader is supposed to be following.

Stop laughing; this is a serious issue for our Millie. Remember, in order to recommend a manuscript to her boss, she has to be able to tell the agent of your dreams what the book is about — and about whom. Being a literary optimist, she begins each new submission with the expectation that she’s going to be telling her boss about it.

Unless the text signals her otherwise, she’s going to assume that the first name mentioned is the protagonist’s. Imagine her dismay, then, when the book turns out a page, or two, or fifty-seven later to be about someone else entirely.

I can still hear you giggling, but seriously, it’s often quite hard to tell. Don’t believe me? Okay, here’s a fairly typical opening page in a close third-person Women’s Fiction narrative. Based on the first few lines, who is the protagonist?

Were you surprised by the sudden switch to Emma? Millicent would have been. Perhaps not enough to stop reading, but enough to wonder why the first half-page sent her assumptions careening in the wrong direction.

That little bait-and-switch would be even more likely to annoy her on this page than others, because Emma seems like the less interesting protagonist option here. Not only is she an observer of the action — Casey’s the one experiencing the tension, in addition to having apparently been married to someone with allegedly rather nasty habits — but she comes across as, well, a bit slow on the uptake.

How so, you ask? Do you know very many super-geniuses who have to count on their fingers to tell time?

Now, as a professional reader, it’s fairly obvious to me that the writer’s intention here was not to make Emma seem unintelligent. My guess would be that the finger-counting episode is merely an excuse to mention how the rings threw the dull light back at the ceiling — not a bad image for a first page. But that wasn’t what jumped out at you first from this page, was it?

Or it wouldn’t have, if you were Millicent. There are three — count ‘em on your fingers: three — of her other pet peeves just clamoring for her attention. Allow me to stick a Sharpie in her hand and let her have at it:

page 1 edit 4

Thanks, Millie; why don’t you go score yourself a latte and try to calm down a little? I can take it from here.

Now that we’re alone again, be honest: in your initial scan of the page, had you noticed all of the issues that so annoyed Millicent? Any of them?

Probably not, if you were reading purely for story and writing style, instead of the myriad little green and red flags that are constantly waving at her from the submission page. Let’s take her concerns one at a time, so we may understand why each bugged her — and consider whether they would have bugged her in submissions in other book categories.

Opening with an unidentified speaker: Millicent remains perpetually mystified by how popular such openings are. Depending upon the categories her boss represents, she might see anywhere from a handful to dozens of submissions with dialogue as their first lines on any given day. A good third of those will probably not identify the speaker right off the bat.

Why would the vast majority of Millicents frown upon that choice, other than the sheer fact that they see it so very often? A very practical reason: before they can possibly make the case to their respective boss agents that this manuscript is about an interesting protagonist faced with an interesting conflict, they will have to (a) identify the protagonist, (b) identify the primary conflict s/he faces, and (c) determine whether (a) and (b) are interesting enough to captivate a reader for three or four hundred pages.

Given that mission, it’s bound to miff them if they can’t tell if the first line of the book is spoken by the protagonist — or, indeed, anyone else. In this case, the reader isn’t let in on the secret of the speaker’s identity for another 6 lines. That’s an eternity, in screeners’ terms — especially when, as here, the first character named turns out not to be the speaker. And even on line 7, the reader is left to assume that Emma was the initial speaker, even though logically, any one of the everyone mentioned in line 7 could have said it.

So let me give voice to the question that Millicent would be asking herself by the middle of the third line: since presumably both of the characters introduced here knew who spoke that first line, what precisely did the narrative gain by not identifying the speaker for the reader’s benefit on line 1?

99.9% of the time, the honest answer will be, “Not much.” So why force Millicent to play a guessing game we already know she dislikes, if it’s not necessary to the scene?

Go ahead and tell her who is speaking, what’s going on, who the players are, and what that unnamed thing that jumps out of the closet and terrifies the protagonist looks like. If you want to create suspense, withholding information from the reader is not Millicent’s favorite means of generating it.

That’s not to say, however, that your garden-variety Millicent has a fetish for identifying every speaker every time. As we have discussed, she regards the old-fashioned practice of including some version of he said with every speech as both old-fashioned and unnecessary. Which leads me to…

Including unnecessary tag lines: chant it with me now, campers: unless there is some genuine doubt about who is saying what when (as in the first line of text here), most tag lines (he said, she asked, they averred) aren’t actually necessary for clarity. Quotation marks around sentences are pretty darned effective at alerting readers to the fact that those sentences were spoken aloud. And frankly, unless tag lines carry an adverb or indicates tone, they usually don’t add much to a scene other than clarity about who is saying what when.

Most editors will axe unnecessary tag lines on sight — although again, the pervasiveness of tag lines in published books does vary from category to category. If you are not sure about the norms in yours, hie yourself hence to the nearest well-stocked bookstore and start reading the first few pages of books similar to yours. If abundant tag lines are expected, you should be able to tell pretty quickly.

Chances are that you won’t find many — nor would you in second or third novel manuscripts by published authors. Since most adult fiction minimizes their use, novelists who have worked with an editor on a past book project will usually omit them in subsequent manuscripts. So common is this self-editing trick amongst the previously published that to a well-trained Millicent or experienced contest judge, limiting tag line use is usually taken as a sign of professionalism.

Which means, in practice, that the opposite is true as well — a manuscript peppered with unnecessary tag lines tends to strike the pros as under-edited. Paragraph 2 of our example illustrates why beautifully: at the end of a five-line paragraph largely concerned with how Casey is feeling, wouldn’t it have been pretty astonishing if the speaker in the last line had been anybody but Casey?

The same principle applies to paragraph 4. Since the paragraph opens with Casey swallowing, it’s obvious that she is both the speaker and the thinker later in the paragraph — and the one that follows. (Although since a rather hefty percentage of Millicents frown upon the too-frequent use of single-line non-dialogue paragraphs — as I mentioned earlier in this series, it takes at least two sentences to form a narrative paragraph in English, technically — I would advise reserving them for instances when the single sentence is startling enough to warrant breaking the rule for dramatic impact. In this instance, I don’t think the thought line is astonishing enough to rise to that standard.)

Starting to see how Millicent considers a broad array of little things in coming up with her very quick assessment of page 1 and the submission? Although she may not spend very much time on a submission before she rejects it, what she does read, she reads very closely. Remember, agents, editors, and their screeners tend not to read like other people: instead of reading a page or even a paragraph before making up their minds, they consider each sentence individually; if they like it, they move on to the next.

All of this is imperative to keep in mind when revising your opening pages. Page 1 not only needs to hook Millicent’s interest and be free of technical errors — every line, every sentence needs to encourage her to keep reading.

In fact, it’s not a bad idea to think of page 1’s primary purpose (at the submission stage, anyway) as convincing a professional reader to turn the first page and read on. In pursuit of that laudable goal, let’s consider Millicent’s scrawl at the bottom of the page.

Having enough happen on page 1 that a reader can tell what the book is about: this is such a common page 1 (and Chapter 1) faux pas for both novel and memoir manuscripts that some professional readers believe it to be synonymous with a first-time submission. In my experience, that’s not always true. A lot of writers like to take their time warming up to their stories.

So much so, in fact, that it’s not all that rare to discover a perfectly marvelous first line for the book in the middle of page 4. Or 54.

How does this happen? As we’ve discussed earlier in this series, opening pages often get bogged down in backstory or character development, rather than jumping right into some relevant conflict. US-based agents and editors tend to get a trifle impatient with stories that are slow to start. (UK and Canadian agents and editors seem quite a bit friendlier to the gradual lead-in.) Their preference for a page 1 that hooks the reader into conflict right off the bat has clashed, as one might have predicted, with the rise of the Jungian Heroic Journey as a narrative structure.

You know what I’m talking about, right? Since the release of the first Star Wars movie, it’s been one of the standard screenplay structures: the story starts in the everyday world; the protagonist is issued a challenge that calls him into an unusual conflict that tests his character and forces him to confront his deepest fears; he meets allies and enemies along the way; he must grow and change in order to attain his goal — and in doing so, he changes the world. At least the small part of it to which he returns at the end of the story.

It’s a lovely structure for a storyline, actually, flexible enough to fit an incredibly broad swathe of tales. But can anybody spot a slight drawback for applying this structure to a novel or memoir?

Hint: you might want to take another peek at today’s example before answering that question.

Very frequently, this structure encourages writers to present the ordinary world at the beginning of the story as, well, ordinary — and the protagonist as similarly ho-hum The extraordinary circumstances to come, they figure, will seem more extraordinary by contrast. Over the course of an entire novel, that’s pretty sound reasoning (although one of the great tests of a writer is to write about the mundane in a fascinating way), but it can inadvertently create an opening scene that is less of a grabber than it could be.

Or, as I suspect is happening in this case, a page 1 that might not be sufficiently reflective of the pacing or excitement level of the rest of the book. And that’s a real shame, since I happen to know that something happens on page 2 that would make Millicent’s eyebrows shoot skyward so hard that they would knock her bangs out of place.

Those of you who like slow-revealing plots have had your hands in the air for quite a while now, haven’t you? “But Anne,” you protest, and not without justification, “I want to lull my readers into a false sense of security. That way, when the first thrilling plot twist occurs, it comes out of a clear blue sky.”

I can understand the impulse, lovers of things that go bump on page 3, but since submissions and contest entries are evaluated one line at a time, holding back on page 1 might not make the best strategic sense at the submission stage. Trust me, she’ll appreciate that bump far more if you can work it into one of your first few paragraphs.

Here’s an idea: why not start the book with it? Nothing tells a reader — professional or otherwise — that a story is going to be exciting than its being exciting right from the word go.

Bear in mind, though, that what constitutes excitement varies by book category. Yes, Millicent is always looking for an interesting protagonist facing an interesting conflict, but what that conflict entails and how actively she would expect the protagonist to react to it varies wildly.

But whether readers in your chosen category will want to see your protagonist weeping pitifully on a train track, fighting off lions bare-handed, or grinding her teeth when her boss dumps an hour’s worth of work on her desk at 4:59 p.m., you might want to invest some revision time in making sure your first page makes that conflict look darned fascinating — and that your protagonist seems like she’d be fun to watch work through it. Whatever your conflicts might be, keep up the good work!

Pet peeves on parade, part XV: speak to me, protagonist. Or blink twice to let me know that you’re alive.

After yesterday’s unusually lengthy post, even by my standards (which is saying something), I thought I’d limit myself this evening to a light, sparkling addendum to last time’s intensive session of nit-picking. It will be a struggle, I fear; well-constructed dialogue is a subject upon which I, like Millicent the agency screener, hold quite passionate views.

Why work ourselves into a lather over dialogue, you ask, instead of, say, punctuation placement? Well, while I, for one, have been known to wax eloquent about our friend, the humble comma, its placement is largely a technical issue: it’s rare that a great new writer will stake her claim to fame upon her bold and innovative use of commas.

Seriously, would you want your name to be passed down to posterity as King of the Commas? Wowing the literary world with an unusually good ear for dialogue, on the other hand, is a goal to which many a fledgling writer of fiction and/or memoir aspires. It’s certainly a worthwhile one: writing dialogue well requires not merely a strong sense of what people actually say and the rhythms in which they say it, but also the creativity to pepper the dialogue with enough originality that it won’t seem ho-hum.

Yet for some reason that perpetually escapes me, even writers who pride themselves on their fresh, original notions and execution frequently choose to bore poor Millicent to extinction with uninteresting dialogue. “But people really talk like that,” they hedge. “It’s not my fault if most people are not scintillating conversationalists.”

Well, that’s not entirely true, realism-huggers. While no one can hold you accountable if the couple at the next table elects to immerse themselves in dull chit-chat (“How about this rain?” “We sure do need it.” “I’ll say.”), it’s not fair to expect readers to suffer through dialogue that has no legitimate claim to attention other than its fidelity to real-life talk.

Or, to put it a bit more bluntly: not everybody in the world is under an obligation to produce entertaining sentences. Writers are.

Messes with your head a little to think of dialogue in those terms, doesn’t it? If so, you’re not alone: most dialogue in submissions is clearly aimed at realism, rather than entertainment. Only a relatively small percentage of submissions demonstrate a commitment to developing character through speech by having characters say interesting and unexpected things in their own distinct voices.

Which is to say: you’d be amazed — at least, I hope you would — by how frequently otherwise creative narratives are bogged down by mundane, unrevealing, or cliché-ridden dialogue.

How common is it? Let me put it this way: if an alien from the planet Targ were to drop from the sky into Millicent’s cubicle tomorrow, determined to learn about how human beings communicate by leafing through a few hundred submissions, it would stroll out of her office sounding just like that couple at the next table. If you ran into it at a cocktail party, you’d be eavesdropping on nearby conversations within a couple of minutes.

What a pity — it might be fascinating to hear about living conditions on Targ these days. But even someone with something interesting to say can seem boring if he doesn’t express himself in interesting terms.

Or if, as we saw last time, if he chooses not to vouchsafe an opinion of his own. All too often, supporting characters — or even more common, passive protagonists whose idea of solving a mystery is to ask one or two questions, then sit back and wait while someone who has defined her very existence by the secret she has kept just blurts out the long-hidden truth — are only nominal participants in dialogue scenes. By not engaging the primary speaker with an alternate point of view, the character becomes simply a monologue-encourager.

Trevor glanced around the musty basement, wondering how anyone could possibly survive for an hour there, much less thirty-eight years. “So you have been in hiding all of this time?”

“You call it hiding.” Veronica’s teeth wobbled visibly with every word. “I call it saving my skin.”

“Really?”

“Oh, yes. When I first sought out the basement, it was merely as temporary shelter from the horrors of the street. I had no idea that I would be spending the better part of my life here.”

“Wow.”

She flipped her lank gray bangs out of her eyes, and just for a second, she resembled the seventeen-year-old she had been when she last stood in natural light. “Well might you say wow. Do you know how long it took me to figure out how to transform the disused washer/dryer unit into a convection oven? Eight long years. Before that, I had to eat the rats that sustain me raw.”

“Eww.”

“Oh, you get used to it. It’s the right seasoning that’s the trick. The same holds true for cockroach goulash, incidentally.”

“Weren’t you going to tell me about the horrible incident that drove you underground?”

She clutched her mouse fur bed jacket around her fiercely. “I swore I would never tell. Never!”

Trevor’s heart sunk within him. He had come so far in the last forty-eight hours; he couldn’t turn back without one last push. “Pretty please? With sugar on top?”

Veronica looked at him, and her last reservation melted. “It was a dark and stormy night in 1973. I was just a girl then, getting ready for the prom. My dress was hanging over my David Cassidy poster, waiting for me to pick out which of my six sets of platform shoes I would wear. Suddenly, I had the eerie feeling I was being watched.”

“Uh-huh,” he prompted breathlessly.

Trevor’s not adding very much to this interaction, is he? By choosing to be a mostly passive listener, rather than a participant in the conversation, he’s done more than abdicate his role as the reader’s guide through this part of the plot; he’s basically pulled up a chair and plopped himself down right next to the reader, drinking in Veronica’s story as though he were just another audience member.

But at least he is responding in a manner that reveals his feelings about what she is saying. All too often, passive protagonists in interview don’t even do that.

Trevor glanced around the musty basement. “So you have been hiding here all this time?”

“You call it hiding.” Veronica’s teeth wobbled visibly with every word. “I call it saving my skin.”

“Saving your skin?

“Oh, yes. When I first sought out the basement, it was merely as temporary shelter from the horrors of the street. I had no idea that I would be spending the better part of my life here.”

“The better part of your life? Why, how long has it been?”

“That depends. What year is it?” She laughed loudly before he could answer. “Just kidding. It’s been thirty-eight years.”

“Thirty-eight years!”

“The trick was keeping myself busy. Do you know how long it took me to figure out how to transform the disused washer/dryer unit into a convection oven? Eight long years. Before that, I had to eat the rats that sustain me raw.”

“Rats? Raw?”

“Oh, you get used to it. It’s the right seasoning that’s the trick.”

Pardon my asking, but couldn’t Trevor’s part in this scene be very adequately played by a parrot? Or a very high, cavernous ceiling that could echo Veronica’s words back to her?

Certainly, he’s providing neither conflict nor any additional information to the scene. Heck, he’s barely contributing any new words.

So what is he doing in the scene at all? Perhaps he is seeking clues to an ongoing mystery he is trying to solve, and is merely going about it poorly. Or maybe he is actually an immensely clever sleuth, trying to lull poor Veronica into a false sense of security by giving incisive questions about what he wants to know a wide berth. Or he could have just suffered a brain injury that deprived him of the ability to understand what someone is saying until he’s heard every part of it twice.

Or maybe he’s just rather stupid. At least, he appears so on the page.

That made some of you real dialogue-echoers sit bolt upright in your desk chairs, didn’t it? “But Anne,” you point out with some vim, “I know that you’ve just been saying that the fact that people actually talk that way shouldn’t be the only justification for a line of text, but people actually do talk this way. Repeating what’s just been said is a standard means of asking for clarification. Why, I can barely watch five minutes of any TV drama without hearing a character repeat a phrase that’s just been said to her.”

I believe it — and that alone might be a good reason not to embrace this conversational tactic in your dialogue. Since the rise of reality television (does anyone but me remember that producers originally embraced the format because the writers’ guild was on strike?), we’ve all become accustomed to highly repetitious speech pouring out of characters’ mouths, often with a blithe disregard for the rules of grammar. Heck, it’s become quite normal for even speakers who should know better to misuse words.

And I’m not talking about tiny gaffes, like saying further when the speaker really meant farther, either. (In response to that silent plea for clarification: the first refers to concepts, the second to distance.) I’m talking about the increasingly common practice of substituting the intended word or phrase with one that sounds similar to it — a doggy-dog world instead of a dog-eat-dog world, for instance, or mano y mano instead of mano a mano — as if getting it right simply didn’t matter. Or simply using a term so loosely that its original meaning dissipates, as when someone dubs an outcome ironic when it’s merely symbolically apt (in itself ironic, since irony is when the intended and literal meaning are at odds). Or says unironically, “We will be landing momentarily,” when he means “We will be landing in a few minutes,” not “We will be landing for a few moments, then taking off again.”

Yes, yes, I know: if I were correcting these commonly-misused phrases in the middle of an actual conversation, I would come across as a joy-killing curmudgeon. (Blame my upbringing: children in the Mini household were expected to be both seen and heard, but never to end a spoken sentence with a preposition.) And to tell you the truth, I wouldn’t have a problem with a writer’s reproducing these gaffes on the manuscript page — provided that their use was limited to dialogue and not every character made similar mistakes.

Which character would I select to talk this way? The one the reader is supposed to regard as a little slow on the uptake, of course.

Oh, you laugh, but back when writers composed and refined every word that fell out of characters’ mouths on TV and in movies, placing improper grammar and malapropisms into dim-witted characters’ mouths was a standard comic device. It was also a time-honored means of establishing a character’s level of education, social class, or susceptibility to prejudice: much of the recent furor over whether it was legitimate to clean up the language in HUCKLEBERRY FINN so that it could be assigned in more high school classrooms turned on Mark Twain’s devastatingly frequent use of a certain pejorative term to illustrate his protagonist’s change of perspective on issues of race throughout the book.

Even now, one of the quickest means of making a character come across as less intelligent on the page is to have him misuse words or repeat what’s just been said to him. The latter can be particularly effective, enabling the dialogue to convey that he doesn’t understand what’s going on without having to resort to the blunt expedient of having another character call him stupid.

Don’t believe that a few misused or repeated words can have that great an impact on character development? Well, they might not to a reader who habitually makes similar mistakes, but to a literate reader — and Millicent, her boss the agent, and the editor to whom the agent pitches pride themselves on their literacy — conversational faux pas will leap off the page. They’re a way to show, not tell, that a character has trouble expressing himself.

I sense that some of you are still not convinced. Okay, here’s an anecdote about how the repetition of a single misused word made a university professor seem substantially less intelligent.

When I was in graduate school, I took several small seminars with Professor Baker, an elegant, well-spoken woman who delighted in quoting Ancient Greek playwrights in even the most informal conversations. No mere cold intellectual, she was deeply interested in her students’ personal development. “Don’t cut off your options,” she would tell us frequently. “Go out and explore. I want to see you living a fulsome life!”

The first time she said this, I was convinced that I must have misheard. Fulsome, after all, means grossly overabundant or insincere; a fulsome complimenter would heap on praise after exaggerated praise until it was impossible to believe anything he said at all. It can also mean disgusting or offensive to the sensibilities. Somehow, I doubted that my professor was wishing me a life that resembled rotting meat.

Yet at the end of practically every seminar session, she would repeat her admonition: she seemed pretty darned insistent that my fellow students and I should be actively pursuing fulsome lives.

What she meant, of course, was that we should lead full lives; she must have just thought the -some bit added emphasis. But when I suggested that she truncate the word, she snapped at me like an irate turtle.

“Are you questioning my erudition?” she demanded. “I would hardly use a word if I were unaware of its definition.”

In that moment, to paraphrase Emily Dickinson, she dropped so low in my regard/I heard her hit the ground. Not because she had consistently been using her favorite word incorrectly, but because she was too inflexible even to consider the possibility that she might have been wrong. And because had she been right, all she would have had to do was stretch that elegant, beringed hand across her well-appointed desk, open a dictionary, and show me the definition.

If she had wielded her pet piece of advice with more discretion, she would probably have gotten away with it, right? I might have chuckled over my notebook, but her momentary gaffe would soon have been obliterated in my memory by other, more lucid statements. But by repeating it so often, essentially turning it into her catchphrase, she made sure that single mistake would become entrenched in my mind as the key to her entire character.

Would this tactic work on the page? You bet, although I would advise giving a fictional character a wider array of conversational missteps. Repeating the same one over and over might well backfire: since professional readers are trained to spot textual repetition — how else would they be able to point out to you that you used the same metaphor twice in 157 pages? — the second iteration might strike Millicent as unintentional. (In answer to what half of you just shouted mentally: oh, you’d be surprised how often aspiring writers will plagiarize themselves within a manuscript. They don’t mean to be repetitious; they simply forget that they have used an image or even a sentence earlier in the book.)

Speaking of low-level carelessness, there’s another reason it might behoove Trevor’s creator to ramp up his contribution to the scene. You really don’t want Millicent to start wondering if the only reason he’s in the scene is to provide the narrative an excuse to show the reader what it’s like down there.

You’re chuckling again, aren’t you? Think about it: in a close third-person (or first-person) narrative, Trevor would have to be there to justify the reader’s venturing into that basement. Including a scene in which he did not appear would necessarily entail jumping into someone else’s perspective — or slipping out of the dominant voice of the book into an omniscient point of view.

“Whoa!” Millicent cries. “This manuscript is breaking its own rules!”

You can hardly blame her for being hyper-sensitive on this point: since tight third person and first person are the two most popular point of view choices, she sees an awful lot of protagonists wander into an awful lot of situations where they have no business being, simply because writers want to include specific scenes in their books. She’s also privy to a great many instances of a narrative’s abandoning the strictures the writer had been following for the rest of the story — sticking to a single perspective, allowing the narrative to be colored by the chosen character’s prejudices, and so forth — because the writer apparently could not figure out a way to show a desired activity from the dominant perspective.

In answer to that collective gasp: yes, she will notice, whether the point of view slips for an entire scene or a single paragraph. She’s going to be on the lookout for such voice inconsistency problems, in fact. It’s all a part of her fulsome rich and meaningful life.

Make sure your protagonists pursue existences almost as full as hers: don’t allow them to become bystanders in their own lives, even for a page. Show them engaging in the world around them; let their presences add substantially to any scene they grace. Those contributions do not need to be limited to the dialogue, either: in a close third-person or first-person narrative, even a protagonist forced to remain stock-still and silent can interrogate her boss in her thoughts, signal another prisoner with a poke of her toe, struggle to breathe calmly while that cursed monologue-happy teacher bellows in front of the chalkboard…

The possibilities are, as they say, limitless. In a universe both frequently fulsome and perpetually full, why restrict the scope of your creativity by not taking complete advantage of your protagonist’s ability to react?

Worth pondering, anyway. Keep up the good work!

Pet peeves on parade, part XIV: am I talking to myself, or is this guy not holding up his end of the conversation?

“A man of genius can hardly be sociable, for what dialogues could indeed be so intelligent and entertaining as his own monologues?” – Schopenhauer

Last time, I went on a rampage about one type of dialogue that tends to get professional readers’ proverbial goats: the astonishingly common practice of constructing tag lines centered upon verbs that do not imply speech. This one’s a goat-napper for good reason: since the whole point of the he said part of a dialogue paragraph is presumably to alert the reader to who is speaking those words encased within quotation marks, it’s both illogical and rather annoying when the text chooses to shoehorn a non-speaking activity into the sentence. As in:

“My uncle may be a murderer,” Hamlet carelessly scooped a nearby scull off the ground and contemplated it, “but you can’t fault his taste in wine.”

Since neither scooped nor contemplated are speaking verbs, they cannot reasonably be expected to form the basis of a tag line, right? What the writer actually meant was this:

“My uncle may be a murderer,” Hamlet said, carelessly scooping a nearby scull off the ground and contemplating it, “but you can’t fault his taste in wine.”

Now, that first comma makes sense: Hamlet said is the tag line completing the dialogue sentence. If a reviser were looking to minimize the number of tag lines in a scene — advisable in most types of adult fiction or memoir, to avoid a Jane, see Dick chase Spot feel to the text — that comma could be replaced by a period, and the original pseudo tag line transformed into an ordinary narrative sentence.

“My uncle may be a murderer.” Hamlet carelessly scooped a nearby scull off the ground and contemplated it. “But you can’t fault his taste in wine.”

After raising this issue and suggesting a couple of viable solutions, I was all set to go merrily on my way — then, as so often happens, some thoughtful readers took issue with one of the fixes. The quite interesting debate in the comments centered around the question of whether the actual speech in a sentence like

“My uncle may be a murderer,” Hamlet said, carelessly scooping a nearby scull off the ground and contemplating it, “but you can’t fault his taste in wine.”

meant something different than

“My uncle may be a murderer.” Hamlet carelessly scooped a nearby scull off the ground and contemplated it. “But you can’t fault his taste in wine.”

The literal meaning is the same, of course; the question here is a matter of rhythm. In the first version, the speeches before and after the tag line are presented as a single sentence: “My uncle may be a murderer, but you can’t fault his taste in wine.” The comma implies only a minimal pause in between the two halves. In the second version, the period indicates a longer pause: “My uncle may be a murderer. But you can’t fault his taste in wine.”

Unquestionably, there is a difference, but would it really matter to most readers? Probably not, unless Hamlet were in the last stages of emphysema, rendering the utterance of a sentence of the length of the first too great a strain on his lung capacity to be plausible. Even Millicent, our favorite long-suffering screener of submissions to agencies, would regard both versions as acceptable, unless the text had already established a speech pattern for Hamlet that rendered either length of pause uncharacteristic.

Was that giant collective gasp I just heard an indicator that some of you had not been carefully constructing individual speech patterns for your major characters? Or did half of you just realize that a professional reader might well be paying attention to how and whether the dialogue permits those characters to breathe?

If you’re like most aspiring novelists, it was probably a little of both. Writers new to dialogue usually concentrate almost exclusively upon the content of what their characters are saying, rather than how they are saying it: it’s no accident that in most submissions, any given line of dialogue could come as easily out of one mouth as another. The vocabulary or grammar might vary a little, but essentially, all of the characters are speaking in the same voice.

“I’m tired,” Hamlet said.

Ophelia sighed. “So am I.”

“Are you hungry? We could grab some cheeseburgers on the way home.”

“That would work for me. We could also swing by that all-night taco stand.”

Hamlet turned the wheel so the truck veered across three lanes. “I like tacos. Let’s do that.”

“You’re crazy,” Ophelia said, clutching the armrest for dear life. “I don’t like tacos enough to die for them.”

In short bursts, this type of dialogue can work very well. It’s not particularly character-revealing, but it gets the job done.

It’s a lost opportunity for character development, though. Look what a difference simply giving one of the characters a different cadence and larger vocabulary makes to this perfectly straightforward scene.

“I’m tired,” Hamlet said.

Ophelia sighed. “I believe it. It’s been an utterly exhausting day.”

“Are you hungry? We could grab some cheeseburgers on the way home.”

“If you that sounds tasty to you. We could also swing by that delightfully greasy all-night taco stand.”

Hamlet turned the wheel so the truck veered across three lanes. “I like tacos. Let’s do that.”

“You’re insane,” Ophelia said, clutching the armrest for dear life. “No taco in the world is worth spattering our brains on the pavement.”

The literal meaning is quite similar, but now, a reader could tell simply by the cadence and vocabulary who is speaking when. There’s also more tension in this version: because most readers assume that complexity of speech is an indicator (although not an infallible one) of complexity of thought, the differential in vocabulary could hints at the potential for underlying conflict. Does she want him to talk more, so she is being wordier — and does that attempt annoy him sufficiently that he wants to scare her by driving dangerously? Was he fired that day, and he’s working up nerve to tell her that their days of going out to fancy restaurants are gone for the foreseeable future? Or has he simply been angry with her for the entire exchange, and was expressing it by being terse with her?

Quite a bit of bang for the revision buck, is it not?

The individuated speech patterns also could reflect what occurred just before this exchange, or ongoing conflict. Her lines would take more breath to say than his simple declarative sentences, as well as more effort: is he conserving his energy because he is dog-tired, or is he the strong, silent type? Did he perceive her statement about the greasiness of the food at the taco stand as a dig about his eating habits, something she has been nagging him about for the entire book? Or do these two people suffer under a chronic failure to communicate, and so they take refuge in discussing only mundane topics like whether they would prefer cheeseburgers or tacos?

Seem like a lot to read into an ostensibly ordinary exchange? Professional readers tend to like dialogue that operates simultaneously on several different levels, not only dealing with what is happening in the moment, but with ongoing dynamics. Such exchanges are not only about what is said, but what is left unsaid.

The pros even have a name for this kind of scene, albeit a rather cumbersome one: there’s more happening than is happening. One also hears it as there’s more going on than is going on, but you get the point. Instead of using the dialogue as a blunt instrument to move the plot along, reserving character development for the narrative sections, complex exchanges move the plot along while revealing character, conflict roiling under a seemingly placid surface, long-concealed resentments, etc.

That’s a nifty trick, one that requires a sophisticated understanding of the characters and the story to pull off. It also requires an acceptance of the notion that the point of dialogue is not merely to reproduce how people speak in real life. Just as not every real-world action is worth depicting on the page, the bare fact that someone might actually say something does not necessarily render it entertaining dialogue. A novelist is not, after all, just a transcriptionist: a writer’s job is to improve upon reality, to embroider upon it, to show it to the reader in new and unanticipated ways.

Which is why, should anyone out there have been wondering, Millicent tends to get bored pretty by conversations that don’t seem to be going anywhere, even if the actual exchange is, as they say, ripped directly from real life. It’s hard to blame her, either, when so much of the dialogue she sees runs rather like this:

“Have a hard day?” Ophelia asked.

“Yes.”

“I did, too.” She glanced at the clouds swiftly gathering over the moat. “Looks like rain.”

“Sure does. Did you bring the cat in?”

“Of course. You might want to bring the car into the garage, in case it hails.”

“It’s certainly been cold enough,” Hamlet agreed, “especially at night.”

“Um-hmm. Could you take the recycling to the curb on your way out?”

“Of course, hon.”

Yawn. We’ve all heard a million conversations like this, but since they are not particularly interesting to bystanders in real life, why would we buy a book to see them reproduced on the page? Or, to recast this in revision terms, if a discussion neither advances the plot nor reveals some heretofore-unseen aspect of character, why keep it?

Perhaps I’m an unusually demanding reader — I hope so; it’s my day job — but if dialogue is not entertaining or informative, I’m just not interested. If a character is spouting things that anyone might say, those stock phrases tell me nothing about who she is as an individual. All that standard chit-chat tells me is that the author has conflated realistic dialogue — i.e., speech that sounds as though a real human being might actually have said it — with real dialogue, actual speech transcribed on the page.

Learning to tell the difference is an essential skill for a novelist (and it’s pretty helpful for a memoirist as well). Why? To a professional reader, every line of dialogue has to earn its place on the page.

I heard all of you slice-of-life lovers gasp and mutter, but honestly, you would be hard-pressed to find even a single professional reader who would agree that any given line of dialogue has a right to appear on a manuscript page just because an actual person said it. Selectivity is the soul of good writing, after all. Realism is fine, in moderation, but after one has read a few thousand manuscripts in which characters say scads of not-very-interesting things simply because people talk that way, dialogue that is merely realistic can lose a lot of its charm.

Hey, didn’t someone mention something about the desirability of dialogue that serves more than one narrative purpose? Or did I dream that?

Exchanges that rely solely upon sounding like actual speech can seem especially trying if the one in front of Millicent happens to be the 10th or 20th of the day’s crop of manuscripts that features dialogue-only scenes. Why are they so common in submissions? Because an astonishingly high percentage of aspiring writers believe that dialogue in a novel is supposed to read like an excerpt from a play.

We’ve all read dialogue-only scenes, right? These exchanges that take the classic writing advice to make the dialogue itself, not an adverb in the tag line, say everything that needs to be said. After establishing who the two (seldom more) discussants are, the speeches alternate, sometimes for pages on end. Due to the subsequent absence of tag lines, descriptions of tone, mental asides, etc., the writer necessarily relies upon the reader to keep track of who is speaking when.

“To be or not to be,” Hamlet observed, “that is the question.”

“No, it isn’t,” Ophelia retorted. “Stop being melodramatic.”

“But I want to die.”

“You don’t want anything of the sort. You just don’t want to tell your mother that you accidentally smashed the vase she gave us as an engagement present.”

“If you had grown up with my mother, the sweet embrace of death would seem like the preferable option here.”

“If I had grown up with your mother, I would have stopped speaking to her by the age of ten and a half.”

“Easy for you to say.”

“And it’s easy for you to avoid telling her the truth. I’m tired of being the one who always has to break bad news to her.”

“You’re not always the one.”

“Who told her last year that our dog had dug up her prize begonias?”

“I was the one who broke it to her that we were getting married.”

“Along the broad spectrum of global disasters, that ranks pretty low.”

“Again, we clearly grew up with very different mothers. Whatever affects mine is a global disaster, by definition.”

This isn’t terrible dialogue, but you must admit, there’s nothing much happening here except what’s happening. Because of the presentation style, all the reader sees is what is on the surface. That’s not entirely coincidental: such exchanges are usually predicated on the assumption that human beings say precisely what is on their minds 100% of the time.

“So much for subtext,” Millicent mutters. “When I bicker, I like to think that my jibes connect on a variety of complex levels.”

I’m with you, Millie: I seldom find long dialogue-only scenes especially realistic, even if the speeches themselves ring true. Why? Well, the import of face-to-face human interactions seldom lies entirely in the words spoken. Tone, body language, nervous tics, grandiose gestures — all of these play into how one party interprets another’s intended meaning. By presenting the dialogue only, the writer is leaving the reader to fill in all of these potentially important details herself.

Then, too, at the risk of shocking you, it’s been my experience that few people say precisely what they mean every time they open their mouths. No one is perfectly articulate at all times, and frankly, who would want to be? Good manners alone dictate that not everything one thinks should come hopping out of one’s mouth.

Ask your mother. She’s with me on this one.

Speaking of not speaking out of turn, I’ve been sensing those of you who favor dialogue-only scenes squirming in your chairs for quite some time now. “But Anne,” tone-eschewers everywhere point out, “my high school English teacher told me that really good dialogue doesn’t need additional narrative text. If the dialogue genuinely fits the character and the situation, all of that body language stuff is merely window-dressing.”

I mean no disrespect to your sainted English teacher, squirmers, but that’s ridiculous. Admittedly, it was a very common type of ridiculousness in high school classrooms for about 40 years — specifically, the years when it was fashionable to try to teach every freshman to write like Ernest Hemingway. In recent years, adjectives and adverbs have come back into style.

The fact that there was a period in 20th-century American literature when they went out of style is why your English teacher encouraged you to minimize their use in tag lines, by the way. S/he was trying to discourage you from engaging in 19th century-style tag lines, known for their heavy reliance upon adverbs to add meaning to speech. Basically, s/he didn’t want you to write like this:

“To be or not to be,” Hamlet observed laconically, “that is the question.”

“No, it isn’t,” Ophelia retorted with some asperity. “Stop being melodramatic.”

“But I want to die,” he said morosely.

“You don’t want anything of the sort,” she replied irritatedly. You just don’t want to tell your mother that you accidentally smashed the vase she gave us as an engagement present.”

“If you had grown up with my mother,” he pointed out angrily, “the sweet embrace of death would seem like the preferable option here.”

“If I had grown up with your mother,” she said understandingly, “I would have stopped speaking to her by the age of ten and a half.”

A little of this style of tag line goes a long way, doesn’t it? Your teacher had a point: if the narrative relies upon how a character said something to convey the primary meaning of the speech, rather than the content or word choice, the dialogue plays a less important role in the scene. The practice discourages packing the maximum meaning into every line of dialogue.

What those of us for whom English class is but a far-off memory tend to forget, however, is that having students write dialogue-only scenes was an exercise intended to break the habit of leaning on tag lines, not a prescription for good dialogue. To extend that exercise and pretend that play-like exchanges are the only way to write dialogue well is to ignore the fact that most of the good novels of the last century have not embraced dialogue-only scenes as the norm.

In fact, acknowledging that human beings sometimes experience mixed motivations and respond to stimuli not in words or thoughts, but with their bodies has been a hallmark of literary and women’s fiction for several decades now. Or, as editors like to put it, “Could we get out of the protagonist’s head and into her body every so often, please?”

That’s not to say, of course, that dialogue-only scenes are never effective on the page — but like so many other high school English teacher-endorsed narrative tricks, it’s radically overused, and often applied to scenes where a fuller presentation of character, motivation, and non-verbal clues about what is going on would provide the reader with a better reading experience.

How so? Well, isn’t one of the primary benefits of a close third-person or first-person narrative the ability to show the reader what’s going on inside the protagonist’s head, torso, legs, and psyche? Dialogue-only scenes take that advantage and throw it out the window.

And with it often flies the sense that more is going on that meets the eye. Take a gander at how easy it is to add complexity to Hamlet and Ophelia’s philosophical debate by allowing for the possibility that the protagonist in this tight third-person scene has mixed motivations — and that her discussant is sending her non-verbal clues as to his mood.

Hamlet hung up the phone with a bang. “To be or not to be, that is the question.”

Oh, God, he was at it again. “Stop being melodramatic.”

“But I want to die.”

Ophelia hauled out her standard soothing argument and dusted it off for reuse. “You don’t want anything of the sort. You just don’t want to tell your mother that you accidentally smashed the vase she gave us as an engagement present.”

He slumped in his chair like a schoolboy waiting outside the principal’s office. “If you had grown up with my mother, the sweet embrace of death would seem like the preferable option here.”

“If I had grown up with your mother, I would have stopped speaking to her by the age of ten and a half.”

He picked at his nails, even though he knew it annoyed her. “Easy for you to say.”

Her jaw ached with the strain of not nagging him to stop. “And it’s easy for you to avoid telling her the truth. I’m tired of being the one who always has to break bad news to her.”

His face lit up; was he enjoying this? “You’re not always the one.”

She pictured him wrapping the lamp cord around his neck, jumping off the nearest bridge, sticking his pinkie into the light socket, but her tone remained sympathetic. “Who told her last year that our dog had dug up her prize begonias?”

“I was the one who broke it to her that we were getting married.”

Yeah, well, you’ve turned out to be no bargain, either, sweetheart. “Along the broad spectrum of global disasters, that ranks pretty low.”

“Again, we clearly grew up with very different mothers. Whatever affects mine is a global disaster, by definition.”

Quite a different scene, isn’t it? Not a syllable of dialogue is changed from the previous two examples, but now that we can see Hamlet’s behavior and hear Ophelia’s thoughts, the scene is infused with an adrenaline burst of conflict. On the surface, it’s not a fight, but few readers would not catch the underlying tension between these two characters.

To put it bluntly, that makes this a more interesting scene. Why? It operates on more than one level.

“But Anne,” those of you who shrink from depicting conflict on the page pipe up gently, “this makes Ophelia seem really hostile. If she were my protagonist, I would worry that readers would find her completely unlikable.”

That’s a completely legitimate concern, sweetness-mongers, but remember, in that last example, she’s not saying any of those things out loud. In fact, she is making a substantial effort not to be aggressive. She’s merely disagreeing with him.

And that would tend to render her a more interesting protagonist, from Millicent’s perspective; her inbox is perennially stuffed to the gills with books about people too nice (or too shy) to disagree with anyone, ever. Interpersonal harmony may be quite nice on the page, but it can make for some pretty stultifying dialogue.

Not sure why unvarying sugar and spice might get a tad tedious? Here is a representative sample of the kind of conflict-avoiding dialogue super-nice protagonists tend to utter.

Ophelia ran to meet Hamlet at the door. “You look exhausted, sweetheart. A bad day?”

“The worst.” He collapsed onto the couch without taking off his dust-covered jacket. “First, my stupid uncle yelled at me for being thirty seconds late to court this morning.”

“That’s awful.”

“After starting off on that delightful note, he then proceeded to lecture me for half an hour about how it was my responsibility to bring Laertes’ sword skills up to standard.”

“That’s so unfair.”

“I mean, why can’t he hire his own fencing tutor? It’s not as though I don’t have anything else to do. Dad keeps me up half the night, roaming the battlements, and Fortinbras is just waiting for my uncle to do something diplomatically stupid, so he would have an excuse to invade.”

“You’re only one person. You can’t do everything.”

He covered his face with his hand. “Sometimes, I just want to end it all.”

“Don’t say that.”

“It’s true.”

“Really?”

Had enough yet? Millicent has. If you’re not sure why, allow me to ask you: what precisely do Ophelia’s lines add to this scene, other than a vague undercurrent of supportiveness?

On the fence about that one? Okay, let’s apply a standard editorial test for whether a section of dialogue has slipped into the realm of monologue. Here it is again, with all but Ophelia’s first line excised.

Ophelia ran to meet Hamlet at the door. “You look exhausted, sweetheart. A bad day?”

“The worst.” He collapsed onto the couch without taking off his dust-covered jacket. “First, my stupid uncle yelled at me for being thirty seconds late to court this morning. “After starting off on that delightful note, he then proceeded to lecture me for half an hour about how it was my responsibility to bring Laertes’ sword skills up to standard. I mean, why can’t he hire his own fencing tutor? It’s not as though I don’t have anything else to do. Dad keeps me up half the night, roaming the battlements, and Fortinbras is just waiting for my uncle to do something diplomatically stupid, so he would have an excuse to invade.”

He covered his face with his hand. “Sometimes, I just want to end it all.”

Pretty much the same, isn’t it? By lobbing softball questions that do little more than prompt Hamlet to continue, Ophelia is not a full participant in this scene — she’s a bystander.

Surprisingly, while this kind of monologue-enabling behavior can seem quite supportive in real life — who doesn’t like someone to make sympathetic noises while pouring out one’s woes? — it usually does not render a protagonist more likable on the page. Why not? Well, think about it: is Ophelia helping move the plot along in the last set of examples? Or is she slowing it down by contributing dialogue that doesn’t add anything substantial to the exchange?

To be fair, a single scene of harmonious agreement is probably not going to lead the average reader to begin muttering, “Get on with it, plot.” That sort of response tends to greet the habitually non-confrontational protagonist.

But Millicent is not the average reader, is she? Particularly in dialogue gracing the opening pages of a manuscript, she wants to see not only conflict — external or internal — but dialogue that reveals character. Beyond the fact that Ophelia is generally supportive of Hamlet, what does her dialogue in that last example reveal?

So if the protagonist seems passive and not prone to complex reactions on page 1, would you keep reading just because she seems like a human being who might be nice to know in real life? Or would you shout, “Next!” and move on to the next submission in the hope of discovering a protagonist more likely to do something to move the plot along or surprise you with unexpected depth?

Don’t worry; I shan’t make you give your answer out loud. It might make you seem less likable to other writers.

Softball questions like “Really?” and “How so?” are one means of disguising monologue as dialogue. Another is to have one of the participants in a discussion go on far longer than most real-life hearers would tolerate. In everyday life, people can’t wait to give their opinions: they interrupt, ask questions, contradict, offer anecdotes from their own experience.

On the manuscript page, however, characters are all too given to waiting in tranquil silence while another character lectures them. Often, such speeches devolve into Hollywood narration, permitting the writer to wedge information that both parties already know into the dialogue, so the reader can learn about it, too.

Go ahead and pitch that softball, Ophelia, so Hamlet can take a swing at it.

“But I don’t understand,” Ophelia said. “You think your uncle did what?”

Hamlet took a deep breath, as if he were about to deliver a monologue in front of a packed house. “He poured poison into Dad’s ear while he slept in the garden. You see, Dad was still exhausted from battle; Uncle Claudius always did know how to keep refilling a wine glass without Dad’s noticing. He was a sitting duck. You know how loudly he snored; an elephant could have lumbered across the lawn, and he wouldn’t have been able to hear it. Uncle Claudius must have seen his chance to hold onto the throne — which, as you may recall, he had been occupying while Dad was off at war. Now that Dad was back, he was in line for a serious demotion.”

She shrugged impatiently. “Other people manage to adjust to a workplace organization without resorting to murder. This seems completely far-fetched to me.”

“That’s because you aren’t taking into account Uncle Claudius’ feelings for my mother. You’ve seen how he looks at her during banquets, after the mead gets flowing. He’s been after her for years, and while she’s done nothing but encourage him in public, she’s been sending him awfully mixed messages. Remember that time he nearly knocked Dad’s block off when Mom said only married or engaged couples could compete in the limbo contest? You thought she was only trying to prevent us from winning, or to push me to pop the question, but I’m positive that she was making sure no one would catch on about her secret limbo sessions with Uncle Claudius.”

“I did think that at the time, I’ll admit. But you still could be imagining most of this.”

Given how strongly Ophelia disagrees with what Hamlet is saying, it’s rather surprising that she lets him go on at such length before she even attempts to chime in, isn’t it? If this were a real-world argument, she would have jumped in every time he paused for breath.

How might a reviser know when that might be? You probably saw this one coming: by reading the scene IN ITS ENTIRETY and OUT LOUD. Unless Hamlet has the lung capacity of an Olympic swimmer, he’s not going to be able to get the extensive arguments above out of his mouth in single breaths. The exchange would probably be closer to this:

“But I don’t understand,” Ophelia said. “You think your uncle did what?”

Hamlet took a deep breath, as if he were about to deliver a monologue in front of a packed house. “He poured poison into Dad’s ear while he slept in the garden.”

She hated it when he stopped taking his medication. “Where anyone might have seen him do it?”

“But the garden was empty. Dad was still exhausted from battle; Uncle Claudius always did know how to keep refilling a wine glass without his noticing.”

“Claudius was wearing body armor that night. He couldn’t have budged without waking every bird in the garden.”

“You know how loudly Dad snored; an elephant could have lumbered across the lawn, and he wouldn’t have been able to hear it.”

She changed tactics. Maybe humoring his fantasy would calm him down. “Okay, let’s assume for the moment that it was possible. Why would your uncle want to kill his own brother?”

He looked at her as though he thought she’d tumbled off her rocker. “Because he didn’t want to give up the throne, of course. Now that Dad was back from the war…”

She shrugged impatiently. “Other people manage to adjust to a workplace organization without resorting to murder.”

“You aren’t taking into account Uncle Claudius’ feelings for my mother. You’ve seen how he looks at her during banquets, after the mead gets flowing.”

Not that old court gossip again. “Do you honestly believe that he has a chance? He’s her brother-in-law, for heaven’s sake.”

“Remember that time he nearly knocked Dad’s block off when Mom said only married or engaged couples could compete in the limbo contest?”

Darned right she remembered: Gertrude had never been light-handed with her hints about their getting married. “She just didn’t want us to win. I could limbo circles around her.”

He leaned close, whispering conspiratorially. “She was making sure no one would catch on about her secret limbo sessions with Uncle Claudius.”

Reads more like an argument, doesn’t it? That’s not only the effect of editing out the Hollywood narration: by breaking up Hamlet’s soliloquies into reasonable bursts of breath expenditure, the rhythm of the scene increases markedly.

Speaking of energy expenditure, that’s quite a few examples for a single post. Rather than lecture you further, I shall save my breath for future posts. Keep up the good work!

Pet peeves on parade, part XIII: repetitive activities and other things that wouldn’t be interesting to most readers if you set them on fire

Before I launch into today’s festivities, campers, I would like to call your attention to some festivities on this coming Saturday, April 9th. At 6 p.m., Seattle’s Wing Luke Museum of the Asian Pacific Experience will be holding its annual fundraising dinner and auction. A door prize for all attendees: a pre-release copy of Harold Taw’s The Adventures of the Karaoke King.

What a creative promotion idea, eh?

If Harold Taw’s name sounds familiar to those of you who have been hanging out here at Author! Author! for a while, it should: Harold is the long-time member of our little community whose first novel got plucked out of the plethora of entries in the Amazon Breakthrough Novel contest and brought to publication through AmazonEncore. I plan to be raising a toast to his book’s astonishing journey to publication at his book release party at Elliott Bay Books on April 27th, by the way, while folks are marking calendars; I’d love to lead the wave in an Author! Author! cheering section.

As eagle-eyed readers may have been able to discern through the lines of that last paragraph, I love announcing my readers’ triumphs along the long and bumpy road to publication. Keep that good news rolling in, everybody!

While we’re on the subject of subtleties of the tossing-a-brick-through-the-nearest-window variety — how’s that for a light-handed segue? — I’d like to devote today’s post to a species of manuscript problem that seems to be practically invisible to most writers who produce it. The fact that it is so hard for a self-editor to catch, however, in no way impairs its ability to irritate professional readers like our old pals, Millicent the agency screener, Maury the editorial assistant, and Mehitabel the veteran contest judge, to madness.

“Not again!” Millicent exclaims, her fingers itching to reach for the form-letter rejection pile. “This submission has gotten caught in a conceptual repetition loop!”

Surprising that a subtle problem could engender such a strong reaction? Don’t be: professional readers are trained to focus on the little stuff. Millicent in particular is trained to be on the look-out for typos, formatting problems, missing words, and all of the other signs that a manuscript is at least one revision away from being ready to market to editors.

Or, to express it in her terms, a submission that causes her itchy fingers to make actual contact with that stack of rejection letters. “Next!” she cries.

Yes, I know: I harp quite a lot on the importance of a manuscript’s being completely clean — at least in the opening pages — in order to skirt the specter of knee-jerk rejection, but I’m continually meeting very talented aspiring writers who complain about how often their work is getting rejected…but haven’t taken the time to remove, or even notice, the seven typos within the first two pages of their texts. While it’s certainly understandable that someone who wants to write for a living would be shocked or even horrified upon learning just how high professional standards actually are, this is no time to be in denial: assuming that one’s first draft is going to meet those standards without further revision or even proofreading has led thousands upon thousands down the primrose path to rejection.

Has that sunk in this time, or shall I play another verse on my harp? My fingers are all warmed up now.

To be fair, even writers who have been working on their craft for years are often stunned to realize that the pros pride themselves on noticing everything. And with good reason: contrary to popular opinion, to a pro, the proper use of language is an integral part of an author’s literary style and voice, not a purely cosmetic addition to it.

As a freelance editor, I find it fascinating how often aspiring writers equate Millicent’s focus on proper language use — which is part of her job, incidentally — with a dislike of good writing. In reality, quite the opposite is usually true: the people who choose to work in agencies and publishing houses almost invariably love beautiful writing and strong stories.

Paradoxically, this affection for the well-constructed sentence often renders reading a promising submission or contest entry more irritating than one where the writing just isn’t very good. “Oh, dear,” Mehitabel says, shaking her head regretfully over a page full of potential, “I hate it when this happens. If only this writer had taken the time to notice that he’s made the same point four times over the course of this scene, it would have been so much more compelling. Next!”

Seem like a petty reason to knock an otherwise well-written entry out of finalist consideration? Actually, it’s a rather common one. As I hope has become clear over the course of this series on notorious professional readers’ pet peeves, the manuscript problems that cause Millicent, Maury, and Mehitabel to rend their garments are not always major gaffes like an authorial indifference to punctuation or a storyline that provokes the ejaculation, “Huh?” every other line.

They see those kinds of submissions, of course, but astonishingly often, the irritant is simply a page of text that makes the same point too many times. Why, here’s an example of that species of scene coming along right now.

See if you can catch the subtle narrative problem that might elicit a cry of, “Next!” Actually, you might want to hunt for three of them.

“What is it you are trying to say, Carol?” With infinite care, Alphonse flicked the blindingly white tablecloth over the polished oak surface. “Apparently, I’m not getting it.”

She sighed. “We’ve been over this same ground thirty-seven times, Alphonse.”

He settled the cloth over the table. “Make it thirty-eight, then.”

“We don’t want to hold you back from other employment opportunities, Alphonse.”

“Nonsense.” He smoothed the tablecloth over the flat surface, checking for any lingering wrinkles his iron had missed. “It’s a pleasure to work here.”

“But Alphonse, we can’t afford to keep you.”

He lowered a fork into its proper place. “I don’t cost much, Carol. I live mostly on my tips.”

She pounded the table, making the fork dance. “Alphonse, you live entirely on your tips. We haven’t paid you in seven months.”

“Well, then,” Alphonse reached to nudge the fork back into line, “you can hardly complain that I’m overcharging you for my services.”

“Alphonse!” Carol shouted. “I’ve fired you thirty-seven times already!”

He smiled, apparently at the fork and spoon he had just placed. “Thirty-eight, isn’t it?”

She slumped. “I give up.”

Alphonse laid down a soup spoon. “You always do, Carol. You always do.”

Come on, admit it — by halfway through this excerpt, you wanted to shout, “Criminy, Alphonse, enough with the table-setting! Move on to something else.”

So would Millicent, and she has the power to enforce that preference. Being editorially trained, she’s more likely to express it as, “Um, couldn’t most of the inter-dialogue narrative have been replaced very adequately by Alphonse set the table with care?” but you get the picture, right? To an intelligent reader who is paying attention, attenuating the description of a process by mentioning each and every step can make a scene seem much longer than it is.

In a case like this, where the activity is not inherently interesting — he’s setting a table, for heaven’s sake, not cross-checking the details for the first manned flight to Venus — it can be downright irritating. That page space could have been used for far more fascinating ends.

We’ve discussed a version of this phenomenon before, right? The Walking Across the Room (WATR) problem dogs many a manuscript submission: instead of just stating that a character does something relevant, like answer a ringing doorbell, the narrative will describe him hearing the ring, rising from his seat, taking step after step across the room, opening the door into the hallway, passing down the hallway, approaching the front door, grasping the knob, turning it, and pulling.

All of which could quite nicely be summed up as The doorbell rang. Yves answered it., right?

The meticulous-minded have had their hands politely raised for the last few paragraphs. Yes? “But Anne,” process-huggers protest, “I don’t agree that Alphonse has a WATR problem. The passage above merely shows his attention to minute detail, showing (not telling) that he’s a perfectionist. That’s legitimate character development, isn’t it?”

Well, in a way, detail-hounds. Yes, it demonstrates character; it’s just not the most interesting way to do it. Nor are these details in and of themselves likely to hold the reader’s attention.

Hey, I wasn’t kidding about these problems being difficult to catch in one’s own work. To Alphonse’s creator, all of the mundane specifics above may well be gripping.

Remember, though, just because a character might conceivably perform an action isn’t necessarily enough reason to include it a manuscript. Since this is a process that it’s safe to assume every reader will have observed before, however, the page space would be better spent demonstrating his attention to detail in an activity with which most readers will be less familiar — constructing a multi-layered wedding cake, for instance.

Or at least one that tells the reader a little more about what kind of restaurant it is. Take a gander at how much more revealing this scene is if our Alphonse busies himself prepping the restaurant’s signature dessert.

“What is it you are trying to say, Carol?” With infinite care, Alphonse sharpened his personal paring knife — off-limits to the rest of the wait staff — on the whetstone he kept in his left pants pocket. “Apparently, I’m not getting it.”

She sighed. “We’ve been over this same ground thirty-seven times, Alphonse.”

He wiped the gleaming knife on his handkerchief. “Make it thirty-eight, then.”

“We don’t want to hold you back from other employment opportunities, Alphonse.”

“Nonsense.” Holding his breath, he began cutting the zest off an orange in one long strip. “It’s a pleasure to work here.”

She held her breath, too; if his blade slipped, the curly peel would be too short for the flames to dance down its liquored length to the customer’s coffee cup. “But Alphonse, we can’t afford to keep you.”

A perfect peel tumbled from his knife into the waiting silver bowl. “I don’t cost much, Carol. I live mostly on my tips.”

“Alphonse, you live entirely on your tips. We haven’t paid you in seven months.”

“Well, then,” Alphonse studded the peel with whole cloves, “you can hardly complain that I’m overcharging you for my services.”

“Alphonse!” Carol shouted. “I’ve fired you thirty-seven times already!”

He smiled, apparently at the brandy awaiting his match. “Thirty-eight, isn’t it?”

She slumped. “I give up.”

With a pointing finger, Alphonse laboriously counted all of the ingredients on his café brulôt cart. “You always do, Carol. You always do.”

Nice way to combine character development for him and information about the restaurant, isn’t it? By killing the proverbial two birds with one stone, the reader is not only treated to a more interesting process to observe, but is faced with far less repetitive and predictable activity throughout the scene.

Speaking of repetitive, did you catch the two subtle narrative problems remaining in the text? Hint: one is on the scene level, and the other is on the sentence level.

If you grasped the nearest tablecloth, waved it over your head, and exclaimed, “The constant name repetition is visually most annoying,” help yourself to an extra orange off Alphonse’s cart. The characters’ names are mentioned far too often than is necessary for clarity. Indeed, since the only two characters in the scene are of different sexes, the narrative sections could dispense with all but the first of those eye-distracting capital letters.

But the narrative repetitions of their names actually account for relatively few if the iterations. The real culprit here is the extremely pervasive phenomenon of having the characters address one another by name far more often than people actually do in real life.

As a group, aspiring writers seem to adore this. Editorial opinion on why varies: some of us maintain that writers tend to compose lines of dialogue in short bursts, rather than entire scenes, so they don’t notice how often their characters are barking their names at one another; others assert that writers just like the names they have picked for their characters to want to see them again and again. (It’s not all that uncommon for first-time novelists to believe that simply changing a name will completely destroy the reader’s conception of the character, as if the name choice were so significant that no other character development was needed or wanted.) The more practical-minded believe that writers sometimes overuse name repetition in dialogue deliberately, to make it easier for readers to follow who is speaking when; the more cynical think that writers repeat the names to remind themselves who is speaking when.

If it’s the last, it’s not a bad strategy — at the composition stage. Alternating lines of dialogue where the count has gotten off is another of Millicent’s pet peeves, after all. It’s surprisingly common in submissions, and it’s often an instant-rejection trigger. Proofreading each and every line of dialogue that does not contain a tag line (the he said bit that identifies who is speaking), then, can make the difference between Millicent’s remaining involved in a dialogue scene and “Next!”

At the polishing stage, though, the training wheels should come off: the extraneous name markers need to go. Fortunately, if the scene is clearly written, with each character’s dialogue being distinct from the other’s, these cuts can be made with virtually no cost to the story.

“What is it you are trying to say, Carol?” With infinite care, Alphonse sharpened his personal paring knife — off-limits to the rest of the wait staff — on the whetstone he kept in his left pants pocket. “Apparently, I’m not getting it.”

She sighed. “We’ve been over this same ground thirty-seven times, Alphonse.”

He wiped the gleaming knife on his handkerchief. “Make it thirty-eight, then.”

“We don’t want to hold you back from other employment opportunities”

“Nonsense.” Holding his breath, he began cutting the zest off an orange in one long strip. “It’s a pleasure to work here.”

She held her breath, too; if his blade slipped, the curly peel would be too short for the flames to dance down its liquored length to the customer’s coffee cup. “But we can’t afford to keep you.”

A perfect peel tumbled from his knife into the waiting silver bowl. “I don’t cost much. I live mostly on my tips.”

“You live entirely on your tips. We haven’t paid you in seven months.”

“Well, then,” he studded the peel with whole cloves, “you can hardly complain that I’m overcharging you for my services.”

“Alphonse!” she shouted. “I’ve fired you thirty-seven times already!”

He smiled, apparently at the brandy awaiting his match. “Thirty-eight, isn’t it?”

She slumped. “I give up.”

With a pointing finger, he laboriously counted all of the ingredients on his café brulét cart. “You always do, Carol. You always do.”

Did it surprise all of you self-editors that I kept Carol’s shout of “Ambrose!” That’s the one that has the strongest emotional resonance: essentially, she is trying to call him back to reality. Now that all of her other repetitions of his name are gone, it stands out as it should.

There’s one final pet peeve that remains uncorrected — and no, it’s not the dubiously-constructed clause about the pointing finger. I’ll give you a hint: there’s an improperly-formatted tag line haunting this scene.

Or, as Millicent would put it: “Studded is not a speaking verb! Neither is reach! Next!”

Not positive what she’s talking about? Okay, here are the offending sentence from each version, ripped out of context.

“Well, then,” Alphonse reached to nudge the fork back into line, “you can hardly complain that I’m overcharging you for my services.”

“Well, then,” he studded the peel with whole cloves, “you can hardly complain that I’m overcharging you for my services.”

See Millie’s point now? No? Okay, would it help to know that what the author originally meant was this?

“Well, then,” Alphonse said, reaching to nudge the fork back into line, “you can hardly complain that I’m overcharging you for my services.”

The problem lies in the first two versions of this sentence using reach or stud, respectively, as substitutes for said. Since only verbs that refer to speech may legitimately be used in a tag line, the end result is improper — and a misuse of that first comma.

How so? “Well, then,” he studded the peel with whole cloves, is a run-on sentence. In a tag line, the comma indicates that a speaking verb is to follow. So while this is correct:

“I’m coming, Harry,” Celeste said.

This is not:

“I’m coming, Harry.” Celeste said.

Nor is:

“I’m coming, Harry,” Celeste put on her hat.

Those last two look very wrong, don’t they? Yet you would not believe how often these errors appear in otherwise well-written dialogue. My theory is that it’s a Frankenstein manuscript phenomenon: aspiring writers may write tag lines correctly the first time around, but come revision time, they change the verb without noticing that they have not altered the punctuation to match.

Millicent, Maury, and Mehitabel can’t believe the frequency with which tag line problems crop up, either, but their explanation tends to be less charitable. “If these people want to write dialogue professionally,” they ask one another over flaming cups of coffee, “why wouldn’t they take the time to learn how tag lines work? Or to proofread?”

You have to admit, those are pretty darned good questions. If you’ll just hang around while I set the table for 18 people, perhaps we could discuss them at length.

Just not, please, on the manuscript page; both life and Millicent’s overloaded reading schedule are too short to read repetitive descriptions of uninteresting activities. Keep up the good work!

Pet peeves on parade, part XII: give that horn a rest, Bozo. Or at least save it for the moment when it will have the most effect.


Every spring, I like to go on a media fast for a few days, just to reset my perspective: I eschew newspapers, television, radio, and yes, even my own blog. Instead of these shiny, frenetic distractions, I walk outside, breathe the fresh air, and bask in light that isn’t reflected from a screen. Then, refreshed, I can return to my work.

Normally, I wait until Seattle is warm enough for me to take those aforementioned walks without being bundled up to my nose in sweaters, jackets, and mufflers. This year, however, the muses were kind enough to provide me with tap on the shoulder and a murmured, “It’s time to go, sweetie.”

Actually, if I’m honest about it, their hint was more of a gigantic shove and a bellow of “Get a move on, doll!” that would have made the late and loud Ethel Merman wheel around in alarm, exclaiming, “What the heck was that?” But omen-watchers can’t be choosers, so out the door I went.

What happened, you ask? Well, at the end of last week, I logged into Facebook (where I have recently erected a fanpage, incidentally) to check in with some friends in Tokyo, as one does when natural and manmade disasters occur simultaneously. When I tried to post a comment, a brusque message informed me that the system had experienced a technical error. The dialogue box invited me to click on an ostensibly helpful link entitled Try Again.

That seemed like sensible advice: I clicked it once. The system then proceeded to post my comment 94 times, of its own accord. And frankly, what I’d had to say would have been interesting to even the most avid reader three or four times, at most.

But in the best tradition of false suspense, Facebook did not show me those 94 comments. Instead, it simply sent me back to my own homepage, as though nothing out of the ordinary had happened. So how did I find out about the infamous 94 at all? Because when I tried commenting on another friend’s page, up popped a genuinely nasty message saying that I was blocked from posting for some indefinite period of time, ranging (it said) anywhere from a few hours to a few days, because of my ongoing patter of (unnamed) malicious behavior annoying or abusive to other users.

What that behavior was, I was left to guess; the message merely referred me to a FAQ page. In the manner of badly-designed FAQ pages everywhere, it simply repeated verbatim what the message that had sent me there said. Grumbling, I went back to my friend’s page and did something that the harsh rebuke had not advised, but should have: I manually deleted 93 of those messages, one at a time. Because the system isn’t set up do mass deletions, this took almost 20 minutes.

Now, I could have taken this blatantly unfair series of events in any number of ways. I could have shaken my head over just how much time advancing technology manages to waste in all of our lives — as any aspiring writer trying to blandish a recalcitrant PC into printing a document in standard format (it’s easier on a Mac), unless the program’s designers happened to envision the problem one wants to solve, even the simplest change can eat up hours. I could also have wondered whether Facebook had invented this glitch on purpose, as an excuse to get rid of subscribers. I could even have thrown up my hands and concluded that the computers have become sentient — if not particularly intelligent — and are now turning on their masters.

But I’m an editor by trade. The very first words I uttered when I finally tracked down what the problem was: “94 posts that all say the same thing! That’s almost as repetitious as dialogue in the average submission.”

Hey, my assistant laughed when I said it. Shortly before I told her to take a long weekend and walked out the door myself, seeking a soothing walk in the rain, early spring flowers, and some peace from computer systems that have apparently decided the next step toward world domination is to create a class of unjustly accused computer outcasts.

Early in my walk, I had intended to use that anecdote as a springboard for a well-justified lecture about the dangers of replicating the extreme redundancy of everyday speech on the manuscript page, but by the time I returned home, rivulets streaming from my hair, the muses had talked me into a sneakier way to make a literary point. Ahem: did you catch the rather fundamental storytelling error I deliberately inserted into that story?

Hint: it happens in comic manuscripts so often that our old pal, Millicent the agency screener, automatically twitches a little at the very sight of it.

If you flung your hand in the air and yelled, “I know, Anne! The narrative had another character, your assistant, laugh as a means of demonstrating that a joke was funny,” you already have an A for the day. If you added, “And the assistant character didn’t appear in the story until she was needed to provide the laugh track,” make that an A+.

What about this narrative trick sets Millie a-twitching, you ask? To a professional reader, it’s a telltale sign of authorial insecurity: if the writer were positive that the joke were really funny, Millicent reasons, why would he think the reader needed a prompt to laugh?

Comedic insecurity’s shows up in a few other twitch-inducing manifestations on the manuscript page. I’ve included specimens of four kinds in the following sterling piece of prose — and, just for kicks, another common non-humor pet peeve. See if you can spot them all.

Melvyn glanced stealthily over his shoulder. No one had ever caught him hacking into someone else’s account to post endlessly redundant messages; he wasn’t even sure what dire punishment would await a brave soul caught doing such a thing. Trembling, he reached a hairy forefinger toward the ENTER key.

“Hey, geek.” Clarice came bouncing into the room, a stack of invoices wedged under her arm. “You hiding from the boss? She’s on a fourteen-apple rampage.”

Melvyn chuckled. Arnette was always on some kind of rampage, so he and the other staffers had come up with a rating scale like the one used for diamonds: the weightier her mood, the bigger the number of carats. Bill had just gotten engaged at the time, so solitaire classifications were much discussed around the office. Then some office wag decided that carats weren’t funny enough and changed them to apples. A fourteen-apple rampage must have been impressive to behold.

If you guessed that one of the problems was that the explanation in the last paragraph was boring enough to send Millicent’s weary eyes wandering morosely toward the window to contemplating the sweet spring day outside, well, you have a point. Like so many inside jokes ripped from real-life situations and reproduced faithfully on the page, this bit of office humor falls a bit flat.

A word to the wise: jokes like this should be test-driven verbally before you even consider typing them into your manuscript — and driven by people who do not know anything about the original context of the joke. If total strangers do not respond with mirth, chances are that, as the saying goes, you had to be there in order to find it funny.

Millicent was most assuredly not there. Need I say more?

What else is wrong with this bit of failed office humor? Did you notice that the text laid no foundation for the joke? Had an earlier scene featured some reference to the carat rating system, Clarice’s changing it to apples might have been spontaneously funny. Heck, there could be a running joke where each staffer substitutes his or her own favored fruit, vegetable, or legume.

Okay, so maybe you still would have had to be there. But there’s no denying that the last paragraph was funnier because it contained the word legume.

Unexpected words can often liven up an otherwise so-so bit of humor. As we saw in the example above, the opposite is also true: uninspired word choices can flatten even a funny situation on the page. And when the situation isn’t all that funny in the first place…

Well, I don’t think any of us want to be there, do we?

I spot a few clowns with their oversized gloves in the air. Yes, Bozo? “But Anne,” the red-nosed one points out, and who am I to deny the request of someone in a rainbow-hued fright wig? “How do we know that the author of that example hadn’t set up the joke earlier in the book? This is just an isolated excerpt; we really don’t know anything about context.”

Good point, but would you mind not honking that ooga horn in my face? Thank you so much. Something in the passage itself told me as clearly as if the author had hoisted a ten-foot banner reading FIRST WE’VE HEARD OF THIS over the page that the text had been a trifle light on set up. Any guesses what it was?

If you immediately started jumping up and down, shouting, “If a foundation had been laid for that joke, the turgid paragraph-long explanation would have been unnecessary,” your cup runneth over with editorial virtue. Properly set-up humor does not require further explanation — in fact, telling someone who didn’t laugh why a joke was funny is one of the surest ways to kill any residual humor that might have been lingering in the atmosphere.

Is that plain, or shall I re-explain it? Over and over again, until you wish I had never brought it up in the first place?

On the manuscript page, explanation after the fact is one of the surest signs that the writer has doubts about the joke. “If she thought that it could stand alone,” Millicent mutters, “why would she have slowed the scene down with a paragraph of explanation. Next!”

In response to what half of you just thought: yes, failed humor is often an instant-rejection violation, at least within the first few pages of a submission — and not merely because it’s a high dive that ended in a belly flop. It’s a voice issue, and a marketing one. While the genuinely funny is quite refreshing to find in the middle of a stack of manuscripts, if only because of its rarity, jokes that don’t work tell professional readers that the writer is not yet closely in tune with his audience.

His intended reading audience, that is, not just first readers he may have plucked from his doubtless wide and admiring acquaintance to serve as first readers. It’s an unavoidable reality of comedy writing that people who know and love the author are far more likely to laugh at his jokes than total strangers.

Trust me, Millicent has heard, “But it made my mom/husband/wife/sibling/coworker howl with laughter!” many, many times; to the pros, it’s simply irrelevant. No matter how much a joke or situation may have ‘em rolling in the aisles of your favorite dispenser of alcoholic beverages, if it doesn’t make a stranger laugh as it is written on the page, it’s likely to be a liability at submission time.

Okay, writers without comedic aspirations, your time has come: what was the other common Millicents’ pet peeve? Hint: it appeared in the following sentence.

Then some office wag decided that carats weren’t funny enough and changed them to apples.

Give up? It’s that pesky then, used in a manner that is actually rare not to find in a novel or memoir submission. (Again, don’t underestimate how much sheer repetition can contribute to a professional reader’s negative reaction to a manuscript gaffe. You try seeing the same narrative device in 75 different submissions in a week, and you might well start twitching, too.)

Okay, so that’s a tiny pet peeve — but as we have seen throughout this series, a series of small missteps can add up to rejection fairly quickly. Especially if several of them have chosen to congregate on page 1.

But why might this innocent-seeming word have begun annoying the pros in the first place? An editorial antipathy toward redundancy, mostly: when used in the way we see it above, to indicate that what came next occurred after what’s just been described, then — and its even more popular sibling, and then — are technically unnecessary. In English prose, unless the reader is specifically told that time is not running in a linear manner, events described are assumed to have occurred in the order they appear on the page.

That being the case, why is it necessary to tell the reader that the office wag’s decision came after the carat joke had spread throughout the office? Does the reader have any reason to think that it didn’t happen next?

Instead, why not reserve then to introduce turns of event that might genuinely startle the reader? Millicent is far less likely to object to it as the clarion call of an unexpected sudden plot twist than as a simple and unnecessary notation of the passage of time. Take a gander:

Bill had just gotten engaged at the time, so solitaire classifications were much discussed around the office. Then in the middle of the fifth straight day of coffee-break chat on the subject, Arnette swept into the employee lounge, wielding a roll of duct tape. She slapped a piece across every kisser that so much as uttered the word carat. Thereafter, we were careful to use euphemisms.

Didn’t see that coming, did you? That’s a surprise more than worthy of being introduced to Millicent by then.

Yes, Bozo? You honked your horn? “I wouldn’t really mind Millicent’s objecting to my use of then, or even not finding my jokes funny; I get that my humor might not be everyone’s proverbial cup of tea. I also get that agency screeners read a lot of submissions in a day. What I object to is not being told what specifically triggered the rejection. How hard would it be to scrawl a single sentence fragment in the margins at the point where they stopped reading, so the submitting writer would know why the manuscript was rejected? Or even just make a mark on the page, so the writer would know where the screener stopped reading?”

I have to say, I’m with you on this one, campers: a simple checklist of the most common rejection reasons would take Millicent very little time to fill out. It would be even speedier to print up a few hundred thousand stickers reading, “Show, don’t tell!” or “Where’s the conflict?” so she could slap ‘em on the manuscript page at the precise point where her pet peeve got to her. At least then, the writer could learn enough from the submission experience to improve the manuscript before trying again.

But that, alas, is not the reality of submission in the current hyper-competitive literary environment. We could expend a great deal of energy resenting that the process is set up not to help aspiring writers learn how to get better at submission, but for Millicent to be able to reject as high a proportion of requested materials as possible, to narrow the masses down to the happy few her boss has time to read and consider.

I don’t know about you, but I would rather invest my energies in teaching you to rid your submissions of the most frequent red flags. For the rest of today’s post, I shall concentrate on the rejection reasons that would make the most sense for agency screeners to rubber-stamp upon submissions: ubiquitous problems that are relatively easy for the writer to fix.

If she knows to fix them, that is.

One of my favorite easily-fixed common problems: a manuscript aimed at an adult audience that has a teenage protagonist in the opening scene. If the teenager is the focus of page 1, Millicent is prone to say, “Oh, this is YA — the writer must think that we represent it. Next!”

Remember, there is no easier rejection than a book category that an agency does not handle. (That’s one reason that most agencies prefer query letters to contain the book category in the first paragraph, FYI: it enables agency screeners to reject queries about types of books they do not represent without reading the rest of the letter.) In an agency that represents both, the submission would be read with a different target market in mind, and thus judged by the wrong rules.

“Wait just a cotton-picking minute!” I here some of you out there murmuring. “This isn’t my fault; it’s the screener’s. All anyone at an agency would have to do to tell the difference is to take a look at the synopsis they asked me to include, and…”

Stop right there, oh murmurers, because you’re about to go down a logical wrong path. As we discussed earlier in this series, you can’t legitimately assume that Millicent is going to read your synopsis prior to reading your submission — or indeed at all. Nor is she even remotely likely to have your query letter at her elbow when she begins your manuscript, so she may refresh her recollection of what the book is about. As an unfortunate but direct result, it’s never safe to assume that the screener deciding whether your first page works or not is already familiar with your premise.

Why? Limited time. Millicent needs to figure out whether the submission in front of her is a compelling story, true, but she also needs to be able to determine whether the writing is good AND the style appropriate to the subject matter. An adult style and vocabulary in a book pitched at 13-year-olds, obviously, would send up some red flags in her mind.

Or even in a book she assumes is aimed at 13-year-olds. For those of you who write about teenagers for the adult market, I have a bold suggestion: make sure that your title and style in the opening pages reflect a sensibility that is unquestionably adult, so your work is judged by the right rules. This can be genuinely difficult if your narrator is a teenager.

Which brings me to another easily-fixed rejection reason: narration in a kid’s voice that does not come across as age-appropriate. This issue crops up all the time not just in YA, but in books about children aimed at adult readers — as a general rule of thumb, if your protagonist is a pre-Civil War teenaged farmhand, he should not speak as if he graduated from Dartmouth in 2002. Nor should a narrator who is a 6-year-old girl wield the vocabulary of an English Literature professor.

Oh, you may laugh. Care to guess how many novels like that the average Millicent sees in a year?

Usually, though, the misfit between narrator and voice is not quite so obvious. Often, teenage protagonists are portrayed from an adult’s, or even a parent’s, point of view, creating narrators who are hyper-aware that hormones are causing their mood swings or character behavior apparently motivated (from the reader’s point of view, anyway) solely by age, not individual personality or the ambient conditions. But teenagers, by and large, do not think of themselves as moody, impossible, or even resentful; most of them, when asked, will report that they are just trying to get along in situations where they have responsibilities but few rights and little say over what they do with their time and energy.

Yet screeners are constantly seeing openings where teenage girls practice bulimia simply because they want to fit in, teenage boys act like James Dean in REBEL WITHOUT A CAUSE, teenage characters flounce off to their rooms to sulk — and everyone between the ages of 10 and 19 habitually says, “Whatever,” and rolls his or her eyes on the slightest provocation. Yes, some teenagers do these things, undoubtedly, but in novels, these behaviors have been documented so often that they come across as clichés. Compounding the problem: teenage characters and narrators who diagnose these activities as an adult would are accordingly rife.

That might not bug a 45-year-old professional reader very much, but agency screeners and editorial assistants tend to be really young: many weren’t teenagers all that long ago. Sometimes, they are still young enough to resent having been pigeonholed in their recent youths, and if your manuscript is sitting in front of them, what better opportunity to express that resentment than rejecting it is likely to present itself?

So do be careful, and make sure you are showing Millicent something she doesn’t see twenty times per week. When in doubt, take a long, hard look at your teenage characters and ask yourself, “Is this kid continually emitting martyred signs because of what’s going on, or because of who he is as an individual? Or — and I need to be honest here — is he doing this simply because this is how I think teenagers in general act?”

Those questions are worth acting with any character who happens to be a member of a commonly-stereotyped group (“Are all of the pretty characters in my book dumb, and the homely ones smart?”), but perhaps because so many first-time novelists of books about teens are the parents of same, Millicent tends to be especially sensitive to stereotyping of the young. And I have to say, I’m with her on this one: the best opening with a teenage protagonist I ever saw specifically had the girl snap out of an agony of self-doubt (which could easily have degenerated into cliché) into responsible behavior in the face of a crisis on page 1. To submission-wearied professional eyes, reading a manuscript where the teenaged protagonist had that kind of emotional range was like jumping into a swimming pool on a hot day: most refreshing.

One of the most common ways to tactics up a teenage scene in the past is an opening including quotes from song lyrics. Yes, this can be an effective way to establish a timeframe without coming out and saying, hey, reader, it’s 1982, but it is also very, very overused. I blame this tactic’s use in movies and TV: in the old days, soundtracks used to contain emotionally evocative incidental music, but in recent years, the soundtrack for any movie set in the 20th-century past is a virtual replica of the K-Tel greatest hits of (fill in timeframe), as if no one in any historical period ever listed to anything but top 40.

I’m fairly confident, for instance, that there was no period in American history where dance bands played only the Charleston, where every radio played nothing but American Pie, or every television was tuned to THE ED SULLIVAN SHOW. Yes, even when Elvis or the Beatles appeared on it. Writers are creative people — don’t we owe it to ourselves as a group to mix it up a bit more?

Other than ubiquity, there are other reasons that agents and their screeners tend to frown upon the inclusion of song lyrics in the opening pages of a book. Unless the song is within the public domain — and the last time I checked, Happy Birthday still wasn’t, so we are talking about a long lead time here — the publisher will need to get permission from whoever owns the rights to the song in order to reproduce it.

Translation: song lyrics on page one automatically mean more work for the editor. And possibly expense. Think that will make the book harder or easier for Millicent’s boss to sell?

Also, one of the benefits of setting a sentiment to music is that it is easier to sound profound in song than on the printed page. No disrespect to song stylists, but if you or I penned some of those lines, we would be laughed out of our writers’ groups. For this reason, song lyrics taken out of context and plopped onto the page often fall utterly flat — especially if the screener is too young to have any personal associations with that song.

Yes, that makes me feel rather old sometimes, too.

It is unclear whether the narrator is alive or dead started cropping up on a lot of agents’ pet peeve lists immediately after THE LOVELY BONES came out. Ghostly narrators began wandering into agencies with a frequency unseen since the old TWILIGHT ZONE series was influencing how fantasy was written in North America on a weekly basis. And wouldn’t you know it, the twist in many of these submissions turns out to be that the reader doesn’t learn that the narrator is an unusually chatty corpse until late in the book, or at any rate after the first paragraph of the first page.

Remember what I was saying the other day about Millicent’s not liking to feel tricked by the early pages of a submission in to thinking the story is about something that it isn’t? Well…

I’ll leave you to ponder the possibilities. I’m off to have dinner with a sulky teenager who prattles on about peer pressure, a child who speaks as though she is about to start collecting Social Security any day now, and a fellow who may or may not have kicked the bucket half a decade ago. Honestly, if agents and editors would only recognize that we writers are merely holding, as ’twere, the mirror up to nature, all of our lives would be infinitely easier.

Insert eye roll here. Followed by a nice, long blast on Bozo’s horn, just in case anyone didn’t get that the last suggestion was a joke. Keep up the good work!