Posted on - No Comments on You look strangely familiar…have we met somewhere before?

You look strangely familiar…have we met somewhere before?

Last time, I suggested that if your novel is thick with named characters, it might be a good idea to make a list of who appears when, so you can see where to cull and who may be combined with whom. And cries of “Madness! Madness!” filled the land.

Now, now — it’s actually a very practical suggestion. Think of it as trying to cast a production of Spartacus with a very small troupe of actors: you probably won’t be able to foist many more duties upon the leads, but the bit players could certainly play multiple roles, right?

Knowing who the players are and in what scenes they appear can also alert you to patterns in where characters tend to pile up in your work in general. If you’re the kind of writer who, for instance, leans toward naming everyone at any given party, you will want to be aware of that predilection before you write your next party scene, won’t you?

Won’t you? Lie to me, if not.

If, on the other hand, you tend to emphasize your protagonist’s loneliness by having other characters engage in banter around him, seeing that pattern manifest on a list may lead you to question whether it needs to happen quite so often in the book to make your point — or with quite so many different people.

It can, in short, alert you to point overkill.

If hell is other people, as Sartre suggests, then wedding and funeral scenes in novels almost invariably reek of brimstone. These events are NOTORIOUS amongst professional readers for introducing entire churchfuls of extraneous characters.

Even when all of the masses are not named individually (although you’d be astonished how often 10 or 20 are), it doesn’t take many lines of physical description or multi-party banter to convey the impression that a small, intimate wedding has a guest list to rival that of Prince Charles and Lady Diana’s nuptials.

Allow me to suggest: if behinds are in pews, it might be a good place to start trimming.

Ditto with coffee shops, bars, class reunions, Ellis Island, airplanes/-ports, and party scenes in general. All of these venues seem to attract single-appearance characters as surely as a red carpet attracts celebrity gawkers.

Was that massive sucking noise I just heard a collective gasp of indignation? “But Anne,” the cast of thousands-mongers cry, “you’re asking me to disembowel the collective identity of modern urban life! How can I describe the complexity of the human environment without enumerating the individuals who are part of it?”

Describe away — and if you’re into enumerating, I’m not going to stop you, although your agent and/or editor may well. All I’m suggesting here is that you not insist on introducing each of the bystanders to the hapless reader as if she were the mother of the bride in a receiving line.

Not only does it tend to get a mite tedious and slow the pace of the narrative to the proverbial crawl, to a professional reader, a group scene where everyone is named down to the last poodle and great-grandfather reads as though it were simply an account of something that actually happened to the author. When the guest lists are long and specific, the jaded reader will think, “Great — when do we get back to the fiction?”

Or the memoir, or the historical account, as the case may be.

Of course, this is not always a fair conclusion, but there is some basis for it: as I mentioned yesterday, when writers lift scenes from real life into their novels, they do tend to include direct one-to-one correlations between the actual people and the fictional ones.

The names may change, but if Aunt Bessie, Aunt Cassie, and odd Cousin George appear in the text so fleetingly that they don’t make an impression upon the reader, it’s a pretty good tip-off to someone who reads a lot of manuscripts that the author is blessed with two aunts and a cousin who might reasonably be expected to buy the book when it is published.

And that is a problem to professional and casual readers alike. Such references, in code or not, can be very amusing for readers familiar with the fine folks mentioned in the book, as well as their kith and kin, but generally speaking, unless a minor character plays an actual role in the plot — as in contributing some action or information that moves the story along — he will not be memorable to readers who do not already know the correlates in question.

You indignant gaspers are getting restive again, aren’t you? “Yes, yes,” you mutter impatiently, and who could blame you? “It’s not the most efficient means of storytelling; I already know that. But I fully intend to rectify that by making Aunt Bessie the gas station attendant in Chapter 47, Aunt Cassie the librarian in Chapter 12, and Cousin George the second corpse who rises from the dead on the honeymoon. Happy now?”

Not necessarily, no. Even if the characters in a crowd scene do appear elsewhere in the book, it can still be pretty tedious for the reader if the narrative engages in a full roll-call. Or even a partial one.

At least when the characters in question are not integral to the action of the crowd scene. Bystanders are not, by and large, memorable to the average reader, but all too frequently, it’s not clear which of the cast of thousands in a scene is the one (or dozen) that the reader is supposed to remember.

If, indeed, it’s important to the plot to remember any individuals among them at all. Even in a memoir, it often isn’t, from a pure storytelling perspective.

And writers, as any editor can tell you, tend to forget that. Every editor in the biz has at one time or another been confronted by an author angrily waving a manuscript in her face and shouting, “What do you mean, where did this character come from? Alice was a guest at Ben’s wedding in Chapter Two, for heaven’s sake!”

Invariably, the irate author is right: the character will indeed have been mentioned by name in passing, as in,

The bridesmaids, Greta, Elaine, and Alice, were dressed in an eye-searing chartreuse that left Ben wondering just what these old friends had done to his bride back in junior high school.

200 pages later, out of those three never-again-mentioned bridesmaids, the author expects the reader to remember Alice.

At the risk of seeming impertinent, why?

“Wait just a minute,” I hear some of you say. “If Millicent finds she’s forgotten who a character is, she has a perfectly easy way to find out — her boss asked that I send a synopsis along with my submission. All she has to do is flip to the back of the packet. Or are you saying that if I have a lot of characters in my opening scenes, I should place my synopsis FIRST in the packet?”

In a word, no — at least, not unless an agency specifies in its submission guidelines that it prefers that order. Long-time readers, chant it with me now: a submitter should always send a requesting agent PRECISELY what s/he asked to see. No more, no less.

Yes, even if she asked for the first 50 pages and your chapter ends a paragraph into page 51.

To which I will add a corollary: any hyper-specific submission guidelines that deviate sharply from the rules of standard manuscript format that an agency might post on its website or an agent might specify at a conference — like, say, specifying that submissions may only be in Helvetica or that they should be bound, both usually no-nos — should be treated as applicable to THAT AGENCY ALONE, rather than to every association of authors’ representatives currently walking the earth.

At least until you’ve done some research on what other agencies are asking to see. Sometimes, an individual preference is just an individual preference.

Aspiring writers often forget that. (And, as always, if you’re unfamiliar with how professional manuscripts differ from printed books or other commonly-scene formats, please see the STANDARD FORMAT BASICS and/or STANDARD FORMAT ILLUSTRATED categories on the list at right.)

If you put the synopsis at the front of your packet, Millicent is just going to toss it aside and go straight to the first page of your manuscript. If dear Millie reads all the way through your submission and likes what she sees, THEN she will read the synopsis.

Maybe.

You’re hoping that I’m kidding, aren’t you? Bizarre but true, typically, not every employee at an agency will take the time to read the synopsis they asked a writer to send prior to sitting down with those first few pages to see whether s/he can write.

Seriously — ask at the next writers’ conference you attend.

There’s a certain logic to this, at least for fiction. After all, if a book made it to the submission stage; presumably, the novel’s premise was deemed acceptable by the query screener or the agent to whom the writer pitched it; the only reason to read the synopsis at the submission stage, then, would be to find out what happens AFTER the last submission page.

And anyway, if Alice’s appearance in Ch. 2 was brief enough, chances are that she won’t have made an appearance in the synopsis the first time around, anyway.

So unless a character is central enough to what’s going on in a scene to warrant development, you might want to consider whisking her out of Millicent’s sight, at least for the time being.

“For the time being?” I hear some ambitious character-generators out there piping hopefully. “Does that mean I can bring Aunt Cassie back elsewhere?”

Sure — just because you take a few (or a few hundred) characters out of your submission draft of a novel doesn’t mean that you can’t reinsert them later in the publication process. There is no law that says that an author can’t offer a stripped-down, swiftly-moving version of her novel to agents and editors — and then, after the ink is dry on the relevant contracts, say to your editor, “You know, I’ve always thought that there should be more bridesmaids in Chapter 2. Like, say, 47. How would you feel about Alice’s being one of them?”

Remember, no manuscript is set in stone until it’s actually in print between covers. (And sometimes not even then.) Keep your options open, keep copies of EVERY major revision of your manuscript, so you can revisit the Alice issue again down the road.

And, of course, keep up the good work!

P.S.: hey, I realized I hadn’t nagged you all about this in a while, but today would be a dandy time to make back-ups of your writing files, wouldn’t it? Especially if you haven’t made another electronic copy since, well, ever?

I hope you never experience the trauma that is a computer meltdown, but I would urge you to make back-ups frequently, just in case. Computer repair facilities see countless writers rending their garments and exclaiming, “But I NEED you to get into my fried hard drive! What do you expect me to do, retype my novel from scratch – and from memory?”

Trust me, you do not want to be one of these people. Make back-ups.

If you’re a PC user unfamiliar with your backup options, intelligent and insightful long-time reader Chris Park has generously wrote an EXCELLENT post on his blog on data loss, back-up solutions, and other nifty save-my-manuscript-from-oblivion ideas — all written in blessedly clear, direct layman’s terms. I would highly recommend its perusal.

Posted on - No Comments on Let’s talk about this: what’s in a name?

Let’s talk about this: what’s in a name?

While we’re on the general subject of character names, let me open a question up to all of you: how do you go about naming your characters? In particular, how do you decide what to name your minor characters — or, indeed, figure out whether you should name them at all?

And once you have christened them, do you ever change their monikers, or are they blessed with their original names for life? Are you a lover of the 18th-century practice of naming characters in accordance with their primary characteristics (the punishment-happy Mr. Thwackum in TOM JONES springs to mind), or do you eschew it as too broad a wink at the reader?

Also, is it ever permissible to use real names — or, in a memoir, to change names to protect the innocent and/or guilty?

I’ve long suspected that every writer cherishes a different philosophy on the subject, so I’m genuinely curious. Thirty years ago, writing teachers used to tell their students routinely that they should just open up a phone book and start searching, but how has that mutated in the Internet age? Is it even a good idea to use a real person’s name?

Your thoughts?

Posted on - No Comments on I said YES. Wait, you want me to say no? Okay, then it’s no — and other less-than-stellar argumentative techniques of fictional characters.

I said YES. Wait, you want me to say no? Okay, then it’s no — and other less-than-stellar argumentative techniques of fictional characters.

I was thinking about you, dear readers, earlier today at an opera rehearsal — hey, I move in some pretty rarified circles. Specifically, I found myself musing about our recent discussions of plausibility in interview technique — as the singers belted their characters’ deepest and darkest toward the back wall of the auditorium. I must have been giggling under my breath, for in the middle of an aria, my SO leaned over to me and whispered, “They can’t have been reading your blog lately.”

Obviously, the composer hadn’t — not entirely surprising, as the music in question first hit the pop charts in the middle of the 17th century; I doubt its author blog-surfed much.

The moment I got home, I rushed straight to my computer and started rifling through my archives — a practice I highly encourage; there’s quite a bit of information stacked in the back room of this blog, you know — because I had a distinct recollection of having written on this very topic sometime last year.

As it turned out, I was right: my last spring’s opera intake included sitting through a classic bad interview scene. Take a listen:

The brave knight Ruggiero, ensnared by the love spells of the evil sorceress Alcina (who had a nasty habit of turning her exes into trees; opera gives one a lot of room for imaginative touches), has deserted both his fighting obligations and his warrior girlfriend, Bradamante. So another sorceress, Melissa, turns herself into an image of Ruggiero’s father, Atlante, to try to free him. Dressed as Atlante (and turning from an alto into a baritone for the occasion, a nifty trick), Melissa berates Ruggiero for lying around in sensual bliss when there’s work to be done.

A single three-minute solo later, Ruggiero’s mind is changed, with no argument from the big guy himself: he is free from the spell, and goes on to bellow some extraordinarily nasty insults at Alcina while Punchinello dances around with a squid.

You had to be there, I guess. It was quite entertaining; the squid was played by a hand puppet. It was also not very good storytelling — and even worse character development.

This type of persuasion in an interview scene — where the protagonist’s mind is changed on an issue about which he is supposedly passionate simply because someone TELLS him he’s wrong, without engaging in convincing argument — occurs in novel submissions more often than you might think. Many a protagonist who is downright tigerish in defense of his ideals elsewhere in the book is positively lamblike when confronted by a boss, a lover, a child, etc. who points out his flaws.

And that, unfortunately, makes the conflict seem much less important than if the characters argue the pros and cons at least a little. Usually, the result is a more compelling scene — and better character development for the arguers.

Oh, heck, I’ll go out on a limb here: it’s almost always better storytelling.

Why? Everybody chant it together now: because conflict is more interesting in a scene than agreement. Unending harmony, as delightful (and rare) as it may be in real life, can be a real snooze-fest on the page.

Even the injection of just a little good, old-fashioned passive-aggression can ginger up a scene no end.

Nor does being easily persuaded, non-confrontational, or generally — brace yourself — nice necessarily render a protagonist (or any other character) more likeable to the reader. No, not even if the reader happens to enjoy the company of such sterling souls in real life.

Why, you cry? Because endlessly making nice tends to kill dramatic tension dead, dead, dead.

That seems to come as a surprise to many aspiring writers, judging by the number of first novels and memoirs where the protagonist bends over backwards never to offend anyone — especially common in manuscripts where the protagonist happens to be female, I notice. Butter wouldn’t melt in some of these ladies’ mouths, as the saying goes.

Which pretty much inevitably results in either a relatively conflict-free plot or a passive protagonist who stands on the sidelines while the less scrupulous (and more interesting) characters act.

To give you some time to digest that particularly bitter little pill — don’t worry; I shall be returning to the problems of the passive protagonist next week — allow me to turn my opera example to another use: to show yet another way in which a screener might read an opening scene differently than another reader.

This object lesson should be a bit easier to swallow. Take this little test: quick, without re-scanning the paragraphs where I glossed over the opera’s plot, try to name as many of its characters as you can.

How did you do?

I originally mentioned six, but don’t be hard on yourself if you only came up with one or two. Most readers would have experienced some difficulty keeping all of those sketchily-defined characters straight.

Heck, seeing them introduced en masse like that, I would have trouble remembering who was who, and I’ve seen the opera!

Introducing too many characters too fast for any of them to make a strong impression upon the reader is EXTREMELY common in the opening few pages of novel submissions. Indeed, sometimes there are so many people lurching around that the reader does not know for several paragraphs, or even several pages, which one is the protagonist.

Why might confusion on this point be problematic? In a word: Millicent.

Agency screeners read fast; if they aren’t sure what’s going on and who the book is about by the middle of page 1 (which is, unfortunately, how they would tend to diagnose the paragraphs above), they generally stop reading.

To use Millie’s favorite word: next!

So strategically, you might want to limit the number of characters introduced within the first couple of pages of your submission. If you’re in doubt about how many is too many — no, Virginia, there is no hard-and-fast rule — there are a couple of tests I like to use.

The first, and the simplest, is a modification of the one I used above: hand the first page to a non-writer. (NOT a relative, lover, or someone with whom you interact on a daily basis, please; these folks’ desire to see you happy may well skew the results of the test.) Ask her to read through it as quickly as possible. As soon as she’s finished, reclaim the manuscript. Then take her out to coffee and ask her to tell you who the main character is and what the book is about.

Why did I specify a non-writer, you ask? Because writers tend to be unusually good at absorbing character names; the average reader is not. Thus, the latter is a better barometer for submission purposes, at least for this particular issue.

Seem counter-intuitive? Think about it: your garden-variety agency screener scans far too rapidly, and reads far too many submissions in a given day, to retain the name of any character who has not either been the subject of extensive description — which, as we’ve been seeing over the past few days, can be problematic in itself — or a mover or shaker in the plot.

Oh, look: the question of protagonist passivity has popped its winsome little head out of its gopher hole again. Can’t imagine how that happened.

I sense some discomfort out there, don’t I? “But Anne,” some intrepid submitters protest, “weren’t you telling us just the other day that professional readers resent having things over-explained? Assuming that they’re smart enough to follow a complex plot, wouldn’t they be able to remember any character I’ve named? After all, even if Millicent forgot who Nicodemus was by the bottom of page 5, she’d merely have to flip back to page 1 to remind herself.”

Oh, I’m glad you asked this question, intrepid submitters. If you take nothing else from today’s post, cling to what I’m about to say next with the tenacity of an unusually stubborn leech:

In preparing ANY manuscript for professional submission, make it your mission to assure that a screener NEVER has to flip back to remind herself who was who or what just happened.

The simple fact is that very few professional readers will take the time to do it. Our old pal Millicent has a lot on her mind, you know — like that too-hot latte that just burned her full pink lip. (You’d think, after how long I have been writing about her, that she would have learned by now to let it cool, wouldn’t you? But that’s an agency screener for you: time is of the essence.)

No, but seriously, folks, most aspiring writers make the mistake of assuming that their submissions will be read slowly, with meticulous care. But Millicent might have 50 submissions to screen between now and the end of the day — you do the math.

The other test for a reasonable character-to-page ratio — and perhaps a better one, as it is also useful to see how well your storytelling skills are coming across: hand the entire first scene to that non-writer and ask her to read it as quickly as possible, to reproduce Millicent’s likely rate of scanning. Then take away the pages and talk with her about something else entirely for ten minutes.

In minute eleven, ask her to tell you the story of that first scene with as much specificity as possible. Note which names she can and cannot remember — if she’s like 99% of skimmers, she will probably remember only the two primary ones.

After thanking her profusely, sit down with your list of passed-over names and the manuscript: do all of these folks really HAVE to make an appearance in the opening scene? Could some of them be consolidated into a single character, to reduce the barrage of names the reader will have to remember?

Or could any of them be there, but not mentioned until later in the book, where the protagonist encounters that character again? (A simple statement along the lines of, “Hey, Clarence, weren’t you one of the thugs who beat me to a pulp last month?” is usually sufficient for later identification, I find.)

Alternatively, are some of the characters mentioned here for purely photographic reasons? In other words, is their being there integral to the ACTION of the scene, or are the extraneous many named or described simply because they are in the area, and an outside observer glancing at the center of action would have seen them lurking?

In a screenplay, you would have to mention their presence, of course — but in a crowd scene in a novel, describing the mob as monolithic can have a greater impact. For instance, which sounds scarier to you, Mr. Big threatening Our Hero while surrounded by his henchmen, Mannie, Moe, and Ambrose — or surrounded by an undifferentiated wall of well-armed baddies?

Personally, I would rather take my chances with Ambrose and Co. than with the faceless line of thugs, wouldn’t you? My imagination can conjure a much scarier array of henchmen than the named three.

I know, I know: when you create a novel, you create the world in which your characters live. And that world is peopled. But in the interest of grabbing an agency screener’s often mercurial attention, would a smaller cast of characters, at least at the outset, render your book more compelling?

Sometimes, less is more. Or at any rate, fewer. Keep up the good work!

Posted on - 2 Comments on A beautiful picture — and a few tips on increasing your protagonist’s interview skills

A beautiful picture — and a few tips on increasing your protagonist’s interview skills

Isn’t that photo GORGEOUS? It’s by one of my favorite art photographers, Lana Z Caplan, from her new book, Sites of Public Execution. Here’s a description:

SITES OF PUBLIC EXECUTION: Photographs and stories of former sites of public execution around the world.

Paired with interesting facts and stories of the events that took place in these public places, sepia-toned photographs, shot in Beijing, Paris, London, Florence, Rome and Massachusetts, present the contemporary appearances of locales used for hangings, beheadings, and burnings, some in the transient fury of revolution, some in long-term state-sanctioned spectacles.

For a PDF preview of the book, please visit Lana’s website.

Normally, I wouldn’t post an announcement about a book of photography here on Author! Author!, but Lana’s work moves me deeply — so much so, in fact, that I have one of her pieces hanging where I can glance up at it frequently while I write. We met at an artists’ colony several years ago; then, the provocative work-in-progress hanging in her studio made me downright giddy.

And yes, I HAVE been posting quite a few announcements of new releases lately — for some reason, I know many, many talented people bringing out books this spring. I can only conclude that publishing houses have started weighing connections to me heavily in their considerations.

Or perhaps I just know a heck of a lot of writers. In any case, this spring has certainly enriched my bookshelves, let me tell you.

Okay: on to the topic du jour.

As we’ve been going through various common narrative problems, I’ve noticed something: either due to my excessive saintliness or a desire to save the best, if not for last, at least for later in this series, I’ve been concentrating for the most part upon avoiding some of the more notorious agency screeners’ pet peeves, rather than merely upon what tends to annoy me in a text. For the next week or so, however, I have decided to cut loose and lay bare the narrative problems that make me foam at the mouth, professionally speaking.

That’s right: for the next little while, it’s going to be all about me, me, me.

Today, I’m going to concentrate upon one of my all-time favorite kinds of expendable text: the kind of dialogue that results from a protagonist’s being a really, really poor interviewer.

I heard that tittering out there. Seriously, a protagonist who doesn’t ask good questions — or necessary follow-up questions — can slow a novel, memoir, or creative nonfiction book to a limping crawl.

Why does it matter how skilled a questioner the protagonist is, you ask, unless s/he is a journalist of some sort? Simple: many, many, MANY novel plots require their protagonists to learn something that they do not already know – and, more importantly, that the reader does not already know.

Who killed the Earl of Cheswick, for instance, or why so many people are interested in that darned ugly Maltese Falcon. In the pursuit of answers to these and other burning questions, the protagonist is, necessarily, frequently forced into the role of interviewer, trying to extract information from other characters.

What a pity, then, that protagonists have a nasty habit of slowing down the collective search for truth by neglecting to promising lines of questioning, failing to follow up on something just said, or just plain being too polite to ask the questions the reader is dying to ask herself, but can’t.

It tends to run a little something like this:

“I swear,” Reginald claimed, one hand over his heart and the other hovering over the graying head of his sainted mother, “that’s all I know. Please don’t ask me any more questions.”

Janet drummed her long piano-player’s fingers on the rich mahogany tabletop. Her every instinct told her that he was not telling the truth — or at least not the whole truth. The very fate of Western civilization rested upon her solving this puzzle before midnight tomorrow.

She stood and offered her hand to the old woman. “Charming to meet you, Mrs. Fezziwig. You must come to my house for brunch sometime. I hate to boast, but I make extraordinary deviled eggs.”

Reginald detached their clasped hands so quickly that Janet’s hand burned. “Must you go so soon? Here’s your coat — I’ll walk you down to the cab stand on the corner before I release the vicious dogs that prowl our estate at night to discourage post-midnight visitors.”

Janet fumed, but what could she do? “Goodbye,” she called back from the hallway.

“Don’t forget to sprinkle your eggs with paprika,” she could hear Mrs. Fezziwig bellowing after her. “I love paprika.”

Why would an exchange like this prove annoying to a professional reader like me? Mostly, because it’s a lost opportunity for interesting conflict — rich potential for drama presented then abandoned by the narrative for no apparent reason.

Actually, writers often have what they consider pretty strong reasons for rushing their protagonists away from conflict. Trying to make them more likeable to the reader by demonstrating common courtesy, for instance, or forcing them to work harder to learn the Awful Truth.

Or wanting to stretch the novel from 100 pages to 200. My point is, regardless of the motive, this practice tends to render those of us who read manuscripts for a living a trifle impatient.

Why? Well, in essence, the protagonist becomes the reader’s surrogate in ferreting out information; as a reader, it’s not as though I can jump into the storyline, grab a microphone and tape recorder, and start grilling the usual suspects. After awhile, an inept interviewer can start to annoy the reader by being a poor tour guide to the plot.

I sense some uncomfortable squirming out there, don’t I? “But Anne,” I hear some of you suspense-lovers cry, “a too-good interview would give the whole plot away! What about building tension?”

You have a fine point, suspense-mongers: revealing the truth in slow increments is one way to create suspense. It’s such a fine point that I’m going to spend most of the rest of the post talking about how to do just that.

However, before I do, allow me to observe that making information unavailable through the simple expedient of not having the protagonist ask anyone about it tends to fall very, very flat with readers.

Why? Well, while readers do like to second-guess what’s going to happen next, trust me, it’s going to make your protagonist substantially less likeable if the reader keeps thinking, “Ask about the elephant in the room, you fool! Don’t just walk away!”

A professional reader — such as an agent, editor, contest judge, Millicent, or yours truly — is likely to react with even less sympathy, because a disproportionate percentage of submitted manuscripts create suspense by DELIBERATELY withholding information from the reader.

As in details that the protagonist already knows. We pros like to call this creating false suspense.

The most famous example, of course, is the sleuth from whose perspective the reader has viewed the entire case suddenly stops communicating his thoughts on the page — then gathers all of the still-living characters in the nearest drawing room (there always seems to be one handy, doesn’t there?) and announces, “You may be wondering why I asked you all here…”

Darned right we’re wondering — the reader wants to know why you suddenly withdrew your confidence from him, Mssr. Poirot.

Don’t start feeling too smug, those of you who write something other than mysteries — protagonists’ playing interviewer role is hardly limited to that genre. Think about it: it’s rare that any novel — or, indeed, any book with a plotline — does not contain at least one scene where somebody is trying to extract unknown facts from someone else.

Queries ranging from “Does that cute boy in my homeroom REALLY like me, Peggy?” to “Where did the cattle go, Tex?” aren’t just dialogue filler — typically, they call for character-developing and/or plot-satisfying responses. In fact, it’s a fair bet that any scene that contains one character exclaiming, “What happened?” is the precursor to an in-text interview.

Are you already warming up the highlighting pens, in anticipation of my ordering you to aim them at the interview scenes in your work? Good idea. Such scenes are often worth flagging for revision, because they are so very hard to pace well.

This is true, incidentally, even when the information being revealed is inherently exciting (“If you do not get across the bridge before sunset, giant bats will eat you, Reginald.”), emotionally revealing (“The reason I turned to piracy is – YOU, Father!”), or downright necessary to make the plot work (“Yes, George, although I haven’t seen fit to mention it once in the course of our sixty-two-year marriage, I have always dreamed of going spelunking!”).

Why? Well, when the point of a scene is for information to be revealed to the protagonist (and thus the reader), many writers become so focused upon that data’s being revealed entertainingly that they run to the opposite end of the reticence spectrum and have characters (secondary ones, usually) blurt out the necessary information practically BEFORE the protagonist asks for it.

This, too, is an interviewing problem — and one of the greatest sappers of narrative tension the world has ever known.

Many, many submissions where secrets that have been kept successfully for 25 years burst out of the mouths of the secretive practically the moment that the protagonist walks into the room. So why, the reader is left to wonder, if these secret-keepers are so willing to spill their guts to the first person to ask a direct question, has this information not been revealed before?

The apparent answer: because the plot required that it NOT be revealed before. And that, my friends, is never a sufficient motivation.

Or, to be blunt about it, the narrative should not make it EVIDENT that the hidden information would have been laughably easy to get all along, if only someone had thought to knock on the door of the only person who actually observed that the setting of that fire a decade before that shaped the entire town’s subsequent history.

You can just imagine all of the townsfolk slapping their heads in unison behind closed doors after that perky newcomer digs up the arsonist’s name in a single afternoon: why oh why didn’t it occur to any of us to ask Aunt Bessie why her nephew kept the garage stuffed to the rafters with matches?

Surprisingly often, the protagonist doesn’t even need to ask a question to elicit the revelations of tremendous secrets from minor-but-essential characters. Often, all she has to do is show up, and the legendary recalcitrant loner begins singing like a Rhine maiden: “So, Mr. Bond, now that I have you tied to that chainsaw, it’s time for me to reveal my evil plan…”

In many instances, the protagonist is reduced to helpful nods and murmured promptings on the order of, “Oh, really?” while the imparter engages in a soliloquy that would make Hamlet himself start looking at his watch.

A novel, the last time I checked, was not an opera: in real life, most people do not go around shouting out their deepest, darkest secrets at the top of their lungs to relative strangers.

And that’s what makes secrets interesting, right? In real life, it is actually rather difficult to convince folks to cough up the truth — partially because after one has lived with a lie long enough, one often starts to believe it oneself.

When you are trying to increase the tension throughout a novel, recognizing that truth is often hard to elicit is a powerful tool, one that can revolutionize how you handle interview scenes. They do not need to be essentially one-sided information dumps they so often are.

Instead of regarding them as just necessary exposition-through-dialogue, to be rushed through quickly, why not use the opportunity to introduce some conflict? Or heck, if you really want to get adventurous, some character development?

How? By making the information-imparter more reluctant — which automatically both forces the protagonist to become a better interviewer and renders the information-seeking process more difficult.

Automatically, this small switch makes the scene more interesting, by introducing viable (if brief) conflict between Character A (who wants to learn something) and Character B (who has very good reasons not to pass on the information).

A couple of fringe benefits: your protagonist will come across as smarter, more active, and more determined — and the information elicited will seem more valuable. As convenient as a suddenly-garrulous secret-hider is to the plot, too-easily discovered information runs the risk of seeming…well, ordinary.

So eschew the magic wand that turns the timid secretary who saw her boss murdered 15 years ago and ran off to live in a cave to avoid talking to the police into the operatic diva belting out precisely the information she has devoted to her life to hiding, simply because someone finally asked her a direct question about it. Banish the clue that only required someone opening the right cupboard drawer to find. Give your protagonist some killer interview skills.

Take, in short, a page from the time-honored pirate’s manual: make your treasures hard to dig up. The more difficult they are to find, the more engaged the reader will be in the search process.

More interviewing tips follow next time. In the meantime, keep up the good work!

Posted on - No Comments on Is that a plot flare I see before me, or did a line of text just spontaneously combust?

Is that a plot flare I see before me, or did a line of text just spontaneously combust?

Over the past couple of posts, as I was making the case for setting up necessary character plot development well before it is needed to explain what’s going in a particular scene — or, heaven help us, the climax of the book — I made passing reference to what I like to call Plot Flares, an early screaming indication that something specific is going to happen later in the story.

Except, I now notice, I never managed to call them by name — so much for my clever plan to refer back to the concept a week or two hence, eh? And now that it occurs to me to check, I realize that I haven’t actually written a post on Plot Flares since sometime in 2006.

This is one of the dangers of blogging so much, you know: the archives start to blur in the blogger’s mind. I’ll be writing along, minding my own business, when all at once a side issue pops to mind. “Oh, I don’t need to attend to that now,” I mutter to myself, resolutely pushing it to the back of my mind for another year. “I blogged about that only a couple of months ago.”

Except it will turn out to have been a couple of years ago. So if I start throwing around terminology more recent readers don’t recall, please don’t hesitate to ask what the heck I’m talking about, okay?

So: plot flares. Once again, this is a phenomenon familiar to all of us from movies: the eventual startling plot twist is revealed in some small way within the first twenty minutes. If the heroine is going to have to shoot the villain at the climax as her Own True Love lies bleeding and weapon-free, for instance, she will almost invariably make a statement about her (a) loathing for guns, (b) aversion to violence, and/or (c) having witnessed some incredibly graphic murder during her formative years during the first act.

Ostensibly so we poor viewers can understand why anyone might have an aversion to, say, picking up a gun and shooting someone in cold blood or some other hard-to-grasp concept like that.

In novels, creative nonfiction, and memoirs, foreshadowing of the denouement often happens within the first 50 pages — or even the first chapter. Heck, it’s not all that uncommon for an actual SCENE of the climax to open the book as a prologue, with the plot jumping backward in time immediately thereafter to figure out how our hero ended up there.

Or, to put it in cinematic terms: “Rosebud.”

From the author’s POV, these hints are generally subtle, mild foreshadowing of events to come. As character development and background, small hints are often advisable, or even unavoidable. If these hints aren’t AWFULLY subtle, though, they can give away the rest of the book, deflating suspense as surely as helium comes out of a balloon when you jab a needle into it.

And to professional readers, who see every plot twist in the book, so to speak, on a literally daily basis, a poorly-done foreshadowing hint glows in the middle of a page like a flare set up around a midnight highway accident: don’t go there.

There are, of course, the classics common to both the silver screen and the printed page: if the female lead faints or mentions putting on weight, she’s going to turn out to be pregnant; if any man announces that he’s counting the days until retirement, he’s going to be killed (and, heaven help us, “Danny Boy” will be played on the soundtrack); if our hero is a sad guy, he will inevitably turn out to have had a beautiful (and often, in the flashback, silent) wife and possibly cherubic child who were slaughtered before his eyes while he watched, helpless.

Pathos, pathos.

And it’s not just lowbrow entertainment that embraces this strategy. These clichés transcend genre or even writing quality: that last example about the dead wife and child was the backstory for both half the action films Charles Bronson ever made and the Sidney Poitier character in GUESS WHO’S COMING TO DINNER (courtesy of a car crash), as well as for the Antonio Banderas character in ONCE UPON A TIME IN MEXICO (courtesy of Bad Men with Guns). It gets around.

The list of such common plot flares is practically endless. In a television detective story, the actor with the best résumé (who therefore cost more than the other players) will turn out to be the murderer; so will Ray Liotta, John Malkevich, Ice-T, and/or Christopher Walken — unless, of course, the directors have elected to incorporate what I like to call the Liotta Lapse, where they use an actor so habitually typecast as the guy you’re SUPPOSED to think did it, so the twist can be that someone else did.

Actually, I’ve always found it rather amusing that people in the movie industry continue to think that we’re all surprised by plot twists set up three miles in advance — in manuscripts, these cliché set-ups tend to be dismissed in the first read-through. I once attended a memorable preview of a forgettable thriller where one of the actors, unfortunately, had shown up to speak to the audience. A fairly well-known TV actor, he swore up and down that the first time he had read the script, he was stunned by the eventual plot twist.

When several audience members laughed uproariously (including, I’ll admit it, your humble narrator), the actor was unwise enough to ask us why. I spoke up: “Because ten minutes into the film, someone mentioned that the guy who turned out to be the murderer ‘had a tough childhood.’ The screenwriter might as well have erected a road sign with a big arrow that read ‘psychopath here.'”

The actor looked at me as if I had just spontaneously derived the theory of relativity from scratch on the spot. “I didn’t catch that,” he claimed, straight-faced.

Now, because I prefer for the sake of the republic to assume that most adults are reasonably intelligent, I assume the actor was lying about his own perceptions in order to protect his film from the all-too-deserved charge of predictability. For such a cause, I can cut him some slack.

However, in book form, agents, editors, and contest judges tend not to cut the author of a manuscript any slack at all. Remember, these are not charitable readers, as a rule, but business-oriented ones. They’re looking for plot twists that are genuinely surprising, not set up by plot flares a hundred pages in advance.

And that’s a problem, because most aspiring writers just LOVE foreshadowing.

Keep your foreshadowing, when you use it, SUBTLE — which means, of course, that unless you’re writing comedy, you might want to avoid having characters say of your politician protagonist in early childhood scenes, “That Harry! Some day, he’s going to be president.”

Um, can anyone out there give me even one good reason that a professional reader like me SHOULDN’T regard this as a glaring instance of telling, rather than showing?

Because it is, to my eye: the author has chosen to tell the reader point-blank that Harry has the qualities that would lead one to expect him to be president, rather than showing him exhibiting the individual characteristics through action.

Ultimately, that’s often the writerly motivation for inserting plot flares, I think: the author doesn’t trust that the reader is going to be able to figure out the irony…or the pathos, or the twist to come. Instead, try letting the circumstances lead naturally to dramatically satisfying conflicts and resolutions, rather than sending up plot flares every few pages to make sure that the reader is following along with the point.

As a writer, I have to assume that every one of my potential readers is as sharp as I am at picking up those clues. Admittedly, I was the person in the theatre who whispered to my date fifteen minutes into THE SIXTH SENSE, “Why aren’t any of the adults consulting with Bruce Willis about the kid’s case? Totally unrealistic, either in the school system or with the parent. He’s gotta be a ghost,” so we’re talking a rather high bar here, but I like plot twists that make readers gasp ALOUD.

If the reader’s been alerted by a flare, that gasp is never going to come, no matter how beautifully the revelation scene is set up. At most, the reader will have a satisfied sense of having figured the twist out in advance.

Keep it subtle, my friends. If there’s a cat in that bag, keep it there until it’s startling for it to pop out. There’s no need to have it meowing all the time first.

Keep up the good work!

PS to those of you currently residing in California: FAAB Joel Derfner is going to be giving readings from his new book, SWISH, in the week to come. If you live in the LA or San Francisco areas, drop by and say hi. Because, really, the primary reason for anyone to go to an author reading is to talk about ME, right?

Seriously, Joel has a lot of interesting things to say about the publication process, so this would be a tremendous opportunity to ask questions not only about how to become the gayest person ever, but about writerly concerns.

Monday, May 19, 7:30-9:00 pm — West Hollywood, CA
A Different Light, 8853 Santa Monica Boulevard

Tuesday, May 20, 7:30-9:00 pm — Long Beach, CA
Barnes & Noble, 6326 East Pacific Coast Highway

Thursday, May 22, 7:30-9:00 pm — San Francisco, CA
Books, Inc. in the Castro, 2275 Market Street

Posted on - No Comments on So we beat on, boats against the current, borne back ceaselessly into the past

So we beat on, boats against the current, borne back ceaselessly into the past

  

Yes, Fitzgerald fans, you have guessed correctly: today, we shall be delving into the wonderful world of the flashback, with special emphasis on avoiding redundancy. Sounds like a good time, eh?

Before the screen begins to go wavy, kudos to reader Sharon for reminding me yesterday that there are in fact cliché-finding programs, as well as websites that will tell you if a particular phrase is (or is close to) a cliché. I tend to downplay the usefulness of such tools, out of fear that they will tempt writers to use them as a substitute for — chant it with me now, everybody — reading a manuscript IN ITS ENTIRETY, IN HARD COPY, and OUT LOUD before submitting it to anyone even vaguely affiliated with the publishing industry.

See how hypnotic repetition can be?

Implemented judiciously, though, cliché-spotting programs can be very helpful indeed, particularly for writers who are not native English speakers or native speakers who do not happen to have grown up in Manhattan or LA. Or at any rate, not in a TV studio, sound stage, or publishing house in either.

As if that weren’t enough help in the self-editing department for one post, public-spirited long-time reader Chris Park, he of the impressive PC skills, has been kind enough to cobble together a shareware program for writers, specifically intended to catch repetition in a text. It’s called Manuscript Analyzer, straightforwardly enough, and because Chris is a generous guy, you may download it for free from his website.

Chris, I am delighted to report, will also have an excerpt from his latest novel, ALDEN RIDGE, used as an example of fine storytelling in Chris Roerden’s soon-to-be-released book on, you guessed it, self-editing, DON’T SABOTAGE YOUR SUBMISSION. Congratulations to Chris — and to Chris, too, while we’re at it!

Okay, now the screen may begin to go wavy.

In my last installment on self-editing, I went to town on the twin dangers of factual redundancy intended to remind readers of salient points (“As I mentioned back in Ch. 2, Maude, I stand to inherit a hefty chunk of change when my Uncle Mortimer dies.”) and screen clichés that have made their way into real life and vice versa (“Say ‘ah,'” kindly Dr. Whitehairedman told the child.). As I pointed out, both species are problematic in submissions, because they are so common.

Translation: professional readers get really, really tired of seeing examples of them. (And your garden-variety cliché-finder program is only going to catch the latter, please note.) But both types of repetition also tend to be, I am happy to report, some of the easiest sentences to cut.

And if you’re like so many aspiring writers in the current market — you know, the ones who clutched their hearts instinctively the first time they heard that a first novel over 100,000 words (estimated — and if you don’t know how to do that, please see the WORD COUNT category at right) is much, much harder for an agent to sell than one that, well, isn’t — this should be very good news indeed.

Because, contrary to popular belief, trimming a manuscript need not necessarily involve cutting entire scenes. Believe it or not, it can be done line by line.

Yes, really. Seriously, I’ve cut 50 pages out of a 400-page manuscript this way.

Redundant lines 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 it 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, try to figure out how much could be cut 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 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. “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 his sawed-off shotgun. “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.”

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, and the suggestion that he would might conceivably pull a well-read reader out of the story; I give you that. But 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:

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, who was standing nearby.

“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 231, a substantial cut obtained through the simple expedient of removing the movie clichés (the double cigarette bit is straight out of the Bette Davis vehicle NOW, VOYAGER) and unnecessary repetition.

Do I see some hands in the air out there? “But Anne,” I hear some of you ask, and rightly so, “was it really safe to cut that much? How did you know, for instance, 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. Like a joke explained after it is told, character development presented as explanation of what someone has just done tends to be substantially less effective than presenting the relevant info earlier in the book, than allowing the reader to recall it at the proper moment.

Makes the reader feel smart, that does.

Think about it: a reader’s understanding of a complex character (or situation, for that matter) doesn’t really need to come in a single lump, does it? Isn’t the reader likely to develop a deeper sense of who the person is if the puzzle pieces are revealed in small shown-not-told increments?

By this logic, the micro-flashback should be cut — or at any rate minimized. If the Colorado rapids scene did happen earlier in the book, the micro-flashback here would be redundant; if it did not, the micro-flashback is not memorable enough in itself to make a lasting impression upon the reader to deserve retaining.

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 flares telling the editor what needs to be done to improve the manuscript. As we saw yesterday, they are often little editors, jumping up and down in the text, shouting at the tops of their tiny lungs, “Show, don’t tell!”

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.

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. Everyone seated comfortably? Here goes:

Think of your draft as a wonderfully immense bouquet, stocked with handfuls of 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 the bouquet is 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 with the most common flower. Pull out half of the daisies; a few are nice, but handfuls make the daisy point a bit more often than necessary.

Where to begin? How about with your favorite phraseology and sentiments?

If I were editing Scott Fitzgerald’s work, for instance, I might scan first for beautiful-but-misunderstood heroines staring into nearby mirrors and moaning things like, “I’m so beautiful — why can’t I be happy?” It’s sort of an interesting statement the first time one reads it (if only to provoke the question, “Would any real woman actually SAY that?”), but it occurs something like 17 times throughout his collected short stories.

This is what the literary criticism people call a trope; professional readers call it by a harsher name: redundancy.

Either way, I’m thinking that 16 of Fitzgerald’s iterations could go. Back to our bouquet metaphor.

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.

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

If you apply a truly diligent eye, you may well find that a single, well-developed past scene inserted early on will replace scores of micro-flashbacks down the line.

It happens. All the time, in fact.

Like a good joke, motivation goes over better with the reader if it can be presented cleanly, without excess in-the-moment explanation. Bear that in mind as you revise, and keep up the good work!

Posted on - No Comments on Writing with teeth…or at least with gums

Writing with teeth…or at least with gums

The beast prior to the procedure

I meant to post yesterday, honest I did, but I couldn’t drag myself to the computer because of an overwhelming sense of guilt. Remember that shelter kitty we adopted last fall, to keep me company while I was lolling on the couch with mono? The one with the past that would make Charles Bukowski turn pale? Well, it turns out that he (the kitty, not Bukowski) had a set of teeth that imply that he spent his kittenhood ingesting crystal meth on a daily basis.

We’re relatively sure that he didn’t, but pretty much all of his front teeth had to go anyway. Thus my Friday o’ Guilt.

Actually, the kitty seems to be taking it all better than I am on this suddenly summer-like spring day:
he’s raring to go; I’m walking around apologizing to him every fifteen minutes.

Oh, no: I inadvertently used the evil phrase, the one involved in my first A CLOCKWORK ORANGE-like aversion therapy for repetitive phrase use. Pardon me, everybody…my vision is going wavy…

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.

So there I was, all eyes and braids, holding my mother’s hand while my father watched my older brother go on D and E ticket rides, waiting in a queue of inexplicable length to cruise around an ersatz London with Peter, Wendy, and the gang. As each ship-shaped (literally) car took a new crew of tourists into the ride itself, Peter’s voice cried out, “Come on, everybody, raring to go-o-o-o!”

Three feet forward. “Come on, everybody, raring to go-o-o-o!”

Six more feet. “Come on, everybody, raring to go-o-o-o!”

Tears have by now come to my mother’s eyes, but we’re too committed to the line to back out now. “Come on, everybody, raring to go-o-o-o!”

After about five minutes of listening to that annoying voice 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.

And that, my friends, is how one grows up to be an editor: howling, “Oh, God, not that same phrase AGAIN!”

Yes, I know: I’ve used this example before here, but I don’t think most writers have any idea just how much word, phrase, and even concept repetition grates on professional readers and contest judges. Fingernails on a chalkboard doesn’t even begin to describe it.

But it makes the average pro want to hide under the bed like a cat threatened with a visit to the vet — and, since folks like me are trained specifically to catch redundancies a hundred pages apart, even a single repetition can sometimes send us diving bedward.

Did some of you out there just go pale? Are you perhaps thinking of my last post, where I mentioned that readers do not necessarily remember every detail about every character?

Good; that means you’ve been paying attention.

For those of you whose blood pressure remained normal, let me disturb it: character trait redundancy is really, really common in submissions. Why? Well, for precisely the reason cited above — fearing that readers may not recall important plot points or characteristics, many aspiring writers repeat such information throughout the book.

How common is this practice? Well, let’s just say that most of us who read for a living (and, I suspect, for most who review movies for a living as well) see the second instance and say immediately, “Oh, okay — THAT fact is going to be crucial to the climax.”

The best way to avoid engendering this reaction, as I suggested last time, is to introduce the relevant facts or characteristics in such a vivid way the first time around — showing them, perhaps, instead of simply telling the reader about them — that the reader may be safely trusted to recall 300 pages hence that the protagonist’s sister is allergic to the beets that are going to kill her on p. 423.

Gee, who saw THAT coming?

Did that sudden stabbing sensation in my back mean that some of you found that last observation a trifle harsh? “But Anne,” the repetition-fond point out, “readers honestly do forget details — my first reader/writing group/my agent/my editor keeps writing in the margin, ‘Who is this?’ when I reintroduce characters toward the end of the book, or even, ‘Whoa — this came out of nowhere!’ when I’d thought I’d laid the groundwork in the first third of the book. I’m just adding the repetition to address these concerns, because, frankly, unless the reader has that information, the conflict loses some of its oomph.”

You could do that, repetition-mongers, but I would translate this feedback differently: if your first readers are not recalling certain salient facts introduced early in the book by the time they reach the closing chapters, isn’t it possible that the earlier introduction is at fault?

My first response would be to rush back to the first mention of the information in question to see if it is presented in a memorable manner. Or if, as we discussed last time, the reader is presented with so much information that the important bits got buried.

Actually, it wouldn’t be a terrible idea to go back and double-check anytime you notice yourself repeating information. Is there a reason that you’re assuming that the reader won’t remember it if it’s mentioned only once?

This strategy will only work, however, if the writer catches the repetition — say, in the course of reading her manuscript IN HARD COPY, IN ITS ENTIRETY, and OUT LOUD before submitting it to an agent, editor, or contest.

I’ve noticed that writers are very frequently unaware of just how much their manuscripts DO repeat themselves. There’s a very good reason for that, of course: repetition is constantly flung at all of us, all the time.

Not just in everyday conversations — although it’s there, too: if you doubt this, go find a community that’s experiencing a heat wave, sit in a popular café, and count the variations on, “Hot enough for ya?” you hear within a 15-minute period — 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, Gladys — cut the RED cord hanging from that bomb, not the yellow one!”), character development (“Just because you’re a particle physicist with a summa cum laude from MIT, George, 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 favorite example of this tendency is the cult TV series Strangers With Candy, a parody of those 1970s Afterschool Special designed to break the news to young folks like me that Divorce is Hard on Everyone in the Family, Outsiders are Teased, and Drugs are Bad. (See, I even remembered the morals, doubtless due to repetition.)

Because it’s not as though we could be trusted to draw conclusions like that for ourselves from real-world observation. Because these playlets were intended to be EDUCATIONAL (as opposed to, say, entertaining), Afterschool Specials tended to hammer home their points with SUBTLE TOUCHES OF IRONY on the order of some minor character’s saying to our tragic heroine (played by someone like Helen Hunt in braces), “You know, Esther, I don’t think that you should even consider taking those drugs. They might make you go CRAZY.”

Any sane viewer, naturally, would recognize that this would mean that Helen Hunt was going to (a) take those drugs, because where would our object lesson be otherwise? (b) in fact go crazy, and (c) probably be dead within the next ten minutes of screen time.

Strangers With Candy had a great deal of fun with this kind of foreshadowing: the heroine, Jerri Blank, often telegraphs 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’s funny in the series, but it’s less funny to encounter in a manuscript, particularly if your eyes are attuned to catching repetition, as most professional readers’ are. Characters honestly do say things like, “But Emily, have you forgotten that I learned how to tie sailors’ knots when I was kidnapped by pirates three years ago?”

All the bloody time. Even when the first 200 pages of the manuscript dealt with that very pirate kidnapping.

At base, this is a trust issue. 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 murderer first revealed that he had a lousy childhood.

Who could have predicted THAT?

I’m sensing some squirming in desk chairs out there. “But Anne,” I hear some consistency-mongers protest, “doesn’t the fact that we ARE all accustomed to being spoon-fed the information we need when we need it mean that we writers should be ASSUMING that our readers will have some memory problems? Especially someone like Millicent, who might read the first 50 pages of my novel, request the rest, then continue reading a month or two later? Surely, I should be including some reminders for her, right?”

Good question, squirmers. Television and movies have most assuredly affected the way writers tell stories. One of the surest signs that a catch phrase or particular type of plot twist has passed into the cultural lexicon is indeed the frequency with which it turns up in manuscript submissions.

For precisely the same reason, 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.

“But WHY?” the consistency-huggers persist.

Come closer, and I’ll tell you a secret: repetition is boring. REALLY boring.

We all know how agents and editors feel about manuscripts that bore them, right? In a word: next!

And here’s another secret: people who read manuscripts for a living are substantially more likely to notice repetition 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.

Let me ask you: just how much control does the average submitting writer have over the OTHER manuscripts Millicent might have already scanned that day?

That’s right: absolutely none. So while following the cultural norm for repetitive storytelling might not annoy a reader who curls up in a comfy chair with only your manuscript, if your tale repeats twice something similar to what the submission before yours saw fit to convey 37 times in 22 pages…

It may not be a problem to which your manuscript falls prey — and if so, hurrah for you; it’s hard to strip a manuscript of them entirely, because they are so pervasive. But just to be on the safe side, here’s a project for a rainy day: 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?

No? What if I also ask you to highlight similar phrases in the narration? First-person narration is notorious for echoing the currently popular TV shows.

Often, it’s unconscious on the writer’s part: it’s brainwashing from all of that repetition. It would be surprising if common dialogue HADN’T made its way into all of our psyches, actually: according to CASSELL’S MOVIE QUOTATIONS, the line, “Let’s get outta here!” is 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?

No? Well, 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 doing 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 inadvertently from time to time.

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 told me that he is constantly meeting private detectives who sound like Sam Spade, for instance, something they apparently didn’t do before the 1930s.

But remember, just because people do or say something in real life doesn’t mean it will necessarily be interesting — or not come across as hackneyed — 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 is kind enough to maintains a database of them.)

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

It’s time for me to go-o-o (curse you, Pan!) for today; I’ve got some cat appeasement to do. (I wonder if he’d like a salmon milkshake…). More tips on catching repetition follow anon.

Keep up the good work!

Posted on - No Comments on The hows and whys of showing, not telling, or, when it pays to get just a trifle graphic

The hows and whys of showing, not telling, or, when it pays to get just a trifle graphic

Before I launch into today’s disquisition on the ins and outs of showing, rather than telling, an announcement for those of you within driving distance of San Francisco: author, blogger, and FAAB (Friend of Author! Author! Blog) Mark Pritchard will be giving a reading in the City by the Bay this coming Saturday, May 17. For those of you not already familiar with Mark’s Too Beautiful blog might want to run, not walk to his fascinating What Are You Working On? series of author interviews.

Mark will be reading in the Progressive Reading Series at 7:00 pm on Saturday, May 17 at the Makeout Room, 3225 22nd Street at Mission, San Francisco.

And hoo boy, is he ever going to be joined by an impressive line-up of writers who could tell you a thing or two about showing, not telling! Lookee:

Josh Bearman and Starlee Kine (This American Life)
Pam Houston (“Sight Hound,” “Cowboys Are My Weakness”)
Adam Mansbach (“End of the Jews,” “Angry Black White Boy”)
Mark Pritchard
Mary Roach (“Stiff,” “Spook,” “Bonk”)
David West

This evening benefits the campaign against California’s Proposition 98, and advance tickets are highly recommended.

Okay, back to business.

Last time, I argued that in both fiction and nonfiction, readers regard summarized information as less important — to the story, to the argument — than material presented in a more fleshed-out form. This is a pretty darned good reason to follow the old show, don’t tell rule in and of itself: vividly-rendered scenes, striking character development, and detailed proof are simply more memorable than quickly-sketched outlines.

Yes, you did read that correctly: I said character development. For some reason that I have never been able to understand fully, the show, don’t tell axiom and character development are seldom mentioned with in the same breath in writerly circles, or even in the same weekend seminar or composition class.

As an editor, I find this a touch odd, as in the average manuscript — come closer, so I may whisper a trade secret to you — a tendency to draw conclusions for the reader almost invariably detracts from the efficacy of character development. Heck, some professional readers would even say that telling is the natural enemy of character development.

Why? Well, several reasons, most of which dance around the issue of how people tend to read.

To understand the first reason, we need go no farther than to the opening paragraph of this post: as anyone who has ever tried to slog through a poorly-written textbook can tell you, readers are less likely to remember (read: think that they will need to remember) information presented as generalities than the same collection of facts enlivened by specifics.

Which means, in practice, that conclusions about a character tend to slip out of a reader’s mind. As you may recall from yesterday, a passage like:

Eustace was an inveterate coward, a hider behind matronly hips that had for many years been too narrow to provide truly effective concealment for his ever-increasing girth. He didn’t particularly care whose hips they were — Mom’s, his sister Rose’s, his girlfriend or wife du jour’s – so long as they were balanced between him and the frightening world.

may be amusing in the moment, but it’s unlikely to stick in the reader’s mind as anything but a pretty passage of prose. If Eustace were an important character, even a single scene that SHOWED him acting cowardly would establish this trait far more effectively than even four or five repetitions of simple assertions about it scattered throughout the text.

Why do I bring up the possibility of this much repetition? Because, alas, many aspiring writers confuse tellin} the reader what a character is like with character development.

But when the pros talk about character development, they don’t usually have broad summary statements in mind. (Yes, even if they don’t say so explicitly.) They’re generally thinking of the many, many different tiny, revealing, and delightful details a writer could use to show what a particular character is like — and how s/he grows and changes throughout the book.

This ideal should not be confused, of course, with the kind of narrative that showers the reader with a million and twelve tiny facts, each presented as equally important. That tends not to go over so well.

Especially — brace yourselves; here comes Millicent — in those all-important first few pages that determine whether a submission gets rejected out of hand or given a fuller reading. Writers seem particularly fond of overloading the reader with physical and environmental descriptions in early chapters, as if everything that could possibly be seen needs to appear in the reader’s first glimpse of the protagonist or can never be mentioned at all.

Let’s take a gander at how the average submission might introduce poor Eustace:

Whey-faced Eustace went more than usually pale, his already-pasty cheeks draining of what little blood had managed to work its way up from its customary pooling place farther south, in the region of the stomach his mother kept so well supplied and the acid-washed jeans in which she still ironed a lovingly uncool razor-sharp crease every morning. Certainly, his blood did not seem to be in the habit of regularly visiting his brain, where it might conceivably have provided some much-needed R&R to the synapses and corpuscles that would have been in charge of critical analysis in a better-lubricated mind. His reddish-blond hair, never too good a scalp covering even in its heyday, now seemed to be fleeing his astonishingly full eyebrows with all possible dispatch. If his chest hair had any aspirations to assert itself, it was still working up the nerve under his carefully-starched button-down shirts — fourteen of them hung lankly in his cedar-stuffed closet, awaiting Mom’s magical touch with spray starch. His shoes, shined to within an inch of their lives — a good trick, with sneakers — all pointed their toes toward the closet door, the front hallway, and the world beyond, as if they felt that Eustace’s timidity were the only thing keeping them from the life of adventure they deserved.

All RIGHT, already: we get the picture. We also would have gotten the picture with half as many details.

Don’t buy it? Okay, here’s a pop quiz: cover the last example and try to list all of Eustace’s physical and sartorial traits in the order they appeared. Difficult, isn’t it?

That’s not the fault of any of the individual details, incidentally. The problem here is one of emphasis — and presentation.

Too many facts in a row simply become a list, in the reader’s mind. By a couple of lines in, all of that information starts to blur together, encouraging — dare I say it? — skimming.

Faced with this kind of reaction (as well as the dread prospect of agents’ turning pale at manuscripts much over 100,000 words), many writers rush to the opposite extreme, cutting details to the proverbial bone in an effort to streamline their work.

Which isn’t necessarily going to improve the manuscript, if emphasis is the problem. What will solve it is removing non-revealing details that only serve to distract from what the writer wants the reader to take from the scene.

That last set of observations raised some hackles out there, didn’t it? “But Anne,” I hear some of the behackled exclaim, “I hate to quibble, but first you tell us not to summarize essential character information, but instead to reveal character through a plethora of details — and then you turn around insist that too many details are the kiss of death. How will I know when my manuscript has reached the right balance between detail and summary?”

Great question, raised hacklers, and one that richly deserves an answer. Unfortunately (and contrary to some writing guides out there promoting the {show, don’t tell} path of righteousness}, there isn’t a magic formula that can be applied to every manuscript.

Time to call in the first readers, in other words.

That advice didn’t sooth all that many savage breasts, did it? “Okay, Anne,” my former questioners continue through gritted teeth, “I can try to accept that. But when I gave my manuscript to my mother/sister/best friend/husband/some total stranger I happened to meet at the café down the street, I noticed that s/he didn’t seem to have all that great a memory for the details you told me to use to reveal character. Why, it says very plainly in Ch. 2 that Dorothea is my protagonist’s lover’s cousin’s au pair, but without exception, all of my feedback-givers wrote, “Who’s this?” in the margin when Dorothea appeared again in Ch. 27.”

Oh, honeys, I hope you’re sitting down, because I have some potentially disturbing news for you: most people don’t actually read every single syllable of a book, much less absorb the impact of every single sentence.

Or, to put it another way, just because a writer mentions something on a page doesn’t mean that any given reader — even a very good one who takes notes as she reads, like yours truly — will necessarily remember it all the way through the reading process.

I hope that didn’t make anyone out there faint.

Seriously, few aspiring writers seem aware of this phenomenon — come to think of it, plenty of published authors are apparently unaware of it as well. The overwhelming writerly tendency is to assume that reader is absorbing every word — otherwise, observations like what do you mean, you don’t know who Dorothea is? She was mentioned in passing 117 pages ago! simply wouldn’t make any sense, right?

You know me — I’m pretty much always on the writer’s side, right? As much as I love creative souls, I must admit that I tend to attribute this attitude to writerly ego: I wrote it, therefore it’s important.

But this isn’t always the message a manuscript is sending to the reader. One of the reasons that summaries make for less effective character development because readers are (for the most part, anyway) quite good at picking up authorial signals about what is and isn’t significant in a text.

Take, for example, the following passage from John Irving’s THE CIDER HOUSE RULES — which should be required reading, I think, for anyone who has fallen in love with 19th-century narrative styles and is trying to implement them now. It’s as jam-packed a sample of character development as you’re ever likely to see in print. Read it over, please:

You had only to know her to know that she was not a Candy; she was lovely, but never falsely sweet; she was a great and natural beauty, but no crowd-pleaser. She had daily reliability written all over her, she was at once friendly and practical — she was courteous, energetic, and substantial in an argument without ever being shrill. She complained only about her name, and she was always good-humored about it (she would never hurt her father’s feelings — or any one else’s feelings, willingly. She appeared to combine her father’s enraptured embrace of the work ethic with the education and the refinements he had allowed her — she took to both labor and sophistication with ease.

Based upon the style here, just how important a role would you expect Candy to play in the rest of the book?

Usually, a character whose traits are introduced in summary is a minor one — but Candy’s actually the most important female character in the book. Leaving aside for the moment the fact that mentioning that a female character speaks without ever being shrill or without ever sounding strident is usually code for her not holding radical feminist views like expecting to be paid for her work or be allowed to vote — or at least not holding them strongly enough to make an issue of them — what message do you think Mssr. Irving is sending the reader here by summarizing so much character development that he could easily have shown through action?

Okay, so maybe that’s not really a fair question to ask folks who may not have read the entire book, but as I have, I’ll hazard a guess: to give the reader a heads-up that Candy is going to be a fairly passive (if complex) character, acted-upon rather than acting.

Of course, that could just be my bias. But I did notice that in the movie version — based upon a screenplay by Mssr. Irving himself — virtually all of Candy’s complexity had been stripped away, her motivation for a life-changing affair with the protagonist reduced to a single line of dialogue thrice repeated in the script: “I’m not good at being alone.”

In other words, the character prefers to be acted-upon than act.

I intend no disrespect to Mssr. Irving (whose work I have loved for years, including this book), but even in a screenplay, wouldn’t it have been pretty easy to show this particular personal preference rather than simply tell about it — say, by placing the character in situations where she chooses to let others act for her?

In a manuscript, the answer is an unequivocal YES — or at any rate, should be, because it’s significantly easier for the reader to envision — and thus remember — characteristics based upon telling details than upon flat assertions.

Allow me to illustrate.

When I was a teaching fellow at a major football school that shall remain nameless (go, Huskies!), the professor whose discussion sections I was leading saw fit to assign a simply dreadful (and dreadfully simple-minded) article about how the great strength of American capitalism was that everybody could find personal fulfillment, because the market was so complex that whatever each of us wanted to sell, there would be someone out there willing to buy.

Not altogether surprisingly, my students were rather confused by this argument; it was my job to come up with a practical example to illustrate the principle. So I told them about a certain distant cousin of mine who, thanks to quite a nice singing voice, an unusual personal preference to appear in public with very little on, and the career-extending blessings of silicone implants, managed to carve out a niche for herself for many years as arguably the world’s most famous topless singer.

Think my students had any trouble remembering THAT example? Heck, when I bump into one of them on the street now, years later, there’s a better than even chance that s/he will mention it.

More to the point, every single one of them used Cousin Carol as an argumentative example on the final exam — even, amusingly enough, the students who evidently misremembered the point of the article.

Now THAT’s a telling set of details.

But that doesn’t really address the question of balance, does it? Do you still have that hard copy of your manuscript handy?

Here’s a radical revision idea: flip through it until you find a scene where it’s imperative that the reader understand that the character(s) involved has certain personality traits. Better yet, identify several scenes. At the top of each page, write a single sentence — no cheating; just one — about what you would like the reader to take away from it.

Not EVERYTHING the reader COULD take away from it, mind you — just the most important single point. (Hint: if you favor summary statements, you may already have a sentence per page that serves this function.)

Whip out your trusty highlighter pen and mark all of the character-revealing sentences. Go back through the pages, underlining all of the summary statements and circling the details.

Now read the scene(s), skipping the summary statements. Is the vital information for each page still coming across? If not, could you add a few telling details that would help bolster your point better than reinstating the summaries?

Next, take a look at the details. Are all of them necessary to make the crucial point? Or would adding a few more clarify the conclusions the reader should be drawing at that point of the text?

Stop right there: part of your brain is still trying to figure out what a topless singer would actually DO in her act, isn’t it? (And to forestall your next question: no, I never caught the act — I was in diapers at the height of my cousin’s fame — so I can’t provide satisfactory answers about it. Believe me, my students asked ALL THE TIME.)

That’s the power of a really good illustration of character, my friends: it sticks in the reader’s mind long after s/he has read it, and thus is easy to recall even 25 chapters later. But if every detail were as vivid, or if there were too many of them, the reader might have difficulty remembering necessary information throughout an entire storyline.

Be selective. Provide killer details that paint an indelible picture. And, of course, keep up the good work!

Posted on - No Comments on Hearsay vs. first-hand observation, or, “He ran into the room and said…”

Hearsay vs. first-hand observation, or, “He ran into the room and said…”

Last week, I waxed poetic on the joys and perils of showing, rather than telling, as we writers are so often urged to do in our work. Theoretically, this advice makes oodles of sense: it is far, far more graceful to allow the reader to draw conclusions unassisted than for the author to state point-blank that a character was like this or that, right?

Well, I guess that settles that. In other news…

Wait a minute: contrary to what some hit-and-run advice-givers would evidently have you believe, in practice, it isn’t always so obvious what should be shown and what for reasons of parsimony or pacing should be merely summarized. Today, I am going to talk a little about how striking a balance between what you choose to show and what you choose to tell can affect a reader’s perception of what’s going on in a story.

Summaries, while often necessary, have the nasty propensity to compress acres and acres of fascinating action into, well, a compressed little bundle. Why is this a problem, you ask, if a writer is trying to cover quite a bit of material quickly?

Well, many aspiring writers make the serious mistake of assuming that if what’s being DESCRIBED is interesting or action-packed, the summary automatically will be as well. However, this is often not the case. Even when the summarized activity is inherently exciting, glossing over it as quickly as possible tends to sap its impact upon the reader. Compare, for instance:

Ghislaine flung her well-muscled arms around her long-lost lover, Robert. In the midst of one of the most passionate kisses the world has ever known, her eyes closed fully for the first time in seven years. Gone was the crowd of blunderbuss-wielding soldiers awaiting her culinary artistry; vanished were the king, queen, jack, and rook whose movements across the checkered floor had diverted her from her labors. Even the snarling dog at her heels, Lord Augustine’s pet, faded from her consciousness until it savagely ripped her foot off at the ankle. As she fell to the ground to be worried into sandwich meat, she saw her kid brother rush forward and stab her one true love between the third and fourth rib.

With:

Ghislaine hugged Robert. Lord Augustine’s dog bit her, and as she fell, her kid brother stabbed Robert.

Both of these passages are describing exactly the same event — and there’s no denying that the second moves the plot along pretty expeditiously. But when speed comes at the expense of enough detail for the reader to understand what’s going on, the story suffers.

And lest you nonfiction writers out there have been feeling a bit smug throughout the discussion of show, don’t tell, over-summarization can also seriously undermine an argument as well. Often, summary in nonfiction will take the form of presenting conclusions before (or even instead of) the detailed facts from which the author is deriving the conclusions.

Don’t believe me? Check out this historical summary about today’s poster girl:

Lucilla was a Roman empress of ill repute. Actually, we only have her successors’ word for that — her younger brother, the emperor Commodus, was no prize himself. The two of them were continually trying to assassinate each other, and Commodus, after having his sister executed, was left in charge of her reputation. As has often been the case with history since, the victors in Roman times used to work overtime to smear the reputations of those whom they deposed. Recently, scholars have begun to argue, albeit not very loudly, that Caligula, Macbeth, and Richard III might not have been such bad guys.

Leaves you wanting something more, doesn’t it? Evidence to support these contentions, for instance, or perhaps some indication of WHY Marcus Aurelius’ children might have been at each other’s throats? Clearly, this is a paragraph that deserves to have SHOW, DON’T TELL scrawled in the margin next to it — in Latin, presumably — even though everything in it is factually correct.

(Yes, really — someone actually is trying to rehabilitate Macbeth’s reputation. Hard to believe that he would care much at this point, but still, it’s kind of sweet.)

In both fiction and nonfiction, readers tend to perceive summarized information as less important than detailed accounts — unless, of course, the author has overwhelmed them with five million tiny facts, each presented as equally important.

We’ve all experienced this as readers, right? As we saw above in poor Ghislaine’s case, if a narrative presents a scene vividly, it’s inherently more memorable than summarized action. In the reader’s mind, s/he was there for the former, but merely told about the latter.

Try this on for size: when the herald comes running into the banquet hall to announce that the army has lost the battle and the enemy is about to storm the castle’s walls — as anyone who has ever seen a filmed costume drama or Shakespearean tragedy would naturally expect him to do — you might want to ask yourself, “Would this scene be more exciting if I SHOWED the army fleeing and the enemy scaling the walls, instead of having good old George just turn up and tell all the rest of the characters about it?”

I’m sensing some discomfort with that last suggestion. “But Anne,” I hear some of you herald-huggers out there protesting, “isn’t George’s running into the room active and exciting? If I show the marauding hordes approaching, won’t that cut into the sense of surprise in the room when they find that they’re under siege?”

Well, yes, announcement aficionados, George’s flinging the door open and yelling at the top of his lungs would indeed be action — but is it the most effective (or important) way to impress upon the reader the practical implications of being overrun? Would it not perhaps be more startling if the revelers had no advance warning at all, so the reader just saw them react when a hundred armed Amazons broke down the door?

I’m just saying.

The classic active-teller vs. shown action misstep is somewhat more complicated than this: a character’s narrating a scene s/he observed to a third party. Here’s an example from Louisa May Alcott’s potboiler BEHIND A MASK, a highly amusing and ethically dubious tale of Jean Muir, an actress who infiltrates an affluent English country family with an eye to the main chance. (The outcome will, I promise you, surprise most readers of LITTLE WOMEN.)

Fair warning: there is more than one problem in this passage; see if you can spot the full array. Lucia has been sitting with her presumptive fiancé, Gerald, who keeps flitting away to spy on his brother and sister being enchanted by the mysterious governess:

Lucia looked at her cousin, amazed by the energy with which he spoke, the anxiety in his usually listless face. The change became him, for it showed what he might be, making one regret still more what he was. Before she could speak, he was gone again, to return presently, laughing, yet looking a little angry.

“What now?” she asked.

“‘Listeners never hear any good of themselves’ is the truest of proverbs. I stopped a moment to look at Ned, and heard the following flattering remarks. Mamma is gone, and Ned was asking little Muir to sing that delicious barcarole she gave us the other evening.

“‘Not now, not here,’ she said.

“‘Why not? You sang it in the drawing room readily enough,’ said Ned imploringly.

“‘That is a very different thing,’ and she looked at him with a little shake of the head, for he was folding his hands and doing the passionate pathetic.

“‘Come and sing it there then,’ said innocent Bella. ‘Gerald likes your voice so much, and complains that you will never sing to him.’

“‘He never asks me,’ said Muir, with an odd smile.

“‘He is too lazy, but he wants to hear you.’

“‘When he asks me, I will sing — if I feel like it.’ And she shrugged her shoulders with a provoking gesture of indifference.

“‘But it amuses him, and he gets so bored down here,’ began stupid little Bella. ‘Don’t be shy or proud, Jean, but come and entertain the poor old fellow.’

“‘No, thank you. I engaged to teach Miss Coventry, not to amuse Mr. Coventry,’ was all the answer she got.

“‘You amuse Ned, why not Gerald? Are you afraid of him?’ asked Bella.

“Miss Muir laughed, such a scornful laugh, and said, in that peculiar tone of hers, ‘I cannot fancy anyone being afraid of your brother.’

“‘I am, very often, and so would you be, if you ever saw him angry.’ And Bella looked as if I’d beaten her.

“‘Does he ever wake up to be angry?’ asked that girl, with an air of surprise. Here Ned broke into a fit of laughter, and they are at it now, by the sound.”

Leaving aside the editor-annoying facts that people do not generally shrug anything BUT their shoulders and that if Gerald could hear the others laughing, chances are that Lucia could, too, did you catch the show-don’t-tell problems here? Or was the over-use of the verb to look just too distracting?

Give yourself a big gold star if you said that the first paragraph watered down Gerald’s changed mien by filtering it through Lucia’s conclusions about it. Give yourself two if you murmured that the transition between her perspective and his was a trifle abrupt.

If you are like most readers, though, none of these things would have qualified as this passage’s biggest problem: its real downfall is the soporific effect of having Gerald narrate this scene, flattening out all of the individual characters’ quirks. To render the reader even sleepier, the tension is lax, since we knew (because the narrative TOLD us) that he returned right away; evidently, then, what he had to tell could not have been particularly dramatic, or at any rate not life-threatening.

Zzzz.

Yet this scene could have been rather amusing and revealing, with slightly different authorial choices. By making Gerald not only the reader’s eyes and ears in a scene in which he is a passive listener AND using him as Lucia’s eyes and ears as well, this scene becomes all about Gerald’s perceptions, not about the actual dialogue he is reporting.

Had our friend Louisa instead elected to hide him behind a curtain and OBSERVE that scene, the narration could have embellished, shown each speaker’s tone, and increased the tension by introducing the possibility that he might get caught eavesdropping.

Instead, Ms. Alcott decided to keep it all from his perspective AND in his voice — anyone out there care to guess why?

To a professional reader, it’s pretty obvious: clearly, because the author wanted to use the line And Bella looked as if I’d beaten her, an impossibility UNLESS Gerald was the narrator at that juncture.

Believe it or not, an aside like this is not an uncommon reason for drafting an uninvolved actor into narrator service.

While I’m on the subject of characters narrating others’ activity, I should probably mention a pet peeve shared by scores of agents, editors, and contest judges the world over: when the narrator reports things s/he could not possibly know, presumably in the interest of not switching out of the chosen narrative voice.

This is VERY common in first-person narratives — where necessarily, ALL the reader should logically hear about is what the narrator can observe or recall. So how could the narrative possibly include other characters’ thoughts, feelings, or incidents that occurred when the narrator was not physically present?

Most of the time, writers choose one of two paths around this problem, both extremely hard to pull off on the page: abandoning the chosen narrative perspective just long enough to include necessary information that the narrator can’t know (dicey, unless the perspective shifts to an omniscient narrator) or by having someone like Gerald lope up to the protagonist and tell him what happened.

I blame television and movies for the pervasiveness of both of these strategies.

Just as the limitations of film have told writers that all human experience should be conveyed merely through the audible and the visible, leaving out other stimuli except as verbally described by the characters, they have also instructed us that where the camera can go, so can the narrator. But in a first-person narrative, this logically is not true.

I have quite a bit more to say on this subject, but for today, suffice it to say that from a reader’s perspective, just because character is shown summarizing action doesn’t make it any less a summary than if the same information appeared in a narrative paragraph. On the showing vs. telling continuum, it tends to fall toward the telling end.

Every so often, consider giving that poor herald a rest. Let the actions — and actors — speak for themselves.

Keep up the good work!

Posted on - No Comments on The hard-and-fast rules about hard-and-fast rules

The hard-and-fast rules about hard-and-fast rules

We begin today with a quiz: what does this photograph depict? More to the point, if you had to describe it in a manuscript, how would you do it?

Why, yes, now that you mention it, those are two rather different questions: the first has a single, fact-based answer, the second no uniquely right answer.

And yes, that IS an excellent parallel for many aspects of the revision process. How clever of you to spot that. Pat yourself on the back immediately.

I have been on retreat for the past couple of days, meditating in a remote mountain cave and living off sips of purest dew while I wrestled with the knotty problem of creating the Platonic blog post on showing, rather than telling — because, as I’m sure some of you have noticed, I’ve been spending the last week or so dancing around various aspects of incisive reader Shelley’s delightfully straightforward request that I address what the oft-repeated writing axiom actually MEANS.

There’s a short answer, of course, which I snuck unobtrusively into an earlier post: telling is when the narrative simply states what is going on and what it means, whereas showing is when the narrative allows the reader to be the primary drawer of conclusions based upon what the various characters do, say, and think.

The longer answer involves, as we’ve seen recently, a whole plethora of very specific writing strategies and techniques. I could keep us occupied for a good month on them, if I really put my mind to it. And I certainly intend to focus on a few of my favorites in the days to come.

But that prospect didn’t relieve me of the feeling that I really owed it to posterity to write the definitive single post on the matter, I must confess. If I crafted my notions persuasively enough, I figured, if I made the case for show, don’t tell so convincing that no reasonable creature could possibly ever disagree with it, if I made the very idea of telling rather than showing sound so unappealing that each and every one of you would feel faint at the very idea of doing the former, I could rest again at night.

I would also be a benefactor of humankind deserving of being carried through the streets of the nearest metropolis by an admiring throng — nay, of every metropolis in the English-reading world, if not actually meriting having my profile appear on future coinage, stamps, and Wheaties boxes.

If I could manage to make it funny as well, someone might even name a dessert of some sort after me, like Napoléon or Pavlova.

In short, I made the task so gigantic in my mind that there was absolutely no possibility of my ever posting on the subject again. Evidently, I was doomed to spend the rest of my natural life in that cave, being fed by those cartoon birds that are always fluttering around Snow White.

What knocked me out of my self-imposed procrastinative funk, you ask? My neighbor, Sarra, made me a mocha that was a work of art, complete with a beautiful top layer of foam patterned like an exotic cat’s pelt.

The subject of the photograph above, in short.

In the proverbial flash, the answer to my dilemma came to me: like so many of the so-called hard-and-fast rules of good writing, show, don’t tell should NOT be applied blindly to a manuscript, but with discretion — and with style.

Let’s face it — it’s not the clearest piece of advice anyone has ever given a writer. In some ways, show, don’t tell is a bit vague; show, don’t summarize is probably clearer advice. At least for the interesting bits that you want to stick in the reader’s mind forever and a day.

Obviously, though, any writer is going to need to summarize certain events from time to time: if every book set during wartime, for instance, had to describe every battle down to the last drop of blood hitting the ground, there wouldn’t be a whole lot of room for character development, would there?

Want a concrete example, do you? Okay, think about the photograph above for a moment. Factually, it’s a picture of a cup of coffee. Narratively, I would have been perfectly within my rights to tell you so from the get-go, correct?

But that simple empirical description wouldn’t have conveyed a whole lot about either the odd, animal-print beauty of the foam on top or how it got there, would it? Or why Sarra, a barista of local repute, might have gone to the trouble of creating such an intricate pattern, would it?

My guess is that she likes me — but that’s an example of the narrator’s drawing a conclusion that the reader might have drawn unassisted from the narrative so far, right?

I could, of course, have just come out and tell you that the foam was gorgeous, but gorgeous is a pretty non-specific descriptor, one that could conceivably apply to each and every one of the beautiful objects and people in a full and lovely universe.

Herd a hundred intelligent, observant people into a room and ask them to define the term, and you’ll end up with a hundred equally valid answers. Possibly more, if some of those hundred happen to be both indecisive and verbose.

By contrast, chestnut brown lushness alternated in chevrons with airy cream foam is awfully darned specific, isn’t it? Given the choice between that description and the foam was gorgeous, which do you think conveys a more vivid impression of what I actually saw?

The former is showing; the latter is telling.

Notice, however, that I did not describe the cup containing the drink of beauty in equal detail, nor the countertop upon which it rested briefly, nor the room in which Sarra and I were standing at the moment I first beheld her artistry.

Had I taken the axiom show, don’t tell very literally, I might have engaged in equally detailed descriptions of all of these — in addition to regaling you with meticulous accounts of the sky visible through a nearby window, the grunt of approval my SO emitted when I showed him my prize coffee, and every article of clothing I happened to be wearing today.

Why didn’t I do that? Because we’d all be here until Doomsday.

Also, these factors were extraneous to the story. Including them would have watered down the intense visual image that I was attempting to impress upon my readers’ brainpans.

Let me repeat that, because it’s vitally important: including too much detail can distract the reader from the main point of a description, scene, or narrative paragraph.

Show, by all means, but not indiscriminately. Apply the technique where it will have the greatest effect.

Dare I say it? Yes, I shall: use your judgment.

I’m sensing some uncomfortable shifting out there at the very notion, amn’t I? “But Anne,” I hear some of you murmur, “isn’t the point of a hard-and-fast rule that we should apply it in EVERY instance? Relying upon one’s individual judgment implies a bit more wiggle room than I am used to hearing about in rule application.”

Great question, anonymous murmurers — but doesn’t the answer depend very much upon what KIND of rule you’re thinking of applying?

Matters of grammar or standard format, for instance, are the stripe of rules that one might want to take literally every time. A semicolon may only be used in a certain limited number of ways, after all, and it would be pretty hard to argue that a 1″ left margin meant anything but that the text should begin one inch from the left-hand side of the page.

Other rules are not so clear-cut.

A very powerful agent who specializes in genre fiction used to tell roomfuls of conference-goers that he ALWAYS stopped reading a submitted novel as soon as he encountered a scene in which characters were drinking coffee, tea, or any other non-alcoholic beverage.

Why? Because he had found over years of scanning submissions that such scenes almost always involve the characters sitting around and talking about what was going on in the plot, rather than going out and doing something about it. Much like scenes where the protagonist sulks in his tent, thinking, these scenes provide analysis of what has already happened, rather making something new happen.

To him, such scenes were the kiss of death: they indicated, he said, that the author did not know how to maintain tension consistently throughout a book.

Now, speaking generally, he probably had a point: it’s not all that uncommon for characters to get together to discuss what the reader has just seen happen, mulling the implications without doing much to change the situation and thus move the plot along.

(Phone conversations are also prone to this tendency — especially, for some reason, when the chat is between the protagonist and his or her mother. Happy Mother’s Day.)

But the rule the agent proposed was not take a good look at any scene where your characters sit around and talk instead of acting, was it? I might go along with that, but no, his advice was very specifically beverage-related: implicitly, he was telling those roomfuls of aspiring writers to cut ANY scene where the protagonist was drinking coffee, tea, or any other quaffable liquid under 50 proof, on pain of getting their manuscripts rejected.

Sure sounds like a hard-and-fast rule, doesn’t it?

But it isn’t — and couldn’t be, in every instance, any more than it would be safe to declare that every scene that takes place in a bar is inherently action-packed.

Especially in my neck of the proverbial woods. Since I edit for many Seattle-based writers, if I advised them to skip every possible coffee-drinking opportunity in their works, I would essentially be telling them to ignore a fairly significant part of local community culture. Their poor characters would wander the streets in the omnipresent drizzle, mournfully wondering where their hang-outs had gone.

I do, however, routinely suggest that aspiring writers flag any lengthy let’s-talk-it-over scenes — no matter what kind of beverage happens to be bouncing about in the protagonist’s digestive system at the time — then go back and read the entire manuscript with those scenes omitted. Nine times out of ten, the pacing of the book will be substantially improved, with little significant loss of vital information.

The moral: pacing is HUGELY important to professional readers; if a discussion scene slows the book down without advancing the plot, consider trimming it or cutting it altogether. Ditto with pages at a time of uninterrupted thought.

What the moral isn’t: the mere mention of potable liquid kills narrative tension. Unless, of course, that liquid can be poured over a plum pudding and set aflame.

If you have ever found yourself wondering why I explain the logic behind my writing and marketing advice so extensively here — even for the rules of standard format, which aren’t negotiable (and if you aren’t sure why, or were not aware that there were professional standards for submitted manuscripts, please see the STANDARD FORMAT BASICS category at right) — this is why.

Yes, some rules of writing are pretty set in stone — but a great many are in fact matters of style, taste, and/or marketing strategy.

For those, you will need to use your own judgment, unavoidably. All I’m trying to do here is give you enough information about why certain stylistic choices and marketing strategies might behoove you to embrace.

Ultimately, though, it’s up to you whether to give ‘em a big old hug.

So if you asked me if it was all right to use business format for a query letter, I might instantly shout, “In heaven’s name, NO!” but that wouldn’t stop me from explaining at great length why I would do everything in my power to discourage you from making that TERRIBLE, TERRIBLE MISTAKE.

(If that last paragraph didn’t tempt you to chortle knowingly, you might want to take a gander at the HOW TO WRITE A QUERY LETTER category in the list at right before you send off your next. I just mention.)

In that spirit, I’ve saved the best possible argument for showing, not telling until after I’ve urged you to weigh the pros and cons of a writing axiom before you apply it. Everyone sitting comfortably? Here goes:

Based upon my description of the cup of coffee Sarra made for me, what do you think she’s like? What kind of a relationship do you think she and I have?

I’m not going to tell you. I’m going to let the details speak for themselves. You’re a good reader; draw your own conclusions.

And that, my friends, is an example of a narrative’s showing, not telling.

More specific strategies follow in the days to come, naturally. In the meantime, keep up the good work!

Posted on - No Comments on Yes, I KNOW that people use run-ons in everyday speech, but Millicent isn’t judging every word that falls out of the guy sitting next to you in the café’s mouth, is she? Anyway, what’s your hurry?

Yes, I KNOW that people use run-ons in everyday speech, but Millicent isn’t judging every word that falls out of the guy sitting next to you in the café’s mouth, is she? Anyway, what’s your hurry?

How are you enjoying our recent foray into craft issues and revision tips? Inspiring? Annoying? A little of both?

Never fear — here at Author! Author!, we never stray very far from marketing issues. As much as I love to talk about writing qua writing, my focus throughout this series is going to remain practical: how to revise your manuscript to minimize its chances of running afoul of screener Millicent’s hyper-critical eyes.

Last time, I began discussing that most overused of words in manuscripts, and. Leaning on this multi-purpose word can lead, I argued, to run-on sentences, dull action sequences, and contracting the bubonic plague.

Well, okay, perhaps not the last. But the results still aren’t pretty.

The other all-too-common and sentence structure, X happened and Y happened, turns up VERY frequently in both submissions and contest entries. It’s appealing because, like stringing together sentences beginning with conjunctions, it artificially creates the impression conversation-like flow:

I woke up the next morning and poisoned my husband’s cornflakes.

See? Chatty, casual: the way your local poisoner is very likely to say it to her next-door neighbor, right?

Many aspiring writers consciously strive for prose that echoes the kind of conversational rhythms and structures one hears every day, particularly when they are penning first-person or present-tense narratives. “I want it to sound real,” they say with engaging earnestness. “My goal is to hold, as ’twere, the mirror up to nature.”

Unfortunately, from Millicent’s perspective, most of these writers don’t realize just how widespread this particular goal is — or that much real-life conversation would be either deadly dull, logically incoherent, or at minimum not literarily interesting transferred directly to the printed page.

Why? Well, to take the reason most relevant to us today, because real-life speakers repeat both words and sentence structures to an extent that would make even the most patient reader rip her hair out at the roots in frustration.

If you doubt this, here’s a little experiment: sit in a crowded café for two hours, jotting down the conversations around you verbatim. Afterward, go home and type up those conversations as scenes, using ONLY the dialogue that you actually overheard.

If you can complete the second part of that exercise without falling into a profound slumber, you have an unusually high threshold for boredom. Or perhaps you have a great affection for the mundane.

In any case, it’s highly unlikely that you would be able to get the result past Millicent, either as dialogue or as narrative. In professional writing, merely sounding REAL is not enough; a manuscript must also be entertaining.

Yes, Virginia, even if it happens to be literary fiction, if it’s book-length. Slice-of-life pieces can be quite effective IF they are short — but frankly, in my opinion, most of what goes on in the real world doesn’t rise to the standards of literature

Far, far better to apply your unique worldview and scintillating ability with words to create something BETTER than reality, I say.

In that spirit, let’s look at that sentence structure beloved of the real-life speaker, X happened and Y happened and see if we can’t improve upon it, eh?

If this structure is used sparingly, it can work very well indeed — but its advocates seldom seem to be able to restrain themselves. Let’s take a peek at several sentences of this type in a row, to see why it might annoy your garden-variety Millicent at the end of a long, hard day of rejection:

Esmeralda blanched and placed her lily-white hand upon her swiftly-beating heart. Rolando nodded with satisfaction and strode toward her, grinning. She grabbed a poker from next to the fire and glanced around for an escape. He chortled villainously and continued to move closer.

See what I mean? Although each of these sentences is in fact grammatically correct, and this structure reads as though it is merely echoing common spoken English, it’s also pretty much the least interesting way to present the two acts in each sentence: the and is, after all, simply replacing the period that could logically separate each of these actions.

By contrast, take a look at how varying the sentence structure and adding the odd gerund livens things up:

Esmeralda blanched, her lily-white hand clutching her swiftly-beating heart. Rolando strode toward her, grinning. She grabbed a poker from next to the fire and glanced around for an escape. He chortled villainously, moving closer every second.

Easier to read, isn’t it? Admittedly, the prose is still pretty purple — or at least flushing lilac — but at least the paragraph is no longer jumping up and down, screaming, “My author knows only one way to structure a sentence!”

Most agents, editors, and contest judges would agree with the paragraph’s assessment, alas. They tend to have a very low tolerance for over-use of this particular sentence structure.

Seriously. I’ve seen pens poked through manuscripts at the third instance of this kind of sentence within half a page.

While you are self-editing, then, it’s a dandy idea to rework ANY sentence in which and appears more than once. (Hey, where have I heard that trenchant advice before?) Chances are high that such a sentence will be a run-on, in any case:

In avoiding the police, Zelda ran down the Metro stairs and out onto the platform and into the nearest train.

This is a classic run-on: too much information crammed into a single sentence, facilitated by those pesky conjunctions.

Some writers, of course, elect to include run-on sentences deliberately in their work, for specific effect: to make the narrator sound less literate, for instance, or more childlike, or to emphasize the length of a list of actions the protagonist has to take to achieve a goal. Or sometimes, the point is to increase the comic value of a scene by the speed with which it is described, as in this excerpt from Stella Gibbons’ classic comedy, COLD COMFORT FARM:

He had told Flora all about his slim, expensive mistress, Lily, who made boring scenes and took up the time and energy which he would much sooner have spent with his wife, but he had to have Lily, because in Beverly Hills, if you did not have a mistress, people thought you were rather queer, and if, on the other hand, you spend all your time with your wife, and were quite firm about it, and said that you liked your wife, and, anyway, why the hell shouldn’t you, the papers came out with repulsive articles headed “Hollywood Czar’s Domestic Bliss,” and you had to supply them with pictures of your wife pouring your morning chocolate and watering the ferns.

So there was no way out of it, Mr. Neck said.

Quite the sentence, eh? (Not the second, silly — the first.)

I’m going to part company with pretty much every other editor in the world for a moment and say that I think that a writer can get away with this sort of run-on every once in a while, under three very strict conditions:

(1) IF it serves a very specific narrative purpose that could not be achieved in any other manner (in this example, to convey the impression that Mr. Neck is in the habit of launching into such diatribes on intimate topics with relative strangers at the drop of the proverbial hat),

(2) IF it achieves that purpose entirely successfully (not a foregone conclusion, by any means), and

(3) If the writer chooses to do this at a crucial point in the manuscript, s/he doesn’t use it elsewhere — or at least reserves the repetition of this choice for those few instances where it will have the greatest effect.

Why minimize it elsewhere? Well, as we have seen above, this device tends to create run-on sentences with and…and…and constructions, technically grammatical no-nos. YOU may be doing it deliberately, but as with any grammatical rule, many writers who do not share your acumen with language include them accidentally.

Let me ask you this: how is a speed-reading agency screener to tell the difference between a literate submitter pushing a grammatical boundary on purpose and some under-read yahoo who simply doesn’t know that run-ons are incorrect?

Usually, by noticing whether the device appears only infrequently, which implies deliberate use, or every few lines, which implies an ingrained writing habit.

I’ve sensed disgruntled rumblings out there since point #3. “But Anne,” I hear some of you protest, “I read a great deal, and I see published literary fiction authors break this rule all the time. Doesn’t that mean that the language has changed, and people like you who go on and on about the rules of grammar are just fuddy-duddies who will be first up against the wall come the literary revolution?”

Whoa there, disgruntled rumblers — as I believe I have pointed out before, I invented neither the rules of grammar nor the norms of submission evaluation. If I had, every agency and publishing house would post a clear, well-explained list of standard format restrictions on its website, along with explanations of any personal reading preferences and pet peeves its staff might happen to have. Millicent would be a well-paid, under-worked reader who could spend all the time she wanted with any given submission in order to give it a full and thoughtful reading, and the government would issue delightful little checks to compensate writers for all of the time they must now spend marketing their own work.

Clearly, then, these matters are not under my personal control, so kindly take me off your literary hit lists.

Even in literary fiction, it’s rather dangerous to include grammatically incorrect sentences in a submission — to someone who hasn’t read more of your work than the first few pages of your manuscript, it’s impossible to tell whether you are breaking the normal rules of grammar in order to create a specific effect, or because you just don’t know the rule. If an agency screener concludes that it’s the latter, she’s going to reject the manuscript, almost invariably.

Thus, unless you are getting a valuable effect out of a foray into the ungrammatical, it’s best to save your few opportunities to do so intentionally for when it serves you best. At the very least, make sure that two such sentences NEVER appear back-to-back, to avoid your submission’s coming across as the work of — gasp! — a habitual runner-on.

Sometimes repeated ands work rhythmically, but to an agent or editor, a manuscript that employs X happened and Y happened as its default sentence structure it just starts to read like uncomplicated writing — which makes it less appealing to the pros.

The other common conclusion trained eyes often draw from over-use of this technique smacks of either the narrative’s trying to rush through an otherwise not very interesting series of events.

This is not always a fair assessment, of course. But when you do find patches of ands in your text, step back and ask yourself honestly: “Do I really NEED to tell the reader this so tersely — or all within a single sentence? Or, indeed, at all?”

“Perhaps,” (you’re still speaking to yourself here, in case you were wondering) “I could find a way that I could make the telling more interesting by adding more detail? I notice by reading back over the relevant paragraphs that my X happened and Y happened sentences tend to be light on telling specifics.”

My, you’re starting to think like an editor, reader.

Since your revision eye is getting so sophisticated, let’s consider the opposite possibility: in paragraphs where ands abound (or, sacre bleu, sentences!), are you rushing through the action of the scene too quickly for the reader to enjoy it? Are some of those overloaded sentences cramming four or five genuinely exciting actions together — and don’t some of these actions deserve their own sentences?

Or, to put it a bit more bluntly, is the repeated use of and in fact your manuscript’s way of saying COME BACK AND FLESH THIS OUT LATER?

C’mon, admit it — almost every writer has resorted to this device at the end of a long writing day, haven’t we? Or when we have a necessary-but-dull piece of business that we want to gloss over in a hurry?

You thought you were the only one who did this, didn’t you?

Don’t be so hard on yourself — writers do this all the time. When the point is just to get lines down on a page — or to get a storyline down before the inspiration fades — X happened and Y happened and Z happened is arguably the quickest way to do it.

It’s a perfectly acceptable time-saving strategy for a first draft — as long as you remember to go back later and vary the sentence structure. Oh, and to make sure that you’re showing in that passage, not telling.

When we forget to rework these flash-written paragraphs, the results may be a bit grim.

Relying heavily on the and construction tends to flatten the highs and lows of a story: within them, actions come across as parts of a list, rather than as a sequence in which all the parts are important.

Which — you guessed it — encourages the reader to gloss over them quickly, under the mistaken impression that these events are being presented in list form because they are necessary to the plot, but none is interesting enough to sustain an entire sentence.

Which is not exactly the response you want your sentences to evoke from an agency screener, right?

When in doubt, revise to minimize the ands. I hate to come down unfairly on any grammatically correct sentence, but the fact is, the X happened and Y happened structure is just not considered very literary in the business. So the automatic assumption if it shows up too much is that the material covered by it is to be read for content, rather than beauty of prose.

To quote Millicent’s real-life dialogue: “Next!”

I would prefer to see your submissions getting long, luxurious readings, on the whole, not getting knocked out of consideration over technicalities. I’m funny that way.

Keep up the good work!

(PS: the lovely picture above appears courtesy of the fine folks at FreeFoto.com.)

Posted on - 2 Comments on Hitting the narrative target: your voice, your whole voice, and nothing but your voice

Hitting the narrative target: your voice, your whole voice, and nothing but your voice

No, the photo above is not a lopsided bull’s-eye: it’s an aerial shot (okay, not a very high aerial shot, as I am not very tall) of a freshly-cut ornamental cherry tree — the one that used to be in my back yard, as a matter of fact. Can’t tell that we get a whole lot of rain in my neck of the woods, can you?

No, you don’t want to know about the freak of landscaping machinery that resulted in our needing to chop it down. But thanks for asking.

Yesterday, I brought up the subject of narrative voice — or, to be a bit more specific, the desirability of revising your manuscript with an eye to making it sound like YOUR writing, rather than like a pale (or even very good) replica of an author whom you happen to admire. In the maelstrom of advice aimed at writers trying to land an agent, the issue of voice often falls by the wayside, as if it were not important.

Or writers might even — sacre bleu! — derive the erroneous impression that their work is SUPPOSED to sound as if it had been written by someone else — to be precise, by an author on the current bestseller list.

Can’t imagine where so many aspiring writers get this idea. Unless it’s from all of those conferences where agents, editors, and marketing gurus speak from behind the safety of podiums (podia?) about how helpful it is to mention in a pitch or a letter what bestseller one’s opus most resembles.

Listen: fads fade fast. (And Sally sells seashells by the seashore, if you’d like another tongue-twister.) Even after a writer signs with an agent, it takes time to market a book to editors — and after the ink is dry on the publication contract, it’s usually AT LEAST a year before a book turns up on the shelves of your local bookstore. A bestseller’s being hot now doesn’t necessarily guarantee that the same kind of voice will be sought-after several years hence.

If you doubt this, tell me: have you met many agents lately who are clamoring for the next BRIDGET JONES’ DIARY?

In the long run, I believe that a writer will be better off developing her own voice than trying to ape current publishing fashions. As long, that is, as that voice is a good fit for the project at hand.

But I’m getting ahead of myself, amn’t I?

Let’s rewind a little. As I mentioned in passing yesterday, part of the reason that many aspiring writers become confused about voice is that — brace yourselves — not all published writing exhibit an original narrative voice.

That “Wha—?” you just heard was from the chorus of readers who missed yesterday’s post, I’m guessing. “But Anne,” these intrepid souls cry as soon as they have regained their gasped-out breath, “I don’t understand. I’ve been going to conferences and writing seminars for years, and unless I wasn’t paying attention, published writing and good writing were used as essentially synonymous terms. At minimum, I’ve always assumed that writing needs to be good to get published. But how is that possible, if not all published work has a unique voice?”

Whoa there, gaspers, take a nice, deep breath. In the first place, I’m going to go out on a limb here and state categorically that not all published writing IS good.

(A long pause while everyone waits to see if a vengeful deity is going to strike me down for sacrilege. Evidently not.)

Books get published for all kinds of reasons, after all. The platform of the writer, for instance, or the fact that he’s a movie star. (I’m looking at you, Ethan Hawke, not Rupert Everett — although, on the whole, I would prefer to gaze upon the latter, for aesthetic reasons.) An eagerness to replicate the success of a freak bestseller. (Ask anyone who tried to sell historical fiction before COLD MOUNTAIN hit the big time.) Having been a prominent publisher’s college roommate. (One hears rumors.)

But in the vast majority of instances, a book without a strong, distinctive narrative voice will be clear. Perhaps not full of insights or phraseology that makes you squeal and run for your quote book, but at least unobtrusively straightforward, informative, and decently researched.

You know, like newspaper writing. Clear, non-threatening, generic, ostentatiously objective.

To have a voice is to take a SIDE. At least one’s own. For some stories, that’s not the best option.

In fact, your more discerning professional readers have been known to wrinkle their august brows over a manuscript and ask, “Is the voice the author chose for this appropriate and complimentary to the story?”

Not all voices fit with all material, after all — and if you doubt that, would YOU want to read a novel about a grisly series of child murders written in the light-hearted voice of a Christmas card? Or a bodice-ripper romance told in the vocabulary of a not-very-imaginative nun?

I’m guessing not.

At the moment, I work in three distinct voices: in descending order of perkiness, my blog voice, my fiction voice, and my memoir voice. (My memoir is funny, too, but as a great memoirist once told me, part of the art of the memoir is feeling sorry enough for yourself NOT to make light of your personal tragedies, for there lies your subject matter.)

Why not write everything in my favorite voice? Because it would not be the best fit for everything I choose to write.

For instance, if I used my memoir voice here, to discussing the sometimes-grim realities of how the publishing industry treats writers, I would depress us all into a stupor. Because Author! Author!’s goal is to motivate you all to present your work’s best face to the world, I use a cheerleading voice.

Minion, hand me my megaphone, please.

One of the great things about gaining a broad array of writing experience is developing the ability to switch voices at will; you have to come to know your own writing pretty darned well for that. I’ve written back label copy for wine bottles, for heaven’s sake, (when I was underage, as it happens), as well as everything from political platforms to fashion articles. Obviously, my tone, vocabulary choice, and cadence needed to be different for all of these venues.

(Some professional advice for anyone who should find herself writing wine descriptions: there are only a certain number of adjectives that may be safely and positively applied to any given varietal; nobody is ever going to object, for instance, to a chardonnay description that mention vanilla undertones. Go ask the enologist who blended the wine you’re supposed to be describing to give you a list of five, then start seeing how many of them you can use in a paragraph. Voilà! Wine description!

See? Every writing project is a potential learning opportunity.)

Granted, not all of those writing gigs were particularly interesting, and I would not be especially pleased if I were known throughout recorded history as primarily as the person who penned the platitude tens of thousands of people read only when their dinner date left the table for a moment and the only reading matter was on the wine bottle. Yet all of my current voices owe a great deal to this experience, just as playing a lot of different roles in high school or college drama classes might give a person poise in dealing with a variety of situations in real life.

Right after I graduated from college, I landed a job writing and researching for the LET’S GO series of travel guides. The series’ method of garnering material, at least at the time, was to pay a very young, very naive Harvard student a very small amount of money to backpack around a given area. The job was jam-packed with irony: I was supposed to do restaurant and motel reviews, for instance, but my per diem was so small that I slept in a tent six nights per week and lived on ramen cooked over a campfire.

You might want to remember that the next time you rely upon a restaurant review published in a travel guide. (See earlier comment about not all published writing’s necessarily being good.)

Let’s Go’s tone is very gung-ho, a sort of paean to can-do kids having the time of their lives. But when one is visiting the tenth municipal museum of the week — you know, the kind containing a clay diorama of a pioneer settlement, a tiny, antique wedding dress displayed on a dressmaker’s form, and four dusty arrowheads — it is hard to maintain one’s élan. Yet I was expected to produce roughly 60 pages of copy per week, much of it written on a picnic table by candlelight.

Clearly an assignment that called for simple, impersonal clarity, right?

I can tell you the precise moment when I found my travel guide voice: the evening of July 3, a few weeks into my assignment. My paycheck was two weeks overdue, so I had precisely $23.15 in my pocket.

It was raining so hard that I could barely find the motel I was supposed to be reviewing. When I stepped into the lobby, a glowering functionary with several missing teeth informed that the management did not allow outsiders to work there.

“Excuse me?” I said, thinking that she had somehow intuited that I was here to critique his obviously lacking customer service skills. “I just want a room for the night.”

“The night?” she echoed blankly. “The entire night?”

Apparently, no one in recent memory had wanted to rent a room there for more than an hour at a stretch. The desk clerk did not even know what to charge.

(If you’re too young to understand why this might have been the case, please do not read the rest of this anecdote. Go do your homework.)

I suggested $15, a figure the clerk seemed only too glad to accept. After I checked into my phoneless room with the shackles conveniently already built into the headboard and screams of what I sincerely hoped was rapture coming through the walls, I ran to the pay phone at the 7-11 next door and called my editor in Boston.

“I have $8.15 to my name,” I told him, while the rain noisily drenched the phone booth. “The banks are closed tomorrow, and according to the itinerary you gave me, you want me to spend the night a house of ill repute. What precisely would you suggest I do next?”

“Improvise?” he suggested.

I elected to retrieve my $15 and find a free campground that night, so Independence Day found me huddled in a rapidly leaking tent, scribbling away furiously in a new-found tone. I had discovered my travel writing voice: a sodden, exhausted traveler so astonished by the stupidity around her that she found it amusing.

My readers — and my warm, dry editor back in Boston — ate it up.

I told you this story not merely because it is true (which, alas, it is; ah, the glamour of the writing life!), but to make a point about authorial voice. A professional reader would look at the story above and try to assess whether another type of voice might have conveyed the story better, as well as whether I maintained the voice consistently throughout.

How would a less personal voice have conveyed the same information? Would it have come across better in the third person, or if I pretended the incident had happened to a close friend of mine?

Appropriateness of viewpoint tends to weigh heavily in professional readers’ assessments, and deservedly so. Many, many submissions — and still more contest entries — either do not maintain the same voice throughout the piece or tell the story in an absolutely straightforward manner, with no personal narrative quirks at all.

What might the latter look like on the page? Like a police report, potentially. Let’s take a gander at my Let’s Go story in a just-the-facts-ma’am voice:

A 22-year-old woman, soaked to the skin, walks into a motel lobby. The clerk asks her what she wants; she replies that she wants a room for the night. When the clerk tells her they do not do that, she responds with incredulity. The clerk gets the manager, who repeats the information. Noting the 7′ x 10′ wall of pornographic videotapes to her right and the women in spandex and gold lame huddled outside under the awning, flagging down passing cars, the young woman determines that she might not be in the right place. She telephones her editor, who agrees.

Not the pinnacle of colorful, is it? A contest judge would read this second account and think, “Gee, this story has potential, but the viewpoint is not maximizing the humor of the story.” She would then subtract points from the Voice category, and rightly so.

Millicent would probably just yawn and yell, “Next!”

Another technical criterion often used in evaluating voice is consistency, as I mentioned last time. Having made a narrative choice, does the author stick to it? Are some scenes told in tight third person, where we are hearing the characters’ thoughts and feelings, while some are told in a more impersonal voice, as though observed by a stranger with no prior knowledge of the characters?

Your more sophisticated professional reader (Millicent’s boss, perhaps, who has been at it a decade longer than she has) will often also take freshness of voice and point of view into account. How often has this kind of narrator told this kind of story before?

Which brings us back to the desirability of copying what you admire, doesn’t it? If imitation is the sincerest form of flattery (which I sincerely doubt), then the narrative choices of bestselling authors must spend a heck of a lot of time blushing.

You wouldn’t believe how many stories were told by the deceased in the years following the success of THE LOVELY BONES, for instance, or how many multiple-perspective narratives followed hot on the heels of THE POISONWOOD BIBLE.

I’m not going to lie to you — there is no denying that being able to say that your work resembles a well-known author’s can be a useful hook for attracting agents’ and editors’ attention. (“My book is Sarah Vowell meets household maintenance!” “My book is BRIDGET JONES’ DIARY set in a rehab clinic!” “The story is SCHINDLER’S LIST, only without the Nazis or all the death!”) However, as the late great Mae West liked to point out (and I like to remind my readers she liked to point out), while copies may sell in the short term, for the long haul, what is memorable is originality.

Perhaps that is one of the best measures of how effective a book’s narrative voice is: three days after a reader has finished it, will he remember how the story was told? Individual phrases, even? In a generic-voiced narrative, usually not.

Of course, after Millicent and her cronies take all of these factors into account, whether the professional reader happens to LIKE the narrative voice is still going to weigh heavily into her calculations. That’s inevitable, and there’s nothing a writer can do about it — except to make her narrative voice as strong and true and individually hers as she can possibly can.

Because then one reader, at least, will be satisfied: you.

Keep up the good work!

Posted on - 7 Comments on Finding your voice, or, yet another post featuring a small, nagging bug

Finding your voice, or, yet another post featuring a small, nagging bug

I begin today with some terrific news about one of our own, FAAB (Friend of Author! Author! Blog) and fabulous writer Caleb Powell has just signed with agent Diane Nine of DC-based agency Nine Speakers, Inc.. Congratulations, Caleb!

Keep that good news rolling in, everybody — we all love hearing about it.

Despite being happy for Caleb, I’m feeling a bit stuffy-headed today, perhaps due to the fact that the great big crabapple tree in my backyard has suddenly burst into magnificent masses of pink blooms. Very beautiful, very pollen-laden.

It reminds me of the small town — a village, really, ensconced within an agricultural preserve — where I grew up, in the Napa Valley. (Note to those not from those parts: PLEASE don’t refer to the entire area as Napa; it makes the locals apoplectic. Napa is a well-developed city on the south end of the quite rural Napa Valley. If you’re thinking of vineyards, you actually mean the latter. Thank you.)

Tourists overrun the Napa Valley in the autumn, when the grapevines sport leaves ranging from bright green to mellow gold to sunburned red, but my favorite time there has always been the early spring, this time of year, when the vines are dormant and the vineyards are full of knee-high fluorescent yellow mustard flowers: acres and acres of neon brilliance.

The local truism runs that if you don’t suffer from pollen allergies during a Napa Valley spring, you never will. Because I am inherently contrary, I never suffered from pollen allergies while I was living there. Then, years later, I moved to Seattle, where the pollen apparently especially virulent.

A-choo.

I bring this up, not merely because my head is stuffy, but as an apt metaphor for today’s topic. Some weeks back, intrepid and curious reader Gordon wrote in to ask:

Anne – How do we tell if our voice is actually …our voice—? Is there an easy answer, or do we rely on our early reader to tell us? Or our editor?

Terrific question, Gordon, and one that is surprisingly rarely discussed at literary conferences or in writing classes. There’s a pretty good reason for this: while craft is general, voice is individual.

Which is, I must admit, why my first response to this question was, “God, no — by definition, the best arbiter for a truly original voice is its author.” Authorial voice can’t really be taught (although there are some writing teachers who would disagree with me on that point): typically, it arises organically, often after years of cultivation.

I already hear some disgruntled muttering out there. “Very pretty, Anne,” these mutterers say, “but we’re looking for practicality here, not philosophy. What precisely IS voice, and why should I worry about whether my work exhibits a unique one?”

For those of you who have heard it bruited about in literary circles but were afraid to ask for a definition, voice is that combination of tone, worldview, vocabulary, rhythm, and style that makes one author’s work differ from another’s, even if they are telling the same story.

It is, to put it as simply as possible, what makes YOUR work sound like YOU, and not like someone else.

In a book with a strong, well-developed voice, every paragraph — indeed, every sentence — will be in that voice, a phenomenon the pros call consistency. And that’s darned hard for a writer to pull off, particularly (as is often the case for those new to the craft) if the writer in question isn’t quite sure what his voice IS.

But think about it: as a reader, don’t you expect consistency of voice — and haven’t you ever read a book where the tone, vocabulary, and/or style abruptly altered so much that it jarred you out of the storyline?

Most readers dislike that feeling of being pulled out of the story, so industry pros tend to edit with an eye to removing it. The result: the authors we tend to love are those whose voices are so consistent that if we took a two-line excerpt from Chapter 2 and another from Chapter 8, we could tell that the same person wrote them.

“Golly,” say the former scoffers, “that sounds awfully important. Why doesn’t every writers’ conference devote huge amounts of time to helping aspiring writers seek out and develop theirs?”

Beats me — unless it’s because by definition, teaching a group means catering to commonalities; to help a writer develop his voice, an instructor would have to read enough of his work to figure out what he does better than any other writer on the planet, the literary acumen to weed out those elements that are borrowed from other authors’ styles (more common than you might think), and the time to encourage the writer, draft after draft, to cater to his own strengths.

Kind of a tough brief for a one-time two-hour seminar with twenty students, no?

To be fair to conference organizers, most submissions do fall under the weight of formatting, grammar, and clarity problems, not an inconsistency of voice, so it does make some sense to offer instruction on those issues first. And when a writer is still struggling to express herself clearly and in a way that will appeal to an established market, those are definitely the skills she should master first.

Or, to put it another way, if her manuscript is not in standard format, contains many grammatical errors, and is confusing to read, an agent or editor’s rending his garments and crying, “But the voice is not consistent!” is probably the least of her worries.

So, to reiterate Gordon’s question, how does a writer know when he’s found his voice? For starters, it’s extraordinarily rare that an author’s distinctive personal voice shows up in her first writing projects, except perhaps in flashes.

Why? Well, as much as we might like to think of ourselves as expressing ourselves as no one else does, doing so in writing is a rather difficult skill to master. Most writers begin by imitating the voices of authors they admire, so it’s not at all uncommon to see a manuscript scene that contains a patch that reads a bit of Annie Proulx, a terse dialogue reminiscent of Ernest Hemingway, and a blistering line or two of Jay Mcinerney cynicism, all tied together by a few straightforward declarative sentences.

Tell me, out of all of those disparate elements, which part is the writer’s own voice?

Usually — and brace yourselves, because some of you may find this rather discouraging — a writer comes to recognize her own voice because over time, it becomes the most natural for her to use. Its consistency sits up and announces itself to be how she should be writing all the time.

Which means, Gordon, that I have quite an annoying answer to your excellent question: you may not know what your voice IS, but you will probably recognize it when you see it.

I know, I know; that sounds very woo-woo, but I swear that it’s true. For most good writers, one day, after seemingly endless writing, a personal voice abruptly emerges and takes over the narration, like all of those crabapple and mustard flowers bursting into bloom.

And the writer says, “Hey, I like that. I think I’m going to write like that all the time.”

To complicate matters, just as those early spring flowers make some people smile and others sneeze violently, a strong, original voice will not appeal to all readers, so not all published writing DOES exhibit an individual narrative voice. The more distinctive the voice, the greater the risk, in a way — it can irritate in a way that a merely clear, pleasant, generic voice may not.

And that, in case you were wondering, is one of the many reasons that journalists are trained to sound so much alike: they are urged to keep their individual voices out of the story, so as not to distract the reader.

The ambient mutters have been steadily growing to a near-roar. “Okay, now I’m REALLY confused,” I can hear some of you saying. “If I understand you correctly, it’s safer NOT to write in an individual voice, but if I want to be known for the beauty of my writing, I need not only to do just that, but to do it consistently throughout my manuscript.”

Nicely summarized, ghostly mutterers: it is a genuine paradox. It’s also a choice that every writer has to make for himself.

Feet continue to shuffle out there, and hips to shift uncomfortably on computer chairs. “What I’m really asking, I guess, is what separates a good voice from a bad voice. Or, to put it another way, how on earth can an agent, editor, or contest judge rate voice on anything but personal preference?”

Remember back in my Book Marketing 101 series, when I pointed out that, contrary to popular opinion amongst the aspiring, a writer shouldn’t want to sign with just ANY agent; she should aspire to signing with one who truly loves her work? This is precisely why — response to voice IS quite individual.

Is the common rejection line I just didn’t fall in love with it making a bit more sense now?

In order to represent you successfully, an agent needs not only to like your voice, but to be able to identify what is individual about it lucidly enough to be able to go to an editor and say truthfully, “Look, based on the books you have been buying lately, I think you are going to like this author’s voice, for these twelve reasons…”

Because a runny nose is apparently conducive to decoding cosmic mysteries, allow me to add: that’s why nonfiction is reputed to be easier to sell than fiction; fiction is inherently much more heavily reliant upon voice, right? Particularly literary fiction, where the freshness and strength of the voice is the book’s primary selling point.

And, let’s face it, no matter how strong a story is, few readers will finish a novel if they dislike the author’s voice. “I just couldn’t get into it,” they will say, setting it aside.

Nonfiction, on the other hand, is much more concerned with the interest of the subject matter, the slant of the approach, and — yes, I must say it — the credentials of the author. (Oh, stop your groaning — you didn’t honestly expect me to talk about selling NF {without} bringing up platform, did you?) While a strong voice may be an additional selling point, clarity is generally the main desiratum.

Unless, of course, it’s a memoir, where voice is nearly as important as in a novel.

Is your head spinning from all this? Not to worry; tomorrow, I shall discuss voice choices in greater detail.

For today’s purposes, it’s less important that you come away from this with a clear idea of the strategic uses of voice than to realize that you may well have more than one voice lurking inside you — and that before you can make it consistent throughout the narrative, you are going to want to give some thought to tailoring the one you choose to emphasize to the book project at hand.

“I’ve got just one more question,” the disgruntled mutterers who have been dogging me throughout this post are piping up to say. “Why did you decide to start talking about voice in what I sincerely hope is the middle, not the end, of a series on keeping our narratives moving?”

Because, my friends, there is more to revising a manuscript than deciding whether this sentence is necessary, that paragraph is clear, or a scene tells rather than shows. All of these are necessary, of course — but ideally, a revising writer should also be asking himself, “But does this part of the manuscript fit with the overall voice? Does it sound like ME?”

Just a small, noisy bug to stick in your ear while you’re reviewing your manuscript. Keep up the good work!

Posted on - 4 Comments on The Short Road Home, part VII: those pesky teenagers — and a major milestone!

The Short Road Home, part VII: those pesky teenagers — and a major milestone!

Sic transit gloria.

The reconstruction of my devastated back yard proceeds apace — there have been so many workmen with great big boots tramping through my erstwhile flowerbeds of late that I’m quite positive the resident mole believes a hostile army has invaded his territory.

The photo above represents the last hurrah of our hot tub before it went the way of all flesh. Since my agent is currently circulating my novel, THE BUDDHA IN THE HOT TUB, it seemed only appropriate that the little statue should be the last thing evacuated.

With great destruction comes the possibility of new growth, though, and I have to say, even as an editor experienced in making large-scale cuts to manuscripts, I have been impressed to see just how many new vista opportunities have been opening up each time a backhoe accidentally knocks over a small tree.

An ornamental cherry, just about to bloom. Talk about killing your darlings.

The process has been reminding me a great deal of the first two years after I sold my memoir to a publisher, actually: after working up courage to dig up a story that hadn’t seen the light of day for over twenty years, all hell broke loose for two solid years. Every time I started thinking, “Okay, I could learn to live with the new status quo around this book,” BANG! Down went another tree. Or a backhoe took a great big hole out a flowering pear, doubtless cutting the coming summer’s crop by a third.

Metaphorically, of course.

The upheaval on both the garden and memoir fronts remains substantial — and ongoing — but I’m sure the wee Buddha would approve of the hourly evidence my environs are giving that nothing is really permanent. And that building something lasting typically involves quite a bit of ground-clearing first.

Doesn’t that just make you want to take out the machete and leap back into revising your manuscript? No? Well, there’s no accounting for taste.

But before we launch into the topic du jour, a drum roll, please, for an announcement of moment: this is my 500th blog on this site!

To those of you who didn’t follow me over from my old Resident Writer blog on the Organization-That-Shall-Not-Be-Named’s website, this total may seem a bit off, as there are about 800 posts archived here, including roughly 300 from my former gig. (Also, I haven’t been counting guest posts and interviews toward the final count.)

So these last half-thousand have all been written specifically for you, the Author! Author! community, under my own aegis. You’re welcome.

When the blog has reached similar milestones in the past, I have gone back and figured out how many pages I’d written, measured in standard manuscript format, but at this point, it’s just too daunting a task. Suffice it to say that it’s been thousands of pages of my ranting at you about the joys and imperatives of standard format, the ins and outs of pitching and querying, and my vast preference for writers reading their work — chant it with me; you surely know the words by now — IN ITS ENTIRETY, IN HARD COPY, and OUT LOUD before sending it to make its merry way through an agency or publishing house.

Clearly, I need to take a weekend off.

But let’s finish this mini-series (so to speak) first, shall we? For the last week, I’ve been talking about that graveyard of literary tension and promoter of telling rather than showing, the Short Road Home, a scene or plot that resolves conflict practically the nanosecond it appears.

After a lifetime of reading and a decade of editing, I have to say, I don’t think that most writers appreciate just how much the average reader enjoys savoring conflict — or how much more trivial an easily-solved problem appears on the page than one with which the protagonist must struggle for pages or chapters on end. Just as an Idiot Plot that is resolved the instant someone thinks to ask Aunt Joyce her ring size is less than dramatically satisfying, a plot resolved by a Short Road Home tends to leave readers feeling underfed.

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

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

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

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

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

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

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

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

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

Not quite a 500th post kind of day, perhaps, but close.

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

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

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

When hard-working Tom Carver opened the front door, arriving home late from work at the stuffed animal plant yet again, his daughter, Tanya, refused to speak to him. Glaring at him silently with all of the dastardly sneer her fifteen-year-old face could muster, she played with her spiky, three-toned hair until the third time he had considerately asked her how her day had been.

“Like you care!” she exclaimed, rolling her eyes dramatically. She rushed from the room.

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

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

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

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

But when instant therapy intervenes, all of that juicy conflict just becomes another case study, rather than gas to fuel the rest of the book, diffusing what might have been an interesting scene that either showed the conflict (instead of telling the reader about it), provided interesting character development, or moved the plot along.

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

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

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

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

ESPECIALLY if it’s the therapist.

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

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

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

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

Which you should strive to do as often as possible — at least in your first book, where you really need to wow the professionals to break in. After you make it big, I give you permission to construct a plot entirely about a couple of characters sitting around talking, motionless.

Happy 500th, everybody — and, as always, keep up the good work!

Posted on - 5 Comments on The Short Road Home, part VI: Tommy! Watch out for that bear lurking at the end of the scene! Tommy!

The Short Road Home, part VI: Tommy! Watch out for that bear lurking at the end of the scene! Tommy!

Yesterday, as I was blithely chattering about the various narrative disadvantages of the Short Road Home — for those of you joining us mid-series, that’s my pet name for when a book introduces a conflict, only to resolve it immediately, often before the reader has a chance to register that the problem raised is at all serious — I mentioned in passing that in both novels and memoirs, agents and editors often see the use of the historical future tense as part of a writerly plot to minimize the tension of what could be a very exciting scene.

How does a simple tense choice set off this level of alarm bells? Because of the alarming ubiquity of section-opening paragraphs that telling the reader how the scene how it’s going to end before the scene even begins. Sometimes, such foreshadowing is subtle:

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

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

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

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

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

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

For the sake of clarity, then, beginning a scene at the beginning and proceeding to the end without extensive temporal detours is the established norm. But this structure holds benefits on a tension level as well, because if the reader already knows what is going to happen before a scene begins, the temptation to skim or even skip the recap can be considerable.

Particularly, say, if the reader in question happens to be Millicent the agency screener, trying to get through a hundred submissions in an afternoon. Maybe she should run out and grab a latte to perk herself up a little…

So if you were looking for a good place to start cutting in order to get your manuscript under 100,000 words, running a quick scan for the historical future tense might be a dandy place to start. Often, such opening paragraphs may be cut wholesale with little loss to the overall story. Ditto with premature analysis.

Of course, in a well-crafted manuscript, editing choices are not always that cut-and-dried, as clever and incisive memoirist/reader Susan commented yesterday. Talk about foreshadowing: I was planning to elaborate upon perils of foreshadowing today, and she asked yesterday:

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

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

Which would be precisely true, yet not really answer the question.

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

Yes, Example #1 does provide analysis of action that has not yet happened, from the reader’s point of view — and doesn’t it make a difference to think of a foreshadowing paragraph that way, campers, instead of as a transition between one scene and other? — but it does not, as Susan puts it, spill the beans.

The reader knows that something traumatic is going to happen, and where, but not enough about either the event or the outcome to spoil the tension of the upcoming scene.

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

Which, again, is dangerous strategy in a submission: such an introduction raises the expectations for the scene that follows pretty high, doesn’t it? If a text promises Millicent thrills and doesn’t deliver them, she’s not going to be happy. Trust me on this one.

Frankly, though, if she’s already in a touchy mood — how many times must the woman burn her lip on a latte before she learns to let it cool before she takes a sip? — the mere sight of the historical future might set Millicent’s teeth on edge, causing her to read the scene that follows with a jaundiced eye.

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

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

Heck, it’s not all that uncommon to see it used more than once within the first five.

By the end of any given week of screening, poor Millie has seen enough variations on But little did I know that my entire world was about to crumble to generate some serious doubt in her mind about whether there’s something about writing memoir that causes an author to become unstuck in the space-time continuum on a habitual basis.

Which, in a way, we do. Since memoirs by definition are the story of one’s past, really getting into the writing process can often feel a bit like time-travel.

After all, how else is a memoirist going to recall all of those wonderfully evocative telling details that enlivened the day a bear ate her brother?

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

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

Most of the time, Millicent would vote for the latter. So would I.

It’s very easy to kill genuine suspense (i.e., the kind that arises organically from the interactions between the characters as the story chugs along) through foreshadowing. All too often, manuscripts tell the story backwards, informing the reader that a shock is to come in such explicit terms that when the shock actually occurs, the reader yawns and says, “So?”

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

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

Seriously, this can pose a tension-reduction problem. Take, for example:

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

Think about this scene-introducer from the reader’s perspective — even assuming that the reader had gleaned no previous inkling that Jacques might be contemplating going AWOL, what does the narrative gain from opening with the scene’s big shocker? Yes, announcing it this way might well evoke a certain curiosity as to why Jacques ran away from home, perhaps, but why not let the reader experience the shock along with the family?

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

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

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

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

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

You may laugh, but as Millicent would have been the first to tell you had not I beaten her to the punch (I defy you to try to diagram this sentence so far), few manuscript submissions contain surprises that are actually surprising to a professional reader. Partially, as we discussed earlier in the week, this is the fault of the pervasiveness of the Idiot Plot in TV and film, of course, but it also seems that many aspiring writers confuse an eventuality that would come out of the blue from the point of view of the character experiencing it with a twist that would stun a reader.

Again, it all depends upon the writing. (Hmm, where have I heard that before?) At the risk of espousing a radical new form of manuscript critique, I’m a big fan of allowing the reader to draw her own conclusions — and of trusting her to gasp when the story throws her an unanticipated curve ball.

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

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

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

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

In fact, a great way to increase plot tension in a story featuring a psychic character is to show him being wrong occasionally. Mixes things up a bit for the reader.

But — correct me if I’m wrong — in real life, most of us don’t hear giant voices from the sky telling anyone who might happen to be following our personal story arcs what is going to happen to us 20 minutes hence.

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

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

Again: if you DO find that your life starts being narrated on the spot by a talking vulture, you might want to seek some professional help.

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

Okay, so that wasn’t one of my better metaphors; darn that noisy vulture for distracting me.

Nice to be chatting about craft again, isn’t it? Keep up the good work!

Posted on - 7 Comments on The Short Road Home, part V: when you SHOULDN’T let your conscience be your guide

The Short Road Home, part V: when you SHOULDN’T let your conscience be your guide

For the last few days, I’ve been talking about the Short Road Home, my pet term for a scene that introduces a potential conflict, only to resolve it so quickly that the reader barely has time to notice an increase in ambient tension. Short Roads Home have been the downfall of many a submitted novel, as such scenes almost invariably tell rather than show, minimize inter-character conflict, and let the tension of the story lag.

Today, I’m going to show you how to recognize the subtle form of Short Road Home, so you may see this common mega-problem in action and learn how to fix it. I want to be as clear as possible about this, so you may spot it as you revise your own work.

Why the urgency? Well, there is a reason that most professional readers will dismiss a manuscript that has more than one Short Road Home in the first couple of chapters: it is one of the single most frequently-seen mega-problems in fiction. So much so, in fact, that an experienced pro might not even have to read more than a couple of lines of a scene to identify it — and shove the submission into the rejection pile.

Long-time readers of this blog, did a light bulb just appear above your heads? Did it occur to you as if archangels suddenly appeared and shouted the news into your awed ears that, as with nonstandard formats, an ultra-frequent mega-problem in a manuscript might actually be a WELCOME sight to an agent, editor, or contest judge, because it means that the work can be rejected without further ado — or further reading time?

If so, congratulations — you now have a much, much firmer grasp of how submissions work than a good 95% of the writers currently slapping stamps on SASEs. It’s one of the great agency paradoxes: yes, they are always on the lookout for that great undiscovered new talent, but the faster they can sift through the rest and reject them, the better they like it.

Or so I’m told. By literally everyone I’ve ever met who has ever worked in an agency.

How may NOT being aware of this paradox harm a submitting writer? Because it often — and I know that all of you are far, far too savvy to do this, dear readers — leads the aspiring to leap to the unwarranted conclusion that an agent or editor will be so delighted by a fresh new voice that s/he is automatically going to be willing to ignore other problems in the manuscript until after the contract is signed.

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

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

And never, alas, does one hear, “This author seems to have trouble moving the plot along and maintaining tension, but that’s nothing that a good writing class couldn’t fix. Let’s sign this writer now, and help her grow as an artist.”

As delightful as it would be if they DID habitually say express such sentiments — better still, if they routinely acted upon them — this just doesn’t happen for writers who don’t already have a solid platform (i.e., a special expertise or celebrity status to lend credibility to a book). I suspect that, say, the first readers of Barbara Boxer’s recent novel or Ethan Hawke’s granted them quite a bit of latitude (not to say editorial help), because, in the industry’s eyes, what is being sold when a celebrity writes a book is the celebrity’s name, rather than the manuscript.

As a non-celebrity writer, you can generally assume that the first reader at an agency, publishing house, or contest is looking for reasons TO weed your work out. Millicent and her ilk don’t worry too much about too quickly rejecting the next great American novel — since writers are resilient creatures who improve their skills on their own time (and dime), the publishing industry is fairly confident that the great ones will keep coming back.

For some reason, people in the writing community — especially those who write for writers’ publications and teach seminars, I notice — don’t like to talk about that much. Maybe it’s so they can put a positive spin on the process, to concentrate on the aspects of this honestly hugely difficult climb to publication that are within the writer’s control. As far as I’m concerned, mega-problems are very much within the writer’s control, as are other rejection triggers — but only if the writer knows about them in advance of submission.

So let’s get down to the proverbial brass tacks and see about clearing up this mega-problem.

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

A common example: when a protagonist apparently shows up to a scene purely in order to comment upon it as an outside observer, rather than participating actively in it.

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

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

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

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

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

Ta da! Situation understood! Conflict eliminated!

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

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

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

It makes for a more involving narrative.

Also, when the instant-analysis device is overused, the reader can become jaded to it pretty quickly. After the third or fourth use — or after the first, if the reader happens to be a professional manuscript-scanner — the reader is apt to become convinced that that there is absolutely no point in trying to second-guess the protagonist, because if the author is going to tell her right away what to conclude from what has just passed.

Which, correct me if I am wrong, completely prevents the reader from enjoying one of the great joys of getting into a novel, trying to figure out what is going to happen next. Hyper-analytical protagonists seldom surprise.

As we saw yesterday (thank you, Elinor Glyn), instant analysis can relieves the conflicting characters of any urgency they might have felt in resolving their interpersonal issues. Since Jiminy Cricket hops on in and spells out everyone’s underlying motivations, the hard work of figuring one’s own way out of a jam is rendered unnecessary.

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

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

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

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

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

I’m going to stop for the nonce, but I shall continue to wax poetic on this subject next time. In the meantime, make sure those protagonists stay active, concentrate on giving the reader enough material so s/he may draw the correct conclusions about what’s going on, and keep up the good work!

Posted on - No Comments on Beefing up that conflict: avoiding the Short Road Home

Beefing up that conflict: avoiding the Short Road Home

Looks like a Christmas tree, doesn’t it? But no, I took this photo last night from my studio’s window. Snow. In Seattle. In April.

I don’t think Persephone’s going to be reunited with her mother anytime soon. She and that groundhog that was supposed to tell us how much longer winter would be are obviously holed up in an underground cave somewhere, shivering.

But that shouldn’t prevent us from pressing on, should it? Bundle up warmly, please; it’s going to be a long trek into the rough terrain of self-editing.

A few weeks back, in the early days of our recent series on getting good at hearing and incorporating feedback, intrepid readers Gordon and Harold wrote in asking about how to increase conflict and tension, respectively, in a manuscript.

As often happens with a request like this, my first instinct was to huff in the general direction of my monitor, “Oh, heavens, not THAT topic again! Didn’t I just cover that a couple of months ago?” Yet in going back through the archives to create these much-needed additions to the category list at right, I noticed — could it be possible? — that it had been over six months since I had addressed either issue in a really solid way.

My apologies. I guess my life must have been too full of conflict and tension for it to occur to me to write about it here. Since it HAS been such a long time, I’m going to go racing back to the basics, so we’re all on the same page.

Let’s define our terms, shall we? Colloquially, conflict and tension are often used interchangeably, but amongst professional writers and those who edit them, they mean two different but interrelated things.

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

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. 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 problems with one often suffers from the other as well. First-time novelists and memoirists are particularly prone to falling prey to both, not only because keeping both high for an entire manuscript is darned difficult, but also because 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 our pal Millicent the agency screener 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 front to back.

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.

Which is, of course, precisely when it’s most tempting NOT to give your work a thorough read-through.

I can’t emphasize enough how great a mistake this can be. 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.

Let’s all chant the mantra together again for good measure: before you send it in, 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 you don’t forget the night before the deadline. (Also, a word to the wise: if you want to leave time to fix mega-problems, waiting until the night before a contest entry needs to be postmarked probably isn’t prudent.)

There are many, many reasons that manuscripts lack conflict and tension, far too many to list here. In the interests 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. For the next couple of days, I shall focus on the full-bodied version.

The Short Road Home is when a problem in a plot is solved too easily for either its continuance or its resolution to provide significant dramatic tension — 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.

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 conflict seems insurmountable — and then it turns out that all the character 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 India leads directly to him.

Ta da! Crisis resolved. No roadblocks here.

Or, to view this phenomenon in the form that Millicent most often sees it: pages at a time pass without conflict — and when a long-anticipated conflict does arise, the protagonist swiftly reaches out and squashes it like a troublesome bug.

Often before the reader has had a chance to recognize the conflict as important. Wham! Splat! All gone, never to be heard from again. It drives Millicent nuts.

Slice-of-life scenes are, alas, particularly susceptible to this type of 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. On the page, good manners tend to be 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.

Hint: if the clue is in plain sight, most professional readers will resent not being filled in 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 for six more chapters. It’s considered a cheap form of tension-building.

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.

“Wait a darned minute,” I can hear some of you say, “The very fact that Mssr. Ebert has a pet name for it means that Idiot Plots are widely accepted in the moviemaking 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 book’s tension? Would fleshing out a conflict increase the book’s tension at a crucial point?

Would, in short, the manuscript exhibit both conflict AND tension on every page if you DIDN’T take those shortcuts?

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. Remember in the classic TOM JONES, where 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 now. 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.

Next time, I’ll talk a bit about how to spot the Short Road Home on the manuscript page — and what to do about it. In the meantime, keep up the good work!

Posted on - No Comments on Writing compelling memoir: enough about you; what about me?

Writing compelling memoir: enough about you; what about me?

Yes, I promise: I WILL begin my long-anticipated series on pitching your work very soon. Tomorrow, in fact, if all goes according to plan. But before I wrapped up perspective for the nonce, I wanted to address a couple of questions reader Susan asked a couple of weeks back:

I know the current series re passivity pertains to fiction, but I wonder if you might offer some observations about memoir… I understand the reflective narrator is an important part of memoir, but I’m worried she may be too prominent in my MS. Any thoughts about how to reign her in? Must every scene be an action scene? Obviously, the reality of what happened shapes what is possible.

Another memoir question — with apologies for going off-topic: how critical is a well-defined narrative arc? Do all memoirs require this?

Actually, glancing back over my masses of posts, I’m rather surprised at just how few of them deal with memoir directly. So while these questions really would take a week to answer properly, instead of pushing them back until after the pitching series, I’m going to take a day to deal with them at least in passing now.

Why is it surprising that I haven’t written more on memoir, you ask? Almost all writers write about their lives at one time or another, and I’m no exception: I won a major award for IS THAT YOU, PUMPKIN?, the first draft of my memoir-still-in-publishing-limbo, A FAMILY DARKLY: LOVE, LOSS, AND THE FINAL PASSIONS OF PHILIP K. DICK. (The limbo part is a long story, with its own category at right, if you’re interested. If not, the short-short version: publishers fear the unsubstantiated opinions of people with gobs and gobs of money.) And my agent is currently circulating the proposal for a memoir I’m co-writing with an environmental and civil rights whistleblower.

Oh, and I edit memoirs all the time. I am, in short, up to my eyeballs in memoir.

So why do I so seldom write about it here? Well, at first, to be quite frank, I was trying valiantly not to whine about what was going on with A FAMILY DARKLY; I started blogging within a week of the first lawsuit threat, and my publisher told me to keep quiet about the details.

(Of the juicy and vitriol-stained variety. But I’m not supposed to talk about that.)

But beyond that, I think it’s more dangerous to generalize about memoir than about most types of writing. Writers tend to be touchier about their autobiographical efforts, for one thing, even at the sentence level. But beyond that, so much of what one might say about memoir seems at first blush self-evident: it’s a first-person narrative, and most definitely an application of the time-honored axiom to Write What You Know.

Which leads to the single biggest problem memoir manuscripts typically have: anecdotalism.

All too often, the author will have apparently told the story on the page so often that the print version carries the vagueness of a verbal telling, as if the reader were a friend who has heard the story ten or twelve times before and might interrupt this particular rendition. Or assumes, incorrectly, that the reader will already be familiar enough with the circumstances of the author’s life for only a brief sketch to be necessary.

But for a memoir to be a success, it’s not enough that the events on the page really happened, or even that the writing is beautiful, right? It must above all things be a good STORY well told, and its actors great CHARACTERS well developed.

Which means — to take Susan’s second question first — that the story arc is quite important. And, as she so rightly points out, that can be genuinely difficult to pull off, at least if you happen to believe that time runs in a linear direction: in real life, stories seldom have a clear beginning, middle, and end. Often, too, actual events crawl precisely where a reader would most like them to speed.

From a reader’s perspective, both phenomena are problematic: even if the writing is gorgeous, most readers want to be able to try to second-guess where a plot is going to go. The reader wants to be entertained, and frankly, given a choice between hearing the precise truth and a more entertaining spin, he’ll usually punk down the dosh for the more exciting version. Human nature, I’m afraid.

That doesn’t mean that the memoirist should lie to create excitement on the page — but it does mean that it pays to be selective about what should and should not be included. There’s a big difference, after all, between a diary, a journal, and a memoir: a diary chronicles quotidian happenings, a journal analyzes them — and a memoir transforms them into a great yarn.

In this very tight memoir market, you really do want to be telling a great yarn — and it’s awfully hard to construct a gripping tale without ongoing incident. Put another way, if a narrative rambles on for too long without dramatically-satisfying crises and resolutions throughout, how is the reader supposed to cheer for the protagonist? “Go, Betty! Keep on surviving!”

Frankly, unless Betty’s life was pretty vivid — as in Anne Frank-level trauma or Augustin Burroughs-level weirdness — it’s unlikely that a mere selection of episodes is automatically going to elicit the “I’m rooting for you!” response in the reader. But if Betty is an interesting character in an interesting situation, learning and growing throughout the course of the book, it’s easier to identify with her story. Particularly if she’s constantly struggling in small ways; rather than being passive.

And that, my friends, is a workable story arc, one that does not involve lying about actual events. The protagonist does not need to revolutionize the world around her in order to keep surprising the reader by how she interacts with it. Resistance can come in some pretty microscopic forms; the only completely passive person in real life is one who never questions the status quo at all.

For a brilliant example of this difficult challenge pulled off with grace, run, don’t walk to your nearest bookstore and pick up a copy of Barbara Robinette Moss’ CHANGE ME INTO ZEUS’ DAUGHTER. This is the book that made me want to write memoir in the first place: the writing is breathtaking, and she welds a soaring dramatic arc out of a collection of recollections that could very easily been simply depressing. She draws her own personality against genuinely overwhelming situations so well that it left me gasping.

Bear in mind, though, that the most compelling way to tell your own story may well not be the way you are accustomed to telling it. In constructing a memoir’s narrative, I find it very helpful to think about the memoir from our pal Millicent the agency screener’s perspective: how would I market this story to someone wandering through a bookstore? What is unique about it? What makes this story fascinating?

A surprisingly high percentage of memoir-writers don’t seem to regard themselves as very interesting; even more seem to be afraid of presenting themselves as fully-rounded characters, proverbial warts and all. Often, this seems to stem from a fear of reader reaction: am I coming across as likeable?

This can be a pretty loaded question, particularly for that large majority of memoirists who imagine their nearest and dearest as their target audiences. Or, if not their kith and kin, then the good people who will take their side AGAINST their kith and kin, which is another way of concentrating upon the reactions of the people already in one’s life.

This is perfectly understandable — after all, writing memoir means exposing one’s innermost thoughts and feelings. Most of us long for the day that our beloveds read our beautiful prose, strike tears from their eyes, and say, “Wow, babe, touché. I had no idea you felt like that. You are much deeper/more wonderful/in desperate need of help than I had ever dreamt.”

However, if you’re going to make a living as a writer, your buddies/lovers/relatives are not your sole audience, or even your primary one. Total strangers are going to need to find your story fascinating — and for it to sell to an agent or editor, that story had better start being interesting on page 1. Actually, it needs to be interesting before page one, as memoirs are generally sold in proposal form, not as entire books. This means that, generally speaking, the memoirist has only a chapter, or at most two, to grab the professional reader.

So what would make the story fascinating from Millicent’s point of view? A great story well-told, of course, with well-drawn characters — and a compelling protagonist who engages with the world around her, rather than just observing it.

Which brings me back to Susan’s first question, how to get the narrative out of the protagonist’s head: when a section gets too think-y, experiment with telling the story as though it were a novel. Concentrating on the story in which the memoirist is a character, rather than primarily upon the narrator’s reactions, can often make a real-life scene spring to life.

Step back and envision the scene as though you were not an actor in it. Who are these characters? What are the ambient conflicts? Where is this story going, and how does what is happening in the moment help get the protagonist/narrator there?

If none of these questions yield interesting answers on any given page, chances are good that the narrative is telling the story, rather than showing it, an extremely common pitfall for memoirs. Remember, the reader doesn’t know ANYTHING about the life you’re describing unless you illustrate it, and it’s the writer’s job in any kind of book to make the characters live and breathe.

So paint as full a picture as possible. Is there a way that you could flesh out a particular incident, or a character within that incident, to make it better-rounded? Are you streamlining the story to make the protagonist look better — or worse — and if so, is it flattening out the drama?

If you can honestly look at a page of text and say that it is neither telling part of the ongoing story nor developing character, I would ask you to be very brave. Gird your loins, take up the manuscript, and bracket the text that does not advance the story. Then go back a page or two and read, skipping the bracketed part.

Did the narrative make sense without it? If so, could the bracketed section be cut?

Another useful means of getting the narrative out of the narrator’s head is to sharpen the focus upon important elements of the story OUTSIDE of the protagonist. What is your story about, other than you, and how can you make it fascinating to the reader?

Yes, yes, I know — memoirs are inherently about their authors, by definition. Yet realistically, only celebrities’ memoirs sell PURELY because they’re about a particular person’s life. Think like a marketer for a moment: other than the truth of the story, what is unique about this book?

Writers don’t ask this question very often before they start jotting down the stories of their lives, but almost without exception, memoirs are about something else as well. The dying mill town where the author grew up; the traveling circus that captured his imagination; the kind aunt who went into the hospital for a hip replacement and came out with a lobotomy. All of these are rich material for grabbing the reader.

Chances are, this secondary focus is already in the book; are there ways that you could bring it out? Specifically, are there parts of the narrative where playing up this other element would take the reader out of the narrator’s head and into the larger world of the book?

Just as every life is unique, so is every memoir. But a life story needs more than truth and bravery to make a good memoir; if that were all it took, there would be no artistry involved. A great memoirist picks through her memories, selecting the juiciest moments, most telling incidents, and most compelling characters. She spins a web of enchantment, as surely as any fictional storyteller does.

It’s your story: make it shine. And, as always, keep up the good work!

Posted on - 10 Comments on And? And?

And? And?

Hey, great news, everybody: reader Jeff Jacobson has written in to say that he has landed an agent! A good one, too: Steve Laube of the Steve Laube Agency.

Congratulations, Jeff! May your writing career continue to prosper – and may I continue to have such wonderful news to report about my readers early and often.

So keep your chins up, everyone – it CAN be done.

Yesterday, I urged you to scan your submission pages (in particular, the first five) for over-use of the words and, but, and then; in fact, I suggested that you print out these pages and highlight these words throughout, so that you might get a sense of just how often you tend to utilize them.

What was I thinking, you ask, to advise such a time-consuming (and potentially ink-consuming) exercise? Well, quick-reading agency screeners and contest judge are routinely ordered to subtract points for grammatical errors – and that habitual roommate of conjunctions, the run-on sentence, is always high on their penalty list. As is word repetition.

So take up your marked pages, please, and let’s observe the frequency of and.

If you’re like most writers, your marking project probably revealed two major patterns of usage: in lists and in the HUGELY popular X happened and then Y happened structure. See if you can spot ‘em here:

Abe took a deep breath and ran his palms over his face. He pulled his handkerchief from his pocket and mopped the red and black tattoo over his left eyebrow. Outwardly composed, he smiled and extended his hand to Emile.

Although these types of repetition may sound merely chatty when read out loud, they come across as structurally redundant on the page. Let’s look at this same paragraph with a screener’s heightened antennae:

Abe took a deep breath and ran his palms over his face. He pulled his handkerchief from his pocket and mopped the red and black tattoo over his left eyebrow. Outwardly composed, he smiled and extended his hand to Emile.

See? The repetition of all those ands can be downright hypnotic – they lull the reader, even if the action being described on either end of the and is very exciting indeed. Why? Because the eye automatically jumps between repeated words on a page. The result: submission pages that are read far, far more quickly than any of us might wish.

The best way to avoid triggering this skimming reaction is to vary your sentence structure, but while you are editing, it’s also a good idea to keep an eye out for any sentence in which the word and appears more than once. As in:

Ezekiel put on his cocked hat, his coat of many colors, and his pink and black checked pantaloons.

It’s a subtle problem, but did you spot it? To eyes trained to catch redundancy, even this minor word repetition can set editorial teeth on edge. Because we writers tend to think of words according to their respective functions within any given sentence, this kind of repetition often flies under our self-editing radars; unless one is looking for it, it’s easy to overlook.

Thus the highlighting pens.

The other common and structure, X happened and Y happened, is a very frequent stylistic choice for relatively new writers. It’s appealing, as I mentioned yesterday, because like beginning sentences with and, it artificially creates the impression conversation-like flow.

You’re already cringing, aren’t you, in anticipation for the conclusion that so often follows upon a declaration that a writing device is pervasive?

Yes, I’m afraid it’s true: agents, editors, and contest judges tend to have a very low tolerance for over-use of this particular sentence structure. Seriously. I’ve seen pens poked through manuscripts at the third usage of this kind of sentence within half a page.

While you are self-editing, then, it’s a dandy idea to rework any sentence in which and appears more than once. Chances are high that it’s a run-on:

In avoiding the police, Zelda ran down the Metro stairs and out onto the platform and into the nearest train.

This is a classic run-on: too much information crammed into a single sentence, facilitated by those pesky conjunctions.

Some writers, of course, elect to include run-on sentences deliberately in their work, for specific effect. If you choose to do this, strategically speaking, you should avoid using it ANYWHERE else in the text except in these arpeggios of evocative lists.

Why minimize it elsewhere? Well, this device tends to create run-on sentences with and…and…and constructions, which are technically grammatical no-nos. You may be doing it deliberately, but as with any grammatical rule, many writers who do not share your acumen with language include them accidentally.

Let me ask you this: how is a super-quick agency screener to tell the difference? Usually, by noticing whether the device appears only infrequently, which implies deliberate use, or every few lines, which implies writing habit.

Even in literary fiction, it’s rather dangerous to include grammatically incorrect sentences in a submission — to someone who hasn’t read more of your work, it’s impossible to tell whether you are breaking the normal rules of grammar in order to create a specific effect, or because you don’t know the rule. If an agency screener concludes that it’s the latter, the manuscript is going to get rejected, almost invariably.

Thus, unless you are getting a valuable effect out of being ungrammatical, it’s best to save your few opportunities to do so intentionally for when it serves you best.

At the very least, make sure that two such sentences NEVER appear back-to-back, to avoid your submission’s coming across as the work of –gasp! — a habitual runner-on.

As with the use of then, it pays to be extremely selective. Sometimes the repeated ands work rhythmically, but to an agent or editor, a manuscript that employs X happened and Y happened as its default sentence structure it just starts to read like uncomplicated writing — which makes it less appealing to the pros.

The other common conclusion trained eyes often draw from over-use of this technique smacks of either the narrative’s trying to rush through an otherwise not very interesting series of events.

This is not always a fair assessment, of course. But when you do find patches of ands in your text, step back and ask yourself honestly: do I really need to tell the reader this? Or is there a way that I could make the telling more interesting by adding more detail? (X happened and Y happened sentences tend to be light on telling specifics, I have noticed.)

Which leads me to the opposite possibility, and a more conceptual editing question: in paragraphs where ands abound (or, sacre bleu, sentences!), are you rushing through the action of the scene too quickly?

Is the repeated use of and in fact your manuscript’s way of saying COME BACK TO THIS LATER?

Almost every writer has resorted to this device at the end of a long writing day, haven’t we? Or when we have a necessary-but-dull piece of business that we want to gloss over in a hurry? When the point is just to get lines down on a page – or to get a storyline down before the inspiration fades — X happened and Y happened and Z happened is arguably the quickest way to do it.

It’s a great strategy – as long as you remember to go back later and vary the sentence structure. Oh, and to make sure that you’re showing in that passage, not telling.

The results for the scene can be a bit grim when we forget to rework these flash-written paragraphs. Relying heavily on the and construction tends to flatten the highs and lows of a story: within them, actions come across as parts of a list, rather than as a sequence in which all the parts are important. This leads to overloaded sentences where four or five genuinely exciting actions are all crammed together.

Which – you guessed it — encourages the reader to gloss over them quickly, under the mistaken impression that these events are being presented in list form because they are necessary to the plot, but none is interesting enough to sustain an entire sentence.

Which is not exactly the response you want from an agency screener, right?

When in doubt, revise. I hate to come down unfairly on any grammatically correct sentence, but the fact is, the X happened and Y happened structure is just not considered very literary in the business. So the automatic assumption if it shows up too much is that the material covered by it is to be read for content, rather than beauty of prose.

I would prefer to see your submissions getting long, luxurious readings, on the whole. Keep those highlighters handy — and keep up the good work!

Posted on - No Comments on Vary your word choices!

Vary your word choices!

That ripple of titters you hear out there in the cosmos, dear readers, is the sound of every soul for whom I have ever critiqued a manuscript guffawing: the title of today’s post is something that I have been scrawling in the margins of manuscripts authored by writers living and dead since I first started proofing galleys in my early adolescence. Today’s piece of self-editing advice comes deep from the lair of my most fire-breathing editorial pet peeve: repetition.

It is not an uncommon source of annoyance amongst professional readers; as any good line editor can tell you, a tendency to become a trifle miffed in the face of writing that could be better is, while perhaps a handicap in polite society, a positive boon in his line of work. I was, of course, trained to react to it from my cradle: in my family, developing a strong editorial eye was considered only slightly less important than learning to walk; it was simply assumed that the children would grow up to be writers. My parents would not so much as commit my name to a birth certificate without first figuring out how it would look in print.

It’s true. Ask the nurse who kept trying to get them to fill out the paperwork.

I come by my pet peeves honestly, in other words, and believe me, this one gets some exercise, especially now that computer use is practically universal amongst writers.
Why? Word and phrase repetition is substantially harder to catch on a computer screen than in hard copy, even on the great big editor’s model currently gracing my desk. I’ve seen 25-pound Thanksgiving turkeys carried on smaller surfaces, but even so, I prefer to edit on paper. And even then, I still read the final version out loud, to check for flow and repetition problems.

Long-time readers of this blog, chant with me now: NEVER let a submission tumble into a mailbox until after you have read it in its ENTIRETY, in HARD COPY, and OUT LOUD. There are manuscript problems that simply cannot be diagnosed any other way.

I had a hard lesson in this truth myself recently, after I had spent a couple of months working on a book proposal. For those of you who have never had the pleasure of trying to market a nonfiction book, a proposal is as nit-picky a document as they come. Rather than demonstrating that the proposed book is interesting and well-written by, say, handing the finished book to editors, the book proposal limits the actual chapters seen to only one or two — and even those come at the end.

What comes first? A lengthy description of what the book is about, why the author is the best current inhabitant of the earth’s surface to write it, and how it is going to blow every other similar book on the market out of the water. The author is expected to name the volumes to be thus trajected into the air specifically, critiquing them with the full knowledge that the editors who worked on them might well be reading the proposal imminently. Next follows a raft of marketing information, identifying the target readership, naming every mortal organization that might conceivably welcome a speaker on the topic, and so forth. After this exercise in tact, the hapless author is expected to come up with entertaining, well-written descriptions of chapters that have not yet seen the light of day.

THEN comes the sample chapter.

In other words, the NF writer has to prove, over the course of 50 or so pages of discussion of matters inherently less interesting than the subject matter of the book itself, that she can write. Piece o’ cake. It is a format in which a typo is both more important and harder to catch — because, let’s face it, the less fascinating a document is, the more the brain wants to skim through it.

By the time I began printing out the 15 copies for submission, I was relatively certain that the proposal was typo-free, so I did not proof it in hard copy. That was not purely an ego-based decision: there were other readers, too. I am writing the book with a very accomplished woman who lives on the other side of the country, in that OTHER Washington, so every draft of every page has flown back and forth electronically dozens of times. My agent (who wrote a great blog post on THE ROAD the other week, by the way. Would I be represented by someone UN-opinionated?) is an excellent line editor in his own right, and he had given feedback on two versions of it. Surely, I was safe.

You can see this coming, can’t you?

So there I am, printing up copy 12. (I like to print all the physical copies of my work that my agents will be circulating, so I can check each page individually. If a photocopier mangles pg. 173, it’s hard to catch.) Out of habit, I read the latest page out of the printer — and realized with horror that for some reason, three lines on page 47 were in 11-point Times New Roman, not 12-point.

It was a difference so subtle that only a professional reader would have caught it — and then only in hard copy. None of the three of us had noticed in the electronic versions, and I have no idea at what point the switch could have occurred, but that typeface change did subconsciously make those lines seem less important. Since it was a page in the middle of the proposal, though, fixing it would require reprinting ten pages of every single copy I had already printed.

Oh, please — was there even a second of viable suspense here? Of course, I reprinted it. I could always use the discarded pages for scratch paper, and then recycle them. Heck, I could even use them to print up a hard copy draft of the next manuscript I’m planning to send to my agent, so I can check for this kind of mistake properly.

My point is, no matter how sharp-eyed you are, or how smart — my proposal had been read numerous times by two people with Ph.D.s AND an agent, recall — you’re better off proofing in hard copy. A fringe benefit: on paper, it is far more apparent when you’re overusing certain words and phrases.

Which brings me back to my pet peeve. Editors hate repetition for a very practical reason: text that repeats a particular word, phrase, or even sentence structure close together is more tiring for the eye to read than writing that mixes it up more.

Why? Well, let me give you an illustration, as well as I can on a computer screen. Try to read through the coming paragraph as quickly as you can:

Without turning in her seat, Mandy suddenly backed the car into the garage. The garage door closed, sealing her and the car inside. The car was warm, cozy, a great place to die. No one would come into the garage for a week, possibly more, and the children never came in here at all. Thinking of the children, Mandy sank back into her seat, the car’s solidity as comforting as a sturdy umbrella in the midst of a sudden downpour. Without thinking, Mandy pushed in the car’s lighter, heating its coils for the benefit of some future cigarette that might never be smoked.

Okay, stop. Notice anything about how your eye moved down the lines? If you’re like most quick readers, your eye tried to jump from the first use of Mandy’s name directly to the next; it’s a very efficient way to skim. If you’re a more sensitive reader, the repetition of “the garage” twice within four words and “the car” twice within five might have led you to skip the next line entirely.

Apart from encouraging skimming — the last thing you want an agency screener to start doing to your work, right? — word and phrase repetition gives a professional reader the impression that the target market for the book in question is not as well-educated than more diverse set of word choices would indicate. (This is true, incidentally, even if a repeated word is polysyllabic, although to a lesser extent.) The more literary your writing, the more problematic such a perception can be.

The average adult novel is aimed at roughly a tenth-grade reading level; literary fiction tends to assume a college-educated reader, and uses vocabulary accordingly. So whenever you see those ubiquitous Mark Twain and Somerset Maugham quotes about never using a complex word when a simple word will do, realize that both wrote for audiences that had not, by and large, shifted the tassel on a mortarboard cap.

There is yet another reason to avoid word and phrase repetition whenever possible: it tends to slow down the pace of a scene. Let’s take another look at poor Mandy’s final moments with all of those redundant words removed and replaced with specific details — note how much snappier her trip to meet her Maker is in this version:

Without turning in her seat, Mandy suddenly backed into the garage. The door closed, sealing her inside. The car was warm, cozy, a great place to die. No one would come to this end of the mansion for a week, possibly more, and the children never ventured in here at all. She sank back into the rich leather upholstery, the Mercedes’ solidity as comforting as a sturdy umbrella in the midst of an unexpected downpour. Without thinking, she pushed in the lighter, heating its coils for the benefit of some future cigarette that might never be smoked.

It’s definitely a smoother read, isn’t it, without all of those eye-distracting repeated words? Yet look how many more character-revealing specifics I was able to incorporate — why, Mandy moved up several tax brackets in the second-to-last sentence alone. And although it reads more quickly and comfortably, it’s actually not substantially shorter: the original was 103 words, the revised version 97.

If weeding out repetition in just one paragraph can yield this kind of dramatic result, imagine all of the room you could clear for telling little details if you eliminated similar redundancies throughout an entire manuscript. You might want to print out a copy of your book — perhaps on the back of all that paper I had to discard from my proposal — and try it sometime.

There are, of course, many flavors of redundancy to torment editorial souls. Next time, I shall dive into another very common species that, in its most virulent form, has broken the tension of many an otherwise worthy scene. In the meantime, keep up the good work!

PS: Congratulations to long-time reader Brian Mercer, who has just sold an article to Llewellyn Publications. Way to go, Brian!

(And please, everybody, remember to keep sending in news of your triumphs, so we can all celebrate. I love reporting good news about my readers’ writing careers!)