Anatomy of a Novel Part 9: Troubleshooting

It’s taken four months, but I’ve finally finished the first read-through of The Iron Line and I’m starting to overhaul it. I naively thought the second book would be easier than the first – because I know what I’m doing now, right? Wrong.

The first draft of Greythorne took three months to write and I let it percolate for only three weeks before I launched into editing and rewriting. The first draft of The Iron Line took a similar amount of time – four months, although it’s also longer than Greythorne – and I finished it in September last year…and haven’t touched it since. To be fair, I also completed a non-fiction book in the middle there and had a few other projects on the go as well, but this one needed a bit more time to stew. The first draft read like a bad episode of Midsomer Murders, and I couldn’t really see a way out.

troubleshooting-your-novel-cover

Then, while I was in Sydney over Christmas, I picked up Steven James’s excellent book, Troubleshooting Your Novel, which was exactly what I needed to get me out of the writing funk I’ve been in. The book is broken into bite-sized chapters that each deal with a different technical aspect of writing, such as causality, escalation, believability, subtext and many more (there are 80 in total!), and James gives great advice on how to identify problems in your manuscript and – even better – how to fix them.

One of the tactics he recommends when looking at causality is to make a list of events (he says in a particular scene, but I did it for the whole book) and how they lead into each other – essentially showing cause and effect. This was a revelation for me and led to a complete overhauling of the plot. When I mapped out the sequence of events it was easy to see that I had the main plot and the subplot mixed up, and the whole thing feels much more coherent now. There are still plenty of things wrong with the story, but I think this problem was the main one. I find I get a gut feeling when a story is working (or isn’t), and with the new outline it feels like the pieces have fallen into place. The same thing happened with Greythorne – everything was slightly out of whack until one of my beta readers suggested a change to the ending, which then fixed a whole bunch of other problems as well.

People tend to think that fiction-writing is primarily a creative or right-brained pursuit, and in the first draft it is. But once that first draft’s done it becomes highly analytical – it’s all about problem-solving, technique and craft. This was the thing it took me many years to learn – that to be a successful writer (‘successful’ by my definition meaning you actually finish things and people read them and don’t think they’re terrible) you have to be able to meld the creative and the analytical. It’s not enough to just have great ideas – you need to have a strong enough understanding of technique to be able to execute them properly. In that sense, it’s like any other art form (no one would suggest you can become a concert pianist without doing lots and lots of scales), but I think most readers – and many beginning writers – don’t understand just how important the craft side is. I don’t think it’s a coincidence that I became a much better creative writer around the same time that my analytical skills were kicked up a gear by doing a PhD in an unrelated field.

Anyhow, after several months of feeling rather ‘bleugh’ about the novel, I feel like I’ve now got my mojo back and I’m ready to tackle the next draft. In the meantime, my new non-fiction book, Communications for Volunteers, will be out in early March. I’ll keep you posted.

Published by Louise Merrington

Louise Merrington is a writer and IPEd Accredited Editor specialising in plain English editing for government, businesses, professional associations and non-profits. She is also the author of several novels, under the name L.M. Merrington.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d