Don't write it down
Summary
Host Kimberly Rhodes joins 37 Signals co-founders Jason Fried and David Heinemeier Hansen to discuss handling customer feedback and avoiding rigid product roadmaps. They argue against designing by anecdote or making long-term promises, which create illusions of agreement and regret. Instead, they advocate for listening to recurring pain points while maintaining the flexibility to iterate based on current realities. The episode also critiques knee-jerk reactions to trends like AI, emphasizing the need for solid, valuable solutions over vague features.
Topics discussed
Introduction: Why you should not write down customer feedback
Exceptions: Tracking unique language and insights
Interpreting feedback: Finding the core pain point
The danger of designing by anecdote and request counts
Why 37 Signals does not use long-term product roadmaps
The illusion of agreement in feature promises
Why vague feature names like 'Calendar' mislead customers
The regret of making public promises and deadlines
Apple Intelligence as a case study in premature promises
AI feedback: Avoiding knee-jerk reactions and shipping 'glimmers'
Listen ad-free on Castria