| |
|
|
|
|
| |
 |
|
 |
Analysing, Designing and implementing new ways of doing things - the inevitable result of a decision to change your IT sourcing - are best run as a unique project.
But every project also requires CHANGE. If it didn’t then it would be pointless. And it affects a just about everyone in the business in one way or another.
There are two ways to handle this – either ignore it and hope it just gets accepted, or do something about it.
The former will at the very least slow down the incorporation of the new order in every day operations. At worst it can destroy your business.
Of the latter, there are another two choices – “like it or lump it” and get on with it, or involve people and introduce the change in a structured way. Either can be relevant at the right time, although the greatest and longest lasting successes come through involving and explaining.
Click on any of the links to view one of the short white papers concerning managing change. It’s not easy – but it’s not difficult either.
Why should you actively Manage Change?
Five easy questions to see if your project is in control
| |
 |
|
|
|
|
|
|
| |
|
|
| |
|
|
|
|
|
