I am a big fan of process management and workflow development. It allows everyone a chance at realistic estimates of their own capacity, it moves projects from natter to development to "product", and it can be improved at anytime given new information and/or knowledge.

 

Unfortunately, groups and others not familiar with workflow think it is a nothing item and often disregard it in favor of ad hoc enthusiasm or "someone-takes-care-of-it-magically-itis". I mean, come on! This often produces intolerable tensions and anger when the goal is lost in a sea of "I forgots" or "I didn't know I was supposed to" or whatever the final arguments happen to use for pointing to the mess that was intended to be a great idea manifested.

 

If, at any stage of development, the principal players sit and gently list all that they are doing, all that needs to be done, all that is wished for, and what kind of assets are in hand, a MUCH clearer picture of reality and getting to the goals is obvious.

 

I will add, however, that endless process development or workflow management is not helpful either. Punctuated review and revision of said workflow is adequate for helping people get along and work to be produced effectively.

 

The problem is that most people do not like to be real with themselves or with team planning groups. They tend to hyper inflate or under estimate their own capabilities. A good workflow session helps remove some of the ego crashes that can occur in a group because you can see who is really doing what and who is doing little at all. Remember, though, if a little is all someone can give, don't bitch at them. The ones that need bitching at are those that volunteer or speak out or are loud in their input but insignificant in their actual task completion or input. It is often amusing to see hot air compared to involvement when rendered with colored sharpie on a big whiteboard.