Heads up! This page uses features your browser doesn't support. Try a modern browser like Firefox or Chrome for the best experience.

Issue a major update 30 days after launch

A quick update shows momentum. It shows you’re listening. It shows you’ve got more tricks up your sleeve. It gives you a second wave of buzz. It reaffirms initial good feelings. It gives you something to talk about and others to blog about.

Knowing a quick upgrade is coming also lets you put the focus on the most crucial components before launch. Instead of trying to squeeze in a few more things, you can start by perfecting just the core feature set. Then you can “air out” the product in the real world. Once it’s out there you can start getting customer feedback and you’ll know which areas require attention next.

This baby-step approach worked well for Backpack. We launched the base product first and then, a few weeks later, added features like Backpack Mobile for handhelds and tagging since those things are what our customers told us they wanted most.

We made Basecamp using the principles in this book. It combines all the tools teams need to get work done in a single, streamlined package. With Basecamp, everyone knows what to do, where things stand, and where to find things they need.