The itch for a new version

What It Covers

Jason Fried explains why 37signals builds new numbered versions of Basecamp rather than continuously adding features, covering the decision framework between major rebuilds versus morphing existing products forward through updates.

Key Questions Answered

• •Version transition strategy: 37signals shifted from ground-up rebuilds (Classic to Basecamp 2 to 3) to morphing updates (3 became 4, 4 becomes 5), eliminating customer migration pain and keeping users at existing price points while delivering substantial improvements.
• •Feedback timing discipline: Ignore all non-bug feedback for thirty days after launching changes because initial reactions are pressure-based and knee-jerk. After thirty days, feedback becomes more accurate as users adapt and identify genuine usability issues versus discomfort with change.
• •Renovation versus rebuild threshold: Build new versions from scratch only when new interface or infrastructure ideas cannot fit the existing chassis, similar to how renovating a house down to studs becomes harder than building new, requiring radical departures that justify starting over.
• •Direct experience design: Basecamp 5 surfaces assignments and upcoming events alongside current work rather than requiring navigation away, adds sidebar pings for messaging without screen changes, and reintroduces full calendar functionality based on sustained customer requests from Basecamp 2 users.