Don't write it down

The hosts emphasize that collecting extensive customer feedback by writing it down or formalizing it can be counterproductive. Instead, they suggest listening to recurring themes and pain points while avoiding reacting to isolated anecdotes. The real insights come from patterns in the feedback, which guide prioritization. They caution against designing solutions based solely on individual requests, as each customer has a unique scenario, and what resonates broadly is what truly matters.

On the technical side, especially with open source users, the approach to feedback differs—DHH mentions they have the freedom to dismiss unhelpful or misguided suggestions because these users don’t pay for the product. The key is to identify the core pain or problem underlying feedback rather than the specific feature requested. Customers often suggest patches or fixes, but the real goal is to understand the underlying issue and address it holistically without falling into the trap of patchwork fixes.

The hosts articulate a philosophy of avoiding detailed, long-term roadmaps, preferring instead to work iteratively and respond to feedback as it emerges. They warn against making concrete promises about future features because it can lead to disappointment and regret when those promises aren’t kept. Instead, they advocate for focusing on current work and allowing the product’s direction to evolve naturally, which fosters flexibility and innovation. Promises made in the past often become regrets when deadlines are missed or expectations aren’t met, exemplified by big tech companies' struggles.

A key theme is that customer requests often reflect problems rather than clear solutions. Customers tend to suggest patches instead of the root fix, and vague promises about future features create misleading expectations. The hosts advise against making commitments based on uncertain plans, arguing it can damage trust and lead to disappointment. They discuss how companies, including Apple, have failed when they set unmanageable deadlines or promise features prematurely, emphasizing the importance of focusing on delivering value with current products.

The conversation turns to rapidly evolving technology like AI, where teams often feel pressured to 'do something.' The hosts stress the importance of maintaining control, shaping projects carefully, and avoiding knee-jerk reactions driven by fear. They share insights from their experience, highlighting that truly valuable AI features are those that are solid, well-shaped, and benefit users—piecemeal or reactionary implementations tend to harm the user experience. The discussion underscores the need for cautious innovation rather than rushing into the latest trends.