<div class="bbWrapper">Prepare yourself for a wall of text; you were warned!<br />
<br />
First, though, a link to a free resource with some useful information about writing technique: <a href="http://bubblecow.net/writing/" target="_blank" class="link link--external" rel="noopener">http://bubblecow.net/writing/</a> Thanks to @<a href="https://www.thefastlaneforum.com/community/members/20530/" class="username" data-xf-init="member-tooltip" data-user-id="20530" data-username="GiroudJD">GiroudJD</a> for posting the link that led me to it.<br />
<br />
<b>Now for the update.</b> My recent decision to test Dragon Naturally Speaking to ward off nerve damage to my hands has forced me to consider the best way to maintain or even improve production rate, as I have found narrating the story aloud quite awkward and slower than typing at first. I was aided by a tip from a mentor to make a scene outline or checklist before starting to dictate. <br />
<br />
I've been asked many times to explain my ability to write up to 10k words per day (not average, as some have said--UP TO). Part of the secret is my willingness to sit at the computer for <i>up to</i> ten hours a day just writing (though it's usually more like eight--that's still a lot of hours at the computer), and part is the mechanics of the planning process I use before I ever start writing the story.<br />
<br />
So I'm going to lay out the process here, again, to include the new step required for my best use of DNS, in the hope that it will help someone who's just getting started. <br />
<br />
This is not to say this is the only way to achieve this production rate, nor even the best. It's simply the way I do it, and furthermore, it's done strictly for commercial advantage; no art here, folks. <br />
<br />
Fair warning: I'm a plotter, not a pantser. I could no more sit down to write a story without semi-detailed planning than fly. If you believe that you produce a better story without planning, stop right here. You probably do, and what follows will likely mess you up, or at least make you go cross-eyed for a few minutes. <img src="/community/imgs/emoticons/em-wink.png" class="smilie" loading="lazy" alt=";)" title="Wink ;)" data-shortname=";)" /><br />
<br />
<b>My process:</b><br />
<br />
<b>Step 1:</b> Determine genre (see @<a href="https://www.thefastlaneforum.com/community/members/15462/" class="username" data-xf-init="member-tooltip" data-user-id="15462" data-username="Held for Ransom">Held for Ransom</a>'s <a href="https://www.thefastlaneforum.com/community/threads/hello-from-denver-self-publishing-success.46006/" class="link link--internal">Hello from Denver - self publishing success</a>) and brainstorm a concept to fit. Write a 1-2 page concept document that captures the idea. You can add to the concept document as the story 'cooks', or not. Your choice.<br />
<br />
<b>Step 2:</b> Select an appropriate beatsheet and determine target length of the story so you'll pace it correctly. By appropriate, I mean there are several out there that have different purposes, and one might be better for your chosen genre than another. <br />
<br />
I started out using Blake Snyder's <i>Save the Cat</i> beatsheet, struggling to understand what the descriptions meant, what each section of the story should contain, etc. It's worth studying, and will begin to make more and more sense as you write and read with it in mind. However, there are a number of others listed here: <a href="http://www.savethecat.com/beat-sheets-alpha/" target="_blank" class="link link--external" rel="noopener">http://www.savethecat.com/beat-sheets-alpha/</a>. <br />
<br />
Most recently, as I write in romance genres, I've been using Jami Gold's version, found here: <a href="http://jamigold.com/2012/11/write-romance-get-your-beat-sheet-here/" target="_blank" class="link link--external" rel="noopener">http://jamigold.com/2012/11/write-romance-get-your-beat-sheet-here/</a>. I apologize to the forum members who first brought these to my attention, as I can't remember now who it was. That's a testament to the many writers who are contributing here, not to mention my poor memory.<br />
<br />
<b>Step 3:</b> This is where I depart from other methodologies. After reading about the Snowflake Method and deciding it was overkill for what I was writing, I developed a second spreadsheet as a companion to the beat sheet. Some of you will consider it impossibly nerdy and way too much trouble, but if you have a good understanding of your spreadsheet application, it's actually quite simple, and IMHO, more useful and less trouble than the snowflake. <br />
<br />
Before I get into it, let me address outlining. As a student, I took notes in formal outline form. For decades, I thought I was quite comfortable with it. Then I was introduced to the mind map. If you aren't familiar with it, here's a wiki: <a href="http://en.wikipedia.org/wiki/Mind_map" target="_blank" class="link link--external" rel="noopener">http://en.wikipedia.org/wiki/Mind_map</a>. I've never considered myself particularly creative, but if I were, this would certainly be superior to the old, rigid, outline form. For those of you who may want a looser planning process than I'm describing here, this may be just the tool you're looking for. Just Google 'mind map' if you'd like software to help.<br />
<br />
<i>Back to my process.</i> My spreadsheet template contains a generic number of rows for scenes in each beat, and total rows that link to the appropriate beat sheet field for a target in a different column. What this spreadsheet does is allow me to briefly describe the purpose of each scene, and as I write them, put the word count in so that as I write I understand how much I have to fill in with to pace the story correctly. I also have columns that show me exactly how many words to go for the beat target, total word count for the manuscript and words to go for the book target.<br />
<br />
Put a different way, it shows me where my plot is thin and new elements must be introduced. The reason for linking the spreadsheets is to automatically update word count per beat if I see that the story is going to take more or less than originally planned; all I have to do is update the word count in the appropriate field of the beat sheet, and it will be calculated and propagated through to the scene map, where I may need to write more or more likely cut to maintain the pacing.<br />
<br />
<b>Step 4:</b> This is the new step necessitated by DNS. Each scene now needs a list of points to be made. As I use Scrivener as my writing environment, I'll use the notecard view of the scenes with bullets for this part, and then simply erase each point as I make it while I build the scene, before transferring the contents of the DNS dictation box into the Scrivener scene.<br />
<br />
<b>Step 5:</b> Begin composing. Even now, after only a few days of dictation and with fits and starts as I speak, I'm approaching the 1000 wph that I expect of myself as a minimum when typing. I'm hoping to triple that with the addition of Step 4. Trust me, you can think much faster than you can type, and if you can train yourself to speak your thoughts out loud, DNS (after suitable training to recognize your speech characteristics) should increase production, though it may require heavier editing afterward. <br />
<br />
@<a href="https://www.thefastlaneforum.com/community/members/15462/" class="username" data-xf-init="member-tooltip" data-user-id="15462" data-username="Held for Ransom">Held for Ransom</a>, I'd welcome you to weigh in on this point, as I'm aware you eventually decided against DNS after plenty of use to test it. If you could elaborate on what you found uncomfortable about it, it may be very helpful to someone. I believe your writing process is quite different from mine, which may make a difference--I guess we'll see as I go along.<br />
<br />
<b>Other points:</b> You will notice that I didn't mention locale descriptions, character charts, etc. Do I use them? Yes and no. I expect to do more of that as I gain more experience, and it will become part of Step 1. Up to now, I've named and described characters and locales as I needed them, but I can see the value in understanding my characters' backstory and environment before I start. I use Scrivener, which makes this very easy to do, as well as making it easy to move scenes or chapters around as required. <br />
<br />
That's it...although I'm sure some will require more detailed explanations here or there. Feel free to ask. None of this is trade secrets, so if I can ease your journey, I'm happy to do it.</div>
