It’s easy to point fingers at team members following a cloud project failure. But learning from what went wrong can help companies move beyond cloud disappointments.
Your cloud project failed. Now what? Look closely at your plans and learn from the results. Failures aren’t fun, but they are important for moving forward with the cloud.
The first step in learning from a cloud project failure is to identify how the project failed. Almost all cloud failures fit into one of three categories: something didn’t work, costs were too high or benefits were too low.
The success of any project, cloud or otherwise, depends on defending and meeting the business case with specific project steps, and this should uncover issues during the project rather than at the end.
The best way to start a cloud post-mortem is to meet with key project members. The meeting objective should be to improve the cloud project process, not set blame for problems. Avoid one-on-one discussions; everything should be out in the open.
Almost half of all cloud project failures aren’t identified as problems until the cloud is complete and the cost/benefit validation has occurred.
Next, identify where the project’s failure was first discussed. Almost half of all cloud project failures aren’t identified as problems until the cloud is complete and the cost/benefit validation has occurred. This is a major problem because either there was no attempt to control costs and validate benefits during the project, or those steps were ineffective