Say No by Default

What It Covers

Jason Fried and David Heinemeier Hansson explain why defaulting to no on product features, pricing complexity, and business commitments prevents regret, reduces technical debt, and maintains product simplicity over 25 years at 37signals.

Key Questions Answered

• •Commitment costs compound: Saying yes feels cheap now but creates expensive future work through unwinding failed experiments, maintaining legacy code, supporting deprecated features, and working around accumulated complexity that limits future product decisions and development velocity.
• •Translation baggage example: Adding eight language translations in 2008 created ongoing drag where every feature required multiple translation steps before launch, slowing development velocity significantly despite only marginal customer acquisition gains, illustrating how yes decisions create permanent operational overhead.
• •The tomorrow test framework: Before accepting any commitment, ask whether you would say yes if execution was required tomorrow instead of months away. This mental model reveals true costs and prevents calendar regret from commitments that feel easy when distant but burdensome when immediate.
• •Dependency debt accumulates: Reusing infrastructure between products like their Signal ID login system created interdependencies that prevented individual products from having optimal user experiences. Self-contained products with minimal cross-dependencies enable better design decisions and easier maintenance over time.