How do you design a calmer company or work environment using the Basecamp principles?
Structure, defaults, and policies that make urgency the exception rather than the operating mode
Jason Fried and David Heinemeier Hansson’s "calm company" philosophy holds that urgency, interruption, and growth-at-all-costs are design choices, not necessities — and that deliberately designing against them produces both better work and a more sustainable organization. The practices are drawn from their books (Rework, It Doesn’t Have to Be Crazy at Work) and direct Basecamp experience; they are practitioner-tested but not controlled-trial validated.
Most organizations operate in a permanent state of manufactured urgency — every message is urgent, every meeting is urgent, every deadline is a crisis. Fried and Hansson argue this is a design failure, not a market reality. Their calm company approach redesigns the defaults: asynchronous communication first, long uninterrupted blocks instead of meeting-saturated days, goals that are realistic rather than aspirational to the point of absurdity. The practices below operationalize the principles, with honest grading of what is observed vs. merely practitioner-asserted.
The practices (7)
Real-time communication (Slack, calls, meetings) fragments attention and creates the expectation of immediate responses, which keeps everyone in reactive mode. Asynchronous communication (written, with an explicit response window) respects the receiver’s attention schedule and forces the sender to think more carefully before writing — which improves the quality of communication and dramatically reduces its volume.
- 1Set a team or personal default: unless something is genuinely time-critical, communicate in writing with a 24-hour response window.
- 2Turn off or mute synchronous message notifications except during designated response windows.
- 3When you feel the urge to send a real-time message, ask: "Does this require their answer in the next hour?" — if not, write it asynchronously.
- 4Write asynchronous messages with enough context that they do not generate four follow-up questions.
Attention residue research shows that real-time interruptions impose significant recovery costs; asynchronous communication reduces these interruptions. Organizations using async-first structures report higher deep-work time.
Honest caveat: Research on async-first workplaces is mostly case-study and survey; controlled comparisons between synchronous and asynchronous-default teams are limited. Coordination costs of async can be higher for certain task types.
- — Leroy (2009), attention residue, Organizational Behavior and Human Decision Processes
Practice this with IX Coach
Reading about a practice changes nothing on its own. IX Coach turns these into a guided, adaptive routine — discerning where you are in real time and walking the practice with you, session after session.
Start with IX Coach →