0.9 Project initiation  (Page 2/2)

For example, an objective of the team principle (project manager) of a Formula 1 racing team may be that their star driver, “finish the lap as fast as possible.” That objective is filled with ambiguity.

• How fast is “fast as possible?” Does that mean the fastest lap time (the time to complete one lap) or does it mean the fastest speed as the car crosses the start/finish line (that is at the finish of the lap)?
• By when should the driver be able to achieve the objective? It is no use having the fastest lap after the race has finished, and equally the fastest lap does not count for qualifying, and therefore grid (starting) position, if it is performed during a practice session.

The ambiguity of this objective can be seen from the following example. The race lap record at the Circuit de Monaco of 1 min 14.439 sec was achieved by Ferrari’s Michael Schumacher in 2004 ( [link] ). However, he achieved this on lap 23 of the race, but crashed on lap 45 of a 77 lap race! So while he achieved a fastest lap and therefore met the specific project goal of “finish the lap as fast as possible”, it did not result in winning the race, clearly a different project goal. In contrast, the fastest qualifying time at the same event was by Renault’s Jarno Trulli (1 min 13.985 sec), which gained him pole position for the race, in which he went on to win ( [link] ). In his case he also achieved the specific project goal of “finish the lap as fast as possible”, but also the larger goal of winning the race!

The objective can be strengthened considerably if it is stated as follows: “To be able to finish the 3.340 km lap at the Circuit de Monaco at the Monaco Grand Prix in 1 min 14.902 sec or less, during qualifying on 23 ^th May, 2009. This was the project objective achieved by Brawn GP’s Jenson Button ( [link] ).

There is still some ambiguity in this objective; for example, it assumes the star driver will be driving the team’s race car and not a rental car from Hertz! However, it clarifies the team principal’s intent quite nicely. It should be noted that a clear goal is not enough. It must also be achievable. The team principal’s goal becomes unachievable, for example, if he changes it to require his star driver finish the 3.340 km lap in 30 seconds or less.

To ensure the project’s objectives are achievable and realistic, they must be determined jointly by managers and those who perform the work. Realism is introduced because the people who will do the work have a good sense of what it takes to accomplish a particular task. In addition, this process assures some level of commitment on all sides; management expresses its commitment to support the work effort and worker demonstrate their wiliness to do the work.

Imagine you are an office manager and you have contracted a painter to paint your office. Your goal or objective is to have the office painted a pleasing blue color. Consider the following conversation that occurs after the job was finished:

This conversation captures in a nutshell the essence of a major source of misunderstandings on projects: The importance of setting clear objectives. The office manager’s description of how he wanted the room painted meant one thing to him and another to the painter. As a consequence, the room was not painted to the office manager’s satisfaction. Had his objective been more clearly defined, he probably would have had what he wanted.