Deep Dive
What is the first shipping principle of 37signals, and why is it significant?
The first shipping principle is 'We only ship good work.' It is significant because it sets a high bar for quality, ensuring that the software is not just 'okay' but genuinely good. This principle allows the team to say no to shipping subpar work, even if significant time has been invested. It emphasizes the importance of delivering software that the team is proud of, rather than rushing to meet deadlines with mediocre results.
Why does 37signals critique the concept of MVPs (Minimum Viable Products)?
37signals critiques MVPs because they believe the 'minimally viable' bar is too low. Testing incomplete or half-baked ideas often yields poor feedback, which doesn't help in evaluating the true potential of a feature. Instead, they advocate for shipping complete, well-thought-out ideas, even if they are smaller in scope, to ensure the feedback received is meaningful and the product is of high quality.
How does 37signals determine when they are confident enough to ship a product?
Confidence in shipping is determined by the criticality of the problem being solved. For less critical issues, a lower burden of proof is acceptable, while for high-stakes features (e.g., billing systems), rigorous testing and reviews are required. The team avoids applying the same level of rigor to all tasks, instead calibrating their confidence based on the potential impact of bugs or failures.
What does the principle 'We own the issues after we ship' mean at 37signals?
This principle means that the person or team responsible for a feature must also handle any issues that arise after it is shipped. They monitor error trackers, respond to customer feedback, and fix problems. This approach ensures accountability and provides developers with real-world feedback, helping them improve their work and avoid isolating themselves from the consequences of their decisions.
Why does 37signals avoid shipping features that 'aren't right'?
Shipping features that 'aren't right' can lead to hidden rules, awkward user experiences, and unsatisfactory explanations for edge cases. 37signals prioritizes solving the root problem effectively, even if it means stepping back and rethinking the approach. They avoid shipping incomplete or flawed solutions, ensuring that the final product aligns with their high standards and provides a seamless user experience.
What does 'We ship to our appetite' mean in the context of 37signals' shipping principles?
'We ship to our appetite' means that 37signals avoids overextending themselves by pursuing ideas beyond their capacity or interest. They focus on delivering good work within their six-week cycles, avoiding 'gold plating' or over-decorating features. This principle ensures that they prioritize clear, impactful ideas over perfection, maintaining a sustainable pace and avoiding burnout.
How does 37signals balance the trade-off between perfection and practicality in their shipping process?
37signals balances this trade-off by focusing on delivering good work rather than perfect work. They prioritize clear, impactful ideas and avoid over-engineering solutions. For example, if a feature is technically clever but based on a flawed premise, they will step back and rethink the approach. This ensures that their solutions are both practical and aligned with their high standards.
Shownotes Transcript