I, erotica writer

Illustration from The Erotic Review for "At the White Stands Motel, 1956"
Illustration from Erotic Review for “At the White Sands Motel, 1956”

I once wrote erotica by accident. Writing and getting the story published is a wild tale.

If you know of anything of my output—my novels, my interactive fiction—that might surprise you. You’ve probably never read anything by me that remotely involves the sex act: No kinky sex, no ho-hum sex, not even missionary style. Generally, I shy away from that kind of thing. Getting a story published in an erotica magazine still tickles me to this day.

The story-behind-the-story begins in a creative writing class. The instructor offered us a list of writing prompts. We were to select one and write an opening.

The first speed bump in this tale is that these prompts were communicated to us orally. The prompt I selected regarded a teenage lifeguard named Hamke. Years later, I learned I had misheard the details. The prompt did not include the name “Hamke” or anything about a lifeguard. How I managed to screw up so much remains a mystery lost to the shroud of time.

In any event, the name and occupation stuck. I assumed it was a German name, as I’d never heard of it before. (Apparently, I’m not alone.) While I enjoy swimming, I’ve never known a lifeguard nor worked as one. Why this prompt caught my interest, I do not know. Over the following week I roughed out a first draft about a teenage Hamke standing guard over a motel pool in Nevada. In need of a title, I jammed one onto the front page of the manuscript: “Living It Up at the White Sands Motel.” (I believe it was a riff on the quip about a cheap lodging being a “low-rent Shangri-la.”)

Around this time, I dated a woman also enrolled in the creative writing program. She was experimenting with poetry about the body. She read many of my stories, which is generous—even when you’re dating a writer, that’s no guarantee they’ll actually read your output. She called my work cerebral, and noted that my characters seemed “detached” from their physical nature. She challenged me to write a story where the main character’s physicality is centered.

Now, this doesn’t necessarily mean “write about sex” or “write about someone with a smokin’ bod.” It could mean the main character is physically challenged, or has suffered some grievous physical damage they’re recovering from. It could mean some aspect of their body defines them in a material way (which is something I had in mind as I wrote my Bridge Daughter series of books.)

In this case, I went for the obvious: Hamke would have sex. More than that, he would lose his virginity.

I poked and prodded at the manuscript—draft after draft—trying to tune all the off-key notes. In workshops, peer writers would scratch their heads trying to figure out what to make of this strange story. There was a lifeguard with a flat-top and a weird name, an empty motel in the desert, and an older couple from New Jersey who invites him to their air-conditioned room for an afternoon romp. By this time I’d renamed it (still flailing for a proper title) “At the White Sands Motel, 1956.”

I submitted to the usual literary magazines, searching high and low for a place to land it. The rejection slips came back a bit more quickly than the other stories I’d sent out. Perhaps the complaints I heard in in the workshops (“‘Hamke?’ Is that Jewish?”) was now confounding editors. The sex was not graphic, but it was on the page and not merely alluded to. The wife was acidic and domineering, and her husband frustratingly passive. Wide-eyed Hamke, who was simply “along for the ride” (so to speak), was not a character to stand up and cheer for.

Enter London-based writer Saskia Vogel. By chance, she came into the bar I tended while working through graduate school. She was working on a study of kink; I despaired over a short story about a lifeguard losing his virginity. We swapped email addresses and kept in touch after she returned to England.

Around this time, fellow grad student Lizzy Acker mentioned off-the-cuff she was developing a new San Francisco reading series with the theme “funny / sexy / sad.” The work writers presented had to feature one of those elements.

“You know,” I said, not entirely innocently, “I have a story that’s funny, sexy, and sad.”

A Concordance of One's Life by Jim Nelson

It’s true: Hamke’s fumbling and awkward loss of innocence is funny. The wife impatiently orders Hamke across a tour of her body as though teaching him to drive a stick shift. It’s sad, too. As one workshop instructor remarked, the boy is robbed of a positive formative experience.

Lizzy included me in the series’ opening night line-up, and the reading went uproariously well. Maxfield’s House of Caffeine was packed. The audience reacted with every twist and turn of Hamke’s awkward journey. They burst out laughing at all the right moments. Red-faced parents held their hands over their children’s tender ears. People were moved by the ending, and a couple of tears were shed. The applause knocked me off my feet. It was, by every measure, the best reading I ever gave.

How the hell could I not get this story published?


Then, an interregnum. I separated from the girlfriend who challenged me to write about the body. I separated from my appendix, and a few months later, I busted up my right shoulder. I separated from graduate school. (Well, a degree was conferred, how’s that.) Hamke’s story remained a magnet for rejection slips. Meanwhile, medical bills ate through my meager bartender savings.

With no more excuses, I returned to full-time employment. The first year with my new company, the sector we were involved in hosted their annual conference in, of all places, the Canary Islands.

La Palmas de Gran Canaria
La Palmas de Gran Canaria. (Photo by the author.)

That’s how, six months after staring down bankruptcy and unemployment, I found myself on a semi-tropical island in the Atlantic a mere 500 miles from Marrakesh. I rented a cheap open-air room overlooking the Las Palmas promenade and a pristine sunning beach. After the conference concluded, I stayed for another week to explore the island and write.

During this vacation I received an email from Saskia Vogel in London. She heard from an editor friend that the UK-based Erotic Review was in need of fiction. Didn’t I have a story about a guy having sex for the first time?

In that low-rent Shangri-la, the couch doubling as my bed and the drapes billowing from the breeze coming off the beach, I hustled one more edit pass out of my aging Hamke story. Thankfully I brought my writing notebook computer with me. This was not a time when Wi-Fi was a sure thing in a rented room, especially in an out-of-the-way place like Gran Canaria, but I in this case I was set. I emailed my little story to editor and publisher Jamie Maclean.

Before I did that, though, I used the Wi-Fi to study up on just whom I was submitting to. My search revealed I was not soliciting some amateur outfit. ER had been around since before 1995, and had published numerous erotic books on top of a monthly subscription-based magazine. Their readers spanned the UK and North America. Not only had I never published a work of erotica, I’d never been published by a magazine that survived solely off subscriptions.

With a healthy taste of self-doubt in the back of my mouth, I pressed the Send button. Then I did what I usually do after submitting a piece to a magazine: I got my mind off things. I went downstairs. I walked the promenade. I had a couple of drinks at a beach bar, and got my toes in some sand.

When I returned to the room, I of course checked my email, fully expecting to find nothing. Instead, an acceptance email waited in my inbox. Compared to the usual turnaround times for literary magazines—one sent me a rejection two years after submission—this was lightning fast. Later it dawned on me that my accidental vacation spot had contributed to the quick response: I was in the same time zone as London, where ER was published.

Three months later, a contributor’s copy of Erotic Review and an international money transfer arrived at my apartment in California. My Hamke story was out there.

And that’s how I became a writer of erotica, scribbler of filth and peddler of smut.


Postscript:

My tale might be seen as a reversal of Ray Bradbury’s strategy to seek out unusual places for his work (such as Gourmet publishing his “Dandelion Wine”). I sought out unusual places to publish an erotica story, and eventually found a natural home for it.

Being published in an erotica magazine has become a point of pride for me. I never set out to write erotica, and I’ve never considered pursuing it since. I once read that no one writes erotica under their real name. Well, I did, although when you have as generic a name as “Jim Nelson,” perhaps it doesn’t matter.

Erotic Review Christmas card

Erotic Review is a class act. They continued to stay in touch. I received editorial updates and invites to ER parties (which, sadly, were all in London). They even sent digital Christmas cards, such as the one above.

Recently ER changed hands and is now retooling under a new editorial staff. If you’re interested in supporting the relaunch, visit them at ermagazine.com.

“At the White Sands Motel, 1956” is collected with nine other short stories in A Concordance of One’s Life.

Crappy cover letters

Anne Lamott
Anne Lamott (Zboralski, CC BY-SA 3.0)

Anne Lamott is the author of nearly twenty books and numerous short stories, but she’s best-known among writers of all stripes for her essay “Shitty First Drafts”. Her pitch-perfect rumination on the writing process captures the messiness of penning books, short stories, plays and scripts, all of which start with a shitty first draft:

This is how [writers] end up with good second drafts and terrific third drafts. … Almost all good writing begins with terrible first efforts. You need to start somewhere.

If I might borrow some of Lamott’s magic, I’d like to a coin a corollary to her term. If the story-writing process starts with a shitty first draft, it ends with a crappy cover letter.

To bust ass to write a great story and then summarize it in a paragraph or two is the tragicomedy of the author’s endeavor. It’s reaching a marathon finish line and having the judges inform you there’s one more mile to go for good measure. As with Lamott’s first drafts, my cover letters are initially shitty, but they are so insubstantial I prefer to view them as merely crappy.

A one-page single-spaced cover letter has to satisfy seemingly a half-dozen tasks at once: Introduce the work, summarize its contents, establish the writer’s bona fides, suggest the writer’s past successes without dwelling upon them, demonstrate the writer is committed to the craft but is someone the editors can work with when revision time rolls around, and most of all, that the work being submitted is perfect for the publisher’s needs and will sell like hotcakes (if that’s their goal; it’s not a given.)

Hence as I’m writing a crappy cover letter to an editor, a voice in the back of my head whines: Can’t you just read my manuscript?

This is my theory why writers generally loathe to tell strangers about their work. (“Oh, you’re a writer? What do you write?”) Standing before someone and explaining a book in twenty seconds is essentially ad libbing a cover letter in audio-book form. When I’m telling a person about my work the same voice in the back of my head whines: Can’t you just read my books?

Whether submitting to a major New York publisher or a twee not-for-profit literary magazine, cover letters don’t merely summarize—the writer has to sell the story in one or two short paragraphs, even if the intention is for no one involved to make a dime. By and large writers are horrible salespeople, hence, crappy cover letters.

(This may be why so many writers love Glengarry Glen Ross. It’s a peek into a bizarre alternate universe no writer would want to inhabit—but damn is the dialogue sharp and the situation taut. Always be closing.)

I recall one published writer whose counsel for success was Write your cover letter first. His bright idea was to make sure your novel can be summarized in a sellable way before writing the novel itself. (Is your cover letter crappy? Write different letters until one is good, and then turn it into a novel.)

I’ve never done this so I can’t advocate for it. Personally, I think it’s kind of crazy. I have to write a novel before I know what I should have written.

I have scant advice to offer a writer confronting the challenge of whipping up a cover letter for their latest story. Know that you’re not the only writer who hates this final mind-numbing step. One option is to limit your cover letter to your credentials and pray the editor reads your story cold. (I’ve done this with short stories to mixed success; I sincerely doubt it would work for a novel.)

Like Lamott’s first drafts, your first stab at a cover letter will read like crap. So, walk your cover letter through a similar process as any short story or novel: Take your time writing it. Put it through several edit passes. Ask your writer friends to critique it. Hell, pass it out at your writing workshop if they’ll allow it. Remember, writing is an iterative process.

And when you think it’s ready to send…let it sit on your computer for a week or two. Trust me, when you return to it fresh later you’ll spot all kinds of problems you missed before.

A fourth alternative to the Iowa writing workshop format

“Writing Workshop 1” (Ant Smith, CC-BY-NC 2.0)

In my last post on writing workshops, I discussed the Iowa format and three alternatives to it: Liz Lerman’s critical process, Transfer‘s submission evaluation, and playwriting workshops. Thinking about those alternatives led me to come up with a hybrid that I hope makes the fiction workshop more constructive.

This hybrid isn’t merely a group discussion structure, it’s a collection (or, less charitably, a grab bag) of suggestions for organizing a workshop. It’s geared toward informal peer workshops rather than academic settings, but some of its points might be useful there too.

I’ve grouped this grab bag into three sections:

  • Organizing the group,
  • managing manuscripts,
  • and the group discussion itself.

Organizing the group

Define the goals of the workshop

For some, the primary goal of a writing workshop—perhaps the only goal—is to make their fiction publishable.

For others, a writing group is a place to receive direction and encouragement toward completing a larger project, such as a collection of short stories or a novel.

Some attend a workshop for the camaraderie, and to maintain a semblance of a writing practice in the face of hectic modern schedules.

Others write for themselves (or a small audience) and have no broader ambitions of mass publication.

For some people, it’s a combination of these things, and maybe more.

In my experience, almost all who attend a workshop go with the goal of eventual publication. But even if everyone agrees on that goal, it only raises more questions: Published where, and for what audience? Can any member in the group really claim knowledge of when a story is “publishable”? (And is there a difference between “ready for publication” and “publishable”?) Genre writers add a monkey wrench to the mix—someone who aims to be published by Tin House, The New Yorker, or The Paris Review might not the best arbiter of when a hard-military science fiction novel is ready for shopping around.

(Really, editors and publishers are in better positions to decide if a story is publishable or not. I was once told a story was unpublishable and weeks later landed it in a highly-regarded magazine.)

Liz Lerman’s process has some applicability here. As a baseline, agree that everyone in the group has an opinion of successful versus unsuccessful fiction, “success” being related to the quality of the work and not who might or might not publish it.

Also agree that everyone in the workshop is attending to make everyone’s fiction more successful, not merely their own.

How a writer uses that successful fiction—publication, independent distribution, blogging, or simply personal satisfaction—is the purview of the writer and not the group.

Agree what’s expected of each member

Most people join a workshop thinking they know what’s expected of them and everyone else. Rarely does everyone truly agree on those expectations.

On a basic level, people should understand they’re expected to

  • read the manuscripts presented to the group,
  • formulate some manner of thoughtful response,
  • regularly attend meetings,
  • and engage with the group discussion.

I’m not a big fan of merit systems, but some groups use them for motivation (such as “you must attend three meetings to submit one manuscript”).

Additional expectations are discussed below, but the point I’m making here is to verbalize (and even write down and share) these expectations. If you’re organizing a workshop for the first time, you might use the initial meeting to allow everyone to air what they expect from the others. Coalesce those points into a list that’s distributed to all members. Differing expectations can lead to headaches later.

Cover the workshop’s agreements with each member

For each new member, go over the group’s structure and policies and goals with all the other members present—in other words, don’t do it privately over email or the phone. This ensures that everyone’s on the same page. It also refreshes the memories of long-time members. Avoiding miscommunication is incredibly important in a workshop group.

Stick to your workshop’s structure unless everyone agrees a change is necessary (or, after a vote).

Don’t make exceptions. Exceptions kill the group dynamic. People begin to see favorites even if no favoritism exists. Remember: This is a peer group evaluating peer writing.

Manuscripts

Enforce page count and style

The era of the 25-manuscript-page short story may be receding (I wish it wasn’t), but that hasn’t stopped writers from penning them. The problem with bringing so many pages to a workshop is that people are bound to skim long work. That means they have less understanding of the story and are less qualified to discuss it. The peer pressure to discuss it remains, however, and so people will, leading to poor results.

I’ve brought in long work many times to workshops. In almost every instance I’ve heard comments (or outright griping) about the length. It seemed odd to me that writers would complain about having to read a measly 25 double-spaced pages, until I reminded myself they’re reading work they probably would not pick up on their own.

I’ve also noticed my shorter work almost always received higher-quality reads and discussion.

Some groups limit submission length to 20 or 25 pages. My suggestion is to go further and require manuscripts be no longer than 10 or 12 pages. Yes, that means having to split long short stories into two or three segments, but the writer will get a better read of those segments. Chuck Palahniuk’s writing group in Portland has such a page count restriction. Its members seem to have done fine by it.

Page count restrictions require basic, common-sense manuscript formats. Make it clear: Double-spaced, 1.5″ margins, 12-point Times New Roman, or whatever format your group decides.

I’ve seen writers game the manuscript format to subvert page counts. Don’t stand for it.

Agree on the role of manuscript edits

A lot of people in fiction workshops think there’s big value in marking up the manuscript itself. In the past, I’ve had manuscripts returned to me so marked-up I didn’t know what to make of them.

Readers drew lines like football plays over my pages, instructing me to cut sentences, split or combine paragraphs, rearrange scenes, and so forth. One workshop reader circled every instance of “has”, “had”, “is”, and “was” to alert me of my overabundance of passive voice, even where no passive voice existed. Others marked words wc (“word choice”), inserted and struck commas, semicolons, em-dashes, and so on.

Drawing attention to typos and misspellings is hard to argue against. Yes, if you see one, go ahead and circle it—but that’s gravy. Indicating confusion (“Who’s saying this?”) or highlighting passages that pop off the page have utility as well.

I’m arguing against line edits that are a matter of taste or philosophy. Telling me I should

  • replace words not in the reader’s vocabulary,
  • never use passive voice,
  • only use “said” or “asked” as dialogue tags,
  • drop all semicolons,
  • strip out all adverbs, and so on,

are not the purview of the workshop reader. I would also argue these comments are counterproductive to a quality workshop experience. Too often the editorial mark-ups are writing lore masquerading as received wisdom (and usually associated with a well-known writer who purportedly counseled them).

On the flip side, I’ve encountered workshop peers who expected line edits, to the point of chiding some of us for not pointing out a typo he made. This attitude is counterproductive as well.

Assume everyone in the group is a capable writer. You are responsible for the fine-detail work in your manuscript, not the group. The workshop’s purview is to locate broader issues in the story and illuminate paths forward for your next revision. Workshops are not editorial services for you, the writer.

My experience has been that people who make fine-detailed edits to others’ manuscripts are expecting the same in return. When they don’t receive them, feelings begin to bruise and grudges are harbored. Notions of equal work loads and reciprocity is a major source of fracture lines in a workshop. (What’s worse are workshop members who don’t offer detailed proofreading of others’ work—but expect it from everyone else. Oof.)

If your group thinks it’s the purpose of the workshop to offer editorial changes, then make it an explicit policy. But I would suggest against it.

Agree on genre

Some fiction workshops will accept creative nonfiction, but rarely poetry or plays, if ever. Some will only accept fiction of a certain length (for example, no microfiction or novels). Some are for science fiction or mysteries, while others are open to all subject matter. I won’t argue one way or the other, but like my other suggestions, make sure everyone in the group is aware of the restrictions. For example, I’ve witnessed sparks where one member kept bringing prose poetry to a fiction workshop.

Agree on readiness

Some people will balk on this next point, but I’ll draw a line in the sand: The group should agree that the workshop isn’t there to critique first drafts. First drafts are too undeveloped and scattered to be productively critiqued in a group setting. Does it make sense to use other people’s valuable time to inform you of your first draft’s (usually obvious) problems? Especially when first drafts stand a high chance of being abandoned by the writer?

Likewise, late drafts are usually too set in concrete to receive any help from a workshop. If you’re unwilling to make substantial changes to the story, then asking the group to find its weaknesses is wasteful. (Never bring a manuscript to a workshop expecting unconditional praise. It never happens. Never.)

My rule of thumb: Workshops should be seeing stories after two or three drafts (or edit passes) and not after six or seven drafts/edit passes.

Some groups allow submitting work previously read by the group. I would add the proviso that the work must have received substantial edits since its last go-around. Other groups may prohibit it or require full agreement before accepting previously-seen work. As before, don’t make this up as you go. Choose a policy and stick to it.

No one should ever submit a published story to a workshop. Yes, people do this. (One possible exception to this rule: The story is up for republication and edits are requested by the publisher, i.e., it’s being anthologized.)

Formulate a written response format

Some groups may forgo written remarks, especially if the manuscript isn’t handed out ahead of time. Otherwise the response format should be agreed on by everyone.

I don’t mean page length (“one page single-spaced”), I mean what questions should be answered in the written response. It doesn’t have to be a fill-in-the-blanks approach. You could simply have a list of questions and ask each member to verify those questions have been answered (in one way or another) in their written response.

My suggestion? Use Transfer‘s system. Each reader writes on a 3-by-5 card a 1–2 sentence reaction to the story and uses the remaining space to describe its strengths and weaknesses. Use both sides of the card. Then the cards are read to the group verbatim. Readers will learn not to use the watered-down language so often found in a full-page responses (“I really like this piece,” or “This is strong.”) From there, launch into the general discussion.

If a 3-by-5 card seems too small a space, choose a longer format, but I still propose a length limitation to elicit thoughtful responses.

I’ve become convinced that the real magic in a fiction workshop lies in the discussion, not the written remarks. By giving each person only a sentence or two for strengths and weaknesses, the discussion can zero in on those thoughts and use them as a springboard for exploration.

The group discussion

Read the story aloud before discussing

As mentioned in my prior post, I noticed in playwriting workshops how reader-actors became invested in their characters. For fiction, even with an eight-page limit, it would take too much valuable group time to read aloud the entire manuscript.

What’s more, fiction is an inherently different experience than theater. A person reading a story aloud will not become as invested as an actor reading their part from a script.

Still, I’ve been in groups where a paragraph or two of the story was read aloud before the discussion, and it did seem to help. Getting the story into the air brings the group together around the manuscript. Everyone is hearing it one more time—the language, the setting, the narrator’s voice, the dialogue.

If your group meets every other week, it’s possible a few people haven’t read the story in ten or more days. (It’s also possible some read it in the Starbucks around the corner fifteen minutes earlier—there’s not much you can do about that.)

The writer shouldn’t read their own story aloud.

Keep the discussion to what’s on the page

Discuss the story as it’s written. Avoid peripheral issues (such as ideology or personal viewpoints) and comparisons to other work (other authors, television shows, movies, and so on).

Personal viewpoints are a good way to poison a discussion. Saying things like “I would never choose what the character chose here” isn’t useful. A better question is: Would the character choose what they chose? Everyone holds a subjective internal logic. Most of us hold several subjective internal logics. Does the character’s actions match their internal logic(s)? Was the suspension of disbelief lost?

While comparison to another work may seem harmless (“Your story reminds me of Mad Men“), popular culture is a kind of safe zone for people to retreat into. Pop culture will also derail a workshop discussion. When the harmless comparison takes over, all discussion becomes re-framed by it. Instead of discussing the story, the group is discussing how the story reads in light of this other work or issue. (“Mad Men focuses on women in the workplace. You could add more of that.”) The story becomes secondary. This is unfair to the author, who has brought their work in to be critiqued on its merits and weaknesses.

Workshop formats (including Liz Lerman’s) will often declare that readers shouldn’t make suggestions without the writer’s permission. This baffles a lot of people; if I’m not making suggestions, then what I am here to offer? Unearned praise and tender nudges? (Liz Lerman is not advocating either of these, I’m pretty sure.)

Rather than distinguish between suggestion and not-suggestion, I say keep the discussion to what’s on the page. Staying close to the page means, for example, suggesting the writer remove a spicy sex scene because it’s dragging down the story. Suggesting the writer remove a sex scene because that would make the story suitable for young adults—a hot market right now—is straying from the page. Both are suggestions, but the latter is not the purview of the workshop.

Maintain a discussion structure

The Iowa workshop format usually runs like this:

  1. Each reader gives a broad reaction to the story.
  2. A general discussion opens between the readers, with the writer only listening.
  3. The writer asks the readers questions.

Lerman’s approach is more involved and (as I discussed last time) more difficult to stick to, but it has some nice features worth including. For example, a workshop could be structured as so (incorporating some of the suggestions above):

  1. A portion of the story is read aloud by one of the readers.
  2. Each reader in turn reads their written remarks (or a summary of them) aloud. (This makes the 3-by-5 card approach more desirable.)
  3. General discussion by the readers. Keep the discussion to what’s on the page. Start with strengths, then move to weaknesses and confusion in the story.
  4. The writer is offered an opportunity to ask questions for clarification and prompt for suggestions.
  5. The writer summarizes what they’ve heard by naming new directions they plan to explore in future drafts.
  6. If the group is open to re-reading work, the writer can announce what changes they intend to make before submitting it next time. (This is probably more useful in a graded academic setting.)

This is not radically different from the Iowa format, but by specifying the goals of each step, they aim to direct the group’s energy toward better revisions and, hopefully, better writing.

Appoint a discussion leader

In academic settings, a discussion leader is naturally selected, with usually the teacher or an assistant taking that role. In informal workshops, the leader is sometimes the member who first organized the group, or has been around the longest. Otherwise, workshop groups will often lack any formal leadership.

Recognize the difference between an organizer and a discussion leader. Organizers solicit for new members, remind everyone when the next meeting will occur, arranges for a location to meet, send emails and make phone calls, and so forth. This is all important work (and harder than it looks) but it doesn’t imply that the organizer should lead the group discussion.

I suggest rotating the role of discussion leader around the group. Round-robin through the members, skipping writers when their manuscript is under discussion. (The writer whose work is under scrutiny should never be the discussion leader.) Or, if multiple writers are “under the knife” at each meeting, let the writer not under discussion lead the group, and then switch the role to the other writer.

Discussion leaders should monitor the group dynamic and gently remind people what stage they’re at, to keep the discussion on-track. Have leaders bring a watch to track the time and make sure everyone (readers and the writer) have a chance to speak. Make sure everyone knows that the leader has the right to interrupt someone if they’re going on for too long or taking the discussion down a hole.

The problem with round-robin is that some people simply aren’t good at this kind of role. (On the other hand, some people are too good at this kind of role.) This is where everyone has to step up to the plate—to rise a little to the occasion.

I’ve heard writers express disdain for discussion leaders, or any manner of hierarchical organization. I would love to agree, but experience has taught me otherwise. There’s tremendous value in having someone appointed to direct the flow of the conversation and cut it off when it’s deviating from the agreed-upon format. I’ve witnessed a few situations where such a leader could have saved a group discussion, and even the group itself.

If you’re organizing a workshop, or are in a workshop and looking for positive change, I hope this ignites ideas and discussion. If you use any of these ideas, let me know in the comments below or via the social networks.

Three alternatives to the Iowa writing workshop format

Liz Lerman
Liz Lerman

The workshop is so pervasive in the writing world it’s been converted to a verb: workshopping. Although workshops occur in disparate settings (academic, informal, living-room writing groups—whatever), a fiction writing workshop usually operates something like this:

A writer distributes their story or chapter to the rest of a group ahead of the meeting. Each workshop member reads the story on their own, away from the group. Each member writes a critical response, usually one page single-spaced. Often readers will mark up the manuscript as well: spelling, grammar, word choice, typos. They’ll highlight passages that are interesting or vivid, cross out passages that seem unnecessary or inappropriate, write question marks near confusing passages, and so on.

Then the group meets. The author quietly sits for twenty to thirty minutes while a half-dozen or more people critically pick apart what may be the most heartfelt and personal story he or she has ever written. The author is forbidden from speaking during this time. The discussion almost sounds as if the author is not present. He or she listens and takes notes while the rest of the room casually dissects hours, maybe tens of hours, of work. Just about any critical opinion that jumps to mind may be aired without fear of crossing a boundary. With the right people, it can be ruthless.

After the discussion, the writer may ask the group questions, and the session concludes.

Although I don’t know how this style of critique developed, I’ve often heard that it originated at the Iowa Writers’ Workshop, and so it’s called the Iowa workshop format. For better or worse, the Iowa model has become the platonic ideal of the fiction writing workshop.

For my purposes, the history of the format is not really important. It’s been handed down to us and dominates the critical process for fiction writers. It’s used in practically every living-room writing group and creative writing course in North America, from weekly adult-extension classes to top-tier MFA programs.

The format is not set in stone. I’ve seen a couple of home-brewed workshop formats, and even endured a writing group that made up the rules as it went along. Some established groups have a formal structure, but often it’s assumed everyone “knows” how to workshop. It’s rare to see the workshop where the group’s goals were enumerated and agreed upon by everyone.

A lot of time in writing workshops and a lot of negative experiences in them have led me to consider alternatives to the Iowa format. I can name three worth examining.

Liz Lerman

The most widely-used alternative to the Iowa workshop format originated in the world of modern dance. When a workshop organizer hands out their Xerox-of-a-Xerox-of-a-Xerox of Liz Lerman‘s Toward a Process for Critical Response, the phrase “dancing about architecture” leaps to my mind. I don’t mean to sound unfair—Liz Lerman’s critical format is so well-known and widely-used, it’s left the world of dance and crossed to fiction (and perhaps other arts). Obviously there are people other than myself seeking alternatives to the Iowa format.

I’ve enrolled in a handful of workshops where Liz Lerman’s process was used. In the first session, the leader selected workshop members to read aloud each section of Lerman’s process while everyone else followed along. Then the leader went over Lerman’s technique in detail, firmly and thoroughly discussing each stage, reiterating its emphasis on decorum, and above all its notions of fairness and neutrality.

For a fiction workshop, Lerman’s critical process structures the group discussion like so:

  1. The readers state what was “working” in the story.
  2. The writer asks question about their story. The readers answer the questions without suggesting changes.
  3. The readers ask the writer neutral questions about the story.
  4. The readers ask the writer for permission to offer opinions of the story.

Lerman’s process is designed to avoid confrontation at all costs. I would also say Lerman’s process requires a strong leader to guide the discussion along—a situation more suitable for an academic situation than a writing group of peers.

Unfortunately, the few groups I’ve been in that used Lerman’s process degenerated in a similar fashion. The first one or two sessions would follow Lerman to a T, but inevitably transgression of the format crept in. People would start questioning if they were “allowed” to say what they want to say. By the third session Lerman’s process all but disappeared from the radar screen. Steps got skipped. One stage would bleed into the next. Time ran out and the process cut short. (You need to go through each step for it to be worthwhile.) Sometimes the workshop turned into a pillow fight…the pillows filled with broken beer bottles.

I’m not blaming Lerman for this situation. Overall, her process is a positive one that emphasizes constructive criticism and neutral questions to give the dancer—or writer, or painter—a grab-bag of vectors for the next iteration of the creative process.

It’s just that I’ve never seen Lerman’s critical process consistently applied in a fiction writing workshop, academic or informal. Lerman’s process requires everyone to agree to it up front. Many people don’t, silently or verbally, either due to confusion (“Is this a neutral question?”) or rebelliousness (“I’m not here to sugar-coat my opinions”). Like so many group activities, if everyone doesn’t buy into the ground rules, problems sprout up.

Transfer magazine

One of the most positive workshop experiences I’ve enjoyed was as a staff member of Transfer magazine, a publication of San Francisco State University’s Creative Writing department.

Transfer used a blind submission process which solicited manuscripts from the student body. Manuscripts were distributed to the staff (20 or so students) who read them on their own and prepared note cards. On each card they described the story in objective terms and listed its strengths and weaknesses.

There’s only so much you can write on a 3-by-5 card. That limitation forced the staff to think hard about what they wrote, particularly since they might have to defend it later.

In group discussion, each story was evaluated in turn. The note cards became a launching pad for the discussion. The story’s author was not present, of course—editors and staff could not submit work. With the author’s name unknown to everyone present (including the editors), the discussion was remarkably fruitful and civil. Many of the manuscripts were teased apart by the group, revealing details and forces within them no single person had noticed on their own.

I’ve thought a lot about how to borrow some of this magic. There’s obvious problems with migrating this process to a standard fiction workshop. Even if the story’s author was asked to leave the room during the discussion, those present would know whose story was under the knife and that their remarks would eventually wind up in the writer’s hands. (Transfer‘s evaluation was not shared with the story’s author.) Anonymity fostered healthy discussion at Transfer, something not easily replicated in a weekly writing group.

On the other hand, the note cards and their space limitation garnered thoughtful responses from the students. The discussion, not the written responses, was where the real critical value lay. Most fiction workshops treat written vs. discussion as a 50-50 split. After Transfer, I’m not so sure.

Playwriting

Playwriting workshops have been another source of remarkably positive experiences for me. The differences between playwriting and fiction workshops are so marked, the first time I took a playwriting workshop I assumed it was a fluke of nature—a fantastical intersection of an energized instructor, great personalities, and wonderful writing. It was all those things, but I’ve enjoyed similar good fortune in the other playwriting workshops as well.

Unlike most Iowa-style formats, scripts are not distributed ahead of time in a playwriting workshop. Scenes are brought to the group and handed out on the spot. The playwright selects her “cast” from the other writers. The scene is performed cold, sometimes sitting at the table, sometimes using one side of the room as a makeshift stage. There is no blocking, no dramaturgy, no Method acting, but of course everyone gets into their roles a little.

The shock and delight of fiction writers attending their first playwriting workshop.

The toughest part for me, as a fiction writer, was this part of the process. Public speaking is difficult enough; acting is painful, and I know I was hamming it up. It’s common for dedicated playwrights to take acting lessons, and many of them did my scenes great justice.

Once the scene is acted out, a general discussion follows. The discussions are rarely structured, nothing as formal as Lerman’s process. If there is structure in the workshop, it’s the leader asking “What’s working here?” and then “Okay, now where is it stumbling?”

Yet there was an extraordinary amount of generosity in those sessions. I never saw the backbiting or sniping that pokes its nose into fiction workshops. The energy level of playwrights is something to see—people eager, anxious even, to help the writer refine her work from something struggling to something great.

There are cultural differences between the world of fiction and the world of theater. Fiction writing is romanticized as an isolated act, and there’s truth in that. Plays are collaborative efforts, from start to finish, and it shows in a playwriting workshop. There’s also the stereotype of personality differences: fiction writers as introverts, theater folk as extroverts. But there were other fiction writers in my playwriting workshops. They shined too. It was the process, not the personality.

Reading a script aloud, cold, and in a performative manner engages everyone in the room. Too often in fiction workshops I’ve received written comments that were scribbled on the last page of my manuscript like it was a cocktail napkin. If the comments were assembled that sloppily, I can only imagine with what impatience my story was read.

Acting through a script makes people pay attention. It creates stakes in the room—the group feels they’re a part of the work, rather than exterior to or above it. The actors make special claims to the play, speaking up about their character’s motivations, speaking about their character in the first-person (“At that moment I really wanted to tell her what I knew”).

Again, like Transfer, I don’t know if this easily translates to the fiction workshop, but it’s worth knowing there are workable and practical alternatives to our age-worn practices. The question is how much of this magic can be adapted into a workshop process that has been pounded into place. That’s what I’ll discuss in my next post.

Next: A fourth alternative to the Iowa writing workshop format

“Never open a book with weather”

"In the Rain", Sascha Kohlmann (CC BY-SA 2.0)

“In the Rain”, Sascha Kohlmann (CC BY-SA 2.0)

Lore is superstition for a modern world that thinks it has shaken off superstition.

Of all the different kinds of lore out there—office equipment lore, marijuana lore, etc.—writing lore is some of the worst. Inevitably writing lore is expressed as an indisputable maxim all writing must follow. Usually writing lore is attached to the name of a well-known, perhaps legendary, author. The august name only burnishes the lore’s authority.

These chestnuts of wisdom that all writers must adhere to thrive and breed unchallenged. Why? Why are we as writers beholden to this set of arbitrary do’s and do not’s?

Hence my peevishness when the Guardian printed a collection of writers’ “Ten Rules for Writing Fiction,” starting with Elmore Leonard’s famed list. (The Guardian cribbed his list from The New York Times, incidentally.) Not everything on these lists is lore—plenty of it is hard-learned personal wisdom—but I have a bone to pick with Leonard’s first rule:

“Never open a book with weather.”

Elmore Leonard isn’t so stupid as to pronounce this absolutism and move on. He offers a justification (“If it’s only to create atmosphere, and not a character’s reaction to the weather, you don’t want to go on too long”) and an exception (“If you happen to be Barry Lopez, who has more ways than an Eskimo to describe ice and snow in his book Arctic Dreams, you can do all the weather reporting you want”). When you contemplate both provisos, suddenly that “never” in “never open a book with weather” melts away like the warming Kilimanjaro snow.

Speaking of, this is what Hemingway wrote to John Dos Passos:

Remember to get the weather in your god damned book—weather is very important.

Hemingway managed to open “A Very Short Story” with a mention of the weather:

One hot evening in Padua they carried him up onto the roof and he could look out over the top of the town.

Here’s his rule-breaking opening to “In Another Country”:

In the fall the war was always there, but we did not go to it any more. It was cold in the fall in Milan and the dark came very early. Then the electric lights came on, and it was pleasant along the streets looking in the windows. There was much game hanging outside the shops, and the snow powdered in the fur of the foxes and the wind blew their tails. The deer hung stiff and heavy and empty, and small birds blew in the wind and the wind turned their feathers. It was a cold fall and the wind came down from the mountains.

Papa again, in “Cross-Country Snow”:

The funicular car bucked once more and then stopped. It could not go farther, the snow drifted solidly across the track. The gale scouring the exposed surface of the mountain had swept the snow surface into a wind-board crust.

I could go on.

In fact, if you think of a story’s title as its true opening, Hemingway is even more guilty: “The Snows of Kilamanjaro”, “Cat in the Rain”, “After the Storm”, even perhaps The Sun Also Rises.

You might object that these openings are reflected in Leonard’s provisos and exceptions. Strange how the circulated lore of “never open a book with weather” usually fails to mention those exceptions, though.

What’s more likely is a writer bringing to a workshop a story that opens with rain drizzling across a window pane, followed by another writing pouncing on the faux pas.

Worse, the lore of “never open a story with weather” is often misattributed to Hemingway, which is crazy. The man made an unstoppable reputation writing about the outdoors. For Hemingway to respect “never open a story with the weather” is like a mystery writer admonishing “never open a story with a murder.”

The prohibition against opening with weather is one more bit of lore designed to mystify and codify the craft. It bedazzles young writers who believe it a key to publication. It offers easy ammunition to every hack who’s entered a workshop ready to shred the story up for review. It’s time to set this tired chestnut aside.