The work process model you just created is so widespread in use and acceptance that it has almost become a cliché. Nevertheless it is a valuable template for how to begin a well-managed team-oriented project. It is like the old country recipe for rabbit stew - first, you catch a rabbit. First, you get a charge. Unfortunately, you do not always have control over the form in which that charge arrives. Ideally, it is a well-written, detailed statement of strategic goals, and a clear empowerment to command the resources necessary to achieve those goals. More often it arrives closer to the way Jim Phelps got his missions.
Your response to the charge, regardless of the form in which it arrives, is to put together a core team and, with that team, decide what you are going to do and in general, how you are going to do it. This becomes the core of your mission statement - a document over which you do have control.
When deciding what to include in your mission statement, your goal should be to provide top management - or whomever issued the charge - the information that they will need to make an informed decision on whether or not to go forward with the program. If time is a critical factor, include a preliminary schedule. If cost is important (when is it not?) include a pro forma budget. Do not include too much information, but do not include too little, either.
Once the charging authority has accepted your mission statement, it - not the charge - becomes your team's working document. Post it on a wall somewhere, or prominently on-line so everyone is constantly reminded of its existence. It will be one of the most important documents in your program, and the ultimate arbiter of disputes, as well. Few questions cut to the heart of a disputed issue like "How does what you are proposing fit into the Mission Statement?"
With the acceptance and publication of the IMF Team's Mission Statement, they have achieved the first milestone in their mission, and you have completed your first TeamFlow work process model.
Begin Lesson 2.
Return to the beginning of this section.
Return to the beginning of Lesson 1.
Return to the Tutorial Table of Contents.
Return to the TeamFlow Home Page
Last Update: October 24, 2005