Generating Story 8: Creative Q&A part 2

I realized I needed to blather a bit more on this topic to warn you against something before I bring the other authors on.

You’re going to be tempted.  You’re going to be tempted to seek for some Holy Grail list of magic development questions.  Some of you are going to be tempted to compile some big old honking list of “the questions that will produce a killer story every time and all I have to do is ask them.”

That list doesn’t exist. If you seek for it, you’re going to waste a lot of time and end up having to fight killer rabbits and fetch shrubberies for weird knights.

Don’t fall for it.

But, John, didn’t you say there were core questions?

I did.  You need answers for those.  But you need to also understand that a writer will ask a great number of development questions when writing a specific novel, some of which he might only ask once.

Last year I was out on the forum at CodexWriters.com and one writer asked the rest of us how we approached developing our stories.  He was looking for some kind of development map, e.g. I have this piece of the story, now I need to develop the rest–how does one go about that? 

That discussion led directly to this series on getting and developing story ideas. My thoughts then were that you need to define and understand the basic elements of story.  Knowing the key story principles behind each element leads us to a handful of core development objectives and questions.  But–

I DO NOT think there’s a comprehensive must-do list. 

Why?

Because it’s been my experience that no two stories are exactly the same, and so no two stories require the exact same questions. And even if stories are similar, questions and techniques don’t always produce the same results each time. One question or technique might prove fruitful one time, but it might be unfruitful the next, or even unnecessary.  So the point of this is NOT to get a checklist of a hundred questions that will lead you to generate the whole story in your mind before you write.

The goal is to develop the six parts. Use the questions you need to develop those parts.

Look at the many setting and character profile question lists that float around. As I’ve used those, I always run out of steam because while some of those questions are interesting and helpful, quite a few of them just don’t apply to the project at hand. They bore me. Maybe I felt a spark of life with one question, but instead of following it as the way into the story, the whole checklist format suggests I need to move on to the next one and fill in the blanks.

But my goal isn’t to fill in blanks. My goal is to make the story come alive in my mind, to make the character come alive, to develop someone sympathetic, deserving, and interesting (if he’s the hero).

So while I think looking for productive questions is important, and I DO think there are some core questions that need to be answered every time, I think a person will be more productive if they step back and identify the key things they want in the story, the scene, the particular character.  This means we’ll have some standard questions and techniques based on how stories work, but it also means we’ll learn how to do the creative Q&A process on the fly, following the zing for the current project, coming up with questions that we could never predict we’d use. 

And we’ll use the objectives for the six core parts as the guide then build upon them.

For example, when finishing up my last draft of Curse of a Dark God, I wrote the opening to a big battle chapter. I know that for things to be clear to the reader, I need to set the stage, have a hook, give the what, why, where, etc. I need to transport them as best I can. Those are my objectives. The questions, while not formally stated, flowed from them–what are some options for a good hook, how do I want to set the scene, etc.

These are fairly standard objectives/questions. They’re story fundamentals. And there weren’t a lot of them. You can get overwhelmed with too many niggling objectives and criteria. I’ve found it’s best to focus on KEY things. To ask myself–what are the Pareto factors, the handful of things that really have the biggest effect in story with character, plot, scene? Once I identify those factors I can easily turn them into questions.

So I had those handful of objectives. But I had some others that were very specific to that scene that I probably won’t use in any other scene ever.  And I couldn’t have really even known about them until I got to the point where I was writing the scene.

For example, one was how to introduce the Dogman of Toth and his pack of maulers in a way that makes the reader say “ho-lee crap those guys are screwed!” Another one was how to introduce the kitemen in a cool way. Another was based on a feeling I was getting from my Spidey-sense that the scene I was writing was going to undercut a later one if I made the hero’s objective to kill one certain character. So I had to ask, what is the right progression of these scenes? Who should the hero attack here so it feels right, like a progression?  Another objective was to make this whole battle scene awesome, thrilling. That’s certainly something I’ll want to do with other battle scenes. But not on all scenes.

With the very next scene I was asking–how can I make this scene tender and heart-breaking? These ad hoc questions about the Dogman and kitemen and the story progression are all great questions flowing from objectives, but they were for that one particular scene.

So I think there are some core objectives or principles of how character, setting, problem, plot, and text work. These are based on key story factors. I listed those out in the last post and in my series on suspense. You can make a “standard” list of objectives and questions out of these. For example, one of those key objectives is for the reader to care about the hero. Another is to find him interesting. I can indeed translate these core objectives into some standard POWER QUESTIONS that might be put on a list.  Along with some core questions, there are favorite techniques (tools) we each use to help us work up what we need and get into a story, scene, character, problem, etc.

But I think a lot of writing is using the creative Q&A on the fly because it’s just impossible to think up all the objectives and questions you’ll encounter before you get into it. 

Have I said that about twenty times now in this post?

Let me suggest you not try to develop everything up front before you begin to draft.  Some development questions occur when you’re sketching or outlining. Others when you’re in details of draft mode. It’s a mistake to try to get it all up front in some list.

The key, I think, is to have our handful of CORE development objectives/questions and ALSO expect to use the QA process along the way. This allows us to move forward in the creation without needing to develop everything up front, which is impossible (no, it really is impossible), and then step back and formulate questions when the need arises, based on our objectives of the moment, and use any number of methods to generate the answers until we have something that rocks.

But John, how do you know when you’re ready to move forward?

For me I need to have generated the story concept–the basics of the character, setting, and problem.  When I have that, I’m usually beginning to “see” things, although certainly not everything.  Often I’ve envisioned a couple of moments or scenes.  Maybe some dialogue, etc.  When I get to this point, I’m able to write a Story Setup statement.  And then I generate a sketch of the plot with a working outline.  I DON’T have all the details, but the story’s alive enough in my mind to proceed. 

Sometimes I begin to draft what I sketched and find out it doesn’t work.  And sometimes I have to draft to get my story concept. Eloise McGraw (I love her book The Moorchild) usually found she had to draft seven chapters before she really knew what the story was about. That’s fine. The key isn’t to use a certain set of tools in a specific sequence. The key is to get to the point where you understand the story you’re telling. If I can do that with a bit of sketching and a little drafting, great.  If I need to do a bit more exploratory drafting to have the story come to life in my mind, that’s fine too.  The key is to know what I need to know about the story and work until I know it. This is writing that’s based on objectives, on principles, not on procedures.

So there ARE core questions you’ll need to answer for every story.  But it’s also true that you will be hunting mythical rabbits if you look for a secret magic question procedure that lists all the questions you need to ask, EVAR!  Having said that, I’ll now let these other authors finally get a few words in edgewise.

For more in this series, see How to Get and Develop Story Ideas

Share

Similar Posts

  • Indie Thoughts: Enticing with price

    The top two factors driving book sales both stem from having a loyal customer base. Building that base is the goal as it is in any business that depends on repeat customers. In a previous post I outlined these parts to building that base.

    1. Create a product (a book in this case) that’s likely to delight a certain set of consumers (readers).
    2. Let those consumers (readers) know about it.
    3. Make it enticing for them to give it a try.
    4. Make it easy for those who liked it to know when they can get another; and make it easy to get.
    5. Get more product (another book that’s similar to the last) out the door so your repeat customers can come back for more.

    In this post I’m going to share some thoughts on #3.

    So how do you entice someone new to give you a try? There are a lot of things I see that play into that:  a great cover, description, sample chapters, and reviews that all say quality and scream genre. But there’s another huge factor to making something enticing. And that is price. Or rather price vs. perceived value.

    I’m looking at Mark Corkers reports from Smashwords.

    I’m looking at slides 65-69. I know many of us have seen them.

    If the patterns are similar at Amazon, which sells more ebooks than anyone else, then a price of $3.99 on average will sell more than double the copies of $6.99.

    $3.99 means MORE readers who might develop some level of loyalty, MORE word of mouth, and it means MORE revenue than at other price levels.

    It means more than double the chances of getting your stuff in front on an influencer.

    More than double the chances for luck to come into play.

    And those odds grow exponentially.

    And, again, all along the way that price earns you more than if you were pricing at $6.99 or $9.99 because you sell more books.

    Of course, these are averages, which means folks are winning at prices above and below this. Furthermore, it’s not the same across genres. For example, it appears romance tends to sell better towards the lower end of the range Corker shows.  But it clearly shows that price is an important part of enticing a reader to give you a try.

    And when I look at the indies who are selling huge numbers and have built their customer base, the vast majority of them seem to have gotten there by tapping into the market forces Corker shows on these slides.

    That doesn’t mean they price all their books the same. Some are doing very well using a loss-leader/sample strategy where they offer the first book in a series for 99 cents or free. This also doesn’t mean they set their price and forget. it. They seem to do just the opposite, experimenting with different prices.  I noticed the Joe Konrath, who became a mega-seller at $2.99, raised his prices to $5.99 recently. He’s dropped them back down to $2.99 and $3.99. But he was clearly testing something. In an interview earlier this year with Simon Duringer, Russell Blake who is doing very well in the thriller category recently said this.

    Probably the most effective thing I did over the last two years other than Select, which came and went in terms of usefulness, was making the first book in my JET and my Assassin series free. That lowered the barrier to giving my work a whirl to nil, and my readership exploded from there. About a month and a half ago I stopped doing that because I saw my conversion rates were averaging about 12-13% from the first to the second book, and I questioned whether, with, say, 500 downloads a day, and seeing 60 sales of book two, it might not be more desirable to get 70 paid sales of book one, and seeing that same 60 on the conversion (because if someone pays for your first book, they’re probably going to read it, and soon, whereas if they get it free, it could take years, or more likely, never happen). So far so good.

    Clearly the folks who are doing well with this are experimenting with price to see which levels maximize revenue and loyal customers. And I think that’s the key. They are looking at what seems to be working for others, experimenting, and basing decisions on results.

     

    Share
  • Generating Story 3: Develop The 6 Core Parts, Start Anywhere

    If you’re going to build a house, you need to know what type of house you want and what you want it to do. A two-man tent is a house of sorts.  So are a suburban rambler, a New York high-rise, and a medieval fort.  Each is a bit different, even if they share elements.

    Building a story is like building a house. You need to know what you’re after. You need to know how stories work in general and how the type of story you want to write works in particular.

    For example, if you love suspense, and it’s going to factor heavily in your story, you’d better learn the principles of suspense. If you love intrigue and mystery, you’d better learn how to build that in a reader. If your current project is a crime story, you need to know how crimes work and how they’re solved. If it’s a love story, you need to know how falling in love works. All of those things you identified as your personal style—you want to know how they work.

    Except sometimes, when you’re starting from scratch, you might not know exactly what kind of story you’re going to build.

    So what do you do?

    You get a list of development objectives. And you begin to work on them. Your mind needs a direction to run.

    Despite the fact that stories are different, they share some common core things. These are the things you want to focus on developing. When I start a new project, I know my task is to develop six core story elements. This gives me a direction. All I have to do is start developing these six things, and sooner or later the story comes to life.

    So what are these core elements?

    • Genre
    • Character
    • Setting
    • Problem
    • Plot
    • Text

    You need to develop all six parts. That’s your job. There’s no particular order that you develop the elements in. You just start with what you have. As you develop all six parts, the story will come to life. Your characters will begin to breathe and speak. They’ll take on a voice and attitude. You’ll see the landscape. Scenes and plot turns will come to mind. If you’re more of an auditory thinker, you might not see anything, but will start hearing the rhythms of the prose. Visual or auditory, you’ll care about and believe in the tale. You’ll have something wonderful to write and share with readers.

    Let’s look at each element to see what you’re trying to develop.

    Genre

    The genre tells you the overall effect you’re going for. It describes the salient aspects of the tale. Those aspects often focus on the emotional mix you’re delivering to the reader (horror, humor, thriller), but can also describe the setting (western, Regency romance), as well as the type of problem your characters will be facing (love story, political thriller), and the audience your writing to (young adult, middle grade, women’s fiction).

    But why do you want to know your genre? Isn’t that just a marketing thing?

    No, it’s not just some marketing thing. If I’m telling a story about a kidnapping, knowing it’s a tale of tale of horror–instead of a romantic comedy, fantasy, western, science fiction, or political thriller—makes a huge difference.

    It gives me an objective. Parameters. Remember, creativity is problem solving. If there’s no objective, there’s no solution. The moment we have an objective, our mighty brains can kick into gear and start suggesting ideas. The more specific we make the objective, the easier it is to think up ideas.

    Now, you might not know the genre when you start. You might simply have a cool bit of dialogue, an image, or newspaper clipping. That’s okay. You don’t need to start with genre, although it often helps. But you eventually want to peg that genre, even if it’s some blend of your own making, so you know the general effect you’re going for.

    Character

    You want to develop a couple of characters, usually at least a protagnoist and antagonist. They need to be interesting to you. If you want your readers to root for someone, that person had better also be sympathetic and likeable.

    What makes a character interesting? What makes them sympathetic and likeable? You might want people to dislike your antagonist. You’ll at least want them to fear him or her. What produces that? Read what I wrote about character here: http://www.sfwa.org/2010/12/key-conditions-for-suspense/. Then start noticing what makes people and characters interesting, sympathetic, and likeable to you, as well as what makes you fear and dislike others.

    There will be other characters you’ll need to develop—a mentor, lover, friend, henchmen, etc. Maybe you start with one of them. That’s fine. Just know you need to be on the lookout for your protagonist and antagonist. Almost every story has both. For the hero, you’ll usually want to develop someone that’s interesting and likeable. For the antagonist, you’ll want to develop someone who is interesting and powerful enough to make us fear for the hero.

    Setting

    Setting may play a huge role in your story as it does in epic fantasies, Westerns, historical pieces. Furthermore, a setting doesn’t have to be faraway place to play a big role. Your story may be set in a prison, rural town, or manufacturing plant, which may factor heavily into the story. Then again, setting may play less of a role. It all depends on what interests you and the type of story you’re writing.

    They key, I’ve found, is to develop the setting with the goal of having it come alive in my mind by identifying things in the setting that are interesting or will affect the hero and plot. I need to transport the reader to a place. I can’t do it, if I myself don’t know what that place is like. And it’s nice for them to find it interesting when they get there.

    Setting is also a great source of ideas for the other elements. When you develop setting, you’ll find characters, problems, and plot ideas galore.

    Problem and Plot

    I wrote a detailed explanation of problem and plot, which you can read here:  http://www.sfwa.org/2010/12/key-conditions-for-suspense/. Read it. I’m not going to rehash it now. But I will say that problem is the engine to your story. Your story is not going to go anywhere without it.

    You want to identify the main problem your character is facing. One that is going to generate enough scenes for the size of story you’re going to write. Read what I wrote about conflicts, obstacles, etc. Ultimately, you’re aiming to develop a problem that you find compelling.

    You might not develop the key aspects of the plot in the beginning. In fact, you’ll probably discover many of them only as you write. However, at this stage it does help to start looking at plot patterns for the type of problem you’re writing about because it helps generate ideas for scenes. For example, a romance about a gal who is a Minuteman or border agent and guy who is a coyote (smuggling folks across the border) will take a different course than one about a farmer trying to find his kidnapped wife.  

    In the first story, we might start by introducing the characters: the border agent interdicting a group suspected of being drug mules; the coyote is leading that group. In the next scene they might meet, and not know what the other is. They’re attracted. They meet again, maybe have dinner or dance or go hunting. The romance deepens. Then one finds out about the other.  If she finds out, does she turn him in? Maybe he inadvertantly leads the drug cartel to her and puts her in jeopardy.

    In the second story, we might start with the husband and wife in some funny situation. He leaves. Comes back. Finds her gone. Finds evidence of her kidnapping. Gets a call or a note. Is told they want him to pay them a ransom. Or maybe turn over title to something. Or maybe he works at a weapon manufacturer, and they want some piece of tech. Or maybe it’s something else.

    The point is that they develop differently. The plot patterns of love stories are different from the patterns of heists, kidnappings, shipwrecks, bullies, etc.  because they’re all different problems and require the hero to take different types of steps to solve them. When first developing a story, I’ve found it’s helpful to think about patterns for presenting, complicating, and resolving those types of problems. I’ve found it helpful to ask, what would I do in this situation?

    For more on plot patterns, see the link above. In addition to patterns, specific plot turns that really spark your interest will present themselves to you. Maybe I don’t have a pattern yet, but as I’m developing the character or setting a cool scene comes to mind. Or maybe it’s a cool plot turn–the border agent is captured by a drug cartel and the coyote goes in to save her. You want to be on the lookout for these.

    So in the beginning, you want to focus on developing a compelling problem, a general plot pattern, and be on the lookout for some cool or fun scenes or turns.

    Text

    Text is the prose on the page. It’s how you translate the story in your head to something the reader can consume. It’s the specific scenes, the dialogue, and narration, which means you don’t stop developing the text until you write “the end.”  Sometimes, the story can come alive without drafting. Sometimes, especially with those writers who are more auditory, you need a rhythm, a voice for the narrator and character before the story clicks. Often it just takes some freewrites or a drew chapters to discover this.  What I’m after is a point of view voice.

    Sum It Up

    Take some time and think about the key elements, how they work, and the core of what you need for each. Make yourself a simple checklist. Here’s one such checklist.

    • A protagonist who is interesting, fascinating maybe, someone you yourself can get behind and want to follow. 
    • An interesting antagonist who raises your anxiety for the protagonist.
    • Asetting that’s alive in your mind as well, including parts of the setting that are interesting—the things and people that are scary, cool, lovely, dangerous, funny, etc.
    • A problem that’s compelling to you. One that’s big enough for the size of story you’re writing. One that suggests a juicy plot.
    • A plot pattern or two. Maybe some scenes or plot turns that really spark your interest.
    • A voice for the main character / narrator. 

    Here’s another I recently shared with some younger writers:  

    It doesn’t matter where you start when you invent a story, but you  need to end up with a character you think is fun, cool, or  interesting, who has a problem other people will find funny or  compelling–that’s the core of your story. The problem can be a mystery the character needs to solve (there are strange green lights in the sewer), a danger or threat to some aspect of the character’s happiness or someone they care about (holy smokes, that big alien that looks like a bug wants to eat my head), or an opportunity for something that will make them happy (I live in a cupboard and get to go to magic school!) You start there. The rest of the story is about how that character goes about trying to solve the problem, the characters who help them, and those who work against them (including tiny evil mice villains). You know you’re done when the mystery is solved, the threat removed, or the opportunity is won or lost.

    Here’s another from Lou Anders that he offered on a Writing Excuses podcast that presents another way to sum up what you’re looking for with character and problem (BTW, I find no evidence that all satisfying stories need what he calls a relationship character; however I do think it’s a fantastic technique for stating theme and clarifying the internal problem in stories that revolve around a character making a change):

    [Lou] The protagonist is usually the most obvious one. He or she is the star of the film. The protagonist is someone who wants something. It has to be something concrete [emphasis added]. It can’t be “I want to be happy” or “I want to be pretty” or “I want to be rich.” It has to be a definite, achievable goal associated with that. So I want him to fall in love with me so that I will be happy. I want to win the game show that I’m going to be on so that I will be rich. I want to rob a casino of the guy who’s dating my ex-girlfriend, that will make us happy.

    [Dan] So I can be happy and rich.

    [Lou] Yes. Exactly. So it has to be a concrete, achievable goal.

    [Lou] The antagonist is the person who places obstacles to that goal in the path of the protagonist. This does not mean the bad guy. Now, we can talk about some very interesting examples. The antagonist is the one whose goals are diametrically opposed to the protagonist, and they’re the one who is blocking the protagonist’s journey.

    These aren’t twenty page design documents. They’re simple checklists. There’s power in keeping your objectives simple. Too many details and you lose your focus.

    I suggest you take some time to write a succient sumary of what you want to develop, one that gives you clear direction. It doesn’t need to be perfect. Just cobble something together. And keep it SHORT! Remember the 80/20 rule.

    Let me suggest you not get bogged down by rules: Rules vs. Objectives. And that you include at least four of the six parts: The 4 Parts. The key is have a list of core things you know you need to develop for the current project. Knowing what you need to develop gives your mind a direction to work in so you’re not just flailing about.

    You can’t know it all up front

    It’s important to know that even though you have a development checklist, you will NOT develop the whole story up front before you begin to draft. You can’t. It’s impossible. It’s a mistake to think you must.

    Even the folks who write detailed seventy-page outlines cannot imagine the exact words and turns of every scene before they actually write them. Furthermore, they are often surprised by ideas that come as they draft and find themselves adjusting their outlines.

    Your goal is NOT to develop a super detailed set of writing instructions that a monkey could follow. Your goal is to get enough ideas in the six parts for the beginnings of the story to come alive in your mind. When the story is alive in your mind, writing is almost like transcribing.

    You might develop your ideas by creating various types of sketches for the plot, problem, character, and setting before you begin to draft. This includes things like summaries, outlines, drawings, maps, character biographies, etc. On the other hand, it may take some drafting before those things begin to breathe.

    Also, it’s rarely the case that you develop the parts sequentially. What usually happens is that you develop a little bits about each part in random order. Maybe you start with the bare bones of a problem, then develop a bit about a character, then setting, which leads you to more about the character, then you see something on TV that sparks your ideas about the problem, then you write a draft of something and get some more details, then your brother says something that sparks an idea that fits. Or maybe you start with a snippet about a character and move to the setting and back to character then to problem. Or maybe you begin with setting and discover a bit about a character.

    It doesn’t matter where you start. The parts build by accretion, like a snowball—here a little, there a little. 

    Selective Attention

    Once you know what you’re trying to develop, ideas will literally jump out at you. It’s all part of the biology of selective attention (http://en.wikipedia.org/wiki/Attention).

    For example, if I tell you to develop a sexy female antagonist, I’m betting some ideas or images immediately leap to mind. If I tell you to present me with three different choices for this antagonist next week, someone who will fit into my kidnapping story, someone who’s a little surprising, and every day you think about this objective, you’ll encounter all sorts of ideas over the next seven days that you might use.

    Why? Because you’re primed to see them. You’re looking for solutions to a specific problem. You’re harnessesing your focus and working memory limitations. That’s selective attention.

    The more specific I get in my objectives, up to a point, the easier it becomes. If I tell you the kidnapping is a comedy set in rural Utah with Mormons and Peruvian sheep herders who work for 9 months and then return to Peru, that will lead you down one path. If I tell you it’s a thriller set in the deep south with Mexican drug gangs and a local police force, that starts you thinking in another.

    An Example

    Let me give you an example of all this. A few years ago, I was on a business trip, and just before checking out of my hotel, I read an interview with Deborah Vetter who used to be the editor for Cicada. She said they loved traditional fantasy stories and that many of those she liked took a common theme and gave it an unexpected twist. Cicada was open to fantasy at the time, and so I asked myself: what’s a twist on a common fantasy element?

    Boom, objective–my mind had a direction to run in.

    I got my luggage together, checked out of the hotel, and drove over to a Lowe’s around the corner to pick up something for the house. All this time I’m running various fantasy elements through my mind—witches, ghosts, dragons, etc.—asking how I might twist them. Trolls? No, boring. Witches? Meh. Vampires? Ugh. I went through a whole bunch of ideas. I got out of the car, entered the store, continued. When I was walking down the trim isle, I finally got to golems.

    Hum, that was interesting to me.

    All the golem stories I had read were about the rabbi creating the golem and what happens. Kind of like Frankenstein’s monster. So I asked: what if it wasn’t about the guy who creates the golem? What’s a twist? What if it’s about someone who finds a golem?

    I immediately saw the bank of a river, the Evanston, Wyoming river my girls and I had been playing on a few weeks earlier. I imagined the river in autumn, yellow leaves on the ground. I imagined a bald man of red clay, half exposed in the freshly shorn bank, the rune of power on his forehead and neck. The river was low, the mint growing on the exposed sand and gravel bars, the smell of leaf mold hanging low over the water.

    My cool meters went wild. Some ideas carry such a delicious energy.

    Did I have a story?

    Of course, not. I only had the first whispers of a character (the golem), setting (a river somewhere), and genre (some kind of fantasy). Maybe a bit of a problem. This was one cool idea, not anything close to a story. I knew I needed to develop character, setting, and problem. That’s what forms the premise of the story. So I got to work on those elements.

    I captured the image on a scrap of paper, and began asking questions. Who finds it? A woman, I thought. Where? I listed some options and liked the woods of North Carolina. And it was some Native American creature. What’s the problem? What’s at issue? Either the red golem has his own agenda, I thought, or it’s others forcing it on him, or he’s trapped. A trapped soul…and the woman and the golem love each other…

    Did I have a story yet?

    No. Not even close. I still didn’t have a clear problem. Or very much about the characters. No plot.

    So what could the problem be? What was the situation?

    I walked around Lowe’s, drove home, thought about it on the way, generating options. I took a few days and generated ideas about American Indians, pickups and rednecks. I researched golems. I asked myself–what would that girl do, if she found this thing?  What if she dug it out and took it home? So I had a girl who digs the golem out and transports it home in her pickup, modern day South Carolina. She takes it home, cleans it, becomes obsessed with it. Takes it into her room. One night she’s lying in the dark, the house is quiet.  And suddenly it takes in a breath. It’s trapped soul–they love one another, she has to say good-bye in the end, a bitter sweet ending.

    Whoa. Cool! Now this thing is alive. But then the more I thought about it, the more I realized I didn’t want to write a story about a woman obsessed with a golem. Golem love? So I tossed it and went back to developing more ideas.

    Here are some of my development notes so you can get a feel.

    <quote>The deep-trench men were admirable monsters. They knew the clay, the feel and pattern of it, for it had long been heavy in their minds and muscles. They were big in three dimensions and their eyes were black and barbarous…</quote>[just a scrap I ran across and put into the folder]

    Okay, this is going to be a hot writing, just letting the ideas flow to see where they take me and trying to simply let the ideas come.

    Zing: what if he leaves, she finds him, does something, and then one day she goes back and he’s gone. And what’s she going to do? He could be hiding there and malevolent. Or he could be following her.

    I like the idea of her falling in love with him.

    The red man in the bank of the river. And I’m pulled to the historical setting, a historical fantasy. Not a contemporary, but one that’s serious about the guy. One that has villagers etc.

    So she’s out there, collecting late berries (currants) or maybe mint, she’s out there and it’s a fine fall day and the water is tumbling, rushing by. And she’s in a dark blue skirt and a white blouse, and she’s got dirt on the skirt, carrying the mint, and she comes around one thicket of willow and there he is.

    He’s not all visible, but she sees the skull and the shoulder and thinks skeleton, perhaps a burial ground, some ancient thing.

    Goes to investigate. It’s not the bones of the dead. A statue? What is it? She digs a bit, dirt in its ear, digs and uncovers more of it. Sees the rune of power on his head. Steps back. He looks like someone struggling to get out of the rock, birthed from the rock. And now its very obvious to anyone coming by and she hides it. Struggling like a man from the womb.

    And so what’s the danger from here?

    She loses the cool thing.

      • He gets out and leaves–gone
      • The villagers or one guy, one big man, goes down to destroy it
        • Her fiancé
        • Her husband, she’s young, very young and he’s her husband?
      • Or she’s alone, very alone.
        • She takes the thing home, gives it a place, talks to it (like Wilson in Outcast)
        • And then one day it’s gone, he’s gone, this thing that’s taken her life, it’s gone and she realizes that it’s alive, the last image, last piece of information shows dirt, red clay dirt in the bottom of a bowl, the spoon laid to the side. Something that would signal that the thing was alive.
        • THIS IS A COOL STORY. Not a long one either. A cool one.
        • So she’s caring for it all the time. Cleaning, scrubbing
        • Does she at one time hear a gasp? Thinks, he’s coming alive. Has a place set for him, a plate etc. But that goes away, it goes long away, too long and she realizes she’s mad.
    • She digs it out? Digs it all out. Heavy as stone.

    It’s all freewheeling sketching.

    Now, I could have stuck with North Carolina and tried something else. But as you read, my interests were pulling me to a different setting. Where else might it be set?

    I listed some locations, and Croatia drew me. I’d just read and seen some cool stuff about Croatia. But I didn’t know much. Was it going to be modern or historical? I began to read about Croatia. And the 1100’s fascinated me. There was all sorts of stuff going on. I decided to set it there.

    Did I have a story?

    No. I still didn’t know what the problem was. So I outlined some options, did some character sketches. Did more research. Looked up old Croatian names and magic. I got out a map. I was wanting it to come to life in my mind. But it wasn’t there yet.

    I went searching for a problem. I didn’t really want that golem love story. I made the following entry in my pre-draft document. 

    What’s at stake? The woman finds this thing, so what? She’s obsessed. But what’s the big issue here?

    • Danger, if she wakens maybe it will kill
    • Maybe if people find out they will want to use
    • Maybe she will be declared a witch
    • Maybe it will eat her out of home
    • Eat her children
    • Maybe it will force her to feed it, force her to bring people to him so he can kill them
    • Is it a thing of danger?
    • Maybe it will force love upon her? Breed with her and create a race of goblins or trolls.
    • It is a great thief–bringing her presents, presents for the master. And one day it brings a child.
    • A goblin with long hair and not dumb, not brutish, by hungry, a predator, one who will eat you, who loves hunt and chase, but can dress and act civilized.
    • Maybe that’s the thing–it draws you, draws your dreams or your mind, feeds on these things until it has strength to go on and takes a part of you with it, you’re longing, longing, longing for it to return.

    I tried a few drafts, still focusing on it being a thing she wakens, but they all eventually lost energy. So I tried something new. Here’s what I wrote:

    What if it IS about him stealing things? “The golem was a thief, and this made her believe it might not have been such a holy thing after all.”

    Or

    She’s looking. Can’t destroy it because of its holiness. But didn’t the wizards of the devil turn rods into snakes in the Pharaoh’s court? And didn’t men always take God’s gifts, like Adam, and throw them away?

    This was a question.

    That last line brought in a voice. I’d recently watched Fiddler on the Roof; I loved the characters and voices in that movie, and it was that yiddish voice. I decided to try that voice on for size and freewrite again. Here’s what I wrote.

    The golem was a thief.

    [That felt exactly right; I love it and continued]

    Nothing in the village, nothing in the whole vale for that matter, was safe. The golem was forever stealing and bringing its thefts to Braslava’s door, laying them on her step like a cat lays down dead birds and mice.

    One day it’s the Butcher’s blue and white Turkish stockings, the next it’s cranky Petar’s new pitchfork.

    And then it would stand there, looking at her, and all she could say was, “You think you’re doing me favors? Take your inscrutable face and go sit.”

    I went maybe two pages before I ran out of steam. At the end of the freewrite, the story was alive and bucking in my hands. I was full of excitement. At this stage in the game, I had three characters I’d sketched, a problem (the thief golem), a setting, a bit of plot. I had a maybe two scenes I knew I wanted to write. I had a narrative voice for the piece. I knew, because I’d been researching the political situation, that a Hungarian lord was going to get wind of what was happening in the little village of Plavca and want to use the golem for war. I didn’t know everything, but I knew enough to start.

    You can read the story for free on my fiction page. It’s called “From The Clay of His Heart” and was the cover story for Orson Scott Card’s Intergalactic Medicine Show, Vol. 8, 2008 and reprinted in Year’s Best Fantasy #9, Ed. David G. Hartwell & Kathryn Cramer. Here’s a thumbnail of the illustration. Nice, eh?

    The key is that I knew the things I needed to develop and kept at it until everything reached a critical mass and the story came to life.  This is how you develop on purpose instead of on accident.

    Now What?

    Take some time to think about the six parts of your current project as well as some general principles about how those parts work. Write out a couple of things you want to develop in those parts. Over the next few days notice how much more productive you become.

    Of course, it helps to know how to go about developing the ideas. It helps to know some specific techniques. Because we can’t just wait for ideas to come along. Again, we want to create on purpose, not by chance.

    And that will be the topic of the next few posts.

    For more in this series, see How to Get and Develop Story Ideas

    Share
  • |

    Your local zombie author appears on Writing Excuses, Plus the Writing Debrief explained

    After a cancerous death, I appeared on Writing Excuses this week to groan and hold forth with the guys on writing second novels and second books in a series.

    During the podcast I talked about my practice of debriefing after every writing project. A reader just asked what that was, and so I thought I’d explain it here.

    The debrief is a simple thing. I learned it back when I worked as a business consultant. It always provides great insights. Sometimes  it provides massive insights. The principle is to pull back and look at the big picture every once in a while. So here’s what I do. When I finish a project, I sit down and simply list out what I struggled with, what went well, and anything I learned. I list out things I’d do again that worked particularly well and things I’d do differently. This might be about craft or process. Sometimes I might take some time to reflect on the nature of story and read a favorite book about the craft or perform a story analysis on another movie or book. Then I write up my insights in a form that I can read later and know what the heck I’m talking about. This can take a few hours or a few days. This last debrief after draft 3 of CURSE coincided with my preparation for a day-long workshop I had agreed to give on story, and so the insights came thick and fast. I recommend the practice highly.

    Share
  • How to tell an author you don’t like their book

    Mette Harrison wrote a blog about how various authors respond when they read a book, don’t like it, and then the book’s author asks them directly what they thought of the book. 

    Here’s my response.

    As an author when I ask someone, especially another author, about their experience with my story, I’m looking for a data point to see how the book’s working or to get some insight. I realize others might be looking for validation. And, of course, I hope that everyone who reads my stuff finds nirvana even if I know that is not going to be the case. But I don’t ask unless I want data. And so I would hope they would report their experience accurately. I also hope they do it in friendly and helpful manner.

    So because that’s what I want, that’s what I try to do for others.  And the sandwich+ method has been one good way for me to do that.

    1. State something specific that works for me, e.g. “I love your character Bill because he’s so outrageous.”
     
    2. State the key thing that’s giving me trouble. For example, I might say, “I am having a hard time with the pacing.” But then I ALWAYS want to give the context of me as reader when it applies to my reaction, e.g. I’m a terribly impatient reader, I like to feel hope in what I read and know I don’t like as much despair as many other readers do, I can’t stand clowns (this is true: clowns are some of the scariest creatures out there, second only to crocodiles). The author should know these readerly things when they apply so the author can understand where the comments are coming from.

    If the book’s in pro shape and I think the issue is mostly my tastes, then it’s also useful to compare their work to another successful piece or author that had the same issue for me, e.g. “This reminds me of Twilight; I know people love it, but I just couldn’t get into that book either for the same reason.”

    I don’t think this is fluff. I think it’s part of being accurate. Our reality is what we focus on. And if I make a statement that leaves an author thinking I think the work is bad, then that’s not accurate because the truth is I think I’m not in the audience.

    If I think it’s a craft issue, then I highlight the main thing I think is causing the problem. A laundry list is usually useless. But thoughtful focus on the key issue can be very helpful. If I can’t tell whether it’s a taste issue or a craft issue, I admit it.

    3. State something else that’s working for me, e.g. “While I just couldn’t get past all those clowns freaking me out, I did think your chapter openers were compelling. I always wanted to read more, but then, alas, clowns.”

    4. The + is not just leaving statements hanging. Asking some sincere questions after demonstrates my genuine interest. And I am interested. If the book is unpublished, I might ask about their plans for the book, are they going to be doing another draft or shopping it, or if my reaction is common. If it’s published I might ask how it’s being received, what others are liking about it, and what’s next.  Maybe they tell me about another project they’re working on that sounds fascinating.

    This is what I’d want an author to do for me–be accurate, interested, and friendly. In such a context, someone having issues with a story is not such a big deal. It really isn’t.

    Share
  • |

    You’re invited to join the novel writing workshop pilot

    I am developing an online novel writing course and am looking for folks to pilot it with me and give me feedback. I’m thinking I want to limit it to 10-12 folks.

    It’s free and will probably take two or three months to complete. If you join, your job will be to do the work. And there will be work. I’m thinking 10-15 hours of work per week. Please don’t ask to join if you don’t want to make this commitment. I only want folks who are serious and ready to give this a shot. In addition to the work, you’ll need to report your experience with the course as we go, sharing with me where you get stuck, what’s confusing, what’s helpful, what does and doesn’t advance your skill. In fact, if at some point the course just isn’t providing you any value, you are welcome to drop. That’s good feedback too.

    It’s going to be a blended format that includes self-paced work and some type of weekly online meeting. I will be guiding the class. At the very least, we’ll meet and chat at my site. I don’t know if we’ll do a live meeting or not. Still working that out.

    I struggled for many years, trying to figure this stuff out, then had a number of epiphanies during Orson Card’s boot camp and continued from there. Of course I still have lots to learn. But I want to share what I have.

    I love teaching and have been teaching in one form or another for the last 20 years. I’m currently an education program manager at a large software firm. What this is all means is that I’m trying to build a course that guides folks through a process that will help them learn to WRITE novels. Not just talk about them.

    So this is not a series of lectures with quizzes that test your ability to recall, although I will quiz you.

    It’s not a course with an end goal of teaching you what I’ve learned about the concepts and principles of plot, character, and setting, although you will need to learn that.

    This is about increasing your ability to get ideas, develop them, and then write.

    It’s about doing the work. It’s about production. It’s about finishing product. And having a good time doing it.

    If you already feel comfortable with your ability to finish novels, this is NOT the course for you.

    You can learn more about the course here by clicking The Path in the On Writing menu.

    Probably the only other thing you need to know is that the class is a PG-13’ish class. While the stories can deal with intense and adult themes, as the teacher, I’m not interested in working with stories with explicit or detailed sex or lots of language of the sort that would earn a movie rating more restrictive than PG-13.

    Remember, this is a pilot. Even though I’ve taught about writing for a number of years to various audiences, there might be some rough spots. We might find we need to change the work requirements or activities or any number of things.

    If you’re interested, click on the Contact link on the menu of my site, and shoot me an email.

    Edit 1/30/15: I’m getting a number of excellent questions about the time commitment and schedule. Let me answer them here.

    The gap I’m trying to fill

    First, you have to understand that I am not interested in talking about novels and writing novels. I’m interested in helping folks finish novels. That’s a big gap I see in most writing instruction. It’s the gap I had. There was nobody to help me move from the theory to the writing, and writing all the way to the end. So this isn’t a class about novels. It’s a class where I hope to help you learn a number of techniques for developing and finishing one. And to learn those techniques, you have to actually use them. Which means you have to develop and finish a novel 🙂

    So why 10 hours as a minimum?

    If you’re a slower writer, it’s going to take you around 50 hours to develop and write a novel of 25,000 words. That’s the size of one of Louis L’Amour’s smaller novels (which we call sometimes call “novellas” today). It’s the size of some smaller romances. A lot of indies are writing serials around this size. If you want to write a 50k book, it’s probably 100 hours, maybe more. A 75k novel? 150-200 hours. The development and first draft of a 100k novel? 200-300 hours.

    These are not exact times. Some writers are faster. But you get the picture. Writing a novel is a big project. And I’ve found that it’s just too hard to get any traction on less than 10 hours per week. When you spend much less time than that, you spend most of your time just trying to remember what the story is about. I’ve found it’s best to keep your writing engine hot, or at least warm.

    So will these 10 hours be in meetings?

    No. I don’t want to have a lot of meetings. That’s the beauty of online. We will have deadlines. But you should be able to complete you work during the times that suit you best.

    What’s the course schedule?

    I can’t give you an exact schedule. I haven’t timed everything. Figuring that out is part of what we’re doing in this course. But I do know what I want you to learn and how I hope to help you learn it. We’ll just have to see how far we get with each weekly 10-hour chunk.

    Share
  • Advice from one of the biggest writers of our time

    How would you like to sit down and get writing tips from someone who created or co-created nearly 40 television series? Someone who wrote more than 450 episodes for those and other series and then went on to produce around 1,500 more.  Oh, yeah, and then after his thirty or so years in television, he published 18 novels. Whoa–eighteen. Like I’m shaking, right?

    It’s not like the guy knows much about telling stories. I mean, millions of viewers entertained–big deal. Still, do you think you might be interested in seeing if he hasn’t maybe one piece of advice that’s useful?

    If so, the guy’s name is Stephen J. Cannell.  He wrote about 9,000 words on developing stories and called it his Writing Seminar. I thought it was pretty good. Well, for a piker.

    Share