Skip to main content
The Rework Podcast

Product walkthroughs, the next open source product & other listener questions

26 min episode · 2 min read
·

Episode

26 min

Read time

2 min

Topics

Investing, Startups, Leadership

AI-Generated Summary

Key Takeaways

  • Unscripted product demos: Record product walkthroughs in single takes without scripts by doing four to five dry runs first, then letting the interface naturally guide the narrative. Start over only if the first minute contains errors, but continue through any later mistakes to maintain authentic flow and enthusiasm rather than robotic precision.
  • Video production philosophy: Avoid over-rehearsing product demonstrations because trying to remember scripted lines kills enthusiasm and makes presenters think from behind instead of performing live on the edge. One Hotwire video took eight to nine hours to produce with perfect precision but performed worse than naturally flowing versions with minor imperfections and human stumbles.
  • Dual tool workflow: Use Fizzy exclusively for bug tracking and issues while keeping Basecamp for broader project work, creating separation where Fizzy notifications only pertain to problems needing immediate attention. This single-purpose approach provides clearer mental context than mixing issue notifications with thirty active Basecamp projects, though both tools connect through Basecamp doors for easy navigation.
  • Open source strategy: Writebook will follow Fizzy into open source after establishing proper bandwidth to process community contributions, as merging contributor code requires significant time investment. The payoff from open sourcing Fizzy has been substantial, with developers creating AI style guides based on 37signals code quality and building their own applications using production-grade examples without negative consequences.
  • Enterprise software delight: Add playful UI touches and Easter eggs to business software without seeking management approval, following the proud tradition of developers shipping delightful details that leadership never notices anyway. The satisfaction comes partly from the small rebellious act of improving user experience despite organizational resistance, and customers may eventually speak up about enjoying these human touches.

What It Covers

37signals cofounders Jason Fried and David Heinemeier Hansson answer listener questions about creating product demo videos without scripts, their approach to open sourcing products like Writebook after Fizzy, how they use both Basecamp and Fizzy internally for different workflows, and why adding delightful UI touches matters even in enterprise software.

Key Questions Answered

  • Unscripted product demos: Record product walkthroughs in single takes without scripts by doing four to five dry runs first, then letting the interface naturally guide the narrative. Start over only if the first minute contains errors, but continue through any later mistakes to maintain authentic flow and enthusiasm rather than robotic precision.
  • Video production philosophy: Avoid over-rehearsing product demonstrations because trying to remember scripted lines kills enthusiasm and makes presenters think from behind instead of performing live on the edge. One Hotwire video took eight to nine hours to produce with perfect precision but performed worse than naturally flowing versions with minor imperfections and human stumbles.
  • Dual tool workflow: Use Fizzy exclusively for bug tracking and issues while keeping Basecamp for broader project work, creating separation where Fizzy notifications only pertain to problems needing immediate attention. This single-purpose approach provides clearer mental context than mixing issue notifications with thirty active Basecamp projects, though both tools connect through Basecamp doors for easy navigation.
  • Open source strategy: Writebook will follow Fizzy into open source after establishing proper bandwidth to process community contributions, as merging contributor code requires significant time investment. The payoff from open sourcing Fizzy has been substantial, with developers creating AI style guides based on 37signals code quality and building their own applications using production-grade examples without negative consequences.
  • Enterprise software delight: Add playful UI touches and Easter eggs to business software without seeking management approval, following the proud tradition of developers shipping delightful details that leadership never notices anyway. The satisfaction comes partly from the small rebellious act of improving user experience despite organizational resistance, and customers may eventually speak up about enjoying these human touches.

Notable Moment

David Heinemeier Hansson advocates treating software tools like mechanical keyboards or clothing choices, where switching between options provides valuable variety without needing to identify one perfect solution. He personally rotates between different keyboards and computers throughout the week simply because the tactile variation and design differences make work more enjoyable, applying the same philosophy to using multiple productivity tools.

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 cofounders of thirty seven Signals, Jason Fried and David Heinemeier. Hands on this week. We're gonna knock out some listener questions. We always love when people submit things, and We're just gonna knock them out. We've gotten some emails, voice mails, YouTube comments. So I'm gonna start with this one. Jason, this one's specifically for you. From Francisco, this is a comment on x. He said, I admire your product walk throughs. There's so much to learn about everything you don't say and how you point attention and in which order. Do you write scripts? Do you do mini takes? What's your process for releasing them? I'm assuming this is related to Fizzy most recently since you've done some product demos on video for that, but you've done for other products as well. Do you script right? Are you just winging it? Tell us a little bit about that. Yeah. I don't write a script. I go through it a few times. I kinda find my way by just going through the product and thinking myself, if I was new, what would I wanna see and in what order, kind of, roughly. And I do a few dry runs, and then I just record a single take. The way I do it is if I screw up in the first minute, I start over. If I get the first minute right without, like, stumbling on something, I just go even if I make a mistake, I don't care. But it bugs me if I screw up in the first minute. I think for the Fizzy one, I did maybe, like, four or five just kinda dry runs, and I'll say it a little bit differently each time. And I'll try to use things that happen in the interface at a certain time to, like, lead me somewhere. So I'll be like, oh, see this column? See how there's a bubble there? Like, what's that about? And then it'll take me there. I won't go look for a bubble. I'll spot a bubble in Fizzy, for example. There's a feature in Fizzy with these little bubbles come up. It says, like, stalled for twelve days or something like that. I know I wanna talk about these bubbles, but I'll wait for them to occur naturally throughout the demo. And then I'll seize on one and go, oh, there's that bubble thing. What's that about? So I kinda let the product experience drive the the conversation. So it's what's always in my head is, like, if I'm just gonna sit down with somebody and I was gonna show them the thing, I wouldn't start over all the time. You I would just keep going if I messed up If I miss something, I'd be fine If I circle back and remember something later, that's fine I'll just …

Get the full transcript (5,586 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 23-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

  • One Hotwire video took eight to nine hours to produce with perfect precision but performed worse than naturally flowing versions with minor imperfections and human stumbles.
  • FizzyRecommended

    by 37signals

    Use Fizzy exclusively for bug tracking and issues while keeping Basecamp for broader project work. The payoff from open sourcing Fizzy has been substantial, with developers creating AI style guides based on 37signals code quality.
  • BasecampRecommended

    by 37signals

    Use Fizzy exclusively for bug tracking and issues while keeping Basecamp for broader project work, creating separation where Fizzy notifications only pertain to problems needing immediate attention.
  • by 37signals

    Writebook will follow Fizzy into open source after establishing proper bandwidth to process community contributions.

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 Investing & Markets 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