Writing Fiction By Ignoring It

(This column is posted at www.StevenSavage.com and Steve’s Tumblr.  Find out more at my newsletter.)

Serdar and I are always discussing where our inspirations come from, and as we’re both Death Star-laser-focused on our current novels, that’s foremost in our minds. We’re fired up to know where our ideas come from, how to improve them, and of course understanding them so we can share them. Fortunately, we have a common conclusion.

The best way to write fiction is to read, watch, and listen to anything but fiction.

I’m aware you’ll probably want an explanation for this, so take my metaphorical hand and let’s wander into the weeds.

When you’re reading fiction you’re getting lessons in things like how to write. There are examples of portraying emotions, plotting a tight story, and so on. You may be inspired by some of the ideas, but inspiration from someone else’s fiction can only take you so far because those ideas come from that given author.

If you only take inspirations from fictional works that you are at best A) deconstructing them (worthy but at times limiting) or B) imitating them (which we have enough of, thanks).

So where are the best fictional inspirations? Simple.

Anything outside of the fiction you’re reading, and preferably radically different.

Seek ideas from other sources.  It can be music or video games, it could be the history of state parks or a cookbook.  Expand your horizons in any way but reading fiction.

Here’s where a lot of my ideas come from for fiction:

  • Richard Florida’s research into cities and megaregions. If you’ve ever noticed I like inventing big cities and complex social arrangements, this is where it comes from.
  • My work in psychology and psychobiology. Pay attention to my fiction and you’ll notice a major emphasis on social and political structures that may seem a wee bit organic if you will.
  • A fascination with maintenance of society and culture. How any human institution, culture, or nation survives and prospers is of great interest to me, and I have a “thing” for tales about “how some group of weirdos keeps it from going to hell.”
  • An interest in positive religious and philosophical experiences. This comes from my personal studies but also M.A.S.H. – Father Mulchahey was a huge inspiration, and he can be seen in my past and present work. There’s almost always one humane philosopher or cleric in my tales.
  • Buddhism and psychology. How people work interests me, of course, as does the impermanent nature of our minds and how we affect ourselves and others.
  • A love of culture and all the little things like where toys come from or the history of fonts.
  • Food. I love food and cooking, and you’ll always find it mentioned in my works because food tells you a lot about a setting, and exploring food in a setting helps you worldbuild.
  • A fascination with worldbuilding, of course. How you make a setting come to life has obsessed me for years.
  • Music. I often find songs that inspire me, in various styles, and those energize me. I know people who make whole playlists for their works.

So there’s a smattering of my (mostly) non-fictional and (sometimes) non-written inspirations. Now, a challenge for you.

What are your inspirations on written fiction that aren’t strictly fictional and/or aren’t always written? I want you to write them down, post them, and link back to me. Then go challenge your other friends to do the same.

Let’s learn from each other.

-Steven Savage

A Quick Note On My Brainstorm Book Posts

(This column is posted at www.StevenSavage.com and Steve’s Tumblr.  Find out more at my newsletter.)

My Brainstorm Book posts are done – for now – as of this post. I wanted to explain a bit about how they were part of a larger project.

Lately, I wondered about what I call “bookblogging.” Taking a subject, exploring it in blog posts, and using that as a way to draft out parts of a book. This way I get feedback, I get insight, I share things over time, and thus can ensure the ideas become a more effective book.

Also if it turns out my idea is awful or not suited, well, I learn that too!

My Agile Creativity was the first experiment to do this deliberately (Way With Worlds was a kind of afterthought), and as that book approaches launch, it seems to have worked out. The Brainstorm Book posts here, rewritten and expanded with what I’ve learned, will be another book in a month or two.

I’m not sure if this’ll work, if it’s a good idea, or what, but it’s going to be a fun experiment. I’ll probably be posting more thoughts on what I learned.

– Steve

The Brainstorm Book: Finishing Up And Following Up

(This column is posted at www.StevenSavage.com and Steve’s Tumblr.  Find out more at my newsletter.)

We’re talking how to solve your creative challenges with a Brainstorm book!  Last time I discussed how to record your ideas and track them.

Of course I assume you’re actually getting things done during this time by whatever method of productivity you choose. So let’s talk what to do to follow up once you get things done.

Signoff

Make sure you have a way to look at one of your projects and say “yeah, that’s done at least for now.” This way you can confidently say you’ve completed what you set out to do. This could be something as solid as a published book, or as ephemeral as a website update you know you’ll change tomorrow. Learn how to say “this is done.”

Defining “Done” means you can complete work. You can evaluate. You can deliver a product. You can relax. “Done” is vitally important to define – so do it as early as possible, including as early as possible when you’re maintaining your lists of all these ideas.

When you do decide something is “Done” have your Brainstorm Book handy – that “Done” will probably inspire other ideas.

Plus you get the peace of mind of something being over.

Retrospectives

It’s important to have a regular Retrospective – a review of how things have gone. I recommend two times to do them – in fact, I recommend both:

  1. First, do a retrospective after any big project completes.
  2. Second, do one after a period of work. For instance if you plan things out by month, then review every month.

On a Retrospective review the following:

  1. What went well?
  2. What did you have problems with?
  3. What work took more effort to do than expected and what work did you miss?

After this review, you should actually ask what concrete actions will you take in the future to make things run better. This could be doing things you did right more, it could be fixing things, it could be staying aware of issues.

Retrospectives help you understand how you brought ideas to life, and how work went from a scrawl in a Brainstorm Book to being real. They spawn new ideas and help you understand your creative process.

Plus each time, you get better.

Success List

Finally, keep an success list. Every month list out what you achieved that month to move your plans forward. That should include:

  • Any major achievements and successes in your plans.
  • Making distinct progress in one of your projects.
  • The completion of a project.
  • Anything you’re particularly proud of.

Reviewing your successess helps you see the results of your actions, appreciate them – and provides you reminders that you can get these things done. It builds habit of self-reinforcement.

All those ideas in your Brainstorm Book? This is when you see that you can make your dreams real.

You’re Not Done Until After You’re Done

Always remember that your brilliant ideas aren’t done when they finish. You want to take time to figure out how to end them, how to review them, and how to learn. That helps tie together all you did and all you learn and all you do at the end.

It’s important to have these kind of closing rituals to know you’ve ended things correctly. And of course, you’ll come up with new things to do or tweak my ideas – good.

Keep learning because even though things are done, creativity doesn’t end . . .

– Steve