Areas of support needed when attempting to roll out a new software system

Posted on DotNetBlocks See other posts from DotNetBlocks
Published on Thu, 06 Jan 2011 23:32:00 -0500 Indexed on 2011/01/09 22:57 UTC
Read the original article Hit count: 217

In general, I think most people tend to be resistant to new systems or even change because they fear the unknown. Change means that their normal routine will be interrupted until they can learn to conform to the new routine due to the fact that it has transformed to the old routine. In addition, the feeling of failure is also generates a resistance to change. Why would a worker want to move from a process that has worked successfully for them in the past? Their fears over shadow any benefits a change in a new system or business process will bring to their work life.

Areas of support needed when attempting to roll out a new software system:

  1. Executive/Upper Management Support
    • If there is no support from the top of an organization how will employees be supportive of the new system?
  2. Proper Training
    • Employees need to train on a new system prior to its rollout. The more training employee’s receive on any new system will directly impact how comfortable they will be with the system and are more accepting of the change because they can see how the changes will benefit them.
  3. Employee Incentives
    • One way to re-enforce the need for employees to use a new system is to offer incentives to ensure that the system will be used.
  4. Employee Discipline/Termination
    • If employees are adamantly refusing to use the new system after several warnings then they need to be formally reprimanded.  If this does not work the employer is forced to replace the employees.

© DotNetBlocks or respective owner

Related posts about Deployment Methodologies

Related posts about Information Technology Managment