When a company buys new software
.... (nearly) nobody thinks about the change process involved
I worked 16 years in the IT industry - first as a trainer for some software tools, later as consultant and in the end as a project manager who took responsibility of rollouts of said new software. My experience in all these years was: a step like introducing new software is highly underestimated.
Most people simply think of the time needed to implement the installations, some customizations and some training. As for the change involved - it seems to me - middle and senior management simply presuppose their employees will adapt soon. That's where the struggle begins. And where it will cost lots of money.
I don't want to go into the gory details (there are many) but simply say this: it's worth to spend some money at the very beginning to get valuable answers to some questions - why do we need new software, what problems will it solve, what problems will it cause, what changes will it require, how ready are our employees to accept it? You might get some surprises :-)
German
English | Writeree.com
