The Scary Results of Mismanaging Change
| Part 1 of 2. Read Part 2, Project Justification: Anticipate Costs of Organizational Change or Anticipate Costs of Career Setback. |
One of the many roles that you must play as a project manager--as if you needed another one--is that of change manager. IT projects inevitably demand change in worker behavior, operational procedures and departmental relationships. The harsh reality is that this type of organizational change does not happen by accident or by fiat.
You may not even realize the full impact of your projects beyond your level of stress. It doesn't matter whether the objective is to upgrade software, add workstations, develop an intranet or establish e-commerce capabilities. All IT projects require changes in how employees perform and interact with each other. Workers and customers must adapt to new services, procedures, policies and practices. In general they don't like to have to put up with annoyances like this. They know how to be successful now, and you are tromping around in their garden. The impact of your project ripples from individuals to teams to departments to the entire organization. What you want to avoid is a big tsunami in return.
Now, how much training have you had on managing change to
Please log in or sign up below to read the rest of the article.
|
"Far out in the uncharted backwaters of the unfashionable end of the Western Spiral arm of the galaxy lies a small unregarded yellow sun. Orbiting this at a distance of roughly 98 million miles is an utterly insignificant little blue-green planet whose ape-descended life forms are so amazingly primitive that they still think digital watches are a pretty neat idea..." - Douglas Adams |




