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

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.