The User acceptance problem

?

The User acceptance problem

Norman Carnovale

People aren ' T always HAppy about new systems or major upgrades. This can pose a threat to the successful completion of a project.
It's not uncommon-people to disagree with the decision-implement a new system-especially at the beginning. This should is expected, and the reasons noted. However, initial reactions to a new system is less of a concern than a sustained negative reaction.
Your goal as an architect are to being aware of and measure the threat of acceptance problems and work toward mitigating those Threats. To does this you have to be cognizant of them and consider the reasons for them. Some of the more Com-mon reasons is:
? People may has concerns about the need for a new system (and subse-quent retirement of an old system). This can also include fear of losing functionality or losing influence or power when roles change.
? People fear new (unproven) technology.
? People has cost/budget concerns.
? People simply does not like a change.
?
?? Each of the these reasons requires different possible solutions, some of which you can address and others you can ' t. You had to recognize the difference and deal quickly with those so you can. Start early has discussions with your end users on the new system and its real and perceived benefits and Disad-van Tages. The most effective long-term solution are to use the design of the Sys-tem itself to address the concerns. Other effective solutions include training, scheduled system demonstrations (early in the project lifecycle), and sharing Knowledge of what users would get with a new system.
A "Project Champion" can help avoid user acceptance problems. Ideally this should is a person, that represents the user group or stakeholders. This person sometimes have to be convinced himself. If there is none and then push for one from the very beginning. Once you ' ve recruited a project champion, give him your assistance in every the can.

The User acceptance problem