The Secret to Getting Great Story Ideas

The Secret To Getting Great Story Ideas Passion GuyLast week I spent a lovely day with the League of Utah Writers at their annual writing conference. I presented “The Secret to Getting Great Story Ideas” which was about how to stop generating great story ideas by accident and start generating them on purpose, whenever you need them. I promised the folks I’d post my PowerPoint and notes. You’ll find them below.

The Secret To Getting Great Story Ideas 2015 LUW – Presenter Notes

The Secret To Getting Story Ideas 2015 LUW – Slides

For those wanting more details, you’ll find the same idea in my series on getting ideas. Here’s the first post: “Can You Create a Redneck Crapper”.

Share

Similar Posts

  • 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
  • When the workshop works

    From a workshop participant at MountainCon:

    I’m going to give a shout out to all the goodness I experienced. So if you don’t really care what happened at the con, you can stop after this paragraph and take this message away with you: Brandon Sanderson (who does Writing Excuses, has published several novels, and is the chosen one to finish Jordan’s Wheel of Time series) and John Brown (with a must buy novel coming up next year) are incredible teachers. If you ever get a chance to attend a class or workshop by any of them, don’t let it pass.

    We loves to hear these things, Precious.

    But we loves it just as much when we can make the students shiver with excitement: more here: http://www.amichopine.com/blog/?p=318

    To those who missed this run of the 3 Things You Must Learn to Write Killer Stories Workshop, know I’ll be holding it again. Check back to see when.

    Share
  • My working process

    Because I get questions about how I work, whether I outline, etc., and to satisfy the curiosity of those waiting for Curse about what I’m doing right now, I’ve decided to share my working process.

    I use five types of documents in Word to write my books.

    1. Pre-draft documents
    2. Working outline
    3. Chapter development docs
    4. Manuscript drafts
    5. Book

    I then import the book into InDesign to create the ebook and POD versions.

    THE PROCESS

    1. PRE-DRAFT

    I start developing and collecting ideas for character, setting, problem, plot, and sometimes even text. This includes brainstorms, zings, setting sketches, character sketches, scene or dialog snippets, plot sketches, photos, maps, story setup statements or problem statements, etc.  I’ll often have separate pre-draft documents for character, setting, problem, and plot. Or it might be one big document. At some point all of that electricity has built to the point where the story starts to buck and kick in my hands. When I start to see scenes rolling out in front of me, I know it’s time to create the outline.

    2. WORKING OUTLINE

    Looking at my pre-draft material, I create a sequenced list of the events or scenes in the story. Sometimes I’ll describe an event with just one line, sometimes I’ll describe it with more. These events or scenes often match up to individual chapters, but they often change as I go because the outline changes as I work. This outline is usually 4-12 pages long.

    I usually have more detail about the first parts of the book when I start than I do the last parts. But even if some parts are sketchy, I usually have at least a line for each of the big events all the way to the end. When I start drafting (steps 3 and 4) and moving through the book, the details for those later parts begin to fill in. Again, it’s a “working” outline so things change.

    3. CHAPTER DEV DOCS

    When I finish the working outline to my satisfaction and start chomping at the bit to write, it’s time to start drafting. I open a new chapter development doc for the first event on the outline and copy/paste the event’s material from the outline into it.

    I do some sketching if necessary (see my posts on scene primers) in the new document. Then I begin to write with the outline material and scene sketch as a guide.

    If I run out of steam, or the take of the scene doesn’t work, I do another take. I just stop, create a new heading titled “Take 2” or 3 or 4 (whatever the take is), and start again. I may brainstorm as well in this document and do other pre-draft work that has finally presented itself to me to be done. There have been a couple of times that I’ve had to do 20+ takes to get a take that works. Most of the time I need 1-3 takes. Using Word navigation view I can see in the sidebar all the takes etc.

    The nice thing about these chapter development documents is that they’re working documents. I can be messy.

    4. MANUSCRIPT

    When I’ve gotten a good take of the scene, I paste that take into my manuscript document which contains all the final takes from the chapter development documents. This is “draft 1” of the manuscript. Usually each scene/event becomes a chapter, although I might split it if it goes long, or combine it with others if it’s short.

    5. REPEAT UNTIL DONE

    I repeat steps 3 and 4 until I’m done with the book. Using Word navigation I can see all the chapters in the sidebar.

    6. CHAPTER REVIEW

    Before I print the manuscript for the cold read, I will review the chapter breaks one more time based on what I feel is right for the length, the right effect, especially at the ending and beginning of the chapter, and what I think goes together.

    7. DRAFT VERSIONS

    After cold reading and marking up the printed form of draft 1, I copy the manuscript file and replace the suffix “draft 1” with “draft 2”, then make the edits for the cold read in draft 2.

    Then I send draft 2 out to my beta readers. When the manuscripts and comments come back, I copy draft 2 and change the suffix to “draft 3” and make the beta reader edits in draft 3.

    I do this for as many drafts as I go through, including those for the copy edits.

    8. BOOK

    When I’m done with drafting, I copy the final draft and replace the draft suffix with “book”. Then I add front matter and back matter (title page, copyright page, teaser, map, author’s note, table of contents, etc.) in preparation for importing into InDesign to create the ebook and POD (print-on-demand) versions.

    9. POD

    I create an InDesign document, import the Word book, then save it with the suffix “POD”. Next I finalize the interior formatting for printing. There’s quite a bit that goes into this with chapter breaks, widows, and orphans, breaks, etc. When that’s done, I upload it to CreateSpace and then print off the proof they provide.  By now the cover is finished as well.

    10. PROOF READ

    I read the POD proof to catch any last errors and make the appropriate updates to both the Word book and the InDesign POD document.

    11. EBOOK

    I copy the POD InDesign document and replace “POD” with “EBOOK”. I then add the appropriate changes (links etc.) to the front and back matter for the ebook. Next I export the InDesign document as an EPUB. I have to use Calibre Book Editor to edit a number of things in the EPUB. When that’s done I open the EPUB with the Kindle Previewer to create the MOBI version (Kindle file).

    12. PUBLISH

    The next step is the easiest–click a few buttons to upload the final version of the POD and ebooks to the various online retail venues. I go direct with Amazon, CreateSpace, NookPress, and Kobo. I use Draft2Digital for iTunes and Smashwords for all the rest. 

    Share
  • What Robinson Wells Learned Last Year

    Look, this is just an excellent post by Robinson Wells: Five Things I’ve Learned In The Last Year About Writing.

    I kept finding myself saying yes, yes, yes!

    Yes! I hate “networking” too. Icky, icky, icky. Like squishy underwear. Like buddying up to someone to get them into your network marketing downline. Like flies in soup. I love how Robinson replaces that with the real deal. I think I’m going to summarize him every time anyone asks me about networking. 

    One point. I do think he might be overstating the you-need-to-know someone deal. It’s easier, sure. But Larry Correia didn’t know anybody. He just wrote a book a lot of people in a certain demographic loved. I didn’t know my agent from Adam. Didn’t know my editor, but did have an endorsement from one of his authors. But that didn’t get me any deal. It probably got me, at most, a fair consideration. I can name others who didn’t know a soul. In fact, go to the facts and figures page in the On Writing section. Look at the author polls there. A lot of authors didn’t know a soul. Of course, knowing someone can help.

    Yes! Be cheerfully flexible. Oh, my gosh. This is such a good approach. And I’m living it right now, although there have been a few moments when I’ve had to regroup for a moment to capture the cheerful.

    Yes! Sometimes the thing you love doesn’t work for the project. Sometimes it does. I would advocate making sure you get to the root of the issue. But we’re artists. If the thing we don’t love doesn’t work, we can create a new thing to love. That’s what it means to be creative.

    Work! Yes! It’s amazing what happens when you work.

    Good stuff.  

    I’m so bullish on this, I say Robinson for President.

    Of what, I don’t know. But he should be President, of something.

    Share