Skip to main content
The Rework Podcast

Say No by Default

32 min episode · 2 min read
·

Episode

32 min

Read time

2 min

Topics

Design & UX, Software Development, Product & Tech Trends

AI-Generated Summary

Key Takeaways

  • 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.

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.

Notable Moment

David admits both founders still regularly fall into saying yes despite knowing better, committing to features or engagements months out that they regret when the work arrives, demonstrating how difficult maintaining no discipline remains even for experienced practitioners.

Know someone who'd find this useful?

Episode Transcript

Welcome to Rework, a podcast by thirty seven signals about the better way to work and run your business. I'm your host, Kimberly Rhodes. And as always, I'm joined by the cofounders of thirty seven signals, Jason Fried and David Heinemeier Hanssen. In their book, Rework, they write about saying no. In fact, they say it's even more important to say no more often than actually saying yes. In fact, they write, quote, you rarely regret saying no, but you often wind up regretting saying yes. Guys, I thought we would talk about it today. Not only making decisions in terms of the products, what you're saying yes and no to, but also in terms of your business, what you're saying yes and no to. I don't know who wants to jump in on this in terms of the product first maybe. I think the point about regretting yeses is actually a good place to start because that's, in many ways, more interesting to me than the saying no part. Saying no obviously is a very, very specific instrument. When you say yes to something, it's kind of a blunt force instrument because, in effect, you're saying no to maybe hundreds of other things that you could consider because you've already taken something on. And oftentimes, what we found is that when you take some things on, you you can end up with a lot of regret down the road. You know, you experiment with something because you think it's a cool idea, and then you're left with sort of the remnants of that idea sort of baked into a website somewhere, or you have, like, seven additional pages on your website you didn't know about or had some, like, pricing thing you implemented and forgot about, or the person who was doing that is no longer here, and now there's this thing that's sort of hanging out there in the wind. And that is one of the biggest penalties are saying yes to too many things, is is that you end up having a few too many things going on. You can't really keep track of all of them necessarily, and they end up increasing the surface area of the business, of a website, of a product, whatever it might be. And you look back on that a year later and you're like, not only do we wish we didn't say yes to this, but now we have to unwind it, which is additional work. So is all the work you put into doing it, now you have to unwind it. Or if you don't unwind it, which most companies end up not really unwinding it fully, and we're guilty of this too, again, you end up with these sort of artifacts that you don't even know about, kinda hanging around. And then when you wanna make some changes later, you're like, we can't or we can, but it's gonna be a real pain in the ass because we've …

Get the full transcript (6,778 words) + summary by email — free

One-time email with the complete transcript and AI summary of this episode. No account needed.

One email, no spam. We’ll also show you what SignalCast does.

Browse all The Rework Podcast transcripts →

You just read a 3-minute summary of a 29-minute episode.

Get The Rework Podcast summarized like this every Monday — plus up to 2 more podcasts, free.

Pick Your Podcasts — Free

Keep Reading

More from The Rework Podcast

We summarize every new episode. Want them in your inbox?

Similar Episodes

Related episodes from other podcasts

Explore Related Topics

This podcast is featured in Best Business Podcasts (2026) — ranked and reviewed with AI summaries.

Read this week's Software Engineering Podcast Insights — cross-podcast analysis updated weekly.

You're clearly into The Rework Podcast.

Every Monday, we deliver AI summaries of the latest episodes from The Rework Podcast and 192+ other podcasts. Free for one show.

Start My Monday Digest

No credit card · Unsubscribe anytime