Batches

It doesn't apply to every workflow, but there is tremendous advantage to doing work in batches.

My work often arrives in bunches, where I will have 10 individual projects within one big project. There are a variety of ways to attack the work.

Some would do Project A start to finish, then dive in on Project B. If each project is different or requires customization, that's the best way to go.

But if each of project is a variation on a theme, or 90% similar but get painted a different color, batch all the work except the painting. (I would paint all at the same sitting, too, but you see where I'm going.)

Even though I'm reasonably good at each of the steps in my workflow, I notice that I'm better at each step if I do all of the action in that step at once.

This can be expanded lots of work that we often do on an individual basis, especially if we generate content. I often write a week or two worth of blog posts in one sitting, and let the software ship a new one each morning. I scribble notes during the week, then sit down and write, often on Sunday night. I feel that my writing is better, and that I do it in less time. When I add more content streams to my professional life, I will develop a batch method to them, also.

I've also cooked multiple entrees on a Sunday afternoon, then reheated each night during the week. I cook when I have the time for it, reheat when I don't. One big kitchen mess beats five little ones.

Some things don't lend themselves to batch work- like mowing the lawn. Batching my writing and cooking lets me mow when the lawn needs it, not when it's convenient to me.