So I’m borrowing an idea from just-in-time delivery: the kanban method. The ideas are (according to Wikipedia):

• Visualize: See what you’re working on and where it is in the workflow. Also, keep track of where you’re approaching the limits.
• Limit work in process: My limit is probably two projects in focus. I work on one at a time. The other is there for switching to if I hit a snag or need to change things up. (See also: Managing Oneself) Everything else is on the back burner, the someday/maybe list, or the “nifty idea but probably not for me” list.
• Manage flow: I’m not paying much attention to this yet. It would be interesting to track how things move from current to back burner. I have some of that data through my timetracking.
• Make policies explicit: What gets a project onto my someday/maybe list, onto my back-burner, or into focus? There are lots of ideas that I’m happy to let other people explore; I pick up only projects that I’m personally motivated by and that I see value in. Of those, I identify which ones I can actually make some progress towards today. I focus on 1-2 things that I like the most (especially if other people want them too). I don’t stop myself from working on back burner things, but I no longer have to feel guilty about letting them lapse. If it turns out that I don’t actually spend time on back burner items in a month or two, that’s usually a good sign it’s a someday/maybe thing due to lack of present motivation or capability.
• Implement feedback loops: I haven’t paid much attention to this yet. Usually, people nudge me if I let some projects take too much of my attention.
• Improve collaboratively, evolve experimentally (using models and the scientific method): Tweaking my mindset to minimize guilt-friction is a good, small improvement. Looking forward to other small improvements!

Strict kanban would probably mean not even starting until I’d cleared off at least one work in progress, I think. I’m not that strict. I’m happy to switch back and forth, but it’s good to be clear about what I’m focusing on. That way, I don’t feel pulled in ten different directions.

Writing is my key project. Drawing, Quantified Awesome, and Emacs swap in and out of the #2 slot. Delegation tends to be more on the back burners. Someday/maybe? More business stuff, getting better at gardening, learning sewing, and so on. If I were better at delegation, I might be able to increase my capacity to do more, but it’s a lower priority at the moment (I appreciate the extra cushion that frugality gives me). I’m cheating with “Writing” and the books on my list – I’m planning to write them in short segments, one blog post at a time.

Knowing this helps because when requests come in for things that I’m not focused on, I can happily and guiltlessly refer them to other people. It makes decisions easier. Do I spend $X to attend a conference or course on Y? No, that’s on my someday/maybe list. It’s good to know what you can say no to in order to say yes to other things.

I might be able to make more progress if I focused on driving 1-2 things to completion, not switching them on and off the back burner. In that case, I would eliminate writing from my list of projects (it’s never done!) and move up the book projects. I tried that kind of intensive writing with Wicked Cool Emacs and it burned me out a little, but maybe I’ve learned since then. I like the interplay of interests, though. Maybe I can experiment with “week on, week off” patterns – there’s value in immersion as well…

Anyway, the point of this post is: I can’t do everything at the same time, so I’m learning to not stress out about it. =) If that’s something you struggle with too, then you might find that clearly identifying the things you are focusing on and gently letting go of the other things (at least for now) might help. Good luck!

You can e-mail me at sacha@sachachua.com.