For some, aligning people means providing training so employees know how to use the system. Others say you need to include communications to align their people. Some advanced organizations even extend their efforts to include mapping out changes to job descriptions and responsibilities.
While these are all important activities to help achieve alignment of people, process and technology, they don’t actually help us understand what alignment is. And if you don’t know what it is, how do you know when you have achieved it?
Alignment only occurs when your people, process and technology all perform together in a symbiotic relationship that delivers the desired results. The people use the technology. The people follow the process. They key here is that the people must actually use the technology and the people must actually follow the process. This requires people, ALL of the people, change their behavior to achieve the desired results.
Focus on Behavior Change to Improve ROI
“Did he just say our technology project needs to focus on changing people’s behavior? I thought we were implementing technology, not disciplining children or providing group therapy. What is all this behavior talk anyway?”
Consider the relationship between user behavior and return on investment (ROI). When do we actually realize ROI from our technology projects? Is it when the technology is delivered? Sadly, no. We only realize our ROI when the people actually use the technology. If a system is delivered, but not used, it does not return any value to the organization. So, while successfully deploying the technology is on the critical path (pardon the gratuitous use of the buzzword) to achieving ROI, the critical path is only completed when the system is used effectively by our people.
Sounds pretty straightforward, right? Wrong. This simple idea has tremendous implications that require advanced thought. It means we need to rethink how we structure technology projects, who we involve in the process, and how we define success. Looking back over the landscape of a typical IT implementation we notice activities focusing on behavior change are conspicuously missing. Worse still, people with skills and expertise in behavior change are typically not even part of the implementation team. This is the problem.
Example: User Behaviors’ Impact on ROI and on the Customer Experience
I worked with a client who did very little to drive desired behavior when implementing a new CRM system. As expected, they had numerous behavior problems that reduced their ROI and degraded the customer experience. Sales reps did not see “what’s in it for me”, so they would often not use the system at all or they would only enter partial, inaccurate customer data. Customer service reps would not reliably create problem tickets, nor would they regularly update their progress on resolving customer issues. Managers would not use the system to track progress or to analyze department performance.
The impact to the organization and to the customers experience was severe. The organization wasted vast amounts of time and effort performing unnecessary tasks, such as tracking down information that was not entered by one individual but was required by others to perform their jobs. The lack of complete and accurate data made it impossible for management to utilize the system reports to make reliable, informed decisions. Executives and sales reps were unable to review vital customer activity data to prepare for additional sales meetings. The customers experience was degraded by delays resulting from having to repeat conversations that were not properly logged in the system.
It was only after the client had experienced these problems for quite some time that management decided to address user behavior. After users changed and demonstrated desired behavior, the system delivered significant value and the customer experienced improved. Had management proactively focused on driving desired behavior earlier they would have avoided the period of poor performance and significantly increased their overall ROI from the start.