Skip to main content
The Rework Podcast

The itch for a new version

23 min episode · 2 min read
·

Episode

23 min

Read time

2 min

Topics

Design & UX, Software Development, Product & Tech Trends

AI-Generated Summary

Key Takeaways

  • 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.

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.

Notable Moment

Fried observes users initially hate changes from version two to three, then defend those same features when version four modifies them again, revealing how people cling to what they eventually adapt to regardless of initial resistance patterns.

Know someone who'd find this useful?

Episode Transcript

Welcome to Rework, a podcast by thirty seven Signals about the better way to work and run your business. I'm Kimberly Rhodes joined by the cofounder and CEO of thirty seven Signals, Jason Fried. As you guys probably know, we are in the process of building a new version of base camp base Basecamp five. And although we can't share a lot about that now, I did think it'd be interesting to talk a little bit about why we're making a new version. But not only this version, but why we choose to make new versions of our products versus just adding new features. So, Jason, maybe we start a little bit with the history. Basecamp started as Basecamp back in the day, and then we made Basecamp two onto Basecamp three, which then became four. Like, as you're doing this kind of process, what kind of things were you thinking about on making something completely brand new, a brand new version, a new number at the end versus just adding features? Yeah. I mean, when we started this, we didn't have any, idea that we'd be making big new versions. Right? We just make Basecamp, which is now called Basecamp Classic, but just Basecamp. And, we did everything we could to make it the best thing it could be. We added a bunch of features and refined it and updated the interface and all the things. And then there comes a point or there came a point, I shouldn't say there comes a point because this is not always the case. But in our case, there came a point where we had a new idea that would not fit on the chassis, let's say, of the existing product. It was a new interface idea. It was a radical departure from what we had done initially. And when we come up with that, you can't really graft that kind of thing on to what we had because it also came with new technology ideas, new structural ideas, infrastructure ideas, have technically grafted it on, but it would have been such a radical departure that it made sense for us to say, let's start from scratch here. Anyone who's like renovated an old house will maybe you understand what I'm talking about. Like it's actually easier to build a new house Yeah. Than is it built to renovate down to the studs in old house because you've got all sorts of things that you gotta deal with versus starting over from scratch. So it was like, we've done a bunch of renovations in the existing place, and, like, that was enough, and then we're gonna decide to build a new house. Now part of that was leaving the original house standing. So Basecamp Classic still stands today, and it's still used by thousands of customers today. So no one was forced to change from Classic to what became known as Basecamp two. We've changed our mind on that over the years …

Get the full transcript (5,155 words) + summary by email — free

One-time email with the complete transcript and AI summary of this episode. No account needed.

One email, no spam. We’ll also show you what SignalCast does.

Browse all The Rework Podcast transcripts →

You just read a 3-minute summary of a 20-minute episode.

Get The Rework Podcast summarized like this every Monday — plus up to 2 more podcasts, free.

Pick Your Podcasts — Free

Keep Reading

Books, tools, and gear mentioned in this episode

SignalCast may earn commission on purchases via these links. As an Amazon Associate, SignalCast earns from qualifying purchases.

Products

  • Basecamp 4By guest

    by 37signals

    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.
  • Basecamp 2By guest

    by 37signals

    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.
  • Basecamp 5By guest

    by 37signals

    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.
  • BasecampBy guest

    by 37signals

    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.
  • Basecamp 3By guest

    by 37signals

    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.

More from The Rework Podcast

We summarize every new episode. Want them in your inbox?

Similar Episodes

Related episodes from other podcasts

Explore Related Topics

This podcast is featured in Best Business Podcasts (2026) — ranked and reviewed with AI summaries.

Read this week's Software Engineering Podcast Insights — cross-podcast analysis updated weekly.

You're clearly into The Rework Podcast.

Every Monday, we deliver AI summaries of the latest episodes from The Rework Podcast and 192+ other podcasts. Free for one show.

Start My Monday Digest

No credit card · Unsubscribe anytime