Skip to content

The One-Meeting Rule: How Eliminating Meetings Improved Output

Most recurring meetings are coordination teams do not need, and they fragment deep work. The one-meeting rule gives each team a single recurring meeting per week and replaces the rest with async standups, written decision documents with comment deadlines, and office hours, which requires training in async writing.

01

What problem did this system solve?

Engineers were spending a large share of their working hours in meetings, leaving fragmented blocks too short for deep technical work.

I audited the calendar data for an engineering organization over several weeks. The average engineer attended a heavy load of meetings every week. The average meeting duration was substantial. Total meeting time: a large share of each engineer’s productive week (after accounting for lunch, breaks, and administrative overhead). But the real cost was not the meeting time itself. It was the fragmentation. The average uninterrupted block between meetings was short. According to research on task switching costs, recovering full cognitive context after an interruption takes 15-23 minutes. A short block, after time spent on context recovery, leaves little productive work. Engineers were operating at a fraction of their cognitive capacity.

02

How was the intervention designed?

I implemented a single rule: each team gets one recurring meeting per week. Everything else must justify its existence or become asynchronous.

The rule was simple but the implementation required replacing the coordination that meetings provided. I designed replacement mechanisms.

First, daily async standups in Slack. Each engineer posts a short update each morning: what they completed, what they are working on, and any blockers. This replaced the daily standup meetings that filled every week. The async version took only minutes to write and to read all team updates. Net time saved: a meaningful amount per person every week.

Second, decision documents for anything requiring group input. Instead of scheduling a meeting to discuss options, the proposer writes a short decision document with the options, their recommendation, and a fixed comment deadline. I tracked decisions in the first quarter. Most were resolved through comments alone. A few required a synchronous conversation, which was scheduled on-demand. This replaced an estimated run of “discussion” meetings every week across the organization.

Third, office hours. Each team lead held open office hours weekly, replacing the ad hoc “quick question” meetings that accounted for a large share of all calendar events. Engineers could drop in or not. The office hours were used well below capacity, suggesting that many of those “quick question” meetings were unnecessary.

03

What were the measurable outcomes?

Average meeting time per engineer dropped sharply. Average uninterrupted work blocks grew from short fragments to long stretches. Features shipped per sprint increased within the first few sprints. Bug reports did not increase, suggesting the additional output was not produced at the expense of quality. The subtraction principle applied directly: removing meetings did not create a coordination vacuum. It revealed that most of the coordination was unnecessary.

04

What would I change in hindsight?

I would have implemented the transition more gradually and invested more in training people to write effective asynchronous communication.

The first weeks were chaotic. Engineers who relied on meetings for information flow felt disconnected. Three team leads reported that they “did not know what their team was doing.” This was a communication skill gap, not a structural failure. The async standup format required a different writing discipline than most engineers had developed. I should have run a training period on async communication before cutting meetings. I also underestimated the social function of meetings. Some engineers genuinely valued the face-to-face interaction. I added optional weekly social time (no agenda, no outcomes required) to address this. Attendance was only partial, confirming the need. The approach connects to what I described in remote work communication infrastructure: async-first requires explicit investment in communication design, not just calendar management. As Basecamp’s research on remote work documented, the transition from synchronous to asynchronous is fundamentally a writing and reading skills challenge.