A Writer’s Life: Taking Notes And Improving Writing

(This column is posted at www.StevenSavage.com and Steve’s Tumblr)

As I write “A Bridge To The Quiet Planet,” I’ve started taking notes on my writing techniques.

Getting back into this was a bit tougher than I thought, so it took me awhile to get going.  Fortunately I kind of got a writing system going again – only, as I used it, I had other insights.

So I figured, why not write them down for later?

This is something I hadn’t thought of before, but as I do so I find the act of reviewing these findings, these new techniques, and recording them helps my writing even more.  I’m activley thinking about how to get better.

This is really classic Agile practice; you don’t just do things.  You review them in order to improve.  I strongly recommend every writer keep a list of “technique notes” and gradually review them.  If possible, actually write up your techniques, maybe review them every work, to help build a system in your head.

This may sound a bit excessive, but so far?  It’s helped me a lot.

Besides, it gives you something to share with other writers . . .

(Remember I do all sorts of books on creativity to help you out!)

– Steve

My Agile Life: Review Lets You Get It Right; Review Lets You Let Go Of Perfection

(This column is posted at www.StevenSavage.com, Steve’s LinkedIn, and Steve’s Tumblr)

More on my use of “Agile” and Scrum in my life!

Perfection is the nemesis of success. The Perfect isn’t just the enemy of the good – sometimes the good is the enemy of ever accomplishing anything. Trying to get everything right can kill you, and sometimes even trying to get it really good is a barrier.

Sometimes you just have to complete something, review it, and improve it or do it again. Reviews are what let you get things done right – not trying to be perfect (which is not the same as being competent).

I learned this in my Agile Life efforts in, of all things – cleaning.

Cleaning is a regular effort – Business As Usual if you want to use bizspeak. It’s also something that may not always go perfect, from a difficult stain to not having a box to throw junk in. It’s also hard to get right as there’s always something else to do if you want to get obsessive.

So I had to do some cleaning and encountered a difficult issue in, of all things, the shower – nasty little stain. I didn’t have the proper cleaner, it seemed ridiculous to run out and buy it for five minutes work, and . . . I let it go. I’d get the stain cleaner at my next grocery run and get it next week.

By accepting yes, this stain wasn’t going to be a disaster, I avoided a half hour of running around for five minutes work I did the next week. Plus I learned to keep certain cleaning supplies on hand.

An agile way to do things – learn and improve and don’t sweat every detail. Delivering, review, and processing what you learn means you get better and waste less time.

Now cleaning is kind of a ridiculous example, but consider other places this applies:

  • If you’re writing something there’s only so right it’s going to be. That’s what editors, pre-readers, and just regular improvement will bring.
  • If you’re decorating the apartment do not think you’ll get it right the first time. Do your best and review it.
  • If you’re working on a web page and a photographer is late maybe you can make due with current photos – or what they sent you.

Finally, I’d note that if you’re doing something regularly – updating a website, cooking, etc. this is a REALLY good place to learn to let it go. Things that might not be perfect can get a bit more perfected next run.

I’d refer to the 10th Agile principle here: “Simplicity–the art of maximizing the amount of work not done–is essential.”

(By the way I do plenty of books for coaching people to improve in various areas, which may also help you out!)

– Steve

A Writer’s View: Flowing Back And Forth

(This column is posted at www.StevenSavage.com and Steve’s Tumblr)

As I write “A Bridge To The Quiet Planet” I keep discovering more about it.  Perhaps I find a theme that I missed or that should be incorporated into the story.  Or I may realize I missed something and that I have rewriting to do. Or something just works better.

For awhile this was irritating, and sometimes I got jammed up around what I called “Big Rocks.” But the more I thought about it, this is normal and in fact, quite healthy.

Writing is really a method of discovery.  So you have to write in order to know what you’re writing.  In turn, you constantly find out more.

This is a lot like software – another insanely complex activity that involves people and information coming together.  As you code and develop you get more feedback and find more problems and get more insights.  This lets you improve the code – removing technical debt, adding new features, etc.

It took me awhile to get into this, but over time I began relaxing about it.  I saw it as a flow of information, the story constantly adjusting and adapting to my insights – again, just like software.

What I do is this:

  • First of all I keep a separate Brainstorm book on my story.  Every few days I review it and put the contents into my world guide, in a list on my story outline, or my other notes.
  • When writing I may get additional ideas and track them the same as my Brainstorm Book entries. or just go and revise some things right there.
  • I go through the list on my story outline every now and then and incorporate it into A) the existing story, B) the rest of the outline.  I make sure to go through each item and completely integrate it.

This gets easier and easier over time, and at about halfway through the book It’s gotten almost natural.  Almost – I still get a bit of annoyance when I revise things, but old habits, you know?

The quality is also much improved.  Each change seems to not only improve the book, but somehow make it more pure, more clear, more refined.  I expected it to become more complicated, but instead it’s more complex, richer, which somehow makes it more understandable.   The book, in its current state, is headed for something notably better than what I had when I started (in my opinion).

What’s really going to be interesting is how this applies to other stories.  If I’m able to edit better when writing, improving plot and characters, how much better will I be next book I outline?  I look forward to seeing what happens in the next book or other fiction pieces.

Of course I have to finish this one . . .

(Remember I do all sorts of books on creativity to help you out!)

– Steve