CONGRATULATIONS! YOU HAVE (ALMOST) no more bugs to fix, you’ve built a product that your trusted testers love, and your team is proud of what they built. You have the system instrumented so you’ll know when you’re doing well. You even have a rough cut of a blog post from way back when you first defined the product.
It’s time to launch, and launching is more complicated than uploading files to a server. There are several major launch steps you can follow to ensure a quality launch:
Just say no.
Start a war room.
Instill a sense of urgency in the team.
Complete the launch checklist.
Write the blog post.
Roll the software out.
Verify the software yourself.
Respond to the positive and negative effects of your launch.
When you’re driving to launch, you must say no as often as possible to features, to bugs, and to changes in the user experience. If you don’t say no, you’ll never finish your software and you’ll never ship. There’s an industry aphorism that goes, “You launch the software you have, not the software you want.” This aphorism is sticky within the software industry because it’s true—sometimes you just have to ship your product, even when it’s not perfect, because shipping something good is better than not shipping something perfect. Most of us can agree that this statement is true, but it’s hard to enforce because the definition of “good” is arbitrary.
To remove some of the arbitrariness from this stage of the project, I check to ensure ...