Showing posts with label change management. Show all posts
Showing posts with label change management. Show all posts

Thursday, June 17, 2010

Trust in the Gulf -- Boot on the Neck

Department of the Interior Secretary, Ken Salazar, made the following statement on CNN: "Our job basically is to keep the boot on the neck of British Petroleum to carry out the responsibilities they have..."

Salazar's remark has now been widely circulated. How do you think the Secretary's statement affects the level of trust between the administration and BP?

How would you react if your client or a user group spoke to you like that? What if your manager told you that he was going to put his boot on your neck until you fulfill your responsibilities? I wonder whether the administration considered what effect its violent tone would have on the trust of those involved in the solution. Perhaps the administration doesn't believe trust has a part to play in the success of this unfortunate project.

Thursday, March 12, 2009

Sacred PM Practices - Change Management

Projects, large and small, must respond to a constant bombardment of proposed changes from customers, upper management, the business, the market, and perhaps even the federal government (e.g., regulatory changes). For a project to be successful, it must formally manage these changes. Or so I thought.

Observations

  • The majority of projects (56%) were successful without formal change management procedures (e.g., documented procedures, forms to be completed, consensus approval).
  • Of the 44% that reported formal change management activities, many project managers reported that the formality was absolutely critical to the success of the project.

I have rarely witnessed formal change management. I have often seen formal change management implemented, but rarely executed. There are forms, procedures, a change control board for those organizations very serious about change. From my viewpoint most of the time, the forms are not completed, the procedure description collects dust, and the change control board meets infrequently. Yet, some projects are successful.

Have you seen/lived formal change? Has it meant the difference between project success and project failure?

Introduced in a Jan 25, 2009 posting, this research project studied the project characteristics of large, successful IT projects.