Skip to main content
The Rework Podcast

Building in Public

20 min episode · 2 min read
·

Episode

20 min

Read time

2 min

Topics

Design & UX, Product & Tech Trends, Psychology & Behavior

AI-Generated Summary

Key Takeaways

  • Pre-launch momentum building: Share product development 6 weeks before launch through blog posts or videos to build anticipation, similar to movie trailers releasing multiple previews. This creates eager customers asking for early access rather than cold launching to an unprepared audience.
  • Avoid future promises: Never commit to specific delivery dates or product announcements publicly. 37signals announced two products but canceled Know It All mid-development, teaching them to say they're working on something without guaranteeing timelines. Use vague terms like "a few months" instead of concrete dates.
  • Real feedback requires real usage: Ignore feedback from people watching demo videos since they only see fragments without full context. Wait until version one launches and users actually interact with the product daily to collect meaningful, actionable feedback worth implementing in future iterations.
  • Show incremental design changes: Document small adjustments like notification card height, color additions, or 15-pixel spacing tweaks that accumulate into great products. Most companies only show polished final results, hiding the 8+ iterations that evolved into the shipped version, missing educational opportunities.

What It Covers

Jason Fried explains 37signals' approach to building products in public through unedited videos and design reviews, sharing work-in-progress features, design iterations, and internal decision-making processes for their new product Fizzy.

Key Questions Answered

  • Pre-launch momentum building: Share product development 6 weeks before launch through blog posts or videos to build anticipation, similar to movie trailers releasing multiple previews. This creates eager customers asking for early access rather than cold launching to an unprepared audience.
  • Avoid future promises: Never commit to specific delivery dates or product announcements publicly. 37signals announced two products but canceled Know It All mid-development, teaching them to say they're working on something without guaranteeing timelines. Use vague terms like "a few months" instead of concrete dates.
  • Real feedback requires real usage: Ignore feedback from people watching demo videos since they only see fragments without full context. Wait until version one launches and users actually interact with the product daily to collect meaningful, actionable feedback worth implementing in future iterations.
  • Show incremental design changes: Document small adjustments like notification card height, color additions, or 15-pixel spacing tweaks that accumulate into great products. Most companies only show polished final results, hiding the 8+ iterations that evolved into the shipped version, missing educational opportunities.

Notable Moment

Jason records all product walkthrough videos in single takes without editing, including moments when features break or he clicks wrong buttons, deliberately showing the messy reality of building unfinished software rather than creating polished marketing content.

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 from the thirty seven signals team joined by the cofounder and CEO, Jason Fried. This week, we're gonna talk a little bit about building things in public. Jason's been sharing a little bit about our new product coming Fizzy and doing some demos online and showing it in the process of being built. So I thought we'd talk a little bit about that. I don't think everyone is doing that, showing things before they're done. So let's dive into it a little bit. Jason, let's kinda talk through the history. I I remember back when Hey first started, you were doing this a little bit, showing things in advance. Is this something you've always done? Tell me kind of where this started. Yeah. We've actually been doing this since the beginning. So we did this for Basecamp, the original version of Basecamp as well, and then future versions of Basecamp as well. But back then, it was not videos, just blog posts. So we would Oh. Kind of share some stuff that was coming or, like, I think we did maybe about six weeks prior to launching Basecamp, we started really revealing, like, some of the features that were gonna be there to us. We had a blog at the time, so it was a small audience. Like, I wouldn't even know. 1,500 people? We're talking, like, Basecamp classic days, like, the original four. Yeah. Way back. We would write up these blog posts just sharing some of the features and some of the ideas behind it to sort of build some anticipation and excitement. So when we launched it, we just had people who are already, like, eager to get it. Because whenever you share something early, usually, someone's like, oh, can I get that? Or how do I get that? And so you just build this it's it's no different than than a trailer for a movie. You know? Yeah. This is sort of the model we follow, which is, like, the the trailer model, essentially. And even some movies have, like, three or four trailers prior to actually releasing the movie. So we did the same thing we've been doing ever since. Now I'm doing with video, and now we're doing it a bit earlier than we normally would. But I feel comfortable with that because Fizzy will be launched in a reasonable amount of time. So I can't tell you when because we don't know exactly, but it's not like it's years away or something like that. You know? We're talking about months. So month months is fine. It's fine to begin to share things early. And the other thing I wanted to do this time was to share work in progress. And actually, like, on a weekly or every two week basis, like, show just what we finished this past week. You know? …

Get the full transcript (4,670 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 17-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

  • FizzyBy guest

    by 37signals

    sharing work-in-progress features, design iterations, and internal decision-making processes for their new product Fizzy
  • Know It AllBy guest

    by 37signals

    37signals announced two products but canceled Know It All mid-development, teaching them to say they're working on something without guaranteeing timelines

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.

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