When implementing new technology, it is essential to consider all of your employees’ roles in its success. Lack of user buy-in is one of the most common reasons new software purchases fail today.Most of the time, failure occurs because:
- the decision was made without user input;
- the wrong software was purchased (often because there was no user input); and
- employees assigned to implement and/or use the new technology refuse to change.
So how can contractors get their employees involved and enthusiastic? It starts well before the actual purchase. Because many people will be using the software daily, don’t limit the planning and decision-making to just a few users. When preparing the needs analysis, get all users involved and solicit feedback from everyone on current software issues and problems, as well as their suggestions. End-user buy-in happens naturally when employees get the sense that their opinions have been taken into consideration.
Next, narrow down your software choices and invite key users to sit in on productdemonstrations so they can ask specific questions and understand how the system works.
Keep in mind that the real work starts after the software program is chosen. When it comes time for training, make sure the schedule is realistic and the methods allow for all learning types. It is easy to see why many employees are less than eager to take on the challenge of new software when they are faced with the prospect of learning a new (and seemingly complex) software system while completing their daily (and long) list of tasks.
Above all, owners and managers must be involved in the entire process and take an active role in the implementation. Communicate to end users not only how the new system will make their jobs easier and more efficient, but also why it will improve the company’s overall effectiveness and competitive edge. Employees are more motivated to learn something new when they see the project as worthy of their time and effort. With the right environment and good communication, contractors should be able to hurdle the roadblock of user rejection.
