Some guidelines from The Checklist Manifesto.

You must define a clear pause point at which the checklist is supposed to be used (unless the moment is obvious, like when a warning light goes on or an engine fails).

You must decide whether you want a DO-CONFIRM checklist or a READ-DO checklist. With a DO-CONFIRM checklist, he said, team members perform their jobs from memory and experience, often separately. But then they stop. They pause to run the checklist and confirm that everything that was supposed to be done was done. With a READ-DO checklist, on the other hand, people carry out the tasks as they check them off.

The checklist cannot be lengthy. A rule of thumb some use is to keep it to between five and nine items, which is the limit of working memory.

But after about sixty to ninety seconds at a given pause point, the checklist often becomes a distraction from other things. People start "shortcutting." Steps get missed. So you want to keep the list short by focusing on what he called "the killer items"--the steps that are most dangerous to skip and sometimes overlooked nonetheless.

All of these points could just as easily apply to something as non life-critical as software development. Developers are more apt to skip any oversight unless it is absolutely minimal drag, and are just as easily prone to solitary labour vs team coordination.

I have a history of using an organizational system for about six months, then getting frustrated and giving up on it. This is usually compounded by my preference for software organizers over paper; I have to deal with technological obsolescence as well. And in my experience, moving from one piece of organizational software to another is just as much of a pain as manually copying out a physical organizer.

Late last year, I told myself that if there were no better options, I would write my own organizer. Failing that I would go back to paper, and just cope.  And it's getting to be about that time.

So without further ado, here's a list of the organizational services I have found, and really should take a close look at:

Pretty much all of these systems are web based.  This doesn't bother me as much as it used to; I almost always have my phone and it's ludicrously oversized data plan with me.  Some of them already have helper programs for my phone.  And many of them are geek friendly, and have exposed APIs as well as calendar and RSS feeds.

One thing that gives me pause is each of these services may disappear at any moment.  In fact, that happened to I Want Sandy when its developer was bought by Twitter.