I worked at a semiconductor manufacturing plant for about two years as a manufacturing engineer. For the first 18 months or so, we were in the process of installing new tools and bringing them online while simultaneously ramping up production. The executives liked to compare what we were doing to building an airplane while in flight (per this EDS ad below).
I'm not sure that's the most confidence-inspiring way to describe your process as a company, but I see parallels to it in my revision process. Plus, the video's just funny.
I've been working almost exclusively on Diego's story for the last few weeks, and ignoring Slow Burn altogether. My thought was that giving the book a rest before looking at it again would give me a fresh perspective and renewed energy. It did, but I was in danger of never getting into the global revisions.
More than the line edit stuff–which would be a waste of time for scenes I may change/delete anyway–I need to focus on the plot changes that I came up with after a helpful critique and a brainstorming session with my CP. I believe the book will be better off with my altered story line, but coming up with the energy to tackle it is sometimes difficult.
The task can seem daunting. Yes, I've rewritten the first five scenes of my current MS three times, but that was starting almost from scratch each time. With the old MS, I'm cutting, splicing, and patching all over the place. I think I may copy the Scrivener file and start in a new version so I don't have to worry about taking snapshots or making duplicates of every scene that might change.
I'm a bit overwhelmed, but excited to get the book into shape in time to pitch it at the RWA National conference in Nashville in July. My goal is to finish the revisions and another pass at basic edits before I move in June. Revising is cutting into my word count goals, but if I can be organized enough to divide my time between both stories, maybe it'll keep me from burning out.
Either that or I'll spontaneously combust.
[tweetmeme source=”yourtwittername” only_single=false]