In 13 years of overseeing databases I got caught without a backup exactly one time. Luckily it was for a dev system and it wasn’t a catastrophe but it did remind me of how important they are. Actually, they’re not just important, they’re your ass if things fall apart. Same goes for products. Your optimal way to go-to-market may not always be open to you. In that case you’ll need contingencies. Say for example that the primary feature in your product, the feature that distinguishes it from your competitors, can’t be implemented. Do you go to market anyway and hope for the best? Hopefully not. Do you wait until you develop a new capability or feature and then release? Or do you release without the feature and release the new capability as soon as it’s ready? It’s one of the last two options, but it’s all up to you to figure out. One of our possible contingency plans is shown here.