As we know, it’s not easy making the complex simple. Consider implementing an enterprise resource planning (ERP) system. The new system is likely to be at least an order of magnitude or two, more complex than the current system making it harder to create efficiencies and have strong adoption.
While the application experts have a strong familiarity with the tool, its definitions, and its inner workings, at the end of the day, the people who will rely on the system day in and day out to do their jobs don’t have the benefit of years of experience. They are more like “deer in the headlights.”
And, all too many application project schedules leave little time before go-live to acquaint the users with all that they need to know to do their jobs seamlessly and effortlessly. How long will it take for users to achieve unconscious competence with the new application?
If your focus is making the complex simple, crossing the chasm between the current system and the new system must be a very high priority. Yet, most application implementations leave end-users frustrated, dazed and confused creating a bad impression that’s hard to overcome.
At the point of go-live, you want the team energized, not frustrated, dazed and confused. Criteria need to be established not only for application readiness but business team readiness to use the application at the point of go-live. Someone needs to focus on the people who have real jobs to perform.
Thought for the week: