So much has been written about how to manage implementation efforts; from the nuances of costing and resource allocation, to the latest methodology that will virtually guarantee success, many of us have spent countless hours focusing on the process of driving an implementation to completion.
|More Patrick Gray on CIO Update|
Be ‘The Business’
Design for IT
If you want to comment on these or any other articles you see on CIO Update, we’d like to hear from you in our IT Management Forum. Thanks for reading.
The time spent of pouring over business cases and sweating through meetings with C-suite colleagues all strives towards that proverbial light at the end of the tunnel, whether it is a celebration of success or acknowledgement of defeat. While IT has grown immeasurably better at getting off the starting blocks and running the race, we are very poor at knowing what to do once we have reached the finish line.
The Failure of Success
Moments after recovering from post-implementation celebrations, IT leaders and staffers breathe a collective sigh of relief, and then immediately ask, “Now what?;” scattering in the direction of the next opportunity.
Consultants are dismissed to control costs, and business users gallop back to their former positions hoping to parlay their project experience into higher positions. Years of project documentation are hastily shuffled to a folder on a shared drive somewhere, and business cases with painstaking return calculations are stuffed into binders, destined to collect dust for years.
Failed projects create a similar rush of people, from consultants rushing for the exit as soon as another client appears, to project staff abandoning ship for the fear that the failed project will leave a mark on their record. No one wants to pick up the pieces, or harvest anything of value lest they be associated with “that” project. Whatever valuable process designs, technical solutions or new tools that have been developed are abandoned, further compounding the losses incurred by the failed project.
Should anyone’s worst fears of having their career unjustly hampered by the failed project actually come true, the tale will become amplified and added to the lore of the organization, so much so that fear of failure will curtail risk taking and decision making, two keys to a successful IT organization.
Ending an implementation means far more than a cocktail party, slaps on the back or a mass stampede running for cover in the case of failure. Most implementation projects produce significant pieces of valuable work that can be captured and used should a similar implementation be attempted in the future. It can also be fed into another project.
Think of the hundreds of hours spent investigating and documenting current business processes. Even if a technology implementation fails, this work can be used in any effort, be it a process redesign or another technology project. In the case of a successful project, there is often similar process-level documentation detailing the new way of doing business that can feed training efforts, or future process redesign efforts.
A forward-thinking IT organization should develop a project closing plan that can be used as a template for every project. Valuable activities like harvesting documentation and ensuring consultants and vendors have actually completed knowledge transfer, to the more mundane, like tracking cubicles and computers that can be returned to the general population, should all be included in this process.