Posted on - 20 Comments on The dreaded Frankenstein manuscript, part XXI: Millicent holds these truths to be self-evident. Trust me.

The dreaded Frankenstein manuscript, part XXI: Millicent holds these truths to be self-evident. Trust me.

signingdec

Ah, another evening, another installment in our gargantuan self-editing series. I have to say, I’ve been having a good time with it — usually, I spend this time of year talking at length about how to construct a winning conference pitch, followed by another couple of weeks devoted to concocting a professional-looking query letter. We’ve been having so much good, productive fun working on revision issues lately, however, that I haven’t wanted to break up the party.

So a summer of craft it is. Onward and upward!

I’m still very much at your service if you are interested in pulling together a pitch, query letter, or synopsis, of course — as always, feel free to ask questions. If you’re in the market for in step-by-step instructions, hie yourself to the quite detailed archive list at the bottom right-hand side of this page, where you will find categories helpfully labeled HOW TO WRITE A PITCH, HOW TO WRITE A REALLY GOOD QUERY LETTER, HOW TO WRITE A REALLY GOOD SYNOPSIS, and HOW TO PUT TOGETHER A QUERY PACKET. After your have pitched or queried successfully, you might want to avail yourself of the posts in the HOW TO FORMAT A BOOK MANUSCRIPT and HOW TO PUT TOGETHER A SUBMISSION PACKET categories.

Or, if you should happen to be perusing these categories in a panic the night before or just after a writers’ conference, searching frantically for the absolute basics, try the HOW TO WRITE A PITCH AT THE LAST MINUTE, HOW TO WRITE A QUERY LETTER IN A HURRY, and HOW TO WRITE A SYNOPSIS IN A HURRY.

In short, please don’t assume that because I’m spending the summer reveling in manuscript problems — because, let’s face it, insofar as anyone can actually revel in manuscript problems, I do — I’m not still interested in helping members of the Author! Author! community with practical marketing. If you don’t find answers to your questions in the archives, please, I implore you, speak up.

Everyone clear on that? Good. Now let’s plunge back into the full enjoyment of revision.

What’s that you say? Enjoy doesn’t precisely capture the emotion current swelling your breast at the prospect of another discussion of manuscript megaproblems? Well, may I at least assume that everyone’s been learning a little something each time?

I sincerely hope that the learning curve has been sharp for many of you, because honestly, I do not think we writers talk amongst ourselves nearly enough about these issues. The art of self-revision is so difficult to teach that many writing gurus eschew it altogether –- and not merely because there is no magical formula dictating, say, how often it’s okay to repeat a word on the page or how many summary statements a chapter can contain before our buddy, Millicent the agency screener, rends her garments and cries, “Enough with the generalizations, already! Show, don’t tell!”

Although experience leads me to believe that the answer is not all that many.

If you take nothing else away from this series, please let it be a firm resolve not to resent Millicent for this response. As we discussed last time, there’s just no getting around the fact that professional readers — i.e., agents, editors, contest judges, agency screeners, editorial assistants, writing teachers — tend to read manuscript pages not individually, like most readers do, but in clumps.

One after another. All the livelong day.

Which, of course, is necessarily going to affect how they read your manuscript — or any other writer’s, for that matter. Think about it: if you saw the same easily-fixable error 25 times a day (or an hour), yet were powerless to prevent the author of submission #26 from making precisely the same rejection-worthy mistake, wouldn’t it make you just a mite testy?

Welcome to Millicent’s world. Help yourself to a latte.

If you’re at all serious about landing an agent, you should want to get a peek into her world, because she’s typically the first line of defense at an agency, the hurdle any submission must clear before a manuscript can get anywhere near the agent who requested it. In that world, the submission that falls prey to the same pitfall as the one before it is far, far more likely to get rejected on page 1 than the submission that makes a more original mistake.

Why, you cry out in horror — or, depending upon how innovative your gaffes happen to be, cry out in relief? Because — feel free to chant along with me now, long-term readers — from a professional reader’s point of view, common writing problems are not merely barriers to reading enjoyment; they are boring as well.

Did the mere thought of your submission’s boring Millicent for so much as a second make you cringe? At this point in our Frankenstein manuscript series, it should.

In not entirely unrelated news, today, I shall be acquainting you with a manuscript problem frequently invisible to the writer who produced it, yet glaringly visible to a professional reader, for precisely the same reason that formatting problems are instantly recognizable to a contest judge: after you’ve see the same phenomenon crop up in 75 of the last 200 manuscripts you’ve read, your eye just gets sensitized to it.

I’m talking, of course, about yet another eminently cut-able category of sentences, statements of the obvious. You know, the kind that draws a conclusion or states a fact that any reader of average intelligence might have been safely relied upon to have figured out for him or herself.

I heard some of you out there chuckle ––you caught me in the act, didn’t you? Yes, the second sentence of the previous paragraph IS an example of what I’m talking about; I was trying to test your editing eye.

Here I go, testing it again. See how many self-evident statements you can catch in this sterling opening. (Sorry about the slight fuzziness of the page here. As always, if you’re having trouble reading the individual words in the example, try holding down the Command key while hitting +.)

obvious example 1

Do correct me if I am wrong, but is not night usually dark? Where else would the moon rise except on the horizon? What else could one possibly shrug other than shoulders — or, indeed, nod with other than a head? Is there a funny bone located somewhere in the body other than the arm, or toes not on the foot?

Seeing a pattern? Are you also seeing abundant invitation for revision, I hope?

Ideally, this sort of statement should send your fingers flying for the DELETE key. Why do I want you to develop a sensitivity to this kind of statement on the page? Well, let me put it this way: any sentence in a submission that prompts Millicent to mutter, “Well, duh!” is a likely rejection-trigger.

Yes, all by itself, even if the rest of the submission is pretty darned clean, perfectly formatted, and well-written to boot. Read on to find out why.

I mention that, obviously, because I fear that some of you might not have understood that in a written argument, discussion of a premise often follows hard upon it, often in the paragraphs just below. Or maybe I just thought that not all of you would recognize the difference between a paragraph break and the end of a blog. I still have a lot to say on the subject.

Rather insulting to the intelligence, isn’t it? That’s how your garden-variety Millicent feels when a sentence in a submission assumes she won’t catch on to something self-evident.

“Jeez,” she murmurs indignantly, “just how dim-witted does this writer think I am? Next!”

Lest that seem like an over-reaction to what in fact was an innocent line of text, allow me to remind you: when you’re reading in order to catch mistakes — as every agency screener, agent, editor, and contest judge is forced to do when faced with mountains of submissions — you’re inclined to get a mite testy. Liability of the trade.

In fact, to maintain the level of focus necessary edit a manuscript really well, it is often desirable to keep oneself in a constant state of irritable reactivity. Keeps the old editing eye sharp.

Those would be the eyes in the head, in case anyone was wondering. Located just south of the eyebrows.

To a professional reader in such a state, the appearance of a self-evident proposition on a page is like the proverbial red flag to a bull: the reaction is often disproportionate to the offense. Even — and I tremble to inform you of this, but it’s true — if the self-evidence infraction is very, very minor.

Don’t believe me? Okay, here is a small sampling of some of the things professional readers have been known to howl at the pages in front of them, regardless of the eardrums belonging to the inhabitants of adjacent cubicles:

In response to the seemingly innocuous line, He shrugged his shoulders: “What else could he possibly have shrugged? His kneecaps?” (Insert violent scratching sounds here, leaving only the words, He shrugged still standing in the text.)

In response to the ostensibly innocent statement, She blinked her eyes: “The last time I checked, eyes are the only part of the body that CAN blink!” (Scratch, scratch, scratch.)

In response to the bland sentence, The queen waved her hand at the crowd: “Waving ASSUMES hand movement! Why is God punishing me like this?” (Scratch, maul, stab pen through paper repeatedly.)

And that’s just how the poor souls react to all of those logically self-evident statements on a sentence level. The assertions of the obvious on a larger scale send them screaming into their therapists’ offices, moaning that all of the writers of the world have leagued together in a conspiracy to bore them to death.

As is so often the case, the world of film provides some gorgeous examples of larger-scale obviousness. Take, for instance, the phenomenon film critic Roger Ebert has dubbed the Seeing-Eye Man: after the crisis in an action film has ended, the male lead embraces the female lead and says, “It’s over,” as though the female might not have noticed something as minor as Godzilla’s disappearance or the cessation of gunfire or the bad guys dead at their feet. In response to this helpful statement, she nods gratefully.

Or the cringing actor who glances at the sky immediately after the best rendition of a thunderclap ever heard on film: “Is there a storm coming?”

Taken one at a time, such statements of the obvious are not necessarily teeth-grinding events – but if they happen too often over the course of the introductory pages of a submission or contest entry, they can be genuine deal-breakers.

Oh, you want to see what that level of Millicent-goading might look like on the submission page, do you? I aim to please. Here’s a little number that I like to call the Walking Across the Room (WATR) problem:

obvious example2

This account is a completely accurate and believable description of the process, right? As narrative in a novel, however, it would also be quite dull for the reader, right because it requires the retailing of so many not-very-interesting events in order to get that door answered. Any reasonably intelligent reader could be trusted to understand that in order to answer the door, she would need to put down the book, rise from the chair, and so forth.

Or, to put it in the terms we’ve been using over the past few days: is there any particular reason that the entire process could not be summed up as She got up and answered the door, so all of the reclaimed page space could be devoted to more interesting activity? Or, if we really wanted to get daring with those editing shears, why not have the narrative simply jump from one state of being to the next, trusting the reader to be able to interpolate the connective logic:

When the ringing became continuous, Jessamyn gave up on peaceful reading. She pushed aside Mom’s to-do list tacked to the front door and peered through the peephole. Funny, there didn’t seem to be anyone there, yet still, the doorbell shrilled. She had only pushed it halfway open when she heard herself scream.

Think Millicent’s going to be scratching her head, wondering how Jessamyn got from the study to the hallway? Or that she will be flummoxed by how our heroine managed to open the door without the text mentioning the turning of the knob?

Of course not. Stick to the interesting stuff.

WATR problems are not, alas, exclusively the province of scenes involving locomotion — many a process has been over-described by dint of including too much procedural information in the narrative. Instead of narrowing down the steps necessary to complete a project to only the most important, or presenting the full array in such a manner that the most vital and interesting steps, a WATR text mentions everything, up to and sometimes including the kitchen sink.

What WATR anxiety — the fear of leaving out a necessary step in a complex process — offers the reader is less a narrative description of a process than a list of every step involved in it, an impression considerably exacerbated by all of those ands. Every detail here is presented as equally important, but the reader is left with no doubt that the account is complete.

WATR problems are particularly likely to occur when writers are describing processes with which they are very familiar, but readers may not be. In this case, the preparation of a peach pie:

Obvious example 3

As a purely factual account, that’s admirable, right? Should every single pastry cookbook on the face of the earth suddenly be carried off in a whirlwind, you would want this description on hand in order to reconstruct the recipes of yore.

As narrative text in a novel, however, it’s not the most effective storytelling tactic. All of those details, while undoubtedly accurate, swamp the story. Basically, this narrative voice says to the reader, “Look, I’m not sure what’s important here, so I’m going to give you every detail. You get to decide for yourself what’s worth remembering and what’s not.”

Not sure why that’s a serious problem? Be honest now: didn’t your attention begin to wander after just a few sentences? It just goes to show you: even if you get all of the details right, this level of description is not very likely to retain a reader’s interest for long.

Or, as Millicent likes to put it: “Next!”

Do I hear some murmuring from those of you who actually read all the way through the example? “But Anne,” you cry, desperately rubbing your eyes to drive the sleepiness away, “the level of detail was not what bugged me most about that pie-making fiesta. What about all of the ands? What about all of the run-on sentences and word repetition? Wouldn’t those things bother Millicent more?”

I’m glad that you were sharp-eyed enough to notice those problems, eye-rubbers, but honestly, asking whether the repetition is more likely to annoy a professional reader than the sheer stultifying detail is sort of like asking whether Joan of Arc disliked the burning or the suffocating part of her execution more.

Either is going to kill you, right? Mightn’t it then be prudent to avoid both?

In first drafts, the impulse to blurt out all of these details can be caused by a fear of not getting the entire story down on paper fast enough, a common qualm of the chronically-rushed: in her haste to get the whole thing on the page right away, the author just tosses everything she can think of into the pile on the assumption that she can come back later and sort it out. It can also arise from a trust issue, or rather a distrust issue: it’s spurred by the author’s lack of faith in either her own judgment as a determiner of importance, her profound suspicion that the reader is going to be critical of her if she leaves anything out, or both.

Regardless of the root cause, WATR is bad news for the narrative voice. Even if the reader happens to like lists and adore detail, that level of quivering anxiety about making substantive choices resonates in every line, providing distraction from the story. Taken to an extreme, it can even knock the reader out of the story.

Although WATR problems are quite popular in manuscript submissions, they are not the only page-level red flag resulting from a lack of faith in the reader’s ability to fill in the necessary logic. Millicent is frequently treated to descriptions of shifting technique during car-based scenes (“Oh, how I wish this protagonist drove an automatic!” she moans), blow-by-blow accounts of industrial processes (“Wow, half a page on the smelting of iron for steel. Don’t see that every day — wait, I saw a page and a half on the intricacies of salmon canning last week.”), and even detailed narration of computer use (“Gee, this character hit both the space bar and the return key? Stop, my doctor told me to avoid extreme excitement.”)

And that’s not even counting all of the times narratives have meticulously explained to her that gravity made something fall, the sun’s rays produced warmth or burning, or that someone standing in line had to wait until the people standing in front of him were served. Why, the next thing you’ll be telling her is that one has to push a chair back from a table before one can rise from it, descending a staircase requires putting one’s foot on a series of steps in sequence, or getting at the clothes in a closet requires first opening its door.

Trust me, Millicent is already aware of all of these phenomena. You’re better off cutting ALL such statements in your manuscript– and yes, it’s worth an extra read-through to search out every last one.

That’s a prudent move, incidentally, even if you are absolutely positive hat your manuscript does not fall into this trap very often. Remember, you have no control over whose submission a screener will read immediately prior to yours. Even if your submission contains only one self-evident proposition over the course of the first 50 pages, if it appears on page 2 and Millicent has just finished wrestling with a manuscript where the obvious is pointed out four times a page, how likely do you think it is that she will kindly overlook your single instance amongst the multifarious wonders of your pages?

You’re already picturing her astonishing passersby with her wrathful comments, aren’t you? Excellent; you’re getting the hang of just how closely professional readers read.

The trouble is, they’re hard to catch. Self-evident statements virtually always appear to the writer to be simple explanation. Innocuous, or even necessary. “What do you mean?” the writer of the obvious protests indignantly. “Who could possibly object to being told that a character lifted his beer glass before drinking from it? How else is he going to drink from it?”

How else, indeed?

Provide too much information about a common experience or everyday object, and the line between the practical conveyance of data and explaining the self-evident can become dangerously thin. I’ve been using only very bald examples so far, but let’s take a look at how subtle self-evidence might appear in a text:

The hand of the round clock on the wall clicked loudly with each passing second, marking passing time as it moved. Jake ate his cobbler with a fork, alternating bites of overly-sweetened ollallieberry with swigs of coffee from his mug. As he ate, farmers came into the diner to eat lunch, exhausted from riding the plows that tore up the earth in neat rows for the reception of eventual seedlings. The waitress gave bills to each of them when they had finished eating, but still, Jake’s wait went on and on.

Now, to an ordinary reader, rather than a detail-oriented professional one, there isn’t much wrong with this paragraph, is there? It conveys a rather nice sense of place and mood, in fact. But see how much of it could be trimmed simply by removing embroideries upon the obvious:

The round clock on the wall clicked loudly with each passing second. Jake alternated bites of overly-sweetened ollallieberry cobbler with swigs of coffee. As he ate, farmers came into the diner, exhausted from tearing the earth into neat rows for the reception of eventual seedlings. Even after they had finished eating and left, Jake’s wait went on and on.

The reduction of an 91-word paragraph to an equally effective 59-word one may not seem like a major achievement, but in a manuscript that’s running long, every cut counts. The shorter version will make the Millicents of the world, if not happy, at least pleased to see a submission that assumes that she is intelligent enough to know that, generally speaking, people consume cobbler with the assistance of cutlery and drink fluids from receptacles.

Who knew?

Heck, a brave self-editor might even go out on a limb and trust Millicent to know the purpose of plowing and to understand the concept of an ongoing action, trimming the paragraph even further:

The round clock on the wall clicked loudly with each passing second. Jake alternated bites of overly-sweetened ollallieberry cobbler with swigs of coffee. Farmers came into the diner, exhausted from tearing the earth into neat rows. Even after they had left, Jake’s wait went on and on.

That’s a cool 47 words. Miss any of the ones I excised, other than perhaps that nice bit about the seedlings?

Fair warning: self-evidence is one of those areas where it honestly is far easier for a reader other than the writer to catch the problem, though, so if you can line up other eyes to scan your submission before it ends up on our friend Millicent’s desk, it’s in your interest to do so.

In fact, given how much obviousness tends to bug Millicent, it will behoove you to make a point of asking your first readers to look specifically for instances of self-evidence. Hand ‘em the biggest, thickest marking pen in your drawer, and ask ‘em to make a great big X in the margin every time the narrative takes the time to explain that rain is wet, of all things, that a character’s watch was strapped to his wrist, of all places, or that another character applied lipstick to — wait for it — her lips.

I am now going to post this blog on my website on my laptop computer, which is sitting on a lap desk on top of — you’ll never see this coming — my lap. To do so, I might conceivably press buttons on my keyboard or even use my mouse for scrolling. If the room is too dark, I might switch the switch on my lamp to turn it on. After I am done, I might elect to reverse the process to turn it off.

You never can tell; I’m wacky that way. Keep up the good work!

Posted on - 20 Comments on The dreaded Frankenstein manuscript, part XX: banishing that dreaded feeling of déjà vu

The dreaded Frankenstein manuscript, part XX: banishing that dreaded feeling of déjà vu

pear blossoms1pear blossoms3
pear blossoms2pear blossoms

Since we’ve been on such a roll, discussing dialogue with vim, I’ve been rather reluctant to wrest us back to a subject that we absolutely must cover before we round out the Frankenstein manuscript series, conceptual redundancy. (Don’t worry, dialogue-huggers; I’ll be getting back to it in a few days.)

Actually, as topics go, it’s not all that far removed from edit-worthy dialogue: as I mentioned in passing just a few days ago, real-life dialogue tends to be rife with both phrase, idea, and even fact repetition. Add to that the simple truth that since it can take a heck of a long time to write a book, a writer does not always remember where — or even if — he’s made a particular point before, and even if he does, he may not be confident that the reader will remember it from 200 pages ago, and our old pal, Millicent the agency screener, ends up grinding her teeth and muttering, “You TOLD us that already!” a great deal more than any of us might like.

Yes, do take a moment to admire that last epic sentence. I doubt we’ll see its like again.

We’ve already talked about some reasons that redundant dialogue bugs your garden-variety Millicent so much, but at least the problem is easy for a reviser to spot. Heck, if your antagonist favors a catchphrase — please tell me she doesn’t — the fix is downright easy: a quick confab with Word’s FIND function, a few creative substitutions, and voilà! Problem solved.

Conceptual redundancy, however, requires both time for close reading of the entire manuscript and a retentive memory for a reviser to catch. Even if that reviser happens to have been blessed with both, after slaving over a Frankenstein manuscript for months or years on end, repeated or largely similar snippets of dialogue, explanations, and even relatively important plot points can seem…well, if not precisely fresh, at least not memorable from earlier in the latest draft.

Unfortunately, this quite predictable byproduct of revision burnout does not always fill professional readers with sympathy for the writer’s dilemma. Quite the opposite, in fact.

“Great jumping Jehoshaphat!” Millicent groans over many a submission. “Didn’t this writer bother to read this manuscript before sending it to us? Couldn’t she see that she TOLD us this already!”

To give you a sense of just why she might have this reaction, allow me to regale you with an anecdote from the dim reaches of my past. Some of you may remember it; it’s an example I have often used before when discussing conceptual redundancy.

I was six years old, standing in line for the Peter Pan ride at Disneyland, back in the days when the quality and popularity of the ride was easily discernable by the level of ticket required to board it. E was the best; I believe this particular ride was somewhere in the B- range.

Frankly, my tepid-to-begin-with enthusiasm had begun to fade practically as soon as I stepped into a queue of inexplicable length to cruise around an ersatz London with Peter, Wendy, and the gang. All brown eyes and braids, I had already spent several hours holding my mother’s hand while my father took my older brother on D and E ticket rides. And I was not particularly enamored of PETER PAN as a story: the business of telling children that if they only wish hard enough, their dead loved ones will come back from the dead has always struck me as rather mean.

Because, honestly, what does that story about the motivations of all of those kids whose late relatives persistently remain dead?

So I was not especially psyched to take this particular ride. It was merely one of the few the guidebook deemed appropriate to literary critics of my tender age. The longer we stood in line, the harder I found it to muster even the appearance of childish joie de vivre.

Why was I feeling so oppressed, the six-year-old in all of us cries? Because as each ship-shaped car took a new crew of tourists whirring into the bowels of the ride, Peter’s voice cried out, “Come on, everybody, raring to go-o-o-o!”

After about five minutes of listening to that annoying howl while inching toward the front of line, I started counting the repetitions. By the time it was our turn to step into the flying ship, Peter had barked that inane phrase at me 103 times.

It’s all I remember about the ride. I told the smiling park employee who liberated us from our ship at the end of the ride that it would have been far, far better without all of that phrase at the beginning.

He patted me on the back as he hurried me toward the exit. “I know,” he whispered. “By the end of the day, I want to strangle someone.”

I was mightily impressed by the power of so much mindless repetition. And that, my friends, is how little girls with braids grow up to be editors.

Actually, it’s probably fortunate that I was aurally assaulted by a cartoon character chez Mouse in my formative years — it’s helped make me very, very aware of just how much repetition is constantly flung at all of us, all the time. Not just in everyday conversations, but in TV and movies as well.

Most of us become inured through years of, well, repetition to the film habit of repeating facts and lines that the screenwriter wants to make sure the viewer remembers, information integral to either the plot (“Remember, Mortimer — cut the RED cord hanging from that bomb, not the yellow one!”), character development (“Just because you’re a particle physicist, Yvette, doesn’t mean you’re always right!”), or both (“You may be the best antiques appraiser in the British Isles, Mr. Lovejoy, but you are a cad!”)

My all-time favorite example of this phenomenon — again, this may seem a tad familiar to some of you, but that sort of is the point here — came in the cult TV series Strangers With Candy, a parody of those 1970s Afterschool Special that let young folks like me into esoteric truths like Divorce is Hard on Everyone in the Family, Outsiders are Teased, and Drugs are Bad. In case, you know, kids might not have picked up on any of that.

The writers and producers of the Afterschool Specials seemed genuinely concerned about the retentiveness of its young viewers’ memories, or perhaps our general level of intelligence: it was rare that any point was made only once — or that the fate of the Good Kid Who Made One Mistake was not obvious from roughly minute five of the program. True to this storytelling tradition, Strangers With Candy’s heroine, Jerri Blank, often telegraphed upcoming plot twists by saying things like, “I would just like to reiterate, Shelly, that I would just die if anything happened to you.”

Moments later, of course, Shelly is toast.

It was funny in the series, of course, but foreshadowing is substantially less funny to encounter in a manuscript, particularly if your eyes are attuned to catching repetition, as many professional readers’ are. Characters honestly do say things like, “But Ernest, have you forgotten that I learned how to tie sailors’ knots when I was kidnapped by pirates three years ago?”

Seriously, Millicent sees this all the time. Yes, even when the first 50 pages of the manuscript dealt with that very pirate kidnapping. And every time such a reference is repeated, another little girl with braids vows to grow up to devote her life to excising all of that ambient redundancy.

At base, conceptual repetition is a trust issue, isn’t it? The writer worries that the reader will not remember a salient fact crucial to the scene at hand, just as the screenwriter worries that the audience member might have gone off to the concession stand at the precise moment when the serial killer first revealed — wait for it — that he had a lousy childhood.

Wow — who could have predicted THAT? How about anyone who has seen a movie within the last two decades?

Television and movies have most assuredly affected the way writers tell stories. As we discussed earlier in this series, one of the surest signs that a catch phrase or particular type of plot twist has passed into the cultural lexicon is the frequency with which it turns up in manuscript submissions.

That’s a problem, because one of the best ways to assure a submission’s rejection is for it to read just like half the submissions that came through the door that day. We all know how agents and editors feel about manuscripts that bore them, right? In a word: next!

Come closer, and I’ll tell you a secret: repetition is boring. Really boring. As in it makes Millicent wish she’d gone into a less taxing profession. Like being a test pilot or a nuclear physicist.

Why, you ask? Here’s another secret: people who read manuscripts for a living are MORE likely to notice repetition of every variety than other readers, not less. (Perhaps Peter Pan traumatized them in their younger days, too.) Not only repetition within your manuscript, but repetition across manuscripts as well.

Yes, I am indeed saying what you think I’m saying. If 6 of the last 10 submissions Millicent has screened were conceptually redundant — a proportion not at all beyond the bounds of probability; it’s hard to strip a manuscript of them entirely, because they are so pervasive — your first repetition may annoy her as much as the eighth in her first manuscript of the day.

And no, there’s absolutely nothing you can do to affect where your work falls in her to-read stack. Thanks for asking, though.

All a savvy reviser can do is — speaking of concept repetition — re-read his submission or contest entry IN ITS ENTIRETY, IN HARD COPY, and OUT LOUD before allowing it to see the inside of a mailbox or hitting the SEND key. Minimizing the conceptual redundancy within the manuscript is the best (indeed, the only) insurance policy a writer can take out against the submissions read just before hers is to make hers as clean as possible.

I see some of you shrugging. You don’t think your manuscript could possibly fall prey to that level of bad luck? Okay, oh confident ones, here’s a challenge for you: sit down with your first 50 pages and highlight every line of dialogue in there that you’ve ever heard a TV or movie character say verbatim. Ever.

Was that giant slurping noise I just heard the sound of the blood rushing out of everyone’s faces at the realization of just how much dialogue that might potentially cover?

Did you find even one? Then you actually do need to worry about Millicent’s cry of, “Oh, no, not THIS again!”

For those of you who did not turn pale: what if I also ask you to highlight similar and culturally-common phrases in the narration, as well as the dialogue?

First-person narration is notorious for echoing the currently popular TV shows. So is YA. Often, it’s unconscious on the writer’s part: it’s brainwashing from all of that repetition.

Honestly, it would be surprising if common dialogue hadn’t made its way into all of our psyches: according to CASSELL’S MOVIE QUOTATIONS, the line, “Let’s get outta here!” is heard in 81% of films released in the US between 1938 and 1985.

Care to take a wild guess at just how often some permutation of that line turns up in submissions to agencies? Better yet, care to take a wild guess at how many agents and editors notice a particular phrase the second time it turns up in a text? Or the second time it’s turned up in a submission this week?

“Come on, everybody, raring to go-o-o-o!”

Unfortunately, just because a writer doesn’t realize that he’s been lifting lines doesn’t mean that an agency screener won’t notice and be annoyed by it. Particularly if three of the manuscripts she’s seen today have used the same line.

It happens. Or, to put it in Afterschool Special terms, Checking for Both Types of Repetition is Good.

I know, I know, it’s tempting to assume that you haven’t used any of the standard catchphrases or plot twists, but believe me, even the most innovative writers do it from time to time. And for good reason: the rest of the population is subjected to the same repetitive teleplays and screenplays as writers are.

Over time, people do tend to start to speak the way they would if they were playing themselves onscreen. A writer of very good hardboiled mysteries tells me that he is constantly meeting private detectives who sound like Sam Spade, for instance.

But remember — once again, this concept should be at least slightly familiar by now — just because people do or say something in real life doesn’t mean it will necessarily be interesting translated to the printed page.

Check. Weed out both repetition within your manuscript AND material unconsciously borrowed from TV and movies. Or, better yet, have a good reader you trust check for you. (And if you’re not sure whether a particular twist or line is common enough to count, film critic Roger Ebert maintains a database of them.)

Often, it’s surprising how small a textual change will turn an incipient cliché into a genuinely original moment. A writer cannot perform that magic trick, however, without first identifying where it should be applied.

Is your head aching from all of the homework I’ve heaped upon you already today? Oh, but I’m far from done.

For starters, here’s a pop quiz: did any of you sharp-eyed self-editors happen to catch the really, really subtle test of your conceptual editing skills cleverly concealed in this post so far?

If your hand immediately shot into the air, accompanied by a vigorous shout of, “By Jove, Anne, I’m glad you brought this up; it’s been driving me mad. Your comments on conceptual redundancy were themselves conceptually redundant. You’ve made some of the points above two or three times — and via examples you’ve used before, too. How relieved I am to hear that you did it on purpose!” not only should you award yourself a full seventeen gold stars for the day, but you should start thinking about offering your services to your writer friends as a first reader.

You, my friend, are starting to read like Millicent the agency screener and Mehitabel the contest judge. Please, for the sake of your sanity, do not attempt to ride the Peter Pan ride anytime soon.

Even if you were not actively annoyed by my repeating myself, you may well have been a trifle insulted by it. Repeating a concept, fact, or sentence too often — or even once, if the bit in question was particularly memorable the first time around — does convey an impression to readers that the author does not trust them to be able to recall salient matters without a narrative nudge. Or perhaps does not believe they are intelligent enough to figure out even self-evident logical connections without assistance.

What other purpose, after all, would a writer have for producing a sentence like I would just like to reiterate, Shelly, that I would just die if anything happened to you?

“In heaven’s name, why must anyone leap to such an unflattering conclusion?” scream those who currently have pages under Millicent’s critical eye. “I could see being a trifle annoyed by hearing a similar argument a week apart, but why would any sane creature have such an intensely negative reaction to it?”

A couple of very sane reasons, actually. First, the Millicents of this world aren’t typically reading just one manuscript in any given day, but dozens. (Rejecting most of them on page 1 speeds up the screening process like you wouldn’t believe.) So in all likelihood, the manuscript that irritates her by repeating herself isn’t the only redundant submission she has handled that day — and certainly not that week. Conceptual redundancy is one of the more common manuscript megaproblems out there, cutting across lines of genre, book category, and the fiction/nonfiction divide.

All of which should sound annoyingly familiar by now, right? Getting the picture?

To be fair, Millicent was probably pretty even-tempered the first fifty times a narrative assumed that she couldn’t remember basic plot elements. Around the 750th time, however, it had gotten old.

By then, too, she would probably have figured out what an experienced editor could have told her — and this is the second sane reason a professional reader might find conceptual redundancy annoying: writers quite frequently retain multiple iterations of the same point simply because they like the writing of each section that discusses it.

Or, as I did above, because they have an illustrative anecdote that they’d really like to shoehorn into the text. (I admit it: I love the Peter Pan example.) Either way, conceptual redundancy is a signal that a manuscript requires quite a bit more revision.

You can feel more homework coming, can’t you? Clever you; you must have seen this movie before.

(1) Print out all or part of any pages you plan to submit to Millicent or anyone remotely like her.

You may use any part of your manuscript, of course, but as submissions tend to get rejected in the early pages — thus leaving the rest unread unfortunately often — page 1 is a dandy place to start.

(2) Read through it, using a highlighting pen — say, yellow — to mark every time the text repeats the same information.

If you have the time to get fancy, it will make your post-exercise life easier if you take the time to make notes on a separate sheet of every time a specific repetition occurs. That list will render figuring out which iteration to keep much, much easier.

(3) Using a different color of highlighter — pink is nice — mark the first couple of paragraphs (or even the scene) that immediately follows the repeated information.

Why, you ask? Hold your horses; I’m building suspense.

(4) Go back and re-read the yellow sections. Are all of them genuinely necessary for the reader to follow what’s going on? Or could some of them be cut without endangering the reader’s ability to follow the plot?

In answering question #4, assume that the reader is of normal intelligence and average memory, but is reading your book in a single sitting. (Millicent’s boss probably will read it in installments, but Millicent often will not.) Ditto with a contest entry: Mehitabel generally reads each one just once.

(5) Immediately after reading each yellow section, re-read the pink section that follows it. Are all of the highlighted bits actually adding something new to the plot, characterization, or argument? Or are they included primarily because you kind of liked how they sounded?

If it’s the latter, don’t be too hard on yourself: the old writing chestnut kill your darlings was coined for a reason. Remember, this is need not be the only book you ever write; you needn’t include every nice piece of writing that falls off your fingertips.

Save something for the sequel, for heaven’s sake. You needn’t always be raring to go-o-o-o.

(6) Be especially attentive to those pink bits in first-person narratives, memoirs — or in a real-life story told as fiction. Are these sections necessary to the story you’re telling, or are they included merely because these things happened in real life?

Often, this is another of Millicent’s most cherished pet peeves — and this one is usually shared by her boss and the editors to whom the agent typically sells. Far too much of the time, memoirists (and novelists who write in the first person) forget that writing the truth from a sympathetic point of view is not enough to make a good book — it must also be an engaging story.

Ditto with novelists who incorporate the real into the texts: just because something actually happened does not mean that it will necessarily be interesting to read. Or add to the storyline of a book.

Gee, where have I heard all of this before?

Judicious cutting is especially important when writing the real. No reader, however intrigued by a premise, wants to hear everything that ever happened to a character, any more than he wants to plow through a complete list of every object in a room where an important scene occurs. Include only what your story needs to make it shine.

Now that I have alerted you to the twin dangers of factual redundancy intended to remind readers of salient points (“As I mentioned back in Ch. 2, Eleanor, I stand to inherit a hefty chunk of change when my Uncle Fritz dies.”) and screen clichés that have made their way into real life (“Say ‘ah,’” kindly Dr. Whitehairedman told the terrified child.), it’s only fair to mention that both types of repetition also tend to be, I am happy to report, some of the easiest lines for a self-editor to identify and cut.

Redundant sentences can often be trimmed wholesale, with no cost to the text at all. And clichés, like pop culture references and jokes that don’t quite work, are often digressions in a scene or dialogue, rather than integral to it. Much of the time, they can be deleted without adding any additional writing.

Which is a pretty good indicator all by itself that a line should be cut anyway, actually: if you wouldn’t miss a sentence if it were gone, it should probably go.

Take, for instance, the following piece of purple prose, full of sentences just begging to hop into the tumbrel and ride to the guillotine. As you read, think about just how much trimming could occur without harming the relationships or plot of the scene:

Marcus Aurelius paced the room, frowning, revisiting in his mind his last encounter with Cardinal Richelieu, two months before, when they had shot those rapids together in the yet-to-be-discovered territory of Colorado. Despite hours of manly good fellowship and moments of undeniable passion, they had not parted friends. The powerful holy man was known for his cruelty, but surely, this time, he would not hold a grudge.

“Can I bum a cigarette?” Marcus asked, to buy more time to recap the plot in his head.

Richelieu laughed brutally, but with an undertone of affection. “How on earth did you pick up the habit? Tobacco had not come to Europe in your time.” He shook two out of the pack and stuck both into his mouth. “And barely in mine.”

He lit the pair and handed both to his erstwhile lover. They sat in silence for a moment, the smoke winding its way around the cardinal’s red hat and through the halo of St. Jerome, who was standing nearby.

Finally, Marcus Aurelius decided he could take this brutal wordlessness no longer. “I’ve come for some information, Armand.”

Richelieu’s hand tightened on the sawed-off shotgun that seldom left his side. “You’re wasting your time.”

“I’m not leaving until you tell me what I need to know.”

“It might,” St. Jerome suggested gently, “go a little faster if you were more specific.”

“Yes, do come to the point.” Richelieu waved a bejeweled hand toward his wall-sized TV screen. “American Idol is on in an hour.”

Yes, text-retentive ones you are correct: I’ve used this example before, too. No exertion of laziness has been spared to drive today’s points home. (Oh, and happy Bastille Day, Cardinal.)

But tell me, how much cutting did you manage to do? Other than the obvious, that is — as a major Stoic, Marcus Aurelius clearly would not have folded so quickly under the pressure; I give you that.

Even ignoring the philosophical problems and the time travel that seems to have happened here, there’s room for some fairly painless trimming that would speed up the scene. Take a gander:

Marcus Aurelius paced the room, frowning. The powerful holy man before him was known for his cruelty, but surely, he could not still be holding a grudge about how they’d parted in Colorado. “Please tell me, Armand. For old times’ sake.”

Richelieu laughed brutally, but with an undertone of affection. The smoke from his cigarette wound its way around his red hat and through the halo of St. Jerome, leaning against the fridge.

“It might,” St. Jerome suggested gently, “be helpful if you were more specific about what you wanted.”

“Yes, do come to the point.” Richelieu lifted a bejeweled hand from his sawed-off shotgun to wave languidly toward his wall-sized TV screen. “American Idol is on in an hour.”

That’s 123 words, down from 253, a substantial cut obtained through the simple expedient of removing the movie clichés (the double cigarette bit was straight out of the Bette Davis vehicle NOW, VOYAGER, right?) and unnecessary conceptual repetition.

How did I know, within the context of an isolated excerpt, that the references to the Colorado scene probably referred to something that happened earlier in the book? Call it well-honed editorial instinct: this kind of micro-flashback almost invariably recaps a scene told more fully elsewhere – and when it isn’t shown at some point in the book, it probably should be.

Seem paradoxical? It isn’t.

A micro-flashback usually provides one or more characters’ motivation(s) in the scene occurring at the moment: here, the earlier romantic interlude has set the stage for Marcus’ belief that Richelieu would do him a favor, as well as Richelieu’s current attitude toward Marcus. Clearly, then, this past episode is important enough to the development of both characters that the reader would benefit from seeing it in its entirety.

Which makes removing the micro-flashback from this scene an easy editorial call. To work as character development — as explanatory asides that deal with motivation must, right? — the reader really should have this information prior to the scene.

What would that mean for our example? Well, if the Colorado rapids scene did happen earlier in the book, the micro-flashback would be redundant; if it did not, the micro-flashback is not memorable enough in itself to make a lasting impression upon the reader.

In other words: snip, snip.

Long-time readers of this blog, chant it with me now: emotionally important scenes are almost always more powerful if they are SHOWN as fully-realized scenes, rather than merely summarized. (Oh, come on — you don’t want to know what happened on those rapids?) Keep an eye out for those micro-flashbacks, my friends: they’re often signposts telling the editor what needs to be done to improve the manuscript.

In this case, the cut can only help: by removing the explanatory summary here, the author will need to make sure that the earlier scene made enough of an impression upon the reader that she will remember it by the time Marcus Aurelius comes looking for information on page 348.

Yes, even if that means going back and writing the earlier scene from scratch. Sometimes, adding a fresh scene is actually a quicker and easier fix for a manuscript that drags than merely trimming the existing text.

The metaphor that I like to use for this kind of revision comes from flower arranging, believe it or not — and yes, I’ve used it before. I simply will not have my long-time readers walking away from this post willing to tolerate conceptual redundancy.

Think of your draft as a wonderful bouquet, stocked with flowers you have been gathering over the last couple of years. It’s lovely, but after it has been rejected a few dozen times, you’ve come to realize that maybe it’s too big for the room in which the agent of your dreams wants to place it; it does not fit comfortably into the only vase she has.

So you need to trim it — but how? A good place to start would be to pull out half of the daisies; a few are nice, but handfuls make the daisy point a bit more often than necessary.

Then you could start searching for the flowers that have wilted a little, or are not opening as well as others. Pulling out the wilted flowers renders the bouquet both smaller and prettier – and the ones that wilt the fastest are the ones that are borrowed from other sources, like movie tropes, which tend to date a book, anyway.

Already, your bouquet is looking lighter, more vibrant, but you liked the color that some of the discarded flowers added. Rather than pulling the cast-off blooms out of the compost bin and putting them back into the vase (as most self-editors will do), adding a fresh flower here and there is often more beneficial to the overall beauty of the bouquet.

Be open to the possibility that trimming your manuscript may well mean writing a fresh scene or two, for clarification or character development. Search your manuscript for micro-flashbacks that may be telling you what needs further elucidation, as well as darlings that could be, if not killed, then at least set aside to grace another book. If you apply a truly diligent eye, you may well find that a single, well-developed scene inserted early on will replace scores of micro-flashbacks down the line.

It happens. All the time. Like a good joke, motivation goes over better with the reader if it can be presented cleanly, without excess in-the-moment explanation.

Okay, it’s well past the time for me to go-o-o (curse you, Pan!) for today. Keep those creative spirits riding high, everyone, and as always, keep up the good work!

Posted on - 3 Comments on The dreaded Frankenstein manuscript, part XIX: the quirkiness of real life, or, so long, Harvey

The dreaded Frankenstein manuscript, part XIX: the quirkiness of real life, or, so long, Harvey

American Splendor poster

I am genuinely sad to record the passing of graphic novel pioneer Harvey Pekar. His intensely-observed presentations of both the most mundane and most trying aspects of everyday life not only stretched his genre, but demonstrated time and time again that accounts of ordinary life need not be ordinary.

I’m morally sure that Mssr. Pekar would have enjoyed the irony of his having joined the choir invisible right in the middle of our discussion of real-life vs. real-sounding dialogue. As any fan of OUR CANCER YEAR (co-written with his wife, Joyce Brabner) could tell you, he relied very heavily upon actual speech — something substantially easier to pull off when animation appears side-by-side with words on the printed page. Yet just when the dialogue seemed most mundane, one of his quirky characters would come out with a zinger:

“15 amps…15 amps! That’s all we’ve got, and I bet my computer uses half that. This place is a fire trap. You know what’s behind this wall? All our wiring is still in its original paper insulation. Melting copper, wrapped with newspaper. With headlines that read, ‘Jack the Ripper Still at Large!’”

That may sound like the extempore chat of any exasperated person, but as we discussed last time, simply transcribing actual speech is not usually the best — and certainly not the only — means of producing realistic dialogue on the page. There’s nothing wrong per se with lifting quotes from real life, but a savvy writer lifts selectively, judiciously.

And always, always with a definite point in mind. Dialogue that apparently serves no other purpose than to demonstrate that the writer is aware of normal, everyday speech tends to provoke an undesirable speech pattern in our old pal, Millicent the agency screener: “Next!”

Especially if, as often occurs in the opening pages of novel submissions, that meticulously-reproduced everyday speech either delays the action from beginning, slows down action already in progress, or — and Millicent sees this more than any of us might like to think — it takes the place of action happening offstage, so to speak. Many a potentially exciting opening scene has been smothered by the protagonist stopping to be polite — or just chatty.

Not sure what I mean? Okay, here are a couple of openings for the same story, each cut off at the point at which Millicent probably would have stopped reading. (Hey, you think it’s easy to come up with fresh examples night after night?)

“Why, Kathy!” Evan exclaimed. “I thought you weren’t going to make it?”

Well might he have asked. Kathy was not the sort of girl who typically turned up in dank attics, covered with cobwebs, soaking wet, and shaking with fear.

Still, her mother had brought her up right. “Hello, Evan. I thought you were going to Sharon’s party tonight.”

“My date came down with the flu.”

“That’s a shame. And after you got all dressed up, too.”

Evan glanced down at his normally spotless khakis. Climbing up that trellis might not have been such a good idea. He’d have to sneak his pants into the wash before Mom saw them, or he’d be in for it. “I hadn’t expected company.”

Kathy looked away. “Can you tell me what the Algebra homework
was?”

A trifle annoying, isn’t it? It’s fairly obvious that something has happened to Kathy just before the scene we’re seeing, but all of the narrative’s energies seem aimed toward delaying showing us what that something was. (And what is that called, campers? That’s right: false suspense.) Other than slowing the action, keeping the reader from knowing what’s going on, and probably pushing off the first scary happening of the book for a few pages, what purpose is this dialogue serving?

Before you answer, let me caution you that from Millicent’s perspective, but people really talk like that! is not a sufficient answer. Yes, two teenagers running into each other in a haunted house late at night might conceivably say things like this, but why does the reader need to see them say it?

Actually, why does the reader need to see this character say that? is a pretty good question for the reviser of a Frankenstein manuscript to ask early and often, especially when going over a scene that doesn’t go much of anywhere for a third of a page or more. (Hey, Millicent often doesn’t read more than that before deciding to reject a manuscript. Screeners read fast.) In a good submission or contest entry, there’s no such thing as a throw-away line, after all.

As we discussed yesterday, any line of dialogue unequivocally worth keeping exhibits one or more of the following characteristics: it either advances/complicates/resolves a plot point, reveals some interesting and relevant aspect of a character previously unseen in the book, or is interesting, amusing, and/or entertaining in its own right. As the closer readers among you may have noticed, practically none of the dialogue in the example above rises to any of these challenges.

So what’s a savvy reviser to do? Well, we have a number of options. We could back the timeline up a bit, to begin with an interesting character in an interesting situation.

Kathy felt fingers running gently through the sweaty tendrils on the back of her neck. So Evan did like her enough to meet her in the haunted house at midnight. “I don’t scare that easily.”

He didn’t answer. She tilted her head, resting it on his caressing hand. It was ice-cold. And bonier than she remembered.

“Okay, enough with the Halloween jokes.” She wiggled in his grasp. He was surprisingly strong for a chess club captain. “Your girlfriend may like this kid stuff, but…”

The side of her head hit the claw-footed bathtub so hard that she saw stars. She’d always thought seeing stars was a myth, just like the Holton Hall ghost. Water flowed over her face, smothering any further thought but escape.

Gets right to the point, doesn’t it? Thinking objectively, which opening would be more likely to spur you to keep reading, this or the first version?

And THAT is why, in case you were curious, writing gurus urge students to begin their works with a hook, to establish interest right away. But capturing a reader’s interest — particularly a professional reader’s interest — is not like tag: once you’ve hooked ‘em, they don’t necessarily remain hooked. Think of maintaining interest as being akin to love: no matter how hard someone falls for you at first, if you do not keep wooing, that interest is going to flag sooner or later.

Too many aspiring writers take their readers’ interest for granted, an often-costly assumption. So let’s talk wooing strategy.

In the industry, the standard term for what keeps a reader turning pages is tension. All too frequently, writers new to the game confuse it with suspense, but suspense is plot-specific: a skillful writer sets up an array of events in such a way as to keep the reader guessing what will happen next. In a suspenseful plot, that writing-fueled curiosity keeps the reader glued to the page between plot points.

Suspense, in other words, is why one doesn’t get up in the middle of a Hitchcock film to grab a bag of baby carrots from the fridge, unless there’s a commercial break. You want to see what is going to happen next.

Tension, on the other hand, can stem from a lot of sources, mostly character-generated, rather than plot-generated: the reader wants to know how the protagonist is going to respond next, a different kettle of fish entirely. Sometimes tension-rich dilemmas are plot points, but not always – and this gives the writer a great deal of freedom, since it’s a rare plot that can maintain a major twist on every page.

Or even every other page. (THE DA VINCI CODE, anyone?)

Some of the greatest contemporary examples of consistent tension in novels are the HARRY POTTER books. Actually, not a lot happens in most of the books in this series, particularly in the early chapters: kids go to school; they learn things; they have difficulty discerning the difference between epoch-destroying evil and a teacher who just doesn’t like them very much; Harry saves the world again.

Of course, the lessons they learn in the classroom ultimately help them triumph over evil, but that’s not what makes the HARRY POTTER books so absorbing. It’s the incredibly consistent tension. If J.K. Rowling’s publisher infused each page with heroin, rather than with ink, her writing could hardly be more addictive; there’s a reason that kids sit up for a day and a half to read them straight through. With the exception of the first 50 pages of the last book (hey, I’m an editor: it’s my job to call authors on their writing lapses), the tension scarcely flags for a line at a time.

Technically, that’s a writing marvel, a achieved not by magic, but by doing precisely the opposite of what the movie and TV scripts with which we’re all inundated tend to do: she gives her characters genuine quirks substantial enough to affect their relationships and problems that could not be solved within half an hour by any reasonably intelligent person.

Rather than making the reader guess WHAT is going to happen next, well-crafted tension lands the reader in the midst of an unresolved moment — and then doesn’t resolve it immediately. This encourages the reader to identify with a character (usually the protagonist, but not always) to try to figure out how that character could get out of that particular dilemma. The more long-term and complicated the dilemma, the greater its capacity for keeping the tension consistently high.

A popular few: interpersonal conflict manifesting between the characters; interpersonal conflict ABOUT to manifest between the characters; the huge strain required from the characters to keep interpersonal conflict from manifesting. Also on the hit parade: sexual energy flying between two characters (or more), but not acted upon; love, hatred, or any other strong emotion flying from one character to another, spoken or unspoken. Or even the protagonist alone, sitting in his room, wondering if the walls are going to collapse upon him.

Come to think of it, that’s not a bad rule of thumb for judging whether a scene exhibits sufficient tension: if you would be comfortable living through the moment described on the page, the scene may not provide enough tension to keep the reader riveted to the page. Polite conversation, for instance, when incorporated into dialogue, is almost always a tension-breaker.

“But wait!” I hear some of you slice-of-life aficionados out there cry. “I hate to be redundant with the questions, but shouldn’t dialogue EVER reflect how people speak in real life?”

Well, yes and no. Yes, it should, insofar as good dialogue reflects plausible regional differences, personal quirks, and educational levels. I’ve heard many an agent and editor complain about novels where every character speaks identically, or where a third-person narrative reads in exactly the same cadence and tone as the protagonist’s dialogue. Having a Texan character use terms indigenous to Maine (unless that character happens to be a relative of our last president’s, of course) is very likely to annoy a screener conversant with the dialect choices of either area.

Yes, Virginia, the pros honestly do notice these little things. That’s one of the many, many reasons that it is an excellent idea for you to read your ENTIRE submission IN HARD COPY and OUT LOUD before you mail or e-mail it off; it really is the best way to catch this flavor of writing problem.

But it’s just a fact of the art form that the vast majority of real-life dialogue is deadly dull when committed to print. While the pleasantries of manners undoubtedly make interpersonal relationships move more smoothly, they are rote forms, and the problem with rote forms is that utilizing them absolutely precludes saying anything spontaneous. Or original.

Or — and this is of primary importance in a scene — surprising. Think about it: when’s the last time someone with impeccable manners made you gasp with astonishment?

Even rude real-life conversation can be very dull on the page. If you don’t believe this, try this experiment:

1. Walk into a crowded café alone, sit down at a table near a couple engaged in an argument (not all that difficult to find, alas) and start taking notes.

2. Go home and write up their actual words — no cheating — as a scene.

3. Read it over afterward. Does it work dramatically? Is it character-revealing? Or do these people sound generic and their bickering dull?

99% of the time, even if the couple upon whom you eavesdropped were fighting or contemplating robbing a bank or discussing where to stash Uncle Harry’s long-dead body, a good editor would cut over half of what the speakers said. And if the two were in perfect agreement, the entire scene would probably go.

Why? Because real-life conversation is both repetitious and vague, as a general rule. It also tends to be chock-full of clichés, irrelevancies, non sequiturs, jokes that do not translate at all to print, and pop culture references that will surely be outdated in a year or two.

In a word: boring to everyone but the participants. It’s an insult to the art of eavesdropping.

So is, incidentally, dialogue that insists upon showing the reader every pause or hesitation, however miniscule. Contrary to popular belief amongst aspiring writers, the mere fact that a speaker stops saying anything for a moment is not invariably important enough to record for posterity. Nor is it, in itself, interesting.

You’re not believing me again, aren’t you? Okay, smarty pants, take a gander at this relatively commonplace example of this type of dialogue.

Sheila stopped in mid-step. “Edmond, what’s wrong? Are you…”

He hesitated before answering. “I’m fine. Just a minor arrhythmia.”

“But are you…I mean, is it something we need to worry about?”

“You worry too much, Sheila.” He paused. “But I should probably get to…a doctor. Or even…a hospital?”

“A hospital!” She couldn’t say anything else for a second. Then she grew brisk: “Edmond, you’re not…thinking clearly. I’m taking you to the emergency room, now.”

“But…”

“But me no buts. Do you need to lean on me to get to the car?”

Quite heavy ellipsis for just a few lines of text, isn’t it? Apart from being repetitive on the page, all of those dots aren’t really adding much to the scene. As those of you who are editing for length will be delighted to see, most of them could be cut entirely without changing the conflict or decreasing the tension of the scene at all.

Look at how painlessly those pauses may be minimized — and while we’re at it, let’s excise some of that redundancy as well:

Sheila stopped in mid-step. “Edmond, what’s wrong?”

“I’m fine. Just a minor arrhythmia.”

“Is it something we need to worry about?”

“You worry too much, Sheila.” He took in a shuddering breath. “But I should probably get to a doctor. Or even a hospital.”

She grew brisk: “I’m taking you to the emergency room, now.”

“But…”

“But me no buts. Do you need to lean on me to get to the car?”

See? All I retained was one reference to stopping and one ellipsis — but the scene is, if anything, more full of tension than when Sheila and Edmond were wasting all of our time by speaking so slowly.

That’s right, those of you who just gasped — I did say that wasting our time. Professional readers aren’t the only ones who tend to bore quickly when faced with dialogue whose primary recommendation is realism.

“But Anne,” the gaspers protest, “I thought the point of good writing was to show the reader the world as it actually is! If their eyes are going to glaze over just because I show a pause or two — which actual people do all the time in the real world, by the way — or include a few pleasantries, how is it going to be remotely possible for me to tell the realistic tale I want to tell?”

It’s more than remotely possible, reality-lovers — it’s probable, provided that you concentrate on what is surprising and interesting about that tale. Usually, the best way to achieve this is to focus upon what is unique about your self-described ordinary characters, rather than how they are just like everybody else.

That’s a taller order than it might at first appear, from an editing perspective. Far too often, slice-of-lifers and Everyman-producers will not differentiate between the expected ordinary details and the specific quirks of individual characters; their Frankenstein manuscripts tend to include everything, up to and including the kitchen sink. The trick to revising such text is to winnow out what the reader might expect to be there, so the genuinely unusual personalities of your real-life characters can shine forth.

Strong character development is as much about what the writer chooses to leave out as what s/he elects to leave in, after all. Mundane, predictable statements, however likely characters like yours may be to utter them in real life, seldom reveal much about the speaker’s personality, do they?

And that’s doubly true if more than one character says the same types of things. Yes, real people do frequently echo their kith and kin in real life, but unless you prefer to define true-to-life as synonymous with dull, I have too much faith in your creativity to believe that you can’t come up with something different for each character to say.

The same holds true for individual quirks. The more seemingly ordinary your protagonist, the more you ought to consider giving him a unique trait or two. Remember, one reader’s Everyman is another’s Ho-Hum Harry.

Ah, the gaspers seem to have caught their breath again. Yes? “But Anne, what you’re saying is problematic, frankly, to most of us who have lived through Creative Writing 101. Weren’t we all told to strive for universality in our prose? Weren’t we all ordered to write what you know? Weren’t we implored to be acute observers of life, so we could document the everyday in slice-of-life pieces of practically museum-level detail? I can’t be the only one who had this writing teacher, can I?”

Unfortunately, no — judging by contest entries and submissions, quite a few writers did. But let’s pause for a moment — you’ll like that, won’t you, slice-of-lifers? — to consider just how reflective of real life those Writing 101 standards actually were. Universality, until fairly recently, was code for appealing to straight, white men; exhortations to write what you know led to forty years’ worth of literary journals crammed to the gills with stories about upper middle-class white teenagers, mostly male. And the popularity of the slice-of-life short story (it’s awfully hard to maintain for an entire novel) left many of us sitting in writing class, listening to aspiring writers read thinly-fictionalized excerpts from their diaries.

Unfortunately, from Millicent’s point of view, all of the good students obediently following this advice has resulted in a positive waterfall of submissions in which, well, not a whole lot happens. Every day, she reads of universal protagonists (read: ordinary people) in situations that their authors know intimately (read: ordinary life) acutely observed (read: the ordinary seen through a magnifying glass).

It’s not that some of these many, many stories aren’t well-written; many of them are. And there’s nothing wrong with portraying all of that ordinariness, per se. It’s just that Millicent sees so darned much of it that it’s hard for an average Joe or Jane protagonist in an ordinary situation not to strike her as…

Well, you get the picture.

Whether that slice-of-life story is presented as fiction or memoir (a book category where it tends to work better on the page), ordinary characters may never be excused for being dull or predictable. Not in a manuscript submission, not in a contest entry, and not in a published book. Millicent is screening to find the extraordinary manuscript, the one with the fresh worldview, spin, or writing style applied to a story about a character (or characters) who are different enough from character(s) she’s seen before to remain interesting for the length of an entire book.

Aspiring writers, particularly memoirists, often seem to fail to take that last part into account when preparing their submissions: if the story presented does not appear from the very first line on page 1 to be about a fascinating person in an intriguing situation, the manuscript is going to be a tough sell to everyone from Millicent to her boss to an editor at a publishing house to a contest judge.

So if a book is about an Everyman living a life with which an ordinary reader might identify, it’s IMPERATIVE that he demonstrate some way in which either he or his story is not ordinary right away. Why? Because otherwise, the manuscript is far too likely to get dismissed as just not very interesting or surprising.

It’s not for nothing, you know, that agents complain about how many submissions they see that took too long for anything to happen, along with its corollary, the story took too much time to warm up, as well as the ever-popular not enough action on page 1. These complaints are reflective of the hard reality they see on a daily basis: many, if not most, first pages have no conflict on them at all, but are purely set-up.

Such an opening scene may be beautifully-written, lyrical, human life observed to a T. But from the business side of the industry’s perspective — and, despite the fact that agents are essentially the first-level arbiters of literary taste these days, they need to be marketers first and foremost, or they are of little use to those they represent — a slow opening translates into hard to sell.

The ordinariness of characters, that is, is something that comes up again and again in agents’ discussions of what they are seeking in a manuscript. An interesting character in an interesting situation is featured in practically all of their personal ads advice on the subject, particularly if the protagonist is not the character one typically sees in such a situation. A female cadet at a prestigious military academy, for instance. A middle-aged stockbroker arrested for protesting the WTO. A veteran cop who is NOT paired in his last month of duty with a raw rookie.

That sort of thing. In Millicent’s world, interesting and surprising are synonymous more often than fans of the ordinary might think.

So while a very average character may spell Everyman to a writing teacher, an average Joe or Joanna is typically a very hard sell to an agent. As are characters that conform too much to stereotype. (How about a cheerleader who isn’t a bimbo, for a change? Or a coach who isn’t a father figure to his team? A mother who doesn’t sacrifice her happiness for her kids’?)

So I ask you: isn’t it possible for you to work an element of surprise onto page 1 of your submission, the best place to catch an agent’s eye?

Before you chafe at that request, remember that lack of surprise can render a protagonist less likable, even for readers who do not, like Millicent, drop a book like a hot coal if the first few paragraphs don’t grab them. For some reason I have never been able to fathom, given how often writing teachers lecture about the importance of opening with a hook, this justification for keeping the opening lively is seldom mentioned, but it is in fact true: ordinary characters tend not to be all that engaging, precisely because they are average, and thus predictable.

For most readers, an unpredictable jerk is more interesting to follow than a beautifully-mannered bore, after all. It’s hard to blame Millicent and her cronies for that.

Or if it won’t work in your story to open with something surprising, how about vitally important? I don’t necessarily mean important on the global scale, but within the world of the story you’re telling.

Seriously, one of the best ways of preventing your protagonist from coming across as too average is to elevate the importance of what is going on in the opening to that character. A protagonist or narrator’s caring passionately about the outcome of a conflict practically always renders a scene more interesting, because it prompts the reader to care about the outcome, too. (Of course, this is a whole lot easier to pull off in an opening scene that features a conflict, right?)

Whatever you revisers of Frankenstein manuscripts do, however, do not under any circumstances allow the reader to become bored for even so much as a sentence of page 1. Or to be able to predict what the next line of dialogue will be. If your current opening scene cannot be edited to avoid both of these dreadful fates, consider beginning your submission with a different scene.

I ask you again: were you drawn into Kathy’s story faster when you saw her attacked by a water-loving ghost, or when she was chatting with a classmate after she’d fought off the spook?

Believe me, “boring” is absolutely the last adjective you want to spring to Millicent’s mind while she’s perusing your work. Even “annoying” is better, because at least then the manuscript is eliciting a reaction of some sort. But once the screener has a chance to think, “I’m bored with this,” if the next line does not re-introduce tension, chances are that the submission is going to end up in the reject pile.

That’s the VERY next line; you can’t count upon your manuscript’s ending up on the desk of someone who is going to willing to be bored for a few paragraphs. Or hadn’t I mentioned that as a group, professional readers bore fast.

Try not to hold it against them. I’ve read enough manuscripts in my time to understand why: the vast majority of manuscripts suffer from a chronic lack of tension.

Dull dialogue that does not reveal interesting things about the characters saying it is a primary culprit. I know, I know, being courteous seems as though it should make your protagonist more likable to the reader, but frankly, “Yes, thank you, George,” could be spoken by anyone. It doesn’t add much to any scene. And reading too many pages of real-life dialogue is like being trapped in a cocktail party with people you don’t know very well for all eternity.

“Deliver us from chit-chat!” the Millicents moan, rattling the chains that shackle them to their grim little desks clustered together under those flickering, eye-destroying fluorescent lights. “Oh, God, not another attractive stranger who asks, ‘So, have you been staying here long?’”

You’re just the writer to answer their prayers, aren’t you? Keep up the good work!

Posted on - 28 Comments on The dreaded Frankenstein manuscript, part XVIII: were you leading up to a point, Chatty Cathy? Or just killing some time with conversation?

The dreaded Frankenstein manuscript, part XVIII: were you leading up to a point, Chatty Cathy? Or just killing some time with conversation?

chatty cathy doll

When last we met, I was urging you, through the oh-so-subtle means of inundating you with example after example, into an appreciation of just how annoying redundant, non-character-revealing, or just plain dull dialogue can be to someone who reads manuscripts for hours on end. Like, say, Millicent the agency screener or Mehitabel the contest judge.

Why bring this up in the midst of an ongoing series on self-editing a Frankenstein manuscript? Well, several reasons. First — and it pains me to tell you this — more otherwise well-written submissions and contest entries drop precipitously in M & M’s respective esteems due to lackluster dialogue than is generally believed. Due to the pervasiveness of this phenomenon (and we’re gearing up for the second reason here), typically, one of the quickest, easiest ways to cut length off an over-long manuscript is to track down and excise the ordinary, everyday dialogue, the chatter that neither advances the plot, creates interesting conflict in the moment, or reveals character.

How can I state that so confidently? Because almost every writer who has taken an English composition course was told repeatedly that good dialogue should sound real, the average novel or memoir manuscript overflows with dialogue that’s apparently there simply because people say those types of things.

Which is not to say that striving to make your dialogue realistic is bad writing advice. It’s very good advice — but what the vast majority of composition teachers should have added immediately thereafter yet did not was an explanation that real-sounding dialogue and the things that people actually say in real life are not the same thing.

The former rings true on the page; while the latter can sometimes be very interesting, it can also lull the reader into a deep, deep slumber. Trust me, when people talk about an author with a good ear for dialogue, they’re referring to someone who consistently produces real-sounding dialogue, not someone who simply holds a microphone up to life and records the unedited results on the page.

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

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

“Oh,” Babette said. “You’re home.”

Rufus nursed the thumb the dodo trod upon earlier. “Yeah.”

“Have a nice day?”

“Um-hm.”

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

“Yeah. We sure got wet that day.“

“Ham sound good for dinner?”

“Yeah.”

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

Ordinary dialogue makes her especially antsy — again, I hate to be the one to break this to you, but if I don’t, who will? — on page 1. And that’s unfortunate, since this kind of chat is quite popular in the opening pages of manuscripts.

Why would the dialogue above have annoyed Millicent? Well, cast your eyes over it and tell me: what’s going on here? What is this story about? Who are these people, and why are 7 of the 10 opening lines of this story wasted on dialogue that doesn’t even begin to answer any of these questions?

Already, I see some hands raised out there in the ether. “But Anne,” writers of the real everywhere protest, and who can blame them? “It’s unfair to assume that every reader, even professional ones, would be turned off by the example above, even if it did appear on page 1. I think that Millicent and Mehitabel would be intrigued by its very terseness; I believe it would render them more likely to keep reading, not less, if only to find out what’s going on. I, for one, want to hear more about that dodo bite.”

I’m glad you brought that up, mythical hand-raisers, because the strategy of withholding basic information from the reader in an opening scene in order to create curiosity about what is to come is a suspense-building technique popular only with aspiring writers. Established writers soon learn not to do it, for the exceedingly simple reason that professional readers like Millicent, Mehitabel, and even Maury, Millie’s cousin who works as an editorial assistant at a publishing house, tend not to find this kind of opening titillating.

How do they regard it? Negatively, almost always. There’s even a term for it: false suspense.

That’s also the term for when an interesting one- or two-paragraph teaser, the kind that aspiring writers so love placing within italics, gives way to an apparently or only tangentially unrelated second scene. “Hey!” Millicent cries, spitting out her mouthful of scalding latte, “what happened to that darn interesting plot I’d gotten absorbed in? What’s this writer trying to do, hook me with something exciting, then drop me into a comparatively mundane storyline?”

Let’s be honest, folks: that’s precisely what most writers who use this trick are trying to do. Professional readers are wise to it by now. Remember, part of being a good storyteller involves knowing when to relieve the suspense.

I’m not here to talk about plotting today, however — but don’t worry; I’ll be coming back to it later in this series. For now, suffice it to say that even if you are one of those writers who absolutely adores reproducing everyday speech down to the last grunt and hesitation, you might want to keep those mundanities off of page 1 of your submission. Or page 2. Or, really, out of the opening chapter.

You wouldn’t want Millicent, Mehitabel, or Maury to mistake your submission for the hundreds of thousands of others that don’t have as good an ear for dialogue as you do, right?

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

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

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

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

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

But I apply a slightly different twist to it. For each line of dialogue, I ask myself: Is this here because it needs to be, or just because it’s something a character like this would say? In memoir and reality-based fiction, it can indeed be there simply because someone actually did say it — but is this particular line essential to the story being told here? And regardless of whether it’s a quote or not, if it isn’t either plot-advancing, character-revealing, or interesting in its own right, does it really need to be on the page at all?

Why, yes, you’re right, everyone who just grabbed the nearest sofa cushion and screamed into it: that is an awfully high standard to apply to every single line of dialogue in a manuscript. Your point?

To help the rest of you understand why your fellow readers felt faint at the mere thought of placing their manuscripts under that powerful a microscope, let’s take a gander at a species of dialogue gets under your garden-variety Millicent’s skin like wet sand under a swimsuit: the de facto monologue.

You know, the kind of ostensible dialogue that involves one character talking about something, while the other character doesn’t really add much to the conversation. It tends to run a little something like this:

“I can’t believe how arrogant that car dealer was!” Antoinette fumed. “You’d think he’d never met a woman who wanted to buy a car.”

“Yeah,” Steve replied.

“You can say that again. I should have told him that I was going home to e-mail the National Organization of Women, to get them to issue a general boycott of his lot.” Angrily, she wrestled to undo the bungee cords that held the driver’s side door onto her 1978 Saab, provided that she never attempted to accelerate above thirty miles per hour. “Did you see how surprised he was that we left?”

“Um-hm.”

“I’ll bet you did. You don’t suppose his telling me that women don’t know anything about cars is his standard sales technique, do you? Other women can’t actually have bought cars after a line like that.”

“No.” Steve was crawling into the passenger seat via the smashed back window. “I imagine not.”

Antoinette dug under the visor to retrieve the seatbelt. “Well, I wouldn’t be so sure. It’s like those construction workers who yell disgusting things at women walking by their worksites: if it didn’t provoke a positive response at least once every 10,000 times, would they keep doing it?”

“Could be.”

“What’s that supposed to mean? You think I’m blaming the victims?”

“I never said that.”

“Anyway,” she concluded after she had successfully hot-wired the car, so she would not have to force the mangled key into the half-melted ignition, “I guess he won’t be offering five dollars on a trade-in again!”

“Absolutely,” Steve murmured, clinging for dear life to what was left of the dashboard.

I ask you: what purpose is Steve serving in this conversation, other than providing validation, the opposite of conflict? And if he isn’t in the scene for any other reason, why doesn’t he just shut up and let Sandy blurt out her entire speech, instead of adding line after excisable line of mostly colorless dialogue?

Not to mention repetitious. We all know by this juncture, I hope, how Millicent and her ilk feel about that in a submission: “Next!”

Even if you find none of those excellent arguments for revision convincing, there’s another, quite practical one you might want to consider. Just look, self-editors concerned about the fact that your manuscript is 40 pages longer than the expected length for a first book in your category, at how much shorter this scene would be if it were presented as an actual monologue:

“I can’t believe how arrogant that car dealer was!” Antoinette fumed. “You’d think he’d never met a woman who wanted to buy a car. I should have told him that I was going home to e-mail the National Organization of Women, to get them to issue a general boycott of his lot.” Angrily, she wrestled to undo the bungee cords that held the driver’s side door onto her 1978 Saab, provided that she never attempted to accelerate above thirty miles per hour. “Saying that women don’t know anything about cars is sure a lousy sales technique. Other women can’t actually have bought cars after a line like that.”

While Steve crawled into the passenger seat via the smashed back window, she dug under the visor to retrieve the seatbelt. She set about hot-wiring the car, so she would not have to force the mangled key into the half-melted ignition.

“Or maybe it’s like those construction workers who yell disgusting things at women walking by their worksites: if it didn’t provoke a positive response at least once every 10,000 times, would they keep doing it?” The engine roared. “Bingo, baby! I guess he won’t be offering five dollars on a trade-in again!”

“Absolutely,” Steve murmured, clinging for dear life to what was left of the dashboard.

See? Steve’s silence makes his unwillingness to argue every bit as clear as his bland continual agreement did above. So what would have been the payoff for retaining his chatter?

Perhaps more to the point, if such lightly-disguised monologues provide neither character development, interesting inter-character conflict, nor, frankly, many sentences worth preserving for posterity, why are they so very popular with aspiring writers? Expediency, mostly: there’s no denying that having a protagonist, villain, or crucial minor character suddenly hold forth like Hamlet is a mighty efficient way to convey information to a reader.

But from the professional reader’s point of view, this use of page space is not efficient at all: it’s the narrative equivalent of having a play’s lead excuse himself to the other characters mid-scene, walk to the edge of the stage, and say, “Look, I really don’t have time to convey everything you need to know in dramatic form, so I’m simply going to tell you what would have happened in the next couple of scenes if we had bothered to stage them, okay?”

It’s not okay, at least according to Millicent. She’s reading your manuscript partially in order to find out how you tell a story — is it honestly in your interest to make her read through filler before reaching your best writing?

Ditto with dialogue that repeats what the reader already knows, as in that archetype of easily cut-able scenes, the one where the protagonist tells another character what happened in a previous scene. As in what the reader has just read. This might be defensible if the protagonist were adding a new twist on the information, but most of the time, s/he recaps the information exactly as the reader has already experienced it because — you can see this coming, can’t you? — it’s what a reasonable person might do in real life.

How easily cut-able are such scenes, you ask? Well, let me put it this way: it’s rare that an accurate retelling, even one that takes up pages of text, could not be summed up in a single sentence: Sheila ran back to the classroom and told everyone what had happened.

Here’s an axiom for the ages: by definition, redundant text adds nothing new to a narrative. It merely takes up space.

That answer didn’t mollify some of you reality-huggers, did it? “But Anne, isn’t realism valuable in and of itself? I know plenty of people who effectively have their own catchphrases.”

As do I, as it happens. In fact, I recently enjoyed a long, gossipy conversation with a very old friend of mine with a very distinctive speech pattern: she says, “Like I said…” every other minute or so. In a long anecdote — to which she is quite addicted, as a world traveler with unusual tastes in traveling companions — she often uses this phrase ten or fifteen times.

Since we grew up together, you would think I would know where she had picked up this rare trope, but I don’t; it’s an adult acquisition. We have both wandered far from home, evidently. But still, you’d think I would have some inkling as to its origin: she and I were so closely allied in high school that at her wedding, both her father AND her uncle spent 45 minutes grilling my boyfriend about his prospects and intentions toward me.

You might say that we come from a close-knit community.

Our hometown does in fact have a distinct speech pattern, a mixture of the lilt remaining when a small town in Switzerland (cow and wine country) picked up and became a small town in California (wine and cow country), certain Mexican-influenced words, a smattering of barrel-related French, and a linguistically inexplicable tendency to pronounce “mirror” as “meer.” Being a farming community (the aforementioned wine), of course, certain agricultural tropes abound in season, such as, “How about this rain? Sure do need it,” “The grapes would have been in by now, 20 years ago” (untrue, incidentally), “Did you hear that bears have been at Farmer X’s grapes?” (true, incidentally; brown bears like expensive fruit), and “Damned drunken tourists have been at my vines again. They think every grape in sight is a free sample.”

But “like I said,” no. So I ask you: would it or would it not be a good means of revealing the background of a character from my home town to incorporate it repeatedly in the text? What about using it as that character’s personal catchphrase?

Pardon my asking, but what precisely would it reveal about her character — other than the not-very-interesting fact that she uses this phrase often? If it does not add anything to the dialogue other than repetition, what possible incentive could I have to reproduce this verbal tick except so readers who already knew the person upon whom the fictional (or memoir) character was based would recognize her?

Is that honestly a good enough reason to bore all of those potential readers who have never had the pleasure of making her acquaintance? Would those excellent souls gain anything but chagrin out of my fidelity in reproducing a rather annoying true-life speech pattern on the page?

The answer to all of those seemingly rhetorical questions was no, by the way. The fact that a real-life person a writer has chosen to use as a character in a book really speaks repetitively does not justify forcing the reader to put up with it.

Now, being a sharp-eyed writer with a strong sense of verisimilitude in dialogue, you may have noticed something about all of the phrases that actually were typical of my home town, real-life tropes that actual people say bloody often in my native neck of the woods. Chant it with me now: they would be DEADLY dull in written dialogue.

As would a character who constantly punctuated her personal stories with “like I said…” Or indeed, almost any of the small talk which acquaintances exchange when they bump into one another at the grocery store. Take this sterling piece of Americana, overheard in Sunshine Foods in my hometown not so long ago:

Mrs. Price: “See you got some sun today, Rosemary.”

Mrs. Darter: “I was picking peaches. Sure is a great crop this year. How did your dentist appointment go?”

Mrs. Price: (Laughs.) “The dentist won’t be buying his new boat on my dime. Was that the Mini girl who just dashed by?”

Mrs. Darter: (Craning her head around the end of the aisle.) Could be. Haven’t seen her for a while. She’s not married yet, is she?”

Mrs. Price: (Shakes her head.) “Oh, hi, Annie.

Dr. Mini: Oh, hello, Mrs. Price. Hello, Mrs. Darter.

Mrs. Darter: I haven’t seen you in a long time, dear. Moving back to town, I hope?

Mrs. Price: Or just visiting friends who have been loyal enough to return to the town that nurtured them as babes?”

Dr. Mini: (Seeking escape route.) How’s your son, Mrs. Price? I haven’t seen him since high school. (Murmurs to significant other, covered by Mrs. A’s lengthy description of the relative heights, ages, and weights of her grandchildren.) Thank God.

Mrs. Darter: And how’s your mother?

Dr. Mini: Oh, fine, fine. I’d better be going. Nice to see you both.

Mrs. Price: Give my regards to your mother. Tell her that we hope to see her soon.

Dr. Mini: (Wheeling cart away.) I will. Remember me to (thinks hard) Bobby.

Mrs. Price: Well?

Mrs. Darter: (Sighing.) Still no wedding ring.

Mrs. Price: Just wait until I tell Bobby. At least he’ll be pleased.

Okay, what’s wrong with this scene as dialogue on the page, over and above its repetition? You can hardly fault this exchange for verisimilitude — it not only is a transcript of an actual conversation, but it sounds like one, literary traits that do not, as I mentioned, necessarily go hand-in-hand — but it’s missing something, right? Any guesses, wild or otherwise?

Give yourself three gold stars if you yelled, “Well, it’s hardly character-revealing, is it? Who are these people as individuals, as opposed to representatives of a collective small-town mentality? And why oh why do we learn so little about Bobby?”

See it now? This exchange might as well have been said by actors, rather than specific people with personal quirks. Granted, as is, it might tell you a little something about the spying capability of my home town’s feared and respected Little Old Lady Mafia, but it doesn’t tell you much about the speakers as human beings, or our relative positions within society.

And if there was a plot (other than to get me married off to someone with whom I might produce more little winemakers, a quest that is ongoing and perpetual), its intricacies are not particularly well revealed by this slice o’life. (But trust me, you don’t want to know more about Bobby. His character strikes me as inherently hostile to development.)

More to the point of this series, the boring bits of this ripped-from-reality dialogue would be significantly more difficult to edit out of a manuscript than a linguistic trope such as my old pal’s “like I said…” Cutting the latter would a particularly easy edit, not only because the writer could simply use the FIND function in word to excise it, but because it would be a pretty sure indicator that the speaker is repeating herself (although interestingly enough, my friend habitually uses this phrase when she ISN’T repeating herself, I notice).

But reworking the exchange above to render it snappy? That would take an almost complete rewrite. Nevertheless, one of the best places for a self-editor to start looking to trim manuscript fat — or even eliminate entire scenes — is generally in scenes taken directly from real life. Most writers cut-worthy include elements in such scenes simply because it happened that way, not because those elements or lines of dialogue add crucial elements to the scene.

To put it bluntly, blandness tends to linger in reality — and that’s potentially problematic at the submission stage. To paraphrase one of Millicent’s most frequent exclamations, via a quote from Nietzsche: “Against boredom, even the gods struggle in vain.”

While I think we can all agree Nietzsche would have made a lousy agency screener — and an even worse agent — his observation might be a good adage to bear in mind while preparing your manuscripts for submission. For one very simple reason: some screeners and contest judges’ maximum tolerance for boredom in a manuscript is well under a minute.

So if you’ve ever heard yourself saying, “Just wait until page 15; it really picks up there,” you might want to give some thought to how to make your submissions more user-friendly for a reader with the attention span of an unusually persistent mosquito. Not that every Millicent, Mehitabel, or Maury would stop reading that quickly — but enough of them would that it just doesn’t make strategic sense to take a chance.

Especially on page 1. Had I mentioned that?

Oh, seven or eight times? Funny, I hadn’t noticed. Keep up the good work!