Synchronous Communication

This mode went unnamed for a long time. Sitting in the same office, you turned around and asked, and that was communication in full. A name became necessary only once the other mode existed.

The problem surfaced when half a team moved to another city or another time zone. One 30-minute meeting with five attendees becomes six in the morning for somebody. Keeping it means one person gives up sleep every week; moving it means somebody else pays the same price. The conversation about when to hold the meeting started running longer than the meeting. No arrangement of the calendar makes that cost disappear.

That's when a question got asked for the first time, and the question created the distinction: does this actually require both of us to be present? Asked plainly, about half of it didn't. Going around the room with last week's progress didn't. Announcing something already decided didn't. Announcements are the easiest half to move into writing and usually the last half anyone moves.

So the two kinds of communication got separate names, so that each occasion could be assigned to one of them. The point isn't reducing this mode; it's choosing where to spend it. Spent well, it's the fastest instrument available.

For it to work at all, two or more people's time has to be free in the same window. Which makes the cost multiply by headcount. A 30-minute meeting with five attendees spends two and a half hours of the company, plus the focus time broken on either side of it. Two half-hours around a meeting are rarely worth the same as one clear hour.

What that cost buys is round-trip speed. Correcting one misunderstanding takes seconds. In writing, the same correction takes half a day, and during that half day the other person keeps working from the wrong understanding. So the occasions this mode suits are the ones needing many round trips. One round trip is almost never worth a meeting.

What actually makes it pay off is the preparation and the closing.

1. Circulate a document first. With background and options written down and attendees having read them, the 30 minutes goes to the decision; without it, 25 of those minutes go to describing the situation. That's why documentation-first — writing before speaking — is the floor this mode stands on.
2. Put the purpose in the invitation. Say whether this is a decision, a discussion, or a broadcast, and if it's only a broadcast, don't open the slot.
3. Invite only the people needed. Anyone not part of the decision follows through the notes. Three extra observers raise the cost and lower the number of people who speak, which is the worst trade available.
4. Write it down before it ends: what was decided, and who does what by when. Skip that and it becomes a decision only the people in the room know about, and two months later the same discussion reopens. The record is also what lets people who weren't there stop asking.
5. Secure the overlapping window in advance. A fixed stretch when everyone is present is core time, and pinning it to 11 to 4 leaves the rest of the day for people to arrange themselves. Without a named window, scheduling becomes a negotiation every time.

Five occasions where this mode earns its cost.

1. Decisions where opinions differ. Three people holding three different proposals need about six round trips to converge in writing, which is three days. In one room it's 40 minutes.
2. Transferring context for the first time. Explaining a product's structure to a new hire, or opening a new project. The receiving side doesn't know what they don't know, so asking back is continuously necessary. Getting this one wrong compounds quietly for months.
3. Incident response. While the service is down, judgment is needed every few minutes and there's no room for anything written.
4. Difficult conversations between people. Feedback and resolving conflict need tone and expression to travel along, and the same sentence reads colder in writing.
5. Generating options together. Throwing out ideas runs on one person's remark pulling out another person's thought, and the combinations that come out of a room don't come out of one person writing a document.

Where it doesn't fit is equally clear. Status sharing, approving something already decided, and passing along information people can read have no reason to be here. Moving those three into writing cuts meeting time nearly in half on many teams, and almost nobody misses them.

At Pagedeck half the team works remotely and one person is three hours off. So meetings only get scheduled between one and four in the afternoon, and everything outside that goes to asynchronous communication. The daily meeting moved into writing, with one 40-minute slot a week kept. The only thing that slot handles is items where opinions split, which is the one thing writing handles worst.

"I won't book a meeting for this. It's a broadcast — I'll send the document."

Weighing the purpose against the cost of opening a slot.

"Three proposals on the table. Let's take 30 minutes; in writing it's three days."

Choosing this mode on the number of round trips.

"Write down just the decisions before we close."

Without the record, the decision disappears.

The week Pagedeck cleaned up its meetings, Mia counted the last month's by purpose. Of 32 meetings, eleven were broadcasts, and multiplying the attendees by the minutes for those eleven came to 22 hours.

After moving the eleven into writing, the character of the remaining meetings changed. Fewer people attended, and the agenda was usually one split opinion. Theo said the bigger difference wasn't the reduced count but that there was now something to read before walking in.

The most common belief is that this mode is fast. One round trip takes seconds, so it feels that way. But getting started is slow. Finding 30 minutes where five calendars overlap usually lands two days out, and nothing progresses during those two days. A question that would come back in half a day in writing comes back in two days once it's a meeting. The speed of one round trip and the speed of finishing are different numbers, which means the honest comparison is calendar days rather than minutes in the room.

The other frequent belief is that removing meetings produces asynchronous work. The other mode looks like the absence of meetings, so that inference comes easily. But strip the meetings without building a replacement and decisions stop happening. Working in writing requires something to read first, and a stated expectation of who responds by when. Teams that cut meetings without that preparation find ten undecided items piled up two weeks later.