Fail Fast but have an exit plan just in case you don’t

In our data and regulatory driven world Innovation may be an essential element to disrupt the marketplace however how many failures should you expect before you find that unicorn and how do you account for these failures?

As more and more products migrate to the internet with SAAS and Cloud offerings becoming the fastest way to Innovate and “test and learn” one of the most important considerations in addition to does the proposition “work” is how do you exit (even if it is a success). As most Cloud offerings use proprietary software its not always in the interest of the supplier to make the breakup easy with the hope that you persist with the trial and continue your adoption however depending on your industry the extraction and preservation of the data or transactions history is probably the biggest consideration to a swift exit.

Therefore in addition to considering your success criteria in 2017 why not add another step and plan your exit from day 1. Most products allow you to extract a certain level of data however if your usage exceeds the basic; a retrospective archive is extremely problematic once you pass this threshold. Knowing how you will exit will not only help you if you “fail fast” but it will help drive your operational support procedures if the Innovation is a success as you will always have the sufficient level of data to exit in the future.

exit

 

 

Advertisements