The Asynchronous Status Communication System
Replace status meetings with written updates -- save 8 hours by writing for 8 minutes
The Asynchronous Status Communication System is Jason Fried's framework for eliminating status meetings -- which he calls the scourge of the modern workplace -- and replacing them with written asynchronous updates. The math is simple: when you pull eight people into a one-hour meeting, you have not spent one hour but eight. And those eight hours are rarely productive -- most people wait for their turn to speak, half-listen to updates that do not concern them, and mentally prepare their own report rather than engaging.
At Basecamp, meetings are rare and almost never involve more than three people. The company's 'Automatic Check-ins' feature replaces daily standups and weekly status meetings. At 5pm, Basecamp automatically asks everyone 'What did you work on today?' Written responses are shared with the team.
The system has multiple advantages over meetings: written updates create permanent, searchable records; team members respond thoughtfully rather than being put on the spot; people read updates when it suits their workflow; and the entire process takes minutes per person rather than consuming an hour of everyone's time. The broader philosophy is that real-time communication should be the exception, not the rule, and that writing forces clarity in a way that speaking often does not.
- An eight-person, one-hour meeting costs eight hours, not one.
- Most people in status meetings are waiting to speak, not listening.
- Writing forces clarity in a way that speaking often does not.
- Real-time communication should be the exception, not the rule.
- Meetings should be the last resort, not the first option.
- Replace Status Meetings with Written Check-InsImplement a daily or weekly written check-in system that asks team members simple questions: What did you work on today? What are you planning for tomorrow? Are there any blockers? Post these to a shared space where everyone can read them when ready. At Basecamp, this happens automatically at 5pm each day. Written responses take a few minutes per person, compared to the 30-60 minutes per person that status meetings consume. The written format also creates a permanent, searchable record that meetings never produce.Pro tipStart with a simple daily question: 'What did you work on today?' Do not overcomplicate the format. Simplicity drives adoption.WarningThe transition requires trust. Leaders must trust that work is getting done without verbal confirmation. Team members must trust that written updates will be read and valued.
- Enforce a Three-Person Meeting MaximumWhen meetings are absolutely necessary -- for genuine discussion, decision-making, or collaborative problem-solving -- limit attendance to three people maximum. This keeps discussions focused and ensures everyone present has a meaningful role. Large meetings become performances where people speak to demonstrate involvement rather than contribute substance. The three-person rule eliminates the audience effect and produces genuinely productive conversation.Pro tipIf more than three people need to be informed of a meeting's outcome, have the three participants write up the decision and share it asynchronously.WarningSome people will feel excluded. Communicate clearly that the three-person rule is about effectiveness, not importance. Everyone receives the written summary.
- Default to Asynchronous for All Non-Emergency CommunicationShift the organizational default from real-time communication (meetings, calls, instant messages) to asynchronous communication (written updates, documents, recorded videos). Most work communication does not require an immediate response. By defaulting to async, teams protect focused work time while staying informed and aligned. This produces better thinking because writing forces you to organize your thoughts and strip away the filler that verbal communication encourages.Pro tipClassify communication urgency into tiers: immediate (call), same-day (direct message), this-week (email or shared document). Most things that feel immediate are actually this-week.WarningAsync-first does not mean async-only. Genuine emergencies, complex emotional situations, and difficult conversations still benefit from real-time interaction.
At Basecamp, the Automatic Check-ins feature replaces weekly status meetings, daily standups, and ad-hoc status requests. At 5pm each day, the system automatically asks every team member 'What did you work on today?' Members write thoughtful responses that are shared with the team. Anyone can read any update at any time, creating a permanent record of work progress.
When meetings at Basecamp are absolutely necessary, the company follows a strict three-person maximum. This ensures everyone present has a meaningful role in the conversation. Jason Fried observed that large meetings become performances where people speak to demonstrate involvement rather than to contribute genuine substance. Limiting attendance to three eliminates the audience dynamic.
Jason Fried developed this system as co-founder and CEO of Basecamp (formerly 37signals), where he has been building remote-first work practices since the company's founding in 1999. Basecamp was a pioneer of remote work long before it became mainstream, and Fried observed early on that the default meeting culture of traditional companies was fundamentally incompatible with productive knowledge work. The specific trigger was recognizing that status meetings consumed enormous organizational resources for information that could be communicated asynchronously in a fraction of the time. Fried and co-founder David Heinemeier Hansson built the Automatic Check-ins feature directly into Basecamp's product, making asynchronous status updates a core part of the platform used by millions of teams. Their books 'Remote' and 'It Doesn't Have to Be Crazy at Work' further developed these ideas.