At a recent education session of the Grand River Writing Tribe, our merry little band of literary miscreants enjoyed a brief sidebar conversation about planning-vs-pantsing in light of the impending NaNoWriMoPocalypse.
pants. Vt. 1. To write a book without meaningful preparation, letting the story and its major elements evolve as the author drafts them. 2. To “fly by the seat of one’s pants” while writing a work of (usually dubious) literary merit. Colloq.
I’m a planner. I have to be; I tried pantsing it, many years ago, but failed miserably. Suitably chastened by that traumatic ordeal, I’ve honed my planning to the point where I think I’ve got a system down that’s worth sharing.
But first: As a publisher, I can usually tell after the first few pages whether a submitting writer is a planner or a pantser. The biggest tell comes from conflict. Insofar as there ain’t no conflict, hoss, in most pantsed stories. Very many pantsed stories rely on plots that consist of one event after another, with pacing mimicked by the introduction of new events in a linear cadence, until a word-count goal illuminates the finish line and the final manuscript stumbles, sweaty and mildly incoherent, through the denouement victory ribbon. Alas, these new events are not tied to a core conflict linked to the eventual identification and resolution of the protagonist’s frustrated desire. They’re just one damn thing after another until “the end.”
The sublime editors at MiFiWriters honed my sensitivity to conflict as the primary driver of plot. I can still hear Sue Ann’s voice echoing in my head: “What does the main character want, and what’s stopping him from getting it?”
With a question that meaty, how can anyone start with backstory?
Pick Your Purpose
One question must set the stage: Is the story intended for private, creative purposes, or for publication? If the former, then to some degree, the sky’s the limit. Writing for yourself offers myriad opportunities to experiment with forms and techniques. But if you think you’d like to shop the manuscript, stop. Don’t ask yourself what story you want to write but rather, what story you want to sell.
Writing for yourself frees you of the rules of genre conformance, word-length targets and whatnot. Do what you want! Shamelessly incorporate whatever silly, tangential writing prompt lands in your Twitter account that morning. Hone your craft by stretching your limits. But if you’re writing for publication, you must pick a genre, strictly plan for that genre’s conventions, and execute with disciplined precision. Otherwise, no editor or agent will pay you the slightest bit of attention.
Earlier this month, I spoke with USA Today bestselling author Zoe Blake. She writes dark romance, and like any genre writer, she knows that if you’re writing to genre, agents and editors welcome very little deviation from the script — especially by emerging authors. (Her insights into this part of the process made our October Get Pressed! event, which she attended, a much richer conversation.) So if you want to write for publication, follow your genre’s standards with religious fervor.
How I Plan
Every author plans a major work differently, so if you’ve seen one approach, you’ve seen one approach. I encourage you, as you review my approach, to recognize that some parts of it might work for you and some of it might not. I’m not suggesting you should do it my way; I’m merely sharing my well-honed process for the benefit of those pantsers out there who’re lost like a fart in a whirlwind on the subject of novel planning.
Let’s begin, then, with the assumption we’re developing a novel-length work of fiction intended for publication.
- Identify external constraints on the final work product. If you’re writing for a contest that features a word-count range or a mandatory subject or theme, those parameters govern everything else that follows. In the absence of any word-count constraint, investigate average counts for your genre. Research from a few years ago suggests that the “average” debut author’s work clocked in at roughly 85,000 words. Put differently: That 55,000-word NaNo novel won’t cut it unless your genre generally supports that small of a manuscript.
- Catalog the attributes to be interwoven into the story. At this stage, I don’t know what I want to write, but I’m starting to get ideas about what I want to write about. For example, in one piece, I wanted to work on character development, so I decided that a primary character needed to be bisexual. In another novel, I set the story in Grand Rapids. In yet another, I explored the concept of regret at various stages in a person’s life. In a recent prototype novel, I wanted the protagonist and antagonist to experience wildly divergent childhood experiences that shaped their response to the story’s core conflict. I usually collect, over a period of three to six months, a list of a dozen or so completely unrelated aspects or subplot themes that — later in the process — coalesce into something resembling a fully formed story idea.
- Settle on a person, story archetype, genre and targeted word count. Think of an archetype as a meta-story, or a story scaffolding. Lists of archetypes vary; a common one, developed by Christopher Booker, lists seven: Overcoming the Monster, Rags to Riches, The Quest, Voyage and Return, Comedy, Tragedy, and Rebirth. Author Ronald Tobias lists 20 “master plots” that go even deeper into the archetypical weeds. Identify the right genre for the work. A single genre, mind you; hybridizing a story into several genres — a process called fusion — is a kiss of death for metadata and is likely to render your story unmarketable. For the purpose of this step, we’ll consider literary fiction to be a genre in its own right. This is the spot, too, where you’ll pick a voice for the narrative (e.g., first person or third subjective distant or whatever).
- Generate a thesis statement of not more than three sentences. This part is tricksy. You’re summarizing the story as if it were a short paragraph in your cover letter, but you’re doing it before you’ve developed any characters, plot or conflict. That’s okay. At this step, you’re still working through a high-level concept. It’s a starting point that you’ll revise over time. Address the basics of genre, archetype and market differentiators while remaining sensitive to the external constraints you’ve identified and the attributes you intend to include. For example:
- Magellan Ascendant is an 85,000-word classic science-fiction quest in which a 300-year-old colony ship from Earth arrives at its destination only to discover that humans have long-since colonized it. The crew of the Magellan must make sense of their new circumstances while forging new alliances with their now-exhausted homeworld and keeping peace among a crew still on edge from tensions that predate their launch.
- Wait two weeks. Let the thesis statement percolate a while. Come back to it in a fortnight with fresh eyes.
- Re-evaluate the thesis statement. Tweak the statement and your various required attributes as you like. Then ask yourself: Is it done? Are you happy with it? If you’ve made changes you deem to be significant to the structure or the content of the statement, wrap up your work and return to Step 5. If you’re satisfied that your changes were minor, proceed to Step 7.
- Wait two more weeks. Even when you’re satisfied with your high-level concept, you’ll find value in waiting another fortnight before beginning the next, crucial phase of planning.
- Sketch a mind map of the characters. You don’t yet know the plot or the people, so start with the people in light of your thesis statement. I like to work with a whiteboard — a physical whiteboard with dry-erase markers. Then I start mind-mapping. A character starts in the center. I don’t know who it is, yet. Then I draw circles around it for other primary characters. Then I start to give the circles names and roles. And then they get lines connecting them in some way, with the nature of the relationship documented on the line. By the time I’m done, I still don’t know what the plot is, but I have a high-level sense of who the characters are and what conflicts simmer among them — in effect, the state of the universe before the words “Chapter One” grace the manuscript. The finished work product from this step in the process includes:
- Brief bio — No more than a sentence or two for each character, often just a name, occupation, age, body type, personality quirk, etc. Remember, no one’s impressed with complex names that are spelled in goofy fashion and defy the laws of English phonics. No one.
- Role in the narrative — What does this character do for the story? A main character? Secondary? Does the character warrant a POV perspective?
- Relationships — How is each character related to every other character? What’s the relevant historical backstory for the relationship?
- Motivation — What’s the character’s main (and perhaps one or two secondary) goals or motives within the narrative?
- Conflict — How do these motivations and relationships engender conflict? Do several conflicts arise? A preliminary whiteboard sketch, without the bio/motivation/conflicts explicit, looks like this:
- Solidify the period and setting. Identify when and where the story takes place. If you’re inventing a fictional world, jot some basic notes (you’ll flesh them out later) about the mechanics of the universe, including rules of magic, social relationships, levels of technology, etc. If you’re writing contemporary or literary fiction that’s not tied to an explicit place, pick a place anyway just for your own purposes.
- Sketch the plot arc. Stick with your genre’s norms. Readers generally expect a three-act story with the first act setting the stage, the second act increasing the tension and the third act leading to resolution. I’ve found that starting the arc with conflict — i.e., starting with what the main character wants, then unfolding how he or she overcomes the obstacles to achieve it — makes the “events” part of the process significantly easier to work through. So with a sense of period, setting, characters, relationships, motivations and overall thesis, I return to my trusty whiteboard to sketch a plot arc:
- Create relevant computer files. Now it’s time to use the computer in earnest. I generally write in plain text with AsciiDoc using Visual Studio Code and my own private GitLab CE repository. Most folks will likely use Microsoft Word or Scrivener unless they’re doing something technical like a math textbook or a computer-science manual. Regardless of your tools, a few base files will likely prove handy:
- 01_chapter-title.adoc to nn_chapter-title.adoc — I allocate one text file per chapter, naming it with a standard logic of a two-digit chapter number offset by an underscore with a hyphenated chapter-title slug. The contents of each chapter go into each file. (A slug is a journalism term; it’s a one-to-three-word abbreviation of a longer title, hyphenated. For example, if Chapter 3 were titled “The Messenger Speaks at Midnight,” a slug might be something like messenger or midnight or messenger-midnight and the resulting filename might be 03_messenger.adoc.)
- notes.adoc — I create a single text file with reference material, including character sketches, scene sketches and facts about the universe.
- control.adoc — This file holds the project’s table of contents (annotated at a scene level, in the next step) as well as a manual record of word counts and to-do items.
- references.bib — (optional) a list for the references. Usually, it’s a placeholder in my non-fiction writing for shortcode ties to a JabRef citation library.
- spine.adoc — in AsciiDoc, a spine file knits all the chapter files together into a single unit for exporting to different formats. The spine includes all the metadata about the story, including metadata you’d need to self-publish the work as an e-book. (AsciiDoc supports natural conversion to HTML, DocBook XML and EPUB 3.)
- Translate the plot/conflict arc into an annotated chapter-and-scene structure. With the files in place, it’s now time to go into control.adoc (or, if you’re using Scrivener, the Binder/Outliner tools) to set up the chapter-and-scene structure of the novel. My goal in this step is to plot to the scene level, with a paragraph describing what happens in the scene as well as context like who the POV character is, how long the scene is, what’s the status of the scene, etc. Keeping the synopsis at about 1/35th of the scene length (e.g., a 2,000-word scene should have a 57-word synopsis) means you can aggregate the scene synopses into a unified traditional novel synopsis without incurring extra development work.
- Because scenes are generally self-contained units of narrative, I’ve taken to dividing my project target word count (e.g., 85,000 words) into 10 to 15 chapters of roughly 5,500 to 8,500 words, with two to four scenes per chapter. Keeping scenes relatively compact yet balanced, length-wise, helps to not only keep the action going, but also to facilitate productivity. It’s easier to write a planned 2,000-word scene in a day than to just “sit down and write.” Put differently: Plan the novel’s structure not just to facilitate your content but also to match your unique style of writing.
- In addition to a scene synopsis, I’ll take notes in this file about plot points that must or must not occur in that scene, and enter a placeholder for follow-up tasks that I should address “later” but which I shouldn’t lose track of. When I write, control.adoc is always open in a panel next to the chapter file.
- Develop relevant contextual notes about characters and settings. Just as the plot/conflict file found its expression in control.adoc, your various character, setting and universe sketches should find a home in notes.adoc — or, if you’re in Scrivener, as cards in the Research folder of your project. I generally put in some bare-bones basics here (mostly around characters), then I augment the during the writing process so I don’t contradict myself later. For example, I might include a paragraph of description and history about an important character, and then in Chapter 5 when the character references that she’s afraid of spiders, I’ll add a bullet to her character sketch that stipulates that she’s afraid of spiders, so that in Chapter 9 I don’t misremember her arachnophobia as agoraphobia.
- Wait two more weeks. Don’t start writing as soon as your prep is done. Give all this literary goodness ample time to percolate ‘twixt your earholes.
- Revise. Look at all your notes: Check your files, re-examine pictures of your whiteboard, whatever. Think about the project in its entirety. Does the conflict make sense? The plot? Are the characters compelling? Do you meet genre norms? Most importantly: Are you excited to write this book? Answer no to any of these questions, revise then return to Step 14.
When you’re done with Step 15, you’re ready to write.
My flow works for me. It won’t work for everyone. But I hope you’ve found something to take away that will help you grow your craft.
This Post Has One Comment
I really love the visualization of “plot” versus “conflict” – it clarifies a thought I feel I hadn’t quite reached the conclusion of yet. I’m currently on the second draft of my novel but I still find so much of this useful so thank you for sharing. I’ll definitely be revisiting this come time for novel number two!