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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Ta da! Crisis resolved. No roadblocks here.

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

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

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

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

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

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

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

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

Or maybe like this:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

“Why, hello, Betty,” Marjorie said.

“Hello, Margie. How are you today?”

“Fine, thanks. And you?”

“Fine. How are the kids?”

“Fine. How is your mother doing?”

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

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

“Yes. Yes, it does.”

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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



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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Suddenly, a noise came from behind her…

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Author! Author! interviews: a chat with Song of the Crow author Layne Maheu about literary fiction, seven-year revisions, and what to do when the water rises above your head

Sorry about the several-day silence, campers — I’ve been trying to adjust to a new set-up. Since my car crash last July, I haven’t been able to write at a desk, so I had become accustomed to writing my blog posts on a laptop while reclining like an ancient Roman at a feast. When the docs told me this week to stop taking that whole laptop thing so literally, I had to figure out a new way to recline whilst typing. It turns out to be doable, but very, very slow.

What’s that you say? That the point of the advice may have been to stop me from typing altogether? I may not be hearing you correctly, what with my fingers stuck in my ears and all.

Besides, my will to communicate is just too strong. This does, however, seem like a dandy time to post another in what I hope will be a long and productive series of interviews with published authors about the craft of writing and the often rocky road to publication. After the rollicking success of February’s highly interesting discussion of literary fiction with debut novelist Heidi Durrow, I’ve been blandishing all kinds of authors into sitting down to chat about their first books.

Why first books, rather than just their most recent offerings? Well, frankly, I feel that there are already quite a few venues for the latter, but surprisingly few where authors, particularly those with recent debuts, are encouraged to talk about the day-to-day challenges, hurdles, and triumphs of writing, at least at the level of specificity we prefer here at Author! Author! I wanted to talk to writers with interesting voices about how they developed them. And to be blunt about it, I wanted to grill them on your behalf about how they went about landing their agents.

Today’s interview with literary fiction author Layne Maheu will cover all of that, of course. But as the second offering in this series, it seems particularly appropriate to be talking to an author positioned at what used to be universally acknowledged as a crucial point in his career: after having produced a well-received first novel, he is finishing up revisions on his second. We began the interview, not entirely surprisingly, by chatting about the inspiration for his first.