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!

Pet peeves on parade, part XI: the many advantages of straying off the beaten path, or, did I drift off again?

I’m a bit drowsy today, campers; blame the lowering skies of a gray Seattle spring day. All I want to do is curl up with a cat or two and a new release by a promising first-time author. I would even feel virtuous doing that, because, let’s face it, if we all want to live in a world that’s open to giving a fresh voice a break, it’s incumbent upon all of us to keep buying debut novels.

Oh, you hadn’t thought about it in those terms? Trust me, agents and editors do. They have to: those books are their bread and butter. And if you hope someday for a book to be your bread and butter, getting into the habit of supporting first- and second-time authors in your chosen book category is the single best way to encourage the agent and editor of your dreams to keep an open mind toward books like yours.

That’s more than enough moral reasoning for a sleepy day, I think. Since I don’t have Millicent’s ever-present too-hot latte in my hand, I’m going to devote today’s post to the kinds of faux pas that tempt her to keep downing them: opening pages that lull her into a deep, refreshing slumber. Or at least a jaw-cracking yawn.

I know, I know — this one couldn’t possibly apply to any of my readers, all of whom are as scintillating as scintillating can be, both on and off paper. Yet strange to report, agents, editors, and their respective screeners routinely report finding many submissions snore-inducing. In fact, slow openings are common enough in submissions that no discussion of notorious pet peeves would be complete without some serious discussion of them.

Thus Millicent’s oft-burnt tongue: she’s just trying to stay awake. Not only due to the dreaded-yet-ubiquitous slow opening — you’d be astonished at how many manuscripts don’t really get going for 4, 5, or 23 pages — but also because once one has been reading submissions or contest entries for a while, the sheer repetition of certain premises begins to…be…

Oh, I’m sorry: did I nod off for a moment?

Frankly, I do not think we writers talk enough amongst ourselves about either of these widespread narrative problems. There’s a awfully good reason for that: since writers commit to spend months or years with a story, we’re usually pretty taken with the story. And nothing renders a section of prose more interesting than agonizing over every word choice, sentence structure, and comma.

So who can blame us if we don’t really notice that nothing much happens on page 1? Or Chapter 1? Or — and this is even harder for a self-editor to catch — if our openings employ similar narrative tricks to hook the reader’s attention and/or stray into plot territory that Millicent has already seen claimed by a few dozen aspiring writers within the last week?

Given how frequently similar tactics and premises crop up in submissions — and how very frequently those of us who read for a living complain about it to one another in private — it’s astonishing how infrequently agents, editors, or even writing coaches bring these problems to aspiring writers’ attention. Perk up your ears the next time you’re at a writers’ conference: when the pros give advice about how to guide manuscripts through the submission process relatively unscathed, the rather sensible admonition don’t bore me is very seldom heard.

Perhaps we can chalk this up to a natural reluctance to admit in a room stocked to the brim with the authors of tomorrow just how little they read of most manuscripts before rejecting them: as those of you who have been hanging around Author! Author! for a while already know, the average submission gets rejected on page 1; one doesn’t hear that mentioned much at conferences, either. And I can easily imagine how an agent might feel a tad sheepish about implying in front of a group of total strangers that he has an attention span that would embarrass most kindergarteners. Or that on certain mornings, the length of time it takes to bore a screener is substantially shorter than others, for reasons entirely beyond the writer’s control.

Hey, they don’t call it the city that never sleeps for nothing, you know. But heaven forfend that an agent should march into an agents’ forum the morning after a long night of the kind of conferring that often happens in the bar that’s never more than a hundred yards from any writers’ conference in North America and say, “Look, I’m going to level with you. If I’m dragging into the office on three hours of sleep, your first page is going to have to be awfully darned exciting for me even to contemplate turning to the second. Do yourself a favor, and send me an eye-opening page 1, will ya? Now where is that conference volunteer with my COFFEE?”

On an entirely unrelated note, had I mentioned to those of you planning to give pitches at upcoming conferences that you might not want the first appointment of the day? Or one of the first several? (You didn’t hear it from me, but at the writers’ conference thrown annually in my neck of the woods, enough conferring goes on that on one memorable occasion, only two of the scheduled dozen or so pitch-hearers showed up for the scheduled morning pitch sessions. If we are to believe the agent who is still complaining about no one having told him that he could have slept in that day.)

Obviously, there’s nothing a writer can do about it if his page 1 — or morning pitch, for that matter — is being judged by someone in desperate need of a gallon of coffee and a B-12 shot, but one can maximize the probability of being the manuscript that makes Millicent’s eyes fly open. One of the best ways of doing this is to avoid having your page 1 read like 4 out of the 16 first pages she has already screened that morning. Or like a third of what she has read in the last week. Even an innocuous writing or formatting problem may begin to annoy a professional reader after she has seen it 700 times.

In response to what half of you just thought very loudly: no, someone who has not had the experience of reading that many first pages probably would not know what those often-repeated problems are. (Although keeping up with new releases in one’s chosen book category would be an excellent means of learning what is and isn’t considered an outdated type of opening.) But yes, the pros honestly do believe that a serious writer would have taken the time to learn her craft well enough to avoid falling into these traps.

Oh, you thought I had devoted so many weeks of posts to common page 1 pet peeves because I liked chatting about them? I’m just trying to give you a peep into what it’s like to hold Millicent’s job.

They also expect, and with greater justification, that a talented writer with a strong premise won’t bore them before the bottom of page 1 — which is not by any means as easy as it sounds. These people see a LOT of plots, after all; if a Millicent is experienced enough to be able to tell from the first reference to a character’s hard childhood that he’s going to turn out to be the perpetrator of those seemingly random murders of everyone who was mean to him as a kid, it’s going to be difficult to keep her interested in the mystery.

And if that reference crops up on page 1 — as happens astonishingly often with plot flares — can you really blame her for muttering, “Well, I’ve seen this before; I want to see something fresh. Next!”

Okay, so maybe you can blame her, if it happens to be your submission over which she is muttering like one of the witches in Macbeth. But you can see why the sight of a genuinely fresh take on a well-worn premise might fill her with gleeful hope, can’t you?

Nor is predictability the only reason she might have the opposite reaction. Over the years, agents and their screeners have been able to come up with many, many reasons that manuscripts bore them, and almost as many euphemisms. Trying to differentiate the various sub-species reminds me of that often-repeated truism about Arctic peoples having many words for different types of snow: to someone not accustomed to observing the variations during the length of a long, long winter, it all kind of looks white and slushy.

But that’s not going to stop me from trying, I notice. Here, for your anxious perusal, are the most common reasons professional reasons give for nodding off over a submission.

Not enough happens on page 1.

Where’s the conflict?

The story is not exciting enough to hold my interest.

The story appears to be boring.

There’s too much repetition on pg. 1 (!)

The narrative takes too many words to tell the reader what happened.

The writing is dull.

Now, to those of us not lucky enough to be reading a hundred submissions a week, that all sounds like snow, doesn’t it? Millicent, however, is in a line of work where she actually does have to come up with concrete criteria to differentiate between not exciting and boring.

Which is to say: all seven of these actually do mean different things, so let me run through them in order, so you may see why each is specifically annoying, even if you weren’t out dancing until 4 a.m. All of them are subjective, of course, so their definitions will vary from reader to reader, but here goes.

Not enough happens on page 1 is often heard in its alternative incarnation, the story took too long to start. On behalf of agency screeners, sleep-deprived and otherwise, all over Manhattan: please, for the sake of their aching heads and bloodshot eyes, get to the action quickly.

And not merely, as so many writing gurus recommend, just any action: toss the reader directly into conflict, by all means, but let that conflict be directly relevant to the story you’re about to tell. Remember, the goal here is to surprise and delight Millicent, after all, not to trick her into thinking that the story that follows is more plot-heavy than it actually is.

That startled some of you out of your late-afternoon doze, didn’t it? “But Anne,” past recipients of open with conflict admonitions point out, rubbing your blurry eyes, “I’ve always heard that the point of a hook is to draw the reader into the story. I’ve literally never heard anyone say that it mattered whether the opening was integrally related to the central conflict of the book.”

Well, I’m saying it now, and for a very good strategic reason. Remember earlier in this series, when I urged you to sit in the chair of that burnt-tongued screener, racing through manuscripts, knowing that she will have to write a summary of any story she recommends?

Think about it for a moment: how affectionate is she likely to feel toward a story that doesn’t give her a solid sense of what the story is about on page 1? Or what kind of novel it is?

You would be astonished — at least, I hope you would — by how many fiction submissions begin with frenetic action that has virtually nothing to do with the plot that follows, or that is wildly out of proportion with the action in the rest of the book. Because so many aspiring writers have heard that they should open their novels with conflict, Millicent’s very, very used to first pages that splatter the reader with blood or appall her with explicit violence. That alone won’t necessarily grab her.

Violence isn’t the only kind of conflict, after all. Nor is argument. Like so many other one-line pieces of writing advice, open with conflict is widely misinterpreted to mean a novel must open with a life-threatening (or life-ending) scene. While that may well work in a thriller, in most fiction book categories, it would be inappropriate.

So what kind of conflict do the pros have in mind when they spout this aphorism? Conflict between the protagonist and other characters, usually, or between the protagonist and a situation. A scene where the main characters disagree about how to solve the central problem of the plot. A disagreement between lovers. A winsome child abruptly noticing that her beloved cocker spaniel is missing.

Or, yes, a rural policeman stumbling upon some body parts, if that is genre-appropriate. Just make sure to pick a scene that is representative of both the story you’re telling and the prevailing tone of your book category.

If you aren’t sure about the latter, I have to ask: have you been reading enough recent releases of first- and second-time authors in your book category? (You didn’t think I’d tumbled off that high horse, did you?)

While you are conducting that little piece of self-examination, let’s move on to the next objection on our list, where’s the conflict? This cri de coeur gained considerable currency in the 1990s, when writing gurus began touting using the old screenwriter’s trick of utilizing a Jungian heroic journey to structure the story arc of a novel. Within that journey, the protagonist starts out in the real world, not to get a significant challenge until the end of Act I, many novels put the conflict on hold, so to speak, until the first call comes. (If you’re really interested in learning more about the hero’s journey structure, let me know, and I’ll do a post on it. But there are a LOT of writing advice books out there that will tell you this is the only way to structure a story. Basically, all you need to know for the sake of my argument here is that this ubiquitous advice has resulted in all of us seeing many, many movies where the character learns an important life lesson on page 72 of the script.)

While this can be an effective way to structure a book, there’s no denying that tends to reduce conflict in the opening chapter. I find this phenomenon fascinating, because most people’s everyday lives are simply loaded of conflict.

Oh, you’ve never had a coworker who got on your nerves?

Even if you want to start out in the normal, everyday world before your protagonist is sucked up into a spaceship to the planet Targ, make an effort to keep that hung-over screener awake: ramp up the interpersonal conflict on page 1. Even if that conflict needs to be purely internal: Arnold cringed at the sound of plastic slapping into metal. Would Bruce never learn to treat the coffeemaker with respect? is, after all, as fraught with tension as Arnold stirred his coffee absently, unaware that Bruce had snuck up behind him, a filter full of steaming used grounds in his hand. They’re merely introducing different kinds of narratives.

Perhaps the best way to figure out how much and what kind of conflict is most appropriate to open your novel is to think about why writing teachers came up with the open with conflict aphorism in the first place: the many, many manuscripts that begin in a mundane present, introducing the protagonist and her environment before the central conflict of the book arrives to trouble her life. Millicent can’t even begin to count the number of page 1s she’s seen within the last month that began with something like this:

Arianna gazed out upon the blue-purple twilight, clutching her ever-present cup of tea. Peaceful tonight on Skullcracker Island, the perfect invitation to curl up by the fire with a good book. Spot rubbed purringly against her legs.

She bent to rub the furry orange head of her most recent shelter find. For a cat the vet had said was suffering heavily from post-traumatic stress disorder, the one-eared beast had certainly become affectionate quickly. “Don’t worry, Spot,” she crooned. “There will be a nice, warm lap for you soon.”

Zzzz…oh, did I miss something?

There’s nothing wrong with this as writing (although rubbed purringly might strike Millicent as rather purplish prose). In fact, it might work very well in the middle of the novel (if for some reason it were necessary to impress the reader with a great deal of information about that cat within a startlingly short stretch of text, and by telling, rather than showing).

But come on, admit it — even if the next line were

The axe severed her hand before the cat had finished rubbing against it.

you might have stopped reading before you got to it, mightn’t you? So would Millicent, in all probability. As a general rule of thumb (severed or not), if the first paragraph of a manuscript does not contain either conflict appropriate to the book’s category or a strong, nicely-described image, it may strike a professional reader as opening too slowly.

That got some goats out there, didn’t it? “But Anne,” openers-with-conflict protest in injured tones, “I’ve always heard that I had to work conflict onto the first page, not into the first paragraph. Consequently, I’ve been making sure that my submissions feature a startling last line on the bottom of the first page, to tempt Millicent to turn to page 2. Are you telling me that she might not have been reading that far, since my first three paragraphs depict my protagonist chatting with her mother on the phone about nothing in particular?”

In a word, yes. And in several words: what on earth made you think that chatting about nothing in particular — your words, not mine — constituted opening with action?

Or, to answer your question on a more practical level: do you really want to make Millicent wait until the bottom of the page before depicting any relevant conflict? When she might not yet have had her morning latte? Or have slept more than a couple of hours last night?

The next two rejection reasons on our list — the story is not exciting enough to hold my interest and the story appears to be boring, respectively — are fairly self-explanatory on their faces, but usually refer to different types of text. A not exciting story is one where the characters are well-drawn and the situation is interesting, but either the stakes are not high enough for the characters or — wait for it — the pace moves too slowly.

On the bright side, having your story called not exciting by an agent is reason to be hopeful: if you tightened it up and made the characters care more about what was going on, it could be compelling reading. A boring story, on the other hand, is devoid of any elements that might hold a droopy screener’s interest for more than a paragraph or two.

Again, I doubt any of my readers produce boring stories, but it’s always worthwhile to run your submission under an impartial first reader’s eyes, just to make sure. The same diagnostic tool can work wonders for a not-exciting opening, too: there’s no better tonic for a low-energy opening than being run by a particularly snappish critique group.

Perhaps one that hasn’t had its morning latte yet, either. You might want to try scheduling your next meeting at 5 a.m.

The final three — too much repetition on pg. 1, taking too many words to tell the reader what happened, and the writing is dull — also respond well to input from a good first reader, writing group, or freelance editor. As we have discussed earlier in this series, agents have good reason to avoid redundant manuscripts: editors are specifically trained to regard repetition as a species of minor plague, to be stamped out like vermin with all possible speed.

Ditto with excess verbiage and lackluster writing: publishing houses issue those people blue pencils for a reason, and they aren’t afraid to use them.

The best way to determine whether your submission has any of these problems is — please chant it with me now — to read your opening page IN ITS ENTIRETY, IN HARD COPY, and OUT LOUD. If the page]s vocabulary isn’t broad enough, or if it contains sentences of Dickensian length, believe me, it will be far more evident out loud than on the printed page. Or on your computer screen.

I’m afraid that you’ll have to trust me on this one. I would give you some concrete examples, but I feel a well-deserved nap coming on. Keep up the good work!

Pet peeves on parade, part VII: why Millicent prefers casting calls to be open

It never fails, campers: every time I start talking here on the blog about Hollywood narration — when one character tells another something that both already know perfectly well, purely for the sake of conveying those facts to the reader– the world around me hastens, nay, lunges to provide me with an abundance of examples. Indeed, one can hardly turn on a television set without encountering backstory being conveyed via dialogue between persons who both already know the information perfectly well, and thus have absolutely no legitimate reason to be having that particular conversation at all.

Nurse (catching up to Orderly in an antiseptic hallway): So how is Naomi doing today?

Naomi (seated sideways in wheelchair, limbs akimbo, face covered in bruises): Unnngh.

Orderly (clutching the handles of Naomi’s wheelchair passionately): “How should she be doing, Clara? What she needs is physical therapy and minute-to-minute care, but Dr. Barton treats her like a…thing. He doesn’t believe she will ever get better.

Nurse: Now, now, you know that Dr. Barton has a fine reputation. He’s been running Seacoastcliffwaterview Convalescent Hospital for seven and a half years now.

Orderly (lowering his voice): But what about those mysterious deaths in the wee hours of the morning, when, unlike most medical facilities that purport to give round-the-clock care, all of us on staff steal off to take four-hour naps?

Nurse (shaking her head thoughtfully): That is a mystery. But no good is going to come of asking disruptive questions.

Our hero (flashing identification from some city/county/federal agency too quickly for any human eye to glean any information whatsoever from it): Excuse me, but I’m trying to learn something about Mr. McGuffin’s death at two o’clock yesterday morning. Has anything unusual been going on here lately?

Nurse (exchanging meaningful glances with Orderly): No, nothing.

Naomi: Unnngh. Unnngh!

Orderly (patting her on her shoulder): There, there. I’d better get you back to your room for your 1:30 AM appointment with Dr. Barton. I just hope you’re going to last the night, honey.

Doesn’t exactly hide the goods, does it? Like much Hollywood narration, this sterling little exchange contains backstory that the reader (or, in this case, viewer) might legitimately need to know, but presented this ungracefully, Naomi might as well have been holding a blinking neon sign in her lap that read PAY ATTENTION — THIS WILL BE IMPORTANT TO THE PLOT.

Think about it — why else would the author bother to include such an improbable exchange unless it were going to be vital for the viewer (or reader) to remember later on? Like the otherwise unmotivated close-up in a movie (“Wait, I recognize the murderer now — the camera paused on his face for no apparent reason half an hour ago!), Hollywood narration is seldom subtle. It’s merely a shortcut for the writer.

It’s just so darned convenient, isn’t it? But as we saw above, it’s also conducive to another guaranteed professional reader-annoyer, a little something I like to call a plot flare: a line of text that warns the reader — sometimes in a subtle manner, sometimes by tossing a brick through the nearest window — about a plot twist to come.

The socially inept stepdaughter of foreshadowing, the plot flare believes it is being clever and unobtrusive, but usually, it’s anything but. It can pop up in the form of a coy clue, but it can also be as simple as an over-reaction to that old writing truism, never have a character vital to the book’s climax appear later than one-third of the way through the story:

Fiorello rushed into the thick of the dancing crowd, searching frantically for his baby sister. Bombarded by writhing bodies on all sides, he tried not to grope anyone as he pushed them out of his way.

He failed, apparently, vis-à-vis a punked-out blonde. “Hey,” she snarled, brandishing her spiked bracelet at him, “those belong to me.”

Fiorello blushed all the way from his receding hairline to his button-down collar. “Oh, I’m so sorry, Miss…Miss…”

“The name’s Allegra.” She flashed him a crooked smile. “Wanna dance?”

Was that Bitsy pogoing near the bandstand? “Oh, excuse me. I have to go.”

“Come find me sometime,” Allegra called after him, “when you’re in less of a hurry.”

Hands up, anyone who would be surprised when Allegra turns up in a coffee shop three scenes hence. Or 150 pages from now. Or if she — who could have seen this coming? — turns out to have a heart of gold that belies her tough exterior.

Believe it or not, this is actually rather subtle for your garden-variety plot flare. Most of the time, Millicent the agency screener finds herself gasping with annoyance over clues so broad that they seem to insult the reader’s intelligence. A popular choice: recounting what is about to happen under cover of a planning session.

Kirk mopped his manly but weary brow. “Here’s how it’s going to happen, everybody. Fifi, you keep the engine running outside the bank. George, you walk in wearing the Bugs Bunny mask. Arnold, you start juggling the flaming torches. While everyone is watching you, I’ll slip around behind the tellers, crack open the vault, and steal the million dollars. Then we’ll all meet back at the car. Any questions?”

Fifi raised a timid hand. “If it’s really that simple, why should anyone continue reading?”

“Ah, but we all know that any story focused on a heist won’t go exactly as planned.” Kirk tapped on his wrist. “Who lifted my watch? We need to synchronize them.”

Okay, so character aren’t always so obvious that they forget to pretend that they are not characters in a novel, but with common plotlines, they might as well be. If the path through the story is so well lit with plot flares that Millicent can tell the basic contours of the plot by page 6, she doesn’t have a lot of incentive to keep reading.

So here’s a radical notion: why not introduce some of that backstory later in the book, rather than within the first 5 pages?

Most novels and memoirs front-load their opening scenes with information about their characters’ pasts, and with good reason: that is how the writers think of these characters. But if the initial conflict is exciting enough, why slow it down with details that aren’t actually relevant to the situation at hand?

You want to see concrete examples, don’t you? Here is a fairly typical front-loaded opening, complete with standard-issue Hollywood narration:

Exhausted from working a fifteen-hour day at the non-union coal mine, Almanzo stopped at the neighborhood bar before returning to his long-suffering wife of four years, Jenny. He peeled the work coat from his strong, wiry frame, shedding black dust everywhere.

“The usual?” Joe the bartender asked.

Almanzo grinned, white teeth contrasting oddly with powder-dark skin. “Isn’t that the definition of usual? Boy, I’ve had a terrible day half a mile below the earth’s crust. Those old-fashioned rope-pulled carts are bound to break and crush somebody someday.”

Joe chuckled, pouring neat cognac into the snifter he always kept warm for Al at the end of the day. “Don’t be silly. Those ropes have been holding steady for a hundred years now.”

Almanzo sipped the potent brew. “Gee, I hope you’re right. Now that the safety inspectors have all been laid low by that mysterious flu, I don’t know how many miners would be killed if there were an accident.”

Harboring any doubts about what’s going to happen in the pages to come? Neither is Millicent.

So why give her and other readers the heads-up? Wouldn’t it be more exciting to begin slightly later in the story, saving the background for later on? In a manner, say, rather like this?

Rope stretched beyond its capacity makes a sound like a giant, stressed-out violin: a mammoth twang of frustration. Almanzo felt it reverberate down the mineshaft even before he heard the sound. He scrabbled his way halfway to side tunnel before it occurred to him to warn the men down the line.

“Runaway cart!” he shouted, but the creak of wheels drowned him out.

More of a grabber, isn’t it? You’d be surprised at how many manuscripts contain both the slow, backstory-laden opening and the conflict-focused one, usually in that order. Aspiring writers often seem reluctant to jump into the story. Unfortunately, if plot flares have already tipped Millicent off about the trajectory of the plot, she’s not likely to keep reading as far as that interesting action scene.

I’m bringing this up not merely to alert you to the plot flare phenomenon — trust me, once you start looking for them, you’ll spot them everywhere — but also as a revision tip for the unhappy many seeking to trim pages from their manuscripts. You might want to take a long, hard look at your opening pages and ask yourself: does the story begin on page 1, or are the opening pages devoted to backstory? If it’s the latter, what would happen if I cut the lead-in and just tossed the reader right into the central conflict of the book?

You might also want to take a quick peek at all of the dialogue scenes in the book. Because Hollywood narration is about backstory, rather than the scene going on in the moment, it can usually be excised with no ill effect whatsoever on the scene.

I sense some raised hands out there. “But Anne, that seems counterintuitive. A paragraph or two of Hollywood narration can replace pages and pages of backstory. So won’t I end up with a longer text if I cut the summary statements out of the dialogue?”

Not necessarily — often, that information isn’t actually vital to the story. Oh, it may be essential to understanding the character to know that she has three children, two ex-husbands and a current one, as well as an English sheepdog, but since there are probably scenes in the book that feature at least a few of those players and relationships, why stop the early pages of the book cold in order to introduce the information?

For most aspiring writers, the answer to that last question is pretty straightforward: because we’ve all seen both plot flares and Hollywood narration used so often in TV shows and movies that it seems like normal storytelling. The latter is one of the standard ways that screenplays introduce background information, after all, and plot flares are almost as common. (Oh, does anyone out there hear, “I would be lost without you, Muffy,” spoken by the protagonist in the first third of a film and not spend the next hour awaiting Muffy’s unfortunate encounter with a speeding bus?) Because we’ve all seen and heard it done so much, many aspiring writers think it’s perfectly okay, if not downright clever, to fill in backstory and foreshadow in these frankly pretty clumsy manners.

The inevitable result: Millicent spends day after over-caffeinated day leafing through hundreds and thousands of pages of Hollywood dialogue. Embracing it as a narrative tactic, then, is not the best means of convincing her that your writing is fresh and original.

The problem is, it’s not always a tactic. Precisely because this kind of dialogue flies at all of us from the screen every day, it’s easy to mistake for the patterns of actual speech — until, of course, a writer sits down with it and says, “All right, what is this character’s motivation for telling his long-lost aunt about his graffiti spree in 1943? Wouldn’t she already be aware that his father, her brother, was a wayward youth?”

That, in case you were wondering, is the single best way to weed out Hollywood narration from a manuscript: reading every line of dialogue OUT LOUD to see if it’s plausible. Ideally, a writer would also — wait for it — perform this reading IN HARD COPY and on the manuscript IN ITS ENTIRETY before submitting it to an agent, editor, or contest.

Oh, you thought I was going to give that advice a rest?

Why read it out loud? Well, in part, to see if speeches can be said within a single breath; in real life, dialogue tends to be possible to speak aloud. If you find yourself gasping for breath mid-paragraph, you might want to re-examine that speech to see if it rings true, or if part of it should be cut. Also, reading dialogue out loud is the easiest way to catch if more than one character is speaking in the same cadence — which, contrary to what the dramatic works of David Mamet and Aaron Sorkin may have lead you to believe, is not how people speak on the street.

Or anywhere else, for that matter. Individual people have been known to have individual speech patterns.

There’s one other excellent reason to hear your own voice speaking the lines you have written for your characters: in this celebrity-permeated culture, many writers mentally cast actors they’ve seen on television or in movies as the major characters in their novels. By saying the dialogue (or first-person narration) in your voice, rather than your favorite actor’s, you’re more likely to catch awkwardness.

C’mon, ‘fess up: practically every aspiring writer does a little mental casting. In some ways, it’s a healthy instinct: by trying to imagine how a specific actor might sound saying a specific set of words, and how another specific actor might respond, a writer is less likely to allow the two characters speak in the same rhythms.

Unless, of course, the writer happens to cast multiple actors best associated for portraying the characters of Aaron Sorkin or David Mamet.

This practice has an unintended consequence, however: due to the pernicious ubiquity of Hollywood narration in screenplays, we’re all used to hearing actors glibly telling one another things that their characters already know. So imagining established actors speaking your dialogue may well make passages of Hollywood narration sound just fine in the mind.

Mentally casting a familiar celebrity voice as your protagonist’s can also render it more difficult to tell when a joke is or isn’t funny — and render it nearly impossible to ferret out what the pros bad laughter, a giggle that the author did not intend for the reader to enjoy. You can tell that a laugh is a bad one when the reader (or audience member; it’s originally a moviemaker’s term) is knocked out of the story by a glaring narrative problem: an obvious anachronism in a historical piece, for instance, or a too-hackneyed stereotype, continuity problem, or unbelievable plot twist.

Or — wait for it — a line of dialogue that no real person placed in a similar position to the character speaking it would actually say.

It’s the kind of chuckle an audience member, reader, or — heaven forfend! — Millicent gives when an unintentionally out-of-place line of dialogue or event shatters the willing suspension of disbelief, yanking the observer out of the story and back into real life. You know, the place where one uses one’s critical faculties to evaluate probability, rather than the desire to be entertained.

Hollywood narration is notorious for provoking bad laughter. By this late date in storytelling history, the talkative villain, the super-informative coworker, and the married couple who congratulate themselves on their collective history have appeared so often that even if what they’re saying isn’t a cliché, the convention of having them say it is.

Take it from a familiar narrator-disguised-as-onlooker: “But wait! Up in the sky! Is it a bird? Is it a plane? No, it’s Superman!” Sheer repetition has made that one sound like plausible speech, hasn’t it?

To resurrect one of my all-time favorite examples of Hollywood narration’s power to jar a reader or audience member into a shout of bad laughter, a couple of years ago, I was dragged kicking and screaming to a midnight showing of a Korean horror film, Epitaph, in which a good 10 out of the first 20 minutes of the film consisted of characters telling one another things they already knew. Much of the remaining screen time consisted of silent shots of sheets blowing symbolically in the wind — in a ghost story; get it? — and characters standing frozen in front of doors and windows that they SHOULD NOT OPEN UNDER ANY CIRCUMSTANCES.

Because that theory has never been tested cinematically before.

For the benefit of those of you who have never seen a horror film, should you ever find yourself in a haunted hospital, don’t touch anything with a latch and/or a doorknob. Especially if you happen to be standing in front of the body storage wall in the morgue. And don’t under any circumstances have truck with your dead mother; it will only end in tears.

Trust me on this one.

Now, I would be the first to admit that horror is not really my mug of java — I spent fully a quarter of the film with my eyes closed and ears blocked — so I did not see every syllable of the subtitles. But my braver film-going companions and I were not the only ones giggling audibly during the extensive backstory-by-dialogue marathons. An actual sample:

Grown daughter: Dad, are you lonesome?

Doctor-who-interned-in-haunted-hospital: (chuckling ruefully) No, of course not.

Grown daughter: You’re too hard on yourself, Dad. Stepmother had a heart condition long before you married her.

Doctor-who-interned-in-haunted-hospital: But we were married for less than a year!

Grown daughter: You can’t blame yourself. Mother died in having me, and Stepmother had been sick for a long time. It’s not your fault. It’s nothing you did.

Doctor-who-interned-in-haunted-hospital: (clearly weighed down by Ominous Guilt) Both marriages lasted less than a year.

I’m sure that you can see the narrative problem — can you imagine a more blatant telling, rather than showing, presentation? — but the laughter from the audience was a dead giveaway that this dialogue wasn’t realistic. Bad laughter is a sure sign that the audience has been pulled out of the story.

Too addled with a surfeit of Hollywood narration to sleep — and, frankly, not overly eager to dream about a maniacally-laughing, high C-singing dead mother standing by her small, terrified daughter’s hospital bed in a ward where there were NO OTHER PATIENTS — I ran home, buried myself under the covers, and reached for the nearest book to soothe my mind and distract my thoughts from the maniacally-laughing, high C-singing dead woman who was probably lurking in my closet. As luck would have it, the volume in question was a set of Louisa May Alcott’s thrillers; I had used it as an example on this very blog not long before. Yet no sooner had I opened it when my eye fell upon this sterling opening to a story promisingly titled “The Mysterious Key and What It Opened.”

Because I love you people, I have excised the scant narration of the original, so you may see the dialogue shine forth in untrammeled splendor.

“This is the third time I’ve found you poring over that old rhyme. What is the charm, Richard? Not its poetry, I fancy.”

“My love, that book is a history of our family for centuries, and that old prophecy has never yet been fulfilled…I am the last Trevlyn, and as the time draws near when my child shall be born, I naturally think of the future, and hope he will enjoy his heritage in peace.”

“God grant it!” softly echoed Lady Trevlyn, adding, with a look askance at the old book, “I read that history once, and fancied it must be a romance, such dreadful things are recorded in it. Is it all true, Richard?”

“Yes, dear. I wish it was not. Ours has been a wild, unhappy race till the last generation or two. The stormy nature came in with the old Sir Ralph, the fierce Norman knight, who killed his only sun in a fit of wrath, by a glow with his steel gauntlet, because the boy’s strong will would not yield to his.”

“Yes, I remember, and his daughter Clotilde held the castle during a siege, and married her cousin, Count Hugo. ‘Tis a warlike race, and I like it in spite of the mad deeds.”

“Married her cousin! That has been the bane of our family in times past. Being too proud to mate elsewhere, we have kept to ourselves till idiots and lunatics began to appear. My father was the first who broke the law among us, and I followed his example: choosing the freshest, sturdiest flower I could find to transplant into our exhausted soil.”

“I hope it will do you honor by blossoming bravely. I never forget that you took me from a very humble home, and have made me the happiest wife in England.”

“And I never forget that you, a girl of eighteen, consented to leave your hills and come to cheer the long-deserted house of an old man like me,” her husband returned fondly.

“Nay, don’t call yourself old, Richard; you are only forty-five, the boldest, handsomest man in Warwickshire. But lately you look worried; what is it? Tell me, and let me advise or comfort you.”

“It is nothing, Alice, except my natural anxiety for you…”

By this point, tangling with the maniacally-laughing, operatic dead harpy was beginning to look significantly better to me. Clearly, the universe was nudging me to set forth again like the Ghosts of Christmas Past, Present, and Future to warn writers to alter their sinful ways before it was too late.

But if I had the resources to commission Gregory Peck and Sarah Bernhardt to read those very lines to you (or the efficient séance facilities), I think it’s a fairly safe bet that they wouldn’t have struck you as so clearly contrived. It’s actors’ job to make speeches seem plausible, after all, and they have, bless their respective hearts and muses, given us all abundant reason to expect them to be very, very good at it.

So are theirs really the best voices to employ in your head to read your dialogue back to you?

And even if they were, Hollywood narration is not especially plausible. Generally speaking, real people do not recite their basic background information to kith and kin that they see on a daily basis. Unless someone is having serious memory problems, it is culturally accepted that when a person repeats his own anecdotes, people around him will stop him before he finishes.

Because, among other things, it’s BORING.

Yet time and again in print, writers depict characters wandering around, spouting their own résumés without any social repercussions. Not to mention listing one another’s physical and mental attributes, informing each other of their respective ages and marital histories, listing the articles of furniture in the room, placing themselves on a map of the world, and all of the other descriptive delights we saw above.

So yes, you’re going to find examples in print occasionally; as we may see from Aunt Louisa’s example, authors have been using characters as mouthpieces for backstory for an awfully long time.

Novel and memoir openings are more likely to contain Hollywood narration than any other point in a book, because of the writer’s perceived imperative to provide all necessary backstory — and usually physical description of the main characters and environment as well — the nanosecond that the story begins. Here again, we see the influence of film upon writing norms: since film is a visual medium, we audience members have grown accustomed to learning precisely what a character looks like within seconds of his first appearance.

We’ve all grown accustomed to this storytelling convention, right? Yet in a manuscript, there’s seldom a good narrative reason to provide all of this information to the reader right off the bat.

Listen: TV and movies are technically constrained media; they rely upon only the senses of sight and sound to tell their stories. While a novelist can call upon scents, tastes, or physical sensations to evoke memories and reactions in her characters as well, a screenwriter can only use visual and auditory cues. A radio writer is even more limited, because all of the information has to be conveyed through sound.

So writers for film, TV, and radio have a pretty good excuse for utilizing Hollywood narration, right? Whatever they cannot show, they must perforce have a character (or a voice-over) tell. How many times, for instance, have you spent the first twenty minutes of a film either listening to voice-over narration setting up the premise (do I hear a cheer for the otherwise excellent THE ROYAL TENENBAUMS, where an unseen but undoubtedly huge and Godlike Alec Baldwin told us all we needed to know? Anybody?) or listening to the protagonist fill in the nearest total stranger on his background and goals?

Again, in film, it’s an accepted convention; movies have trained their audiences to continue to suspend their disbelief in the face of, among other things, giant-voiced Alec Baldwins in the Sky. It’s shorthand, a quick way to skip over action that might not be all that interesting to see played out. See for yourself:

Pretty neighbor (noticing the fact that our hero is toting several boxes clearly marked ACME MOVING AND STORAGE): “Why, hello there. Are you just moving into the building?”

Hunky hero (leaning against the nearest doorjamb, which happens to be beautifully lit, as doorjambs so frequently are): “Yeah, I just drove in from Tulsa today. This is my first time living in New York, New York. When my girlfriend left me two weeks ago, I just tossed everything I owned into the car and drove as far as I could.”

Pretty neighbor (edging her way into his good lighting: “Well, I’m a New York native. Maybe I could show you around town.”

Hunky hero: “Well, since you’re the first kind face I’ve seen here, let me take you to dinner. I haven’t eaten anything but truck stop food in days.”

Now, this economical (if trite) little exchange conveyed a heck of a lot of information, didn’t it? It established that both Hunky and Pretty live in the same building in New York, that he is from the Midwest and she from the aforementioned big city (setting up an automatic source of conflict in ideas of how life should be lived, if they should get romantically involved), that he has a car (not a foregone conclusion in NYC), that they are attracted to each other, and that he, at least, is romantically available.

What will happen? Oh, WHAT will happen?

When the scene is actually filmed, call me psychic, but I suspect that this chunk of dialogue will be accompanied by visual clues to establish that these two people are rather attractive as well. Their clothing, hairstyles, and accents will give hints as to their respective professions, upbringings, socioeconomic status, and educational attainments.

Writers of books, having been steeped for so many years in the TV/movie/radio culture, sometimes come to believe that such terse conveyance of information is nifty — especially the part where the audience learns everything relevant about the couple within the first couple of minutes of the story. They wish to emulate it, and where restraint is used, delivering information through dialogue is a legitimate technique.

The problem is, on film, it often isn’t used with restraint — and writers of books have caught that, too. It drives the Millicents of the world nuts, because she, I assure you, will not automatically cast Sir Lawrence Olivier as your protagonist — or voiceover artist — in her mind. So if your narrative was relying upon tone and/or delivery to make the dialogue or first-person narration funny, poignant, surprising, or anything else, you’re going to run into difficulties at submission time.

Chant it with me now, campers: a professional reader can only judge a submission by what’s on the page. Don’t expect her to guess what your casting preferences are. Oh, and keep up the good work!

Pet peeves on parade, part VI: seriously, dialogue was the only way to convey this information to the reader?

I begin today’s foray into the niggling little manuscript problems that drive Millicent the agency screener daily another few steps toward cynicism about artistic production with an anecdote. Back when I was in graduate school, I used to spend my summers working at a local hospital, writing patient education literature. When I wasn’t busy figuring out how to explain an MRI in a fourth-grade vocabulary, I was entrusted with guarding the office’s thermostat from the four menopausal women who kept yanking the controls from Antarctica to the Gobi Desert, as the day’s hot flash schedules dictated. No sooner would one sneak over to crank it down than another would appear to spin the dial upwards again. Not once did more than two of them manage to have the same temperature demands at the same time, so working in this environment comfortably required keeping both a tank top and a ski sweater in my desk, in order to avoid perishing from exposure.

So when Marni the medical coder came charging toward my desk one Friday, I instinctively dove toward the thermostat. She had more than the local weather on her mind, however. “Do you happen to have any rubber bands that will fit around this?” She held up pile of papers seven inches thick. “You know, just lying around.”

Since the supply cabinet stocker favored taunting the office staff with rubber bands apparently designed by orthodontists to tug braces a millimeter in this direction or that, industrial-sized rubber bands were not the kind of thing we happened to have lying around. “No, but I’m sure we could order some.”

Marni sighed and reached for the thermostat. “Never mind.”

I was baking in the tropical humidity the following Friday when she repeated the request, this time brandishing a nine-inch stack of papers. “I don’t think I have ever personally handled a rubber band that would encircle that,” I told her. “But since you seem to need large bands on a regular basis, why don’t you pick up a package at a stationary store, and have the hospital reimburse you?”

“No, no,” Marni said, slinking back into the undergrowth where tigers and cobras lay panting in the heat. “I just thought you might have some.”

By midsummer, I had arranged so many office supply catalogs along the path between Marni’s desk and the thermostat that visitors mistook them for seating. Yet still, every Friday, she would reappear to ask for rubber bands, teeth chattering or wiping the sweat from her brow, as the day’s temperature battle dictated.

“Marni,” I was begging by the end of the summer. “Why do you keep doing this to yourself? If you need the darned things, just get some!”

“Oh, no.” She tossed me a sad, disappointed smile. “I don’t really need them. I just thought you might have some around.”

From a character-development point of view, it’s easy to dismiss this as passive-aggressive behavior, right? Marni wanted the rubber bands, but was not brave enough to ask her boss for them; if she asked me often enough, I might break down and ask the fearsome Madge for her. Or I might have become so frustrated that I would invest some of my own cash in behemoth bands. Unfortunately for either of these plans, I always headed back to school in September.

I’m bringing this up not merely as an a example of how to work tension into an otherwise pretty mundane situation — hey, it allowed me to bring up at least two more temperature changes than I could have gotten away with otherwise — but because many, many aspiring writers employ Marni’s logic, if not her methodology. They want an agent to offer them representation, so they regularly send out queries and, when those queries are successful, submissions.

When those queries or submissions get rejected, these writers, like all writers, are sad and disappointed. But is their response to learn a bit more about the publishing industry, to find out if there is a standard format for submissions (there is), if there is an upper length limit that tends to trigger knee-jerk rejection (there is, but it varies slightly by book category), or if agency screeners are trained (and they are) to reject manuscripts that run afoul of certain common agents’ pet peeves?

Oh, I know that your response would be to invest the time in learning about these matters. But not all aspiring writers are as industry-savvy as you: like Marni, they keep doing the same thing over and over, yet expecting the outcome to be different next time.

I realize that it’s frustrating that agencies now only rarely give concrete reasons for rejecting a manuscript — and virtually never justify rejecting a query. Form letters with generalities are the most common response, if indeed an agent chooses to respond at all. There’s nothing an aspiring writer can do to change that.

He can, however, stop expecting that the rubber bands he wants will magically appear, simply because he wants them so much. He can plan ahead so Millicent will have fewer reasons to reject his next submission than did her counterpart at the last agency to which he submitted. He can change his behavior to increase the probability of the outcome he wants.

On a not entirely unrelated note, in my last post, I brought up how frustrating many professional readers find it when a narrative forces them to follow a poor interviewer through an information-seeking process that seems one-sided or lacking in conflict. Or when — heaven forbid — the answers just seem to fall into the protagonist’s lap without significant effort on her part, exactly as if someone had planned for her to happen onto precisely the clues she needed to solve the book’s central puzzle.

What a happy coincidence, eh? And just in time to wrap up the mystery by the end of the book. Perhaps if she waits long enough, flying monkey will drop a carton of extra-large rubber bands at her dainty feet, too.

This marvelous atmosphere for coincidence is not only indigenous to the end of a plot, either. Ineffectual interview scenes are often employed to slow down a plot, creating false suspense. If the protagonist is too lazy, too distracted, or just too dimwitted to ferret out the truth early in the book, it’s substantially easier to keep the reader in the dark about salient details of the variety that might, if revealed, cause a reasonably intelligent reader to figure out whodunit by the end of Chapter 2.

A protagonist who is bad at asking questions — and his creative Siamese twin, the antagonist or supporting character who is suspiciously eager to cough up information — are also frequently used as means to speed up a narrative by shoehorning necessary information into the plot. It’s a classic tell, don’t show strategy, good for heaping backstory into the book, but typically, low on conflict, believability, and character development.

How might that annoy Millicent on the page? Observe, please, the lethal combination of a passive interviewer and a too-active interviewee compresses what could have been a relatively lengthy but conflict-filled interrogation scene into a few short exchanges:

interview bad

“Wait a second,” Millicent mutters upon encountering a scene like this. “Who is interviewing whom here? And what are all of those rubber bands doing in my desk?”

Well might she ask. This kind of inverse interview, as well as plot giveaways every bit this broad, turn up in manuscript submissions and contest entries all the time. These techniques may well be the quickest way to tell a story, but they make it pretty easy to see the wheels turning in the authorial mind. That’s not a complex plot — that’s a straight line.

None of these quite legitimate complaints would necessarily be Millicent’s primary objection to the scene above, however. Any guesses? Hint: it’s one of her perennial pet peeves.

Oh, wait, that doesn’t narrow it down very much, does it?

Give yourself a pat on the back if you instantly cried, “This kind of implausible exchange pulls the reader out of the story!” Even though a reader would have to be pretty obtuse indeed (or very into the postmodern conceptual denial of individual authorship) not to realize that any protagonist’s adventures have in fact been orchestrated by a writer, a too-obvious Hand of the Creator can yank the reader out of the story faster than you can say, “Sistine Chapel ceiling.”

To work on the printed page, fate has to move in slightly more mysterious ways. Or at least in more interesting ones.

Was that wind that just blew my cat from one side of my studio to the other the collective irritated sigh of those of you who have been laboring to revise Frankenstein manuscripts? “Oh, fabulous, Anne,” the bleary-eyed many whimper, wearily reaching for their trusty highlighter pens. “Now I not only have to scrub my manuscript until it gleams at the sentence level, but I also have to make sure all of my interview scenes are both plausible AND contain surprising plot twists? When do you expect me to be ready to submit this baby, 2018?”

Well, yes and no. No, I don’t expect you to spend years polishing your manuscript — unless, of course, it needs it — and yes, I do expect your work to abound in gleaming sentences, believable, conflict-ridden interview scenes, and twists I couldn’t see coming. So, incidentally, does Millicent.

That expectation, incidentally, serves her well in winnowing down any given day’s stack of submissions, because interview scenes are legendary in the biz for drooping, even in an otherwise tight manuscript. Especially toward the middle and the end of a book, where protagonists — or is it their creator? — often become a tad tired of searching for the truth.

At that point, crucial clues hidden for years like Ali Baba’s treasure frequently start leaping out of the woodwork, screaming, “Here I am, right under this neon sign — discover me, already! ”

Since almost every book-length plot involves some element of detective work, however minor, it’s worth triple-checking ALL of your manuscript’s interviews for flow, excitement, and plausibility. In fact, I would recommend making those interview scenes your first stops for tightening (or, less commonly, slackening) the pace of your narrative. Besides presenting a pacing problem, clues that seem too anxious to fling themselves in a protagonist’s way, feigning casualness when they are discovered littering the path, can actually render said protagonist less likable to readers.

Why? I refer you back to our question-averse reporter above. Just as it doesn’t make a character seem like a stellar interviewer if he just strolls into a room at the precise psychological moment that the taciturn miner who’s kept his peace for 57 years abruptly feels the need to unburden himself to the nearest total stranger, it doesn’t make a protagonist seem particularly smart if he happens upon a necessary puzzle piece without working to find it.

And the protagonist is not the only one who runs the risk of coming across as a trifle dim-witted: a mystery or conflict that’s too easy to solve or resolve doesn’t offer the reader much food for conjecture. Readers like to feel smart, after all; piecing the puzzle together along with — or even a little ahead of –the protagonist is half the fun, isn’t it?

It’s considerably less amusing when the protagonist just stumbles onto necessary information, is slow to act, or isn’t on the ball enough to ask the right questions of the right people. While a poor interviewer is almost always an obstruction to the reader finding out crucial information, too-garrulous antagonists and the interview scenes that enable their yen to spout monologue tend to make the stakes seem lower, causing the reader to care less about the outcome.

Why, you gasp in horror? As convenient as a suddenly chatty secret-hider can be to moving the plot along, information discovered too easily runs the risk of seeming…well, ordinary.

Think about it: if the reader gets to watch the protagonist run down a false lead or two, struggle to remove that rock from in front of the cave to rescue the Brownie troop, a brace of nuns, and three golden retriever puppies gasping for breath within, genuinely have to put two and two together in order to make four, etc., it’s not only usually more exciting than an unresisted search, but your protagonist will come across as smarter, more active, and more determined than if she just stands around while these things happen around her. She’ll also be more likable, someone a reader might be eager to follow throughout an entire book.

(I heard some of you gasp, but that last bit’s not a foregone conclusion. If the reader, particularly a professional one, does not either like or love to hate a manuscript’s protagonist, he’s unlikely to keep reading for long. Just a fact of the life literary.)

That plot-level logic applies equally to an individual interview scene. If the information the protagonist is seeking just drops into her lap, as it does in the example above, the reader has no reason to become invested in the search: after the first couple of times, tremendous, long-held secrets being blurted out will simply become the normal way the manuscript reveals things.

But what if our scheming reporter above had been forced to try really, really hard to pry Mrs. Quinine’s whereabouts out of Ernest Borgnine? What if he was not only recalcitrant, but had an agenda of his own? What if he told her half-truths that would require still more backstory to render useful? Wouldn’t the information she elicited — even if it consisted of precisely the same set of facts Ernest blurted out spontaneously in the version above — seem more valuable? Or at least more fun for the reader to watch her ferret out?

The answer to both of those last two questions was yes, by the way. As you would have known had you not been playing with those giant rubber bands.

Contrary to popular belief amongst that sizable portion of the aspiring writing community that apparently enjoys killing conflict on the page practically the moment it draws its first breath, readers like to see protagonists struggle to achieve their goals. It’s interesting, as well as character-revealing.

Stop shooting rubber bands in my direction. I was going to call on you. “But Anne,” those of you limp with revision fatigue murmur, taking aim, “complexity is all very nice, but I’m worried about my manuscript’s getting too long, or the pace starting to drag, if I start inventing a digressions in my hero’s pursuit of the MacGuffin he’s desperately seeking throughout my story.”

While it is quite reasonable to draw a line on the length of a manuscript you’re planning to submit to an agent, whether a particular scene seems overly lengthy to a reader is largely a matter of presentation, not actual number of lines on a page. There are plenty of short books, and even short scenes, that, to borrow a phrase from industry parlance, read long.

The trick lies in selectivity. Try ridding your interview scenes of plot shortcuts or too-easy revelations. Some suggestions:

(a) Any line in which anyone’s pointing out something obvious (“Hey, aren’t you the guy who’s been walking around town, asking all of those pesky questions?”)

(b) Any line that consists entirely of one character agreeing with or simply prompting another to speak. While “Yes, dear,” and “You’re so right,” may be charming to hear in real life, it seldom adds much to a scene.

(c) Simple yes or no answers to simple yes or no questions. Yes or no is almost never the most interesting way to frame a question or response, and the latter often shuts off interesting follow-up questions.

(d) I don’t know tends not to add much to a scene, either, especially if a first-person narrator is given to saying it. If your protagonist doesn’t know, have her take steps to find out.

(e) Any new development that’s not actually surprising. (“Wait — you mean that your long-lost brother first described as a miner on pg. 4 might possess a map to the very mine we need to explore? Astonishing!”)

(e) Any scene where the interviewer doesn’t have to work to elicit information from the interviewee.

These may not seem like big cuts, but believe me, they can add up. In many manuscripts, making these revisions alone would free up pages and pages of space for new plot twists, if not actual chapters of ‘em.

It’s also worth your while to consider whether a low-conflict interview scene is even necessary to the storyline: could your protagonist glean this information in another, more conflict-producing manner?

That question is not a bad one to write on a Post-It note and stick to your computer monitor. If a scene — or even a page — does not contain recognizable conflict, it’s a prime candidate for trimming.

A grand place to start excising the unsurprising: the first scene of the book, since that is the part of any submission that any Millicent, agent, editor, or contest judge is most likely to read. If you’re going to have your plot surprise or your protagonist impress the reader with her interview acumen anyplace in the book, make sure that she does it within the first 5 pages.

That’s just common sense, really: an agent, editor, screener, and/or contest judge needs to get through the early pages of a submission before getting to its middle or end. Therefore, it would behoove you to pay very close attention to the pacing of any interview scene that occurs in the first chapter, particularly within the first few pages, as this is the point in your submission where an irritated Millicent is most likely to stop reading.

Was that giant gust of wind the collective gasp of all of you out there whose novels open with an interview scene? I’m sympathetic to your frustration, but next time, could you aim away from my cat?

An AMAZINGLY high percentage of novel submissions open with interviews or discussions of the problem at hand. The protagonist gets a telephone call on page 1, for instance, where he learns that he must face an unexpected challenge: violà, an interview is born, as the caller fills him in on the details. While he says, “Uh-huh,” four times.

Or the book opens with the protagonist rushing into the police station and demanding to know why her son’s killer has not yet been brought to justice: another interview scene, as the police sergeant responds.

“Uh-huh,” she says. “Go on, Mrs. Smith.”

Or the first lines of the book depict a husband and wife, two best friends, cop and partner, and/or villain and victim discussing the imminent crisis. “Uh-huh, that’s the problem,” one of them says ruefully. “But what are we going to do about it?”

Or, to stick to the classics, this dame with gams that would make the 7th Fleet run aground slinks into the private dick’s office, see, and says she’s in trouble. Bad trouble — as opposed to the other kind — and could he possibly spare a cigarette?

“What kind of bad trouble?” he asks — and lo and behold, another interview begins. Probably with a lot of agreement in it.

There are good reasons that this scene is so popular as an opener, of course: for the last decade and a half, agents and editors at conferences all over North America have been imploring aspiring writers to open their books with overt conflict, to let the reader jump right into the action, without a lot of explanatory preamble. Conversation is a great way to convey a whole lot of background information or character development very quickly, isn’t it?

Or, to put it in the language of writing teachers, dialogue is action.

Those of you who have been hanging out here at Author! Author! for a good long time are giggling right now, I suspect, anticipating my launching into yet another tirade on what I like to call Hollywood narration (a.k.a. Spielberg’s disease), movie-style dialogue where characters tell one another things they already know, apparently for no other reason than to provide the audience with background information as easily and non-conflictually as humanly possible.

As it happens, you were right, oh gigglers. Openings of novels are notorious for being jam-packed with Hollywood narration. As in:

“So, Serena, we have been shipwrecked on this desert island now for fifteen years and seven months, if my hash marks on that coconut tree just to the right of our rustic-yet-comfortable hut. For the first four years, by golly, I thought we were goners, but then you learned to catch passing sea gulls in your teeth. How happy I am that we met thirty-seven years ago in that café just outside Duluth, Minnesota.”

“Oh, Theobold, you’ve been just as helpful, building that fish-catching dam clearly visible in mid-distance right now if I squint — because, as you may recall, I lost my glasses three months ago in that hurricane. If only I could read my all-time favorite book, Jerzy Kosinski’s BEING THERE, which so providentially happened to be in my unusually-capacious-for-women’s-clothing coat pocket when we were blown overboard, and you hadn’t been so depressed since our youngest boy, Humbert — named after the protagonist of another favorite novel of mine, as it happens — was carried off by that shark three months ago, we’d be so happy here on this uncharted four-mile-square island 200 miles southwest of Fiji.”

“At least for the last week, I have not been brooding so much. Taking up whittling at the suggestion of Archie — who, as you know, lives on the next coral atoll over — has eased my mind quite a bit.”

“Yes, I know. How right you were to follow Archie’s advice, given that in his former, pre-atoll life, he was a famous psychologist, renowned for testifying in the infamous Pulaski case, where forty-seven armed robbers overran a culinary snail farm…

Well, you get the picture. That’s not just information being handed to the protagonist without any sort of struggle whatsoever; it’s backstory being spoon-fed to the reader in massive chunks too large to digest in a single sitting. Just about the nicest comment this type of dialogue is likely to elicit from a professional reader is a well-justified shout of, “Show, don’t tell!”

More commonly, it provokes the habitual cry of the Millicent, “Next!”

While we are contemplating revision, did you notice the other narrative sins in that last example? Guesses, anyone?

Award yourself high marks if you dunned ol’ Serena for over-explaining the rather uninteresting fact that she managed to bring her favorite book with her whilst in the process of being swept overboard by what one can only assume were some pretty powerful forces of nature. As character development goes, this is the equivalent of knocking Gilligan on the head with a coconut to induce amnesia when the Skipper needs him to remember something crucial: a pretty obvious shortcut.

Besides, as much as I love the work of Jerzy Kosinski, in-text plugs like this tend to raise the hackles of the pros — or, to be more precise, of those who did not happen to be involved with the publication of BEING THERE (a terrific book, by the way) or currently employed by those who did. Besides, revealing a character’s favorite book is not a very telling detail.

I hear writerly hackles rising all over the reading world, but hear me out on this one. Writers who include such references usually do so in the charming belief that a person’s favorite book is one of the most character-revealing bits of information a narrative could possibly include. However, this factoid is unlikely to be of even the vaguest interest to someone who hadn’t read the book in question — and might well provoke a negative reaction in a reader who had and hated it.

It’s never a good idea to assume that any conceivable reader of one’s book will share one’s tastes, literary or otherwise. Or worldview.

But let’s get back to analyzing that Hollywood narration opening. Give yourself an A+ for the day if you said, “Hey, if the island is uncharted, how does Serena know so precisely where they are? Wouldn’t she need to have either (a) seen the island upon which she is currently removed upon a map, (b) seen it from space, or (c) possess the magical ability to read the mind of some future cartographer in order to pinpoint their locale with such precision?”

And you have my permission to award yourself a medal if you also cried to the heavens, “Wait — why is the DIALOGUE giving the physical description here, rather than, say, the narrative prose?”

Good call. This is Hollywood dialogue’s overly-chatty first cousin, the physical description hidden in dialogue form. It often lurks in the shadows of the first few pages of a manuscript:

Will glanced over at his girlfriend. “What have you been doing, to get your long, red hair into such knots?”

“Not what you’re thinking,” Joceyln snapped. “I know that look in your flashing black eyes, located so conveniently immediately below your full and bushy eyebrows and above those cheekbones so chiseled that it would, without undue effort, be possible to use them to cut a reasonably soft cheese. Perhaps not a Camembert — too runny — but at least a sage Derby.”

“I’m not jealous.” Will reached over to pat her on the head. “Having been your hairdresser for the past three years, I have a right to know where those luxurious tresses have been.”

She jerked away. “Get your broad-wedding-ring-bearing fingers away from my delicate brow. What would your tall, blonde wife, Cynthia, think if you came home with a long, red hair hanging from that charm bracelet you always wear on your left wrist, the one that sports dangling trinkets from all of the various religious pilgrimage sights you have visited with your three short brunette daughters, Faith, Hope, and Katrina?”

Granted, few submissions are quite as clumsy as this purple-prosed exemplar, but you’d be surprised at how obvious some writers can be about introducing their characters. Remember, just because television and movie scripts can utilize only the senses of sight and sound to tell a story doesn’t mean that a novelist or memoirist must resort to Hollywood narration to provide either backstory or physical details. We writers of books enjoy the considerable advantage of being able to use narrative text to show, not tell, what we want our readers to know.

Pop quiz, campers: why might introducing physical descriptions of the characters through opening-scene dialogue seem a bit clumsy to someone who read hundreds of submissions a month?

If you said that Will and Joceyln are telling each other things they obviously already know, kiss yourself on both cheeks. In this era of easily-available mirrors, it’s highly unlikely that anyone would not know that he possessed, say, dark eyes, and even the most lax of personal groomers would undoubtedly be aware of her own hair’s color and length. Thus, the only reason this information could possibly appear in dialogue between them, then, is to inform a third party.

Like, for instance, the reader. Who might conceivably prefer to be shown such details, rather than hear them in implausible dialogue.

How can a conscientious writer tell the difference between Hollywood narration and good old physical description? A pretty good test: if a statement doesn’t serve any purpose other than revealing a fact to the reader, as opposed to the character to whom it is said, then it’s Hollywood narration. And it should go — to free up page space for more intriguing material and good writing.

If you also said that Will and Joceyln are engaging in dialogue that does not ring true, give yourself extra credit with sprinkles and a cherry on top. With the exception of medical doctors, art teachers, and phone sex operators, real people seldom describe other people’s bodies to them.

It’s just not necessary, and it’s not interesting conversation. I am a chatty person, but I cannot conceive of any impetus that might prompt me to say over dinner, “Pass the peas — and incidentally, your eyes are green.”

My habitual tablemate’s eyes are indeed green, and I might conceivably want you to know it. But honestly, was just blurting it out — and to him, no less — the most interesting way to introduce this information?

In the interest of scientific experimentation, though, I just tried saying it out loud. It did not produce scintillating conversation. Turns out that being possessed of a mirror — nay, several — he already knew.

Who could have seen that plot twist coming, eh? And aren’t we all stunned by the depth of that character and relationship development in the last few paragraphs?

While I’m at it, let me share one of my pet peeves, both on the page and in real life: men who keep commenting on how pretty their dates are. To their dates. As in:

“Mona, there’s something I’ve been wanting to say for weeks now…” Alex waited until the waiter had poured the wine and retreated. “Um, you look great tonight.”

She dimpled prettily. “Thanks. After a long day’s work at the nuclear physics lab, I figure I deserve a nice night out.”

“You have such pretty eyes. Brown, aren’t they?”

“Well, more of a neon green, since that radioactive spider bit me.” She reached across the table for his hand. “But enough about work. What did you want to say?”

He squeezed her hand. “I love your hair. So wavy and alive.”

Her hand flew to her scalp self-consciously. “Snakes are so hard to handle. I’ve just washed them, and I can’t do a thing with them. I wouldn’t recommend peeking into Medusa’s cage until we find an antidote.”

“You’re lovely, you know that?”

Mona suppressed a sigh. Did he honestly think she didn’t own a mirror? Well, come to think of it, if she looked in one now, she would be turned to stone. Perhaps he thought he was doing her a favor. “But enough about me. Let’s talk about you.”

He jerked his head sideways, to avoid the nearest snake’s trajectory. “I just love looking at you. That’s such a nice dress.”

You can hardly blame the snake for lashing out at him, can you? As gratifying as compliments are to hear, a flattery barrage like this should not be confused with conversation. Not only isn’t it particularly interesting for the reader — a simple physical description would have been a far more effective way to display Mona’s charms — but as we may see from her reaction, it isn’t even interesting to the person being complimented.

On the page as in life, a single compliment is sweet. But when fifteen of them tumble out of your dinner partner’s mouth, you start to wonder if he’s avoiding saying something. It’s auditory filler.

And did you notice that even after Alex has rhapsodized about her looks, we still don’t have a particularly clear idea of what Mona looks like? Oh, the narrative sentences give some specifics, but the dialogue is vague: she looks great, has pretty eyes, has mobile hair, is lovely, is sporting a nice dress.

Hardly enough to enable the reader to pick her out of a police lineup, is it?

Yes, a lot of people, especially shy ones, do pepper their conversation with compliments, but as we have discussed, the point of dialogue is not merely to provide a transcript of real-world conversations. It’s to entertain the reader, develop character, and move the plot along. And frankly, don’t you suspect that Mona has quite a bit more going on in her life than Will’s conversational choices are revealing?

Heck, those snakes seem to have more on their minds than he does. Keep up the good work!

Phrases an aspiring writer should not touch with a hundred-foot pole

Can we talk?

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

“Boys will be boys.” Granddad shuffled back to Jeremy. “Where have you been, son? Jitterbugging at the malt shop to that newfangled rock-and-roll?”

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

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

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

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

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

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

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

“Fine. How are you?”

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

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

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

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

“Sure could use it.”

“Sure could. Ah-choo!”

“Bless you.”

“Thank you.”

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

“Thanks. Watch out for that puddle.”

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

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

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

“You, too, Ambrose.”

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

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

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

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

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

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

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

Right? Anyone out there?

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

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

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

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

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

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

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

She would look perplexed. “It isn’t?”

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Ladies and gentlemen, I bring you the premiere of Author! Author! Interviews: a chat about literary fiction with Bellwether Prize winner Heidi Durrow

Welcome back, campers! How was your week? Mine was, as predicted, hectic, but the niece is married, the dishes washed (no mean feat, considering the family produced a five-course sit-down dinner for the wedding reception), and we are now living on leftovers.

How stressful was it all? Well, let me put it this way: my doctor offered to write me a note to excuse me from all of this ostensible frivolity.

But off with the shackles of the past — on to a monumental new development in the ever-evolving Author! Author! community offerings. Today, I am delighted to bring you the first in what I hope will be may in-depth conversations with wonderful recently-published authors about not only their books, but also the art and craft of writing itself.

You know, the kind of chat that writers find fascinating, but disillusions non-writers and those who would prefer to believe that good writing simply falls from the heavens into the author’s mind, with no actual work involved.

In this series, I’m going to be talking with these authors about the actual work of writing. I’m very excited about this, not only because I suspect that these conversations will prove inspirational and educational to members of the Author! Author! community — and to that end, please feel free to post questions and comments; I shall forward them to the authors — but also because, frankly, when a book comes out, 99% of interviewers will ask precisely the same set of questions.

All of us who read author interviews are familiar with the standards, right? So how did you get the idea for this book? Is this novel autobiographical? How did you get started writing in the first place? Did you always want to be a writer — as opposed to, say, a fireman? Are any of the characters based upon real people? What’s your next book about? No, really, what part of this novel is based upon real life?

It’s all fun and interesting for the author the first dozen or so times, but after that, one begins to feel that one’s part in the interview process could very adequately be played by a tape recorder. Nor is this phenomenon new: I spent a large part of my childhood and adolescence helping science fiction author Philip K. Dick prepare for interviews — oh, you thought that established authors didn’t rehearse? In what sense is an author interview not a public performance? — and believe me, in any given year, we could count the original questions interviewers asked on the fingers of two hands.

Believe me, we longed to be able to start counting on our toes.

So part of my goal in this interview series is to allow good authors more latitude than they are generally allowed in literary interviews — because, let’s face it, what is likely to interest other writers about a book is not necessarily what will fascinate other readers. These interviews will be by writers, for writers.

Are you picturing yourselves chatting with me when your first book comes out? Excellent — you’re in the perfect mindset to enjoy my January 11, 2011 conversation with the exceptionally talented Heidi Durrow, author of the recent literary fiction debut, The Girl Who Fell from the Sky, now available in paperback.

If Heidi’s name sounds familiar, you’ve probably either been perusing Best Books of 2010 lists or were hanging out here at Author! Author! in recent months. For those of you who missed my glowing tribute to what I consider the best debut of last year, allow me to introduce you to a writer I believe is going to be remembered as one of the greats. Take a peek at the publisher’s blurb:

Take a gander at the publisher’s blurb:

Durrow book coverRachel, the daughter of a Danish mother and a black G.I., becomes the sole survivor of a family tragedy after a fateful morning on their Chicago rooftop.

Forced to move to a new city, with her strict African-American grandmother as her guardian, Rachel is thrust for the first time into a mostly black community, where her light brown skin, blue eyes, and beauty bring a constant stream of attention her way. It’s there, as she grows up and tries to swallow her grief, that she comes to understand how the mystery and tragedy of her mother might be connected to her own uncertain identity.

This searing and heartwrenching portrait of a young biracial girl dealing with society’s ideas of race and class is the winner of the Bellwether Prize for best fiction manuscript addressing issues of social justice. In the tradition of Jamaica Kincaid’s Annie John,Toni Morrison’s The Bluest Eye, and Sandra Cisneros’ The House on Mango Street, here is a portrait of a young girl—and society’s ideas of race, class, and beauty.

The book has developed something of a cult following amongst lovers of serious literary fiction. How much do its fans respect it? Well, let me put it this way: when I first discovered the novel in a wee bookstore in Lexington, Kentucky, the clerk nearly knocked me over, so eager was she to rush to my side to recommend the book.

Apparently, that enthusiasm was catching, for by the time my plane was over the Rockies, heading home to Seattle, was already raving about the book to everyone in the seats near me. Flight attendants will remember that as the time two of them sidled down the aisle to ask, “Um, why are all of you talking about falling from the sky? Flying is perfectly safe, you know.”

The intriguing mystery of just how and why an entire family fell from a Chicago apartment building’s roof — yes, veteran interviewers, based upon a real-life incident — may be the unusual premise of the story, but the core of the writing is centered upon the growth and development of incredibly real-feeling characters.

As I mentioned before, Heidi pursued character in a completely original manner, calculated to delight those intrigued by the interesting use of language: via punctuation in dialogue. THE GIRL WHO FELL FROM THE SKY depicts social class and intellectual development through such subtle nuances in the characters’ speech patterns that at first, I kept having to re-read lines to make sure I was not imagining it.

I wasn’t; it’s one of the most brilliant uses of dialogue I’ve seen in years. (And trust me, I read a lot of dialogue in any given year.) Join me, please, for a discussion of it, conducted at the ever-fabulous Third Place Books, just north of Seattle.

A quick technical note before you click on the video: my apologies for the background noise; the Author! Author! staff did not realize that the microphone would pick it up so well, or that it should have been placed a trifle closer to Heidi. Turning up the volume on your computer before you start watching might prove helpful.