Organization Is Inspiration

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

This is a bit of a personal take on things, not advice or anything. But I was talking with a friend about organization and planning and wanted to share something.

I find Organization inspires me.

Planning, scheduling, breaking work down, and so on gets me going. There’s something about it that gets my imagination going and gets me inspired. So yes, I preach a lot about organizing and Agile and the rest, but I want to note how it helps me imagine.

I realized in that talk that sometimes when I’m down, planning gets me going again.

For instance, recently I was feeling uninspired and didn’t have a sense of what I was doing. So I made some finer-grained plans on my major projects – in fact, I felt driven to do it. It made me a lot more aware, a lot more organized, and a lot more “into” what I was doing.

I think there’s two parts of this.

First, when you plan and organize projects, you get into them. You feel what made you want to do them. You imagine ways to do them. You become aware of them and experience them more intimately.

Secondly, when you plan and organize projects, you can see how to get them done. You see the end goals, you see the path, you know your challenges and your workarounds. You know how to get them done – which probably energizes you as well.

So ironically, now I the planning and organizing guy, realize I may need to do it a little more now and then. That’s a useful realization – sometimes even I need to do a little more work breakdown for reasons over work breakdown.

But that’s why I share these things. Putting it into words makes me think, feedback from you the readers helps me process, and we learn together.

So let’s get organized – in an inspiring way.

Steven Savage

The Importance Of Not Doing

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

Do you have a schedule and plans? Daily plans? Weekly plans? Do you do them – them decide “well, I’ve got a bit more time” and go farther? Do you then realize . . . maybe you’re overdoing it?

Then do you try to not overdo it and still fail, going beyond your plans to do even more and burning out?

I had a realization about this recently as I was trying to keep up my daily schedule. I use schedules to keep myself focused during the Pandemic, and they’ve helped me “anchor” myself in these strange times. But I noticed on a day I was getting everything done, I asked what more could I do.

Then I caught myself. Why did I want to do more? Why couldn’t I stop?

Then I realized something. Schedules are not just ways to ensure things get done – they’re ways of setting limits so you don’t burn out. Part of the reason you have a schedule is to tell you what not to do or when to stop.

And of course, this ties into two parts of the Agile Manifesto. If you didn’t think I was going to tie this to Agile, you must be new here. Welcome aboard.

Anyway, in the Agile Manifesto, the tenth Agile Principle states “Simplicity–the art of maximizing the amount of work not done–is essential.” I always liked this as it was a good reminder to avoid unneeded tasks and technology. But recently I realized this applies to your schedules and plans – there’s a time to stop and not do things.

This also ties into the eighth Agile Principle: “Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

Good, sustainable work is at a pace you can keep up. This means not just being sustainable, but asking if you need to do something, removing things from your plans or not putting them in. Make a schedule that works for you, and remember that there is a time to not do something. Sure you may do it later, but you don’t have to do it now.

In fact, celebrate the fact you set limits! That should be one of your goals. Being able to not do something effectively is a success – you have time to rest, recuperate, and come up with the next neat thing to do . . .

Steven Savage

A Timeline Must Be Valuable

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

As I work on the sequel to A Bridge to the Quiet Planet, keeping up my schedule is challenging. You’ve probably read enough of my blog analysis on this, and you’re probably gonna keep hearing about it. My latest insight is that we misuse timelines by having them for the wrong reasons.

What’s the value of a timeline?

This question can be shocking. We’re often taught to regard them as valuable, almost sacred. Timelines are important, right? We should all get as much done as possible, right?

Too often, sticking to a Timeline is regarded as a virtue. The Timeline we’ve set (doubtlessly under different circumstances) is regarded as sacrosanct. To challenge it is unacceptable in many people’s minds. In short, we make following the Timeline something we must do over anything else.

And that’s wrong because a Timeline is just a tool. A Timeline is something we should use because it brings value. A Timeline isn’t sacred, and more than the Ivy Lee method or flowcharts or whatever.

You use a Timeline and create one because there’s value in it. If there’s no value then don’t create one.

For instance, with myself I found my novel was best approached with a sort-of Timeline as it kept me focused. Other things like blogging work on tight Timelines. Some of my coding practice is better handled with vague goals. In some ways I juggle multiple kinds of Timelines, and allowing myself to do that is comforting.

But Timeline for Timeline’s sake? Why?

Timeline? Good, I’m all for them – when they’re useful.

Steven Savage