One of the problems that I'm trying to solve here is the notion that I need to keep all the balls in the air across several projects. Let's say I have five projects going on:
- main product release
- prototype release
- client issue
- next release plan
- lab expansion plan
I can choose to work them serially (today I'm doing main product release, tomorrow next release plan, etc). However, it means I'm touching each of them only once a week, and in the week that elapses, well, that's a lot of other people also working on these projects who are waiting. No good.
So I have to choose to work on each of them frequently enough to keep current. It doesn't have to be much, and the frequency varies based on the priority of the project overall. In general, I sit down and say, "what is most blocked by me?" and work on that.
How do you handle balance, at the fine-grained tactical level?