Avoiding Transformation Program Fails
Blog: KWKeirstead's Blog
McKinsey & Company claimed in 2013 that 70% of Transformation Programs Fail (AIPMM, September 2013)
https://www.slideshare.net/aipmm/70-26633757
The breakdown on fails went like this (Employee Resistance: 39%;
Lack of Management Support: 33%; Inadequate Resources or budget: 14%; Other: 14%).
My first takeaway viewing the slide presentation was that it was mostly about not taking the time up-front to model the run-time platform that users would eventually be using.
Since work is all about converting information into action, system designers should reasonably look to a generic workflow/workload management platform where organizational processes can be mapped, rolled out and made available to users for modeling purposes. If the user perception is that work is easier under the new system than under the current system, resistance is likely to decrease.
The mapping should be done by the users, with a facilitator present. Clearly, having to learn a notation or language in order to be able to map out a process is a turn-off. Same for having to build/maintain database tables, building data display/data collection Forms at process steps and putting in place any required rule set development.
The solution here is to have an initial modeling phase that uses images of eventual forms and summary narrative descriptions of rule sets.
My second takeaway was that a good portfolio management (proposed initiatives, threat assessments, ROI/SROI and explicit funding/project auditing mechanisms) relieves Management of the need to provide ongoing “support”. That said, the fast pace of business today requires that Management continuously scan the horizon for opportunities/problems and monitor the progress of initiatives during implementation phases.
Stay tuned for a description of orderly processes for planning and managing Transformation Programs.
“Success Evolving Strategies (methods, tools, platforms)”
Then, a second article
“Success Achieving Operational Efficiency and Effectiveness (methods, tools, platforms)”
Leave a Comment
You must be logged in to post a comment.
