Driven by a desperate need to prepare for Y2K, global corporations spent over a trillion dollars in the late 1990s to replace legacy systems with ERP applications that promised to solve the Y2K problem and enable automation. While ERP software did avoid the great disaster of January 2000, it failed to deliver much of the promised productivity gains. Why? The users hated the new systems and spent huge energy to circumvent the new investments. The issue of user adoption was born.
Since marketing automation has gained momentum a full decade after the ERP era, marketers have the benefit of learning from the mistakes of early adopters. User adoption is something to focus on before, during, and after the technology phase of the project. Here are some of the best practices that successful companies use to conquer this pesky challenge:
- Make it a priority and define an owner. In the same way that an IT project manager is responsible for the success of technical integration, an individual should be clearly responsible for transitioning the organization. Start here and your chance of success doubles.
- Start early with the user community. Users should be involved from the very beginning of the process. Choosing representatives from your end users and including them in the planning process will avoid push back and resentment later. They will also help you avoid gaps that will become big problems later on.
- Define the future state process. All of our clients agree on one thing—the future state process should be defined, reviewed, and approved before any technology is implemented. User representatives will provide feedback and you can avoid the inevitable calamity that will result from technology that fails to align with the planned processes.
- Define and execute a communications plan. Users should understand your vision and enthusiasm for the new solution. The executive sponsors should be in agreement on the goals and objectives of the new automation system. We recommend that you communicate to your user community at least twice a month during the full length of system development.
- Obsess over your business requirements. Capturing the requirements of your business and users will result in a system that hits the mark when it is released. Gaps should be identified and work arounds provided ahead of time. Users will check out when they sense that you have failed to capture the detailed requirements of their jobs.
- Celebrate early success. As users begin their involvement, frustrations will happen. Make sure that you identify early success and celebrate. Partnering with your HR department can be helpful.
- Provide time to do the work. Very often the individuals selected to participate in the change process are well respected leaders within their teams. This implies that they are the busiest and most important individuals to get daily work done. Managers must explicitly take work away from key participants so they may focus on the process transition.
- Focus on user acceptance testing (UAT). Too often UAT focuses only on very specific technical functionality. UAT should be a critical part of creating user adoption. The requirements should reflect the future state process that will be implemented.
- Time user enablement for success. We have seen clients provide training months in advance of UAT. Training has a shelf life of about four weeks if not put to immediate use. Make sure that you provide adequate training and that it gets delivered at the right time.
- Lean on your executive sponsors. Users will look to your leadership to evaluate their commitment to the new technology and process. Executives need to understand the importance of their attitudes toward success. Users will quickly sense any cracks in their commitment.
In most cases, careful planning and use of best practices such as these will ensure the engagement of your user community. In those cases where the future state process is a radical departure from the past, a more formal change management process might be required. In those cases, the use of a specialty organization may be helpful.