Monday, May 28, 2007

Setting stretch goals

We've often heard that by setting stretch goals we have a better chance of achieving the desired outcomes. This is true, but you also need to establish a strategy and plan to get there.

About twelve months ago I attended a running seminar given by the founder of the Running Room, John Stanton. By the end of the seminar, I was motivated to take my casual running to the next level and set a goal to complete my first marathon before I turned forty. I wanted to do something for me for a change.

I started a running regimen over the next eighteen weeks and registered for the Montreal marathon. I did not have a heart rate monitor nor was I able to accurately gage my running pace. I simply used a pedometer to estimate distances of my runs over the course of those weeks and logged the miles per the plan. Having registered for the marathon kept me motivated to keep training. September came and the big day arrived. The weather was perfect. I had visualized the course over the previous few days and had planned all the hydration stations in my run strategy. I figured I would complete the distance in the 4:30 pace group. For the first 21km, I felt strong and completed the half in 2 hours flat. Then I started to slow at about km 30. My legs felt heavy and the people who had been running around me started to pull ahead. By km 34, I was literally on autopilot and was shuffling along. It took everything I had just to keep going. I had to break it down into short objectives ; "just to the top of the hill; "just to the next corner; "just to the next km marker..." It was the most brutal experience of my life. I finally completed the second half in 2:45. I had achieved my goal but my execution was not the greatest.

In January, I registered for the Ottawa marathon. This time, I had a heart rate monitor and also was able to measure my pace and speed. I set a goal to complete the marathon in 4 hours and planned my training distances and speeds to support that objective. My training was more structured and my progress was measurable. Come my last training run, I was confident I would meet my stretch goal. I completed the marathon in 3:52!

The morale of the story here is that when you set stretch goals, you have to make sure they are agressive enough to be a challenge but not so agressive that they are impossible to achieve. The other part is that by setting stretch goals, we often achieve more than we thought possible provided that we set ourselves up for success by ensuring we have the proper elements to execute the plan to meet those goals.

Thank-you, John, for the motivation!

Friday, May 25, 2007

Project failure survey

I have seen alot of statistics on project failures (up to 70%!). I have also seen alot of reasons given for project failures, but I have not come across any statistical data on the distribution of those reasons. So, in an attempt to try and be a bit more data driven on this subject, I would ask that you provide me with your feedback and we'll see what it gives.

Here is the question:

In your experience, please rate the percentage of project failures that can be attributed to the reasons below (the total does not have to add up to 100%, of course) :



  • Ineffective or lack of change management (people side of change)

  • Poor scope control

  • Schedule overruns

  • Cost overruns

  • Deliverable did not meet expectations

  • Other (please specify)


Sample answer: Suppose I have been involved directly or indirectly in 8 projects that I woul classify as failures. 4 had ineffective change (50%), 1 had poor scope control (13%), 6 had schedule overruns (75%), 4 had cost overruns (50%), 2 did not meet expectations (25%), and 1 was abandoned (13%).

____________________________


Here are the survey results....

of 15 respondents :

a. 73.3% cited Ineffective or lack of change management (people side of change) as a cause of project failures.

b. 80% cited Poor scope control

c. 80% cited Schedule overruns

d. 53.5% cited Cost overruns

e. 73.3% cited Deliverable did not meet expectations

f. 86.7% cited Other causes as well

Interesting to note that most feel that cost overruns are not really a cause but rather a consequence of some other cause.

Also interesting is that the Other causes can be grouped into two main categories; poor project management (or manager), and sponsorship (or lack thereof).

The affinity for each of these causes is as follows:

Poor PM includes unrealistic planning, poor manager, lack of participation, lack of acceptance of roles and responsibilities, poor business knowledge, bad communications, poor documentation, lack of discipline, bad PM approach.

Poor sponsorship includes unclear requirements, unrealistic expectations, project abandoned, change of heart or direction of project, management change, lack of support.

As for the distribution of results, it gives something like this:

Percentage of project failures attributed to:

51% - Poor PM

41% - Poor change management (people side)

32% - Schedule overruns

30% - Cost overruns

28% - Poor scope control

20% - Poor sponsorship

17% - Deliverable not meeting expectations

Thanks again to all those who participated. Hope this in informative for you.