<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Building Stories &#38; Birthing Books</title>
	<link>http://www.sfnovelists.com/2007/09/20/building-stories-birthing-books/</link>
	<description>A mutual support group for SF/F Novelists</description>
	<pubDate>Fri, 25 Jul 2008 01:51:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.1</generator>

	<item>
		<title>By: Jackie Kessler</title>
		<link>http://www.sfnovelists.com/2007/09/20/building-stories-birthing-books/#comment-487</link>
		<author>Jackie Kessler</author>
		<pubDate>Sat, 22 Sep 2007 23:28:57 +0000</pubDate>
		<guid>http://www.sfnovelists.com/2007/09/20/building-stories-birthing-books/#comment-487</guid>
		<description>Like Simon, I have to hand in an outline before I hand in the manuscript. But when it comes to actual brainstorming the plot...I dunno. I visualize it, write it down, see if it's crap, delete what doesn't work, flesh out what does. Make sure to connect the dots. Then I give it to my crit partner to see if it holds water.

(Man, that was helpful, wasn't it?)

"Hence the ‘uncorrected’ on the cover!"

Oh YEAH. Totally!</description>
		<content:encoded><![CDATA[<p>Like Simon, I have to hand in an outline before I hand in the manuscript. But when it comes to actual brainstorming the plot&#8230;I dunno. I visualize it, write it down, see if it&#8217;s crap, delete what doesn&#8217;t work, flesh out what does. Make sure to connect the dots. Then I give it to my crit partner to see if it holds water.</p>
<p>(Man, that was helpful, wasn&#8217;t it?)</p>
<p>&#8220;Hence the ‘uncorrected’ on the cover!&#8221;</p>
<p>Oh YEAH. Totally!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Haynes</title>
		<link>http://www.sfnovelists.com/2007/09/20/building-stories-birthing-books/#comment-474</link>
		<author>Simon Haynes</author>
		<pubDate>Fri, 21 Sep 2007 01:02:47 +0000</pubDate>
		<guid>http://www.sfnovelists.com/2007/09/20/building-stories-birthing-books/#comment-474</guid>
		<description>My editor likes to see a short outline before I embark on my latest, so I can't just hit the WP and start writing.

I find the following works for me:

1. Use Freemind (freeware mind mapping type prog) to grow the plot &#38; characters. The great thing about this program is the way you can add nodes &#38; hang others off them. Back in June I posted &lt;a href="http://halspacejock.blogspot.com/2007/06/entire-hal-4-outline-right-here.html" rel="nofollow"&gt;a composite image&lt;/a&gt;&lt;a&gt; which shows the entire outline in something like 1pt font. Looking at that, you can see how I start with a few nodes and get more and more detail in there. Freemind allows you to drag and drop whole branches, which makes it easy to try different arrangements.

2. Next I export the tree to a file and distill it down to the essentials. This is what I send my editor, along with character sketches. She'll read it and comment, I'll fiddle with it and eventually we'll both agree the plot is workable.

3. Now I split the outline into chapters and scenes, using yWriter. I avoid making changes if possible, at least until I've done.

4. From here it's just a case of picking an interesting-sounding scene and writing it, two or three a day. I work in order, beginning to end, but I'll skip scenes I don't feel like writing.

5. During the writing I'll hit dead-ends, characters will refuse to cooperate and certain plot choices will prove to be unworkable. I stay flexible, and allow myself to alter the plot as I go. If there's anything major I'll ring my editor (perhaps twice per book) to explain why things are Going to be Different.

6. When I finish the last chapter it's time to start at the beginning again, writing (or cutting) the scenes I didn't want to do in the first place. I also have a better idea of the ending, which means I can insert a bit of foreshadowing.

7. At this stage I still haven't printed anything, and my goal is just to get a draft where I can read from beginning to end with no little comments and to-dos in the text.

8. When that's done I print the draft and hide away somewhere quiet with a red pen. I go crazy at this stage, with arrows, instructions to 'move this chunk to A', 'insert tab B in chapter C' and so on. Sometimes I get 2/3 the way through and realise I've made so many changes there's no point reading the rest - that can wait for the next draft.

9. I sit down and apply all the changes to the yWriter project, page by page.

10. I repeat 8 and 9 two more times. During the final draft I'm still making changes to &lt;/a&gt;&lt;a href="http://halspacejock.blogspot.com/2007/08/hal-4-is-winched-onto-slab.html" rel="nofollow"&gt;this  degree&lt;/a&gt;.

11. I send the manuscript to my editor as a doc file. Two weeks later she sends it back heavily marked up AND with a separate doc full of comments, and I'm back to stage 8 for two or three more loops.

12. I submit the final and she'll read it again, quicker. This time I get it back as a doc file with comments attached. Back and forth we go for the next couple of weeks, until we're both happy, and then it's submitted for proofing.

With my latest book (4th novel) steps 1-11 have lasted from April-September. The final draft needs to be handed in mid-late October, so we're getting there. The last date for cover blurbs is 1st November though, so we really need to post out ARCs by the end of September. Hence the 'uncorrected' on the cover!</description>
		<content:encoded><![CDATA[<p>My editor likes to see a short outline before I embark on my latest, so I can&#8217;t just hit the WP and start writing.</p>
<p>I find the following works for me:</p>
<p>1. Use Freemind (freeware mind mapping type prog) to grow the plot &amp; characters. The great thing about this program is the way you can add nodes &amp; hang others off them. Back in June I posted <a href="http://halspacejock.blogspot.com/2007/06/entire-hal-4-outline-right-here.html" rel="nofollow">a composite image</a><a> which shows the entire outline in something like 1pt font. Looking at that, you can see how I start with a few nodes and get more and more detail in there. Freemind allows you to drag and drop whole branches, which makes it easy to try different arrangements.</p>
<p>2. Next I export the tree to a file and distill it down to the essentials. This is what I send my editor, along with character sketches. She&#8217;ll read it and comment, I&#8217;ll fiddle with it and eventually we&#8217;ll both agree the plot is workable.</p>
<p>3. Now I split the outline into chapters and scenes, using yWriter. I avoid making changes if possible, at least until I&#8217;ve done.</p>
<p>4. From here it&#8217;s just a case of picking an interesting-sounding scene and writing it, two or three a day. I work in order, beginning to end, but I&#8217;ll skip scenes I don&#8217;t feel like writing.</p>
<p>5. During the writing I&#8217;ll hit dead-ends, characters will refuse to cooperate and certain plot choices will prove to be unworkable. I stay flexible, and allow myself to alter the plot as I go. If there&#8217;s anything major I&#8217;ll ring my editor (perhaps twice per book) to explain why things are Going to be Different.</p>
<p>6. When I finish the last chapter it&#8217;s time to start at the beginning again, writing (or cutting) the scenes I didn&#8217;t want to do in the first place. I also have a better idea of the ending, which means I can insert a bit of foreshadowing.</p>
<p>7. At this stage I still haven&#8217;t printed anything, and my goal is just to get a draft where I can read from beginning to end with no little comments and to-dos in the text.</p>
<p>8. When that&#8217;s done I print the draft and hide away somewhere quiet with a red pen. I go crazy at this stage, with arrows, instructions to &#8216;move this chunk to A&#8217;, &#8216;insert tab B in chapter C&#8217; and so on. Sometimes I get 2/3 the way through and realise I&#8217;ve made so many changes there&#8217;s no point reading the rest - that can wait for the next draft.</p>
<p>9. I sit down and apply all the changes to the yWriter project, page by page.</p>
<p>10. I repeat 8 and 9 two more times. During the final draft I&#8217;m still making changes to </a><a href="http://halspacejock.blogspot.com/2007/08/hal-4-is-winched-onto-slab.html" rel="nofollow">this  degree</a>.</p>
<p>11. I send the manuscript to my editor as a doc file. Two weeks later she sends it back heavily marked up AND with a separate doc full of comments, and I&#8217;m back to stage 8 for two or three more loops.</p>
<p>12. I submit the final and she&#8217;ll read it again, quicker. This time I get it back as a doc file with comments attached. Back and forth we go for the next couple of weeks, until we&#8217;re both happy, and then it&#8217;s submitted for proofing.</p>
<p>With my latest book (4th novel) steps 1-11 have lasted from April-September. The final draft needs to be handed in mid-late October, so we&#8217;re getting there. The last date for cover blurbs is 1st November though, so we really need to post out ARCs by the end of September. Hence the &#8216;uncorrected&#8217; on the cover!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
