Written vs Verbal, Sync vs Async

The last four pages taught you to lead with the point, write so people read, speak so people act, and listen and ask well. Each of those assumed you’d already chosen how to deliver the message — in a document, a meeting, a quick chat, a call. That choice is not a detail. Pick the wrong channel and even a perfectly worded message can misfire.

This page gives you a simple map and a decision rule. By the end you’ll be able to look at any message you’re about to send and ask two quick questions — write or speak? and now or later? — and land on the channel that fits.

The two axes

Almost every way you communicate at work sits on two axes.

The first axis is written vs verbal. Written means words on a screen or page — an email, a message, a document, a shared note. Verbal means spoken words — a meeting, a call, a hallway conversation, a video huddle.

The second axis is synchronous vs asynchronous. Synchronous (“sync”) means everyone is present at the same moment: a meeting, a phone call, a live chat where you’re both typing in real time. Asynchronous (“async”) means you send now and the other person responds when they can: an email, a recorded message, a document left for review.

Put the two axes together and you get four quadrants:

                 SYNCHRONOUS (now)        ASYNCHRONOUS (later)
              +-------------------------+-------------------------+
   VERBAL     |  meeting, phone call,   |  voice note,            |
   (spoken)   |  video call, huddle     |  recorded video message |
              +-------------------------+-------------------------+
   WRITTEN    |  live chat, war-room    |  email, doc, message,   |
   (text)     |  thread, screen-share   |  wiki page, memo        |
              +-------------------------+-------------------------+

Each quadrant is good at some things and bad at others. The whole skill is knowing which is which.

What each quadrant is good and bad at

Async written (email, doc, message) is the workhorse. It’s good at carrying information precisely, at reaching many people at once, at letting the reader engage on their own schedule, and — crucially — at leaving a record. It’s bad at emotion, nuance, and back-and-forth: tone gets lost, a two-sentence question can spawn a twelve-message thread, and a sensitive point can read as cold or hostile.

Sync verbal (meeting, call) is good at exactly what async written is bad at: reading tone, resolving ambiguity fast, handling emotion, building trust, and untangling anything that needs rapid give-and-take. It’s expensive, though — it consumes everyone’s time at once — and it evaporates. Say something important in a meeting and, a week later, half the room remembers it differently.

Sync written (live chat, a war-room thread during an incident) is fast and leaves a trail, but it’s shallow — good for quick coordination, poor for depth or feeling.

Async verbal (a voice note or a short recorded video) is the least-used quadrant. It adds warmth and tone to an async message without demanding a live meeting — useful when the words alone would sound cold but the matter isn’t urgent enough for a call.

Match the channel to the purpose

Here’s the core of the framework. Don’t ask “what’s my habit?” or “what’s easiest for me?” Ask: what does this message need to do?

• Information, plans, decisions of record → async written. Anything the reader needs to absorb carefully, refer back to, or act on later belongs in text they can keep. A project update, a policy, a decision and its reasons, meeting notes.
• Conflict, ambiguity, emotion, trust → sync verbal. Anything where feelings are in play, where you’ll need to read the other person and adjust, or where a misread could do damage. Difficult feedback, a disagreement, bad news, a delicate negotiation.
• Quick coordination → sync written, or a short live chat. “Are you free at three?” doesn’t need a meeting or a memo.
• Warmth without a meeting → async verbal. A thank-you, a bit of encouragement, a nuanced heads-up that would sound curt in text.

In practice — the same news, two channels

A ward manager in a hospital needs to tell the team two things. First: the new shift-handover checklist starts Monday — six steps, in order. Second: one nurse’s repeated late arrivals are now affecting the team.

The checklist is information of record: she writes it, so everyone can re-read the six steps at 6 a.m. when they need them. The lateness is sensitive and emotional: she says it, in a private conversation, where she can read the nurse’s face, hear the reason, and adjust. Same manager, same morning, two completely different channels — chosen by purpose, not habit.

The rule of thumb: heat moves you toward real-time and voice

If you remember one thing from this page, remember this: the more emotional, sensitive, or high-conflict a message is, the further you should move toward real-time and toward voice or face.

Think of it as a dial. A neutral status update sits at one end — async, written, fine. As the emotional temperature rises — disagreement, disappointment, bad news, anything that could wound or be misread — you slide the dial the other way: first toward a call, then toward face-to-face. The reason is simple. Text strips out tone, and a stripped-down message defaults to the worst reading in the receiver’s head. Voice and face put the tone back. They also let you course-correct the instant you see the message landing wrong — which written words, sent and gone, never let you do.

   low heat  ------------------------------------------> high heat
   async text   →   async voice   →   live chat   →   call   →   in person

The common trap — hiding behind text for the hard stuff

The hardest conversations are the ones we most want to avoid — so we reach for the channel that lets us avoid the other person’s reaction. We fire off the tough feedback, the “we’re letting you go,” the sharp disagreement over message or email, telling ourselves we were just “being efficient.” We weren’t. We were dodging the discomfort of a live human response, and we pushed the cost onto them: they read hard news alone, with no tone to soften it and no way to ask a question. The rule is nearly absolute — if it’s hard to say, that’s the signal to say it, not type it.

The cost of the wrong channel

Picking the wrong quadrant isn’t a small inefficiency. It has two classic, expensive failure modes.

A hard message sent as text that should have been a call. You write, “We need to talk about your performance — let’s find time.” You meant it neutrally. The reader spends the next eighteen hours in a spiral of dread, reading menace into every word, rehearsing their defence. By the time you actually talk, they’re braced for a fight over something that was going to be a supportive coaching chat. The text didn’t save time; it manufactured fear and damaged trust before you said a word.

A meeting that should have been an email. You gather nine people for forty-five minutes to “walk through” a status update. Everyone could have read it in four minutes on their own schedule. You just spent roughly seven person-hours delivering information that needed no discussion — and taught the team that their calendars aren’t respected.

The evidence — meetings are costlier than they look

Surveys of managers and knowledge workers consistently find that a large share of meeting time is rated as unproductive, and that the true cost of a meeting is easy to underestimate because it’s paid by everyone in the room at once. The useful reframe: before booking a meeting, multiply its length by the number of attendees to get the real time cost. A one-hour, ten-person meeting isn’t an hour — it’s more than a full working day of someone’s time. Much of it would be cheaper, and just as effective, as something people read.

Case study — Amazon’s six-page memo

Sometime in the early 2000s Amazon banned slide presentations for major meetings in favour of a narrative memo of up to six pages, read in silence at the start of the meeting. The lesson isn’t “always write memos.” It’s a sharp illustration of channel choice: a decision that needs careful reasoning deserves a written artefact dense enough to hold that reasoning — something slides and talking can’t do — and the synchronous meeting is then spent on discussion, not transmission. Write the thinking; meet on the judgement. (The exact page limit and rules have varied; the principle is what endures.)

The record problem: verbal decisions evaporate

There’s one failure that catches even people who choose channels well, so it deserves its own warning.

Verbal decisions evaporate. A decision made in a meeting or on a call feels solid in the moment and is gone within days. People remember different versions. The person who wasn’t there never learns it. Weeks later the “decision” is relitigated because no two people agree on what was actually decided.

So the rule is: anything that must persist needs a written trail, even if it started as a conversation. The conversation was the right channel for reaching the decision — the ambiguity, the debate, the reading of the room all needed sync verbal. But the output has to be written down: the decision, who owns it, by when. This is why good meetings end with someone typing the notes, and good calls end with a follow-up message: “Confirming what we agreed…”

You’ll often use two channels in sequence, and that’s not a failure of planning — it’s the point. Talk to decide; write to remember.

In practice — the two-channel handoff

A café owner and her head barista argue for twenty minutes about whether to drop a slow-selling drink. The argument needs to be live — there’s disagreement, some ego, a lot of “but the regulars…”. They talk it through and land on a decision: pull it for a month, review sales, then decide for good. That night the owner sends one short message: “Confirming — [drink] comes off the menu tomorrow, we review sales on the 1st, and decide then. Shout if I’ve got that wrong.” The heat needed voice. The decision needed ink.

How it connects

Channel choice is the setting your other communication skills operate inside. Leading with the point and writing that gets read make your async written messages land; speaking so people act and listening make your sync verbal ones land. And it sets up the next page, over-communicate and tailor the message: once you can pick the right channel for one message, the question becomes how to repeat and reshape a message across channels and audiences so it actually sticks.

Try this

This week, catch yourself once before you send a hard message by text — a piece of critical feedback, a disagreement, some bad news. Pause and run the dial: how much heat does this carry? If the answer is “a lot,” close the message window and either call the person or walk over. Notice how differently it goes. Separately, look back at your last week of meetings and ask of each: could this have been something people read? Cancel or convert one recurring meeting that’s really just information transfer.

Reflect

1. Think of a recent message that misfired. Was it partly the wrong channel — text where you needed a call, or a meeting where you needed a doc?
2. Which channel is your default — the one you reach for out of habit regardless of the message? What kind of message does that default serve badly?
3. When you avoid a hard conversation by putting it in writing, what discomfort are you actually dodging — and who ends up paying for it?
4. Which of your regular meetings exist mainly to transmit information that people could read? What would you lose, and gain, by converting one to a document?
5. Where in your work do decisions “evaporate” — get made verbally and then forgotten or relitigated? What written trail would fix it?

Show reflections

1. The aim is to separate what you said from how you sent it. Often the words were fine and the channel was the fault — a tone-sensitive message sent as tone-free text. Naming that turns a vague “that went badly” into a repeatable fix.
2. Everyone has a comfort channel — the chronic emailer, the person who calls a meeting for everything. Your default is invisible to you until you name it. The useful insight is the specific message type it fails: the emailer mishandles conflict, the meeting-caller wastes time on information.
3. This targets the trap head-on. Honest answers usually land on fear of the other person’s reaction. Seeing that the cost doesn’t vanish — it just transfers to the receiver, who now processes hard news alone — is what makes the “say it, don’t type it” rule stick.
4. Good answers weigh it both ways: a document costs you writing effort and loses the room’s energy, but it buys back everyone’s time and creates a record. The best candidates to convert are status and update meetings with little real discussion.
5. Look for the recurring argument that keeps coming back because “we decided that already” but nobody wrote it down. The fix is cheap — a one-line confirmation after the conversation — and it’s the highest-leverage habit on this page.