What are the key takeaways from this The Rework Podcast episode?

Key insights include: **Publishing velocity:** Write and ship content in one day rather than spending three days perfecting it, because inspiration is perishable and additional editing time often adds minimal value while killing momentum and completion likelihood.; **Response time expectations:** Never require immediate responses unless it's a true emergency. The expectation of instant replies is toxic to productivity. Use phone calls specifically for urgent matters, making the medium itself signal importance rather than assuming all messages demand speed.; **Clarity in high-stakes communication:** When discussing important topics, use simple, direct language with minimal surface area for misinterpretation. Avoid flowery writing that can be perceived multiple ways, as ambiguous words will typically be understood in the most harmful interpretation possible.

What did Jason Fried and Kimberly Rhodes discuss on The Rework Podcast?

Jason Fried and David Heinemeier Hansson explain their 30-point guide to internal communication at 37signals, covering principles like avoiding immediate response expectations, using long-form writing over chat, and shipping content quickly without approval processes. Key topics include: **Publishing velocity:** Write and ship content in one day rather than spending three days perfecting it, because inspiration is perishable and additional editing time often adds minimal value while killing momentum and completion likelihood.; **Response time expectations:** Never require immediate responses unless it's a true emergency. The expectation of instant replies is toxic to productivity. Use phone calls specifically for urgent matters, making the medium itself signal importance rather than assuming all messages demand speed..

How long is this episode of The Rework Podcast?

This episode is 27 minutes long. SignalCast provides an AI-generated summary so you can get the key insights in about 3 minutes.

The Rework Podcast

Principles of Communication

October 23, 2024

27 min episode · 2 min read

Jason Fried,Kimberly Rhodes,David Heinemeier Hansson

Episode

27 min

Read time

2 min

Topics

Productivity, Product & Tech Trends, Philosophy & Wisdom

AI-Generated Summary

Published Dec 25, 2025

Key Takeaways

✓Publishing velocity: Write and ship content in one day rather than spending three days perfecting it, because inspiration is perishable and additional editing time often adds minimal value while killing momentum and completion likelihood.
✓Response time expectations: Never require immediate responses unless it's a true emergency. The expectation of instant replies is toxic to productivity. Use phone calls specifically for urgent matters, making the medium itself signal importance rather than assuming all messages demand speed.
✓Clarity in high-stakes communication: When discussing important topics, use simple, direct language with minimal surface area for misinterpretation. Avoid flowery writing that can be perceived multiple ways, as ambiguous words will typically be understood in the most harmful interpretation possible.
✓Time as decision tool: Let heated discussions cool over days rather than forcing immediate resolution. Arguments that feel critical in the moment often become inconsequential within 24 hours, and waiting allows people to reconsider positions and acknowledge when others are right.

What It Covers

Jason Fried and David Heinemeier Hansson explain their 30-point guide to internal communication at 37signals, covering principles like avoiding immediate response expectations, using long-form writing over chat, and shipping content quickly without approval processes.

Key Questions Answered

•Publishing velocity: Write and ship content in one day rather than spending three days perfecting it, because inspiration is perishable and additional editing time often adds minimal value while killing momentum and completion likelihood.
•Response time expectations: Never require immediate responses unless it's a true emergency. The expectation of instant replies is toxic to productivity. Use phone calls specifically for urgent matters, making the medium itself signal importance rather than assuming all messages demand speed.
•Clarity in high-stakes communication: When discussing important topics, use simple, direct language with minimal surface area for misinterpretation. Avoid flowery writing that can be perceived multiple ways, as ambiguous words will typically be understood in the most harmful interpretation possible.
•Time as decision tool: Let heated discussions cool over days rather than forcing immediate resolution. Arguments that feel critical in the moment often become inconsequential within 24 hours, and waiting allows people to reconsider positions and acknowledge when others are right.

Notable Moment

The founders describe having no approval process between them after 20 years of trust. They publish directly without legal review or editorial back-and-forth, believing the alternative to shipping imperfectly is never shipping at all.

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 I'm joined as always by the cofounders of thirty seven signals, Jason Fried, and David Heinemeier Hanssen. On the thirty seven signals website, there is a write up called the thirty seven signals guide to internal communication. There are 30 different points of how we aim to communicate both internally and with the public. And so today, I thought we would talk a little bit about that. I'll link to this in the show notes. We're not gonna go over all 30, but I pulled out a few that I wanted us to discuss. But before we get to that, I don't even know how this started, to be honest. Like, did you guys write it together? Did one of you write it? Kinda tell me the story of how this came to be, and then we'll kinda dig into it. I wrote this primarily as an answer to a series of very similar questions I was getting from people, primarily on Twitter. I'd say something, and they say, well, how do you do it? Or, I don't think that's a good idea. Well, what's a good idea? So I would just kinda answer these things one off, which is why if you go through the list of 30, they're kind of tweet length answers in a sense. So I just started writing this list of, like, questions I've been asked recently, questions I was asked a long time ago, things I know that people are curious about, and embodies things about meetings. It talks about duration of a meeting. It talks about, like, long form writing, short form writing, when to decide on something, when not to, things like that. And at the end, I kinda get into more detail, which is, you know, about, like, how do we use Basecamp for this? How do we talk about kickoffs and heartbeats and a variety of other things? So it was sort of this all encompassing guide to, basically, how we talk internally, primarily principles based. It's not, like, specific except for the bottom part. The bottom part is way more specific. The top is, like, things to keep in mind, things to think about, principles to consider, philosophies to think about as you're wondering how to communicate internally. And then I put it together in this format because I was originally thinking about writing it as more of a, again, like a long form paragraph based thing. But then I realized it's actually easier to digest this way. And further, like, I didn't feel like I wanted to have any filler connecting these 30 things, which are not really connected. They're just separate things. They're like separate thoughts. They're separate thoughts. I mean, you could certainly, like, pull a bunch together and say there's groups of them or whatever, but this is what you …

Get the full transcript (5,469 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 →