Steve’s Update 6/19/2017

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

It’s my weekly Scrum style standup for the audience.  Here’s what’s up – but first a note.

The last two months have been pretty intense, its all been books and writing for the most part.  I may be changing some of my plans around so it’s a bit more diverse.

So what have I done the last week?

  • Way With Worlds Minibook #1: All formatted and ready to go!  Pretty much I can launch it any time.
  • Way With Worlds Minibook #6: Writing away.  I’m going to try and block out time to just finish it, but not making any plans.
  • “A Bridge To The Quiet Planet:” The plot is outlined!  In fact the “draft” was better than I thought!
  • Social: I spoke at Hydra-Con, made lots of new contacts, and had a great time.  Promising new con!

What am I going to do this week:

  • Way With Worlds Minibook #1: Setting up marketing and getting publishing queued up!  You should see it later next week.
  • Way With Worlds Minibook #6:  Writing more of it.
  • “A Bridge To The Quiet Planet:” Working on Chapter #1.  I might try to blitz it this weekend, but the goal is a readable draft end of month.
  • Writing: The usual blogging, plus a few other things I want to write.

Challenges:

  • Some friends are moving, which might require some of my time.

– Steve

A Writer’s View: Timey-Wimey

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

Plotting stories, and indeed writing them, is a process of discovery.  A discovery at the end of your tale changes what you think of the beginning.  Closing a scene helps you find a theme that alters the scene.  A character you thought you new surprises you.

Writing, in the words of a certain madman with a blue box is Timey-Wimey.  You finds things out about your world out of order.

We’re frustrated with this because our work feels unreliable, unpredictable, almost as if it’ll betray us.  Ever encounter someone who treated their stories and characters with suspicion?  Yeah, you probably have – it may have been you.

I’ve found that we have to accept this.  Simply put, writing encompasses such breadth of possibilities there’s always a bit of unpredictability, of discovery.  If it’s too predictable, it’s not a creative act.

What we can do is embrace this timey-wimey, acknowledge it, minimize the negative effects, and maximize the positive.

First, be open to the timey-wimey.  Accept that things change, that you’ll have these amazing insights, and that the act of plotting and writing reveals new depths.  This back-and-forth  of do-find-redo makes your work alive.

Secondly, learn to use these insights.  Figure the best way to find them, embrace them, and apply them.  Maybe you keep timelines, maybe you iteratively improve things.  Maybe you have to accept some rewriting.  Maybe you keep extensive notes.  Find a way to make the timey-wimey issues a tool.

Third, don’t fight it.  This is just part of the creative process.  You may have great onslaughts of ideas, or have to accept you can’t tweak a story anymore.  Run with it and make good work first, don’t get lost in frustration or fiddly bits.

Fourth, accept imperfection.  At some point it’ll be good enough to be as good as it needs to be.  Don’t run with the timey-wimey aspects of work so long you’re revising forever.

I’ve found a huge key to using the timey-wimey creativity, and writing in particular is:

  • To improve iteratively.  Engage in gradual review of your work.
  • Gradually deepen your work.  Start with simple ideas and improve them over time, going deeper, adding detail.
  • Every time you go a bit deeper into your work, review the big picture a bit more.
  • Work out a system to do these reviews and do them regularly.
  • Practice!

A lot of this is like Agile practices – which I’ve also been working with.  Agile is about iterative improvements, and is a good mindset for a writer.

– Steve

My Agile Life: Only Me

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

(My continuing “Agile Life” column, where I use Scrum for a more balanced and productive life continues).

The Blame Game is the bane of good organization, good companies, good productivity, and happiness. Yet, how many times do we blame others for problems automatically? How many times have we been blamed for problems automatically?  How many great projects have failed because people fling blame at each other?

OK we know the answer; a lot.

When I began doing my Agile Life, I had a most interesting experience; I had only myself to blame for anything.  I was the only responsible one when most anything went wrong.

Something was late? My fault. Something not done well? My fault. Very, very few cases of things that wreren’t due to me. To blame anyone else would have required a Herculean effort of self-delusion that I just don’t have the energy or lack of morals for.

This was awesome.

Because I am the major or only cause of failure, I am aware of why things go wrong.

Because I am the major or only cause of failure, I know what to improve.

Because I am the major or only cause of failure, I must acknowledge my flaws.

Because I am the major or only cause of failure, I am the major source of success.

Agile is about a mixture of heavy personal responsibility and team responsibility teaches you a lot about dealing with failure.  This personal Agile experience is an excellent compliment to group Agile because it teaches you that responsibility very, very fast.

I’ve also become much, much more aware of my own flaws and mistakes – what I do wrong, what I do write, and how I screw up. I’m a much better person for doing personal Agile.

Of course it’s also painful. I have work habits that are a bit bizarre seen from the outside (mixing casual, obsessive, distractable, and focused). My Scrum Master abilities focus a bit too much on the rituals with the idea they’ll help fix things “eventually.” My “Product Owner” side can forget my “Scrum Master side’s” recommendations on unfamiliar work and forge ahead on spewing ideas to my “Team Member” side.

But at least I have all these insights. I can’t blame anyone else.

Which is great.  Are you ready to try Agile in your life and learn your flaws?

– Steve