Seven Shipping Principles

Key takeaways

Aim to ship good work, not just what is 'better than nothing'.
Assess the confidence level based on the criticality of the feature being shipped.
Take ownership of issues after shipping by addressing customer feedback directly.
Prioritize holistic product integrity over mere technical correctness.
Avoid 'gold plating' features by staying aligned with the team's capacity and appetite.

Summary

Only Ship Good Work

In this segment, David shares the importance of not shipping subpar software. The principle underscores that 'good' should be the benchmark, not 'okay.' Both Jason and David argue that shipping something that is 'better than nothing' is not a worthwhile standard. It’s essential to assess the overall quality rather than just individual components, ensuring that every piece of a product meets the company's high standards.

Confidence in Shipping

The discussion shifts to the idea of confidence when shipping. David emphasizes that confidence in shipping is context-dependent, varying according to the criticality of the software feature. Different layers of rigor need to be applied based on the level of potential risk associated with the software, which helps avoid unnecessary over-engineering for less critical updates.

Ownership of Issues Post-Launch

In addressing how to handle mistakes after shipping, the principle of owning issues post-launch is put forth. Developers are encouraged to monitor feedback actively and fix any problems that arise, linking their development work with real-world outcomes effectively. This approach is portrayed as integral to maintaining quality and ensuring that developers take accountability for their work.

Perfection vs. Good Work

Jason adds nuance to the conversation by describing how the concept of 'not shipping if it isn’t right' entails more than technical correctness. He stresses aesthetic and functional integrity, advocating for a holistic view of product relevance. The focus should remain on identifying and solving the core problem rather than getting stuck in perfectionism.

Understanding and Adjusting to Appetite

David rounds out the discussion by pointing out that just as great companies can be terrible stocks, a good feature can become problematic if pursued past its scope. Caution is advised against 'gold plating'—over-decorating a solution. Ensuring the work stays aligned with the team's appetite and not straying into perfectionism is essential for remaining practical in development.

Show notes

How does 37signals decide when software is ready to ship? In this episode of The REWORK Podcast, 37signals’ co-founders Jason Fried and David Heinemeier Hansson discuss the company's Seven Shipping Principles. They dive into when a product update is good enough to ship and the importance of making updates to solve actual problems.

Key Takeaways:

00:11 – We only ship good work.
03:36 – The problem with MVPs
04:41 – We ship when we're confident.
10:08 – We own the issues after we ship.
13:41 – We don’t ship if it isn’t right.
17:11 – Making sure your solution tackles a real problem
20:00 – We ship to our appetite.

Links and Resources: