Glance at a knowledge worker’s week and you will not see a shortage of collaboration. You will see a surplus of surface: stacked invites, polite syncs, and conversations that feel like progress because everyone was present for them.
Most of us do not schedule those meetings because we have carefully concluded that live debate is the cheapest way to move the work. We schedule them because talking feels like the legitimate first move.
Building first feels lonely. Sending a written ask feels abrupt. Declining a “quick sync” feels rude. So we rent a room — Zoom or glass — and we process status, assignment, mild disagreement, and a surprising amount of social nicety through the most expensive medium we have: everyone’s simultaneous attention.
Call the premium what it is: a talk tax.
The tax is not merely “time on a calendar.” It is the cost of enlarging the surface area of discussion — how many people can change the plan while everyone is watching. Efficient work does the opposite. It builds most of the thing in writing or code, pushes or pulls the minimum information asynchronously, and spends scarce live sync on the thin slice that actually requires presence.
This is the uncomfortable inversion. The talk-heavy, build-light pattern feels safer. The build-heavy, talk-light pattern usually works better. (The “90/10” version of that claim is a provocation about emphasis, not a stopwatch rule for your week.) The rest of this essay is about why the expensive path feels rational — and how to shrink the surface without becoming the person who “doesn’t do meetings.”
A familiar Wednesday
Here is a composite, assembled from meetings many of us have booked or endured.
Alex needs engineering to prioritize a billing edge case before month-end. Alex could write four sentences: what breaks, who feels it, what “fixed” means, and the date that matters. Instead Alex sends: “Quick sync to align on billing prioritization?” Five people accept. Twenty-five minutes later the group has restated the problem, swapped two anecdotes, agreed that it “matters,” and scheduled a follow-up. Nobody left with an owner and a definition of done. Everybody left having performed collaboration.
Alex was not foolish. Alex bought a social receipt. If the edge case slips, there was a meeting. The talk tax purchased legitimacy. It did not purchase the fix.
Same week, different invite: two leads disagree about whether to cut a customer-facing feature to hit a compliance date. Values collide. The tradeoff is ugly either way. They meet with a one-page pre-read and a single decision question. That room earns its surface — not because it was on a calendar, but because the work was the disagreement between people who have to live with the call.
Spotting rule: If you can delete the invite and replace it with a message that names owner + ask + done + when, you are looking at talk tax. If you cannot — because values collide, trust is thin, or the work is being in the room together — you are looking at a meeting that may be earning its surface.
The same rule applies to recurring invites. A standing meeting is often a talk tax on subscription: the surface stays open whether the week produced a real decision or not. If the series cannot pass the spotting rule most weeks, the series is the product, not the work.
What you are actually paying
A meeting’s sticker price is duration times headcount. The talk tax shows up in the medium: live verbal social space.
In a room, ambiguity is cheap. You can say “we should align on direction” without defining direction. You can nod through a status update that could have been three bullets. You can expand scope because someone had a thought in real time and nobody wanted to be the person who said “that’s a different document.” Niceties are not optional garnish in that medium; they are part of the protocol. Every protocol has overhead.
Surface area grows with:
- Attendees who can reopen decisions live
- Live ambiguity with no written “done”
- Social padding required to keep the room feeling kind
A fifteen-minute “quick sync” with five stakeholders can cost more than a forty-five-minute decision between two owners — because the first maximizes renegotiation surface, and the second may actually decide.
This is not only a vibes complaint. Microsoft’s Work Trend Index Annual Report (2022) reported roughly a 252% increase in weekly meeting time for the average Teams user from February 2020 to early 2022, with chats rising alongside meetings rather than replacing them. Later Work Trend Index releases reported the same skew: more time in communication surfaces than in creation tools, and a large share of meetings landing in peak focus hours. The calendar did not merely get fuller. It colonized the hours that used to be for making things.
Still: volume is not the deepest problem. The deepest problem is default. We reach for high-surface talk before we ask whether the job needed that surface at all.
Why the expensive path feels safer
If talk-first were only stupidity, smart people would have quit. They have not. The tax feels like insurance.
Permission. A meeting is a socially licensed start line. Leaving with “alignment” is a receipt you can wave if the work later fails. Starting from a draft without a ritual can feel like going rogue — even when the draft is better than the ritual. When the content is thin and the ritual is the point, call those invites permission meetings. A short live kickoff before hard contested work can still be useful. The tax is the stamp that replaces the work.
Ambiguity aversion. Conversation lets vagueness stay shared. Writing forces edges: owner, ask, deadline, definition of done. Edges create accountability, and accountability creates the fear that you will be wrong in public — permanently. So we stay where wrongness can be softened in real time.
Belonging works the same way. Tone, care, and status checks are easier face-to-face (or face-to-tile). A crisp async message can read as cold even when it is respectful. Many “alignment meetings” are partly care work wearing a project title. That care is real. Using a calendar invite as the only vehicle for care is what creates the tax.
Status theater is the career version: being in the room signals diligence; building alone is invisible until output appears. In organizations that reward presence more than artifacts, talk-heavy weeks are rational — especially when a manager’s anxiety is soothed by faces on a grid.
And then there is the feeling of progress. Debate feels like coordination even when nothing is decided. A written brief is coordination, but it offers less of the sensation of being heard. If you are optimizing for that sensation, you will schedule the room when the work needed a paragraph.
None of this makes you weak. It makes you adapted to environments where social risk is priced higher than throughput. Sometimes the tax is not optional at all: it is tribute to a power structure that demands face time.
Even then you can shrink surface inside the mandatory meeting — pre-read, single decision question, named owner — instead of treating the hour as an open mic. Pay tribute if you must. Do not tip.
What we are not arguing
The skeptic’s version of this essay writes itself: You want to kill human connection. You want everything to be a ticket. You privilege fluent writers. You will cancel the kickoff and then wonder why nobody trusts each other.
Keep the meetings whose job is presence.
Kickoffs, intros, grief, celebration, mentoring, and truly contested tradeoffs — where values collide and the decision cannot be separated from the people — are not “async failures.” They are human work. A tool or essay that pretends otherwise is lying for engagement.
Also true: writing-first can favor people who write easily in the dominant language of the company. High-surface meetings punish a different set of people: caregivers on fragmented schedules, roles that need deep work, anyone whose best thinking does not happen on the spot. If your team moves async, invest in short genres and templates so “good writing” means clear, not literary. Voice-to-text counts. A five-line ask beats a performative essay. The equity move is better written defaults — not an infinite Zoom as the accessibility strategy.
And systems matter. Calendar software makes “Add meeting” easier than “Write brief.” Manager norms can punish anyone who opts out. Individuals did not invent those incentives. Individuals still choose the next invite they control — and how they answer the ones they do not.
Shrink the surface
The alternative is not monastic silence. It is smaller surface area for the same job.
Async push — a brief that informs without a room: what changed, what it means, what you need people to know. No RSVP required for comprehension.
Async pull — a written ask: who owns the answer, what “done” looks like, by when. Pull is how you collect input without hosting a debate club.
Narrow sync — live time reserved for contested decisions, co-creation, or relationship. If none of those are present, you are probably paying talk tax for a status performance.
Async is not automatically low-tax. A Slack thread that pulls in the same five people, renegotiates live, and never lands an owner is a meeting wearing sneakers. The medium changed; the surface did not. Low-tax async is specific: bounded ask, named owner, definition of done, and a bias toward closing the loop in writing — not recreating the room in scrollback.
The build-first variant is the same idea with sharper teeth: produce most of the artifact first (doc, prototype, decision memo, even a prompt an agent can run), then talk about what remains sharp. Amazon’s six-pager tradition — widely described as silent reading first, discussion second — is the corporate ancestor of writing as the gate to talk, not talk as the gate to writing.
Return to Alex. The invite was:
Quick sync to align on billing prioritization? (5 people, 30 min)
The smaller-surface version is:
Owner: Sam (Eng)
Ask: Can we sequence the billing edge case (duplicate tax on retry) ahead of the export polish for the month-end cut?
Done: Yes/no + if no, what date is realistic
By: Thursday 2pm
Happy to jump on a 15-min only if the tradeoff is contested.
Same job. Fraction of the surface. If Sam replies “contested — finance disagrees,” then you earn the room.
If you are on the invite, not the organizer, you still have leverage. Propose the cheaper medium:
Happy to help async — send owner / ask / done / when and I’ll respond by Thursday. If this is actually contested, flag me and we should sync.
You are not rejecting the person. Many organizers accept with relief. Some will insist on the room anyway. You have still narrowed what the room is for.
When you need language that declines the room without declining the person, say the medium out loud. This looks like a written ask, not a sync. We need an owner and a deadline more than we need debate surface. If it’s contested, let’s meet; if it’s status, let’s not.
If you want help running that triage — meet versus don’t meet, with editable email and short-message substitutes when a room is optional — use Interview on Make This Meeting a Text. It will not cancel your kickoff for you. It should not. It will help you notice when the invite is mostly talk tax.
After you already paid
Sometimes you will hold the meeting. Politics, urgency, or genuine contention will demand it. Paying talk tax once can be rational. Paying it twice is costly: once in the room, again when nobody turns the talk into work.
That second payment looks like recaps nobody reads, action items without owners, and a week later the same “quick sync” to remember what you already said. The meeting was never the work. The translation was. What you want afterward is not another paragraph of vibes — it is an executable brief: objective, constraints, tasks, owner, and how you will know it is done — something a human or an agent can run without re-litigating the room.
When the room already happened, transform the notes into a prompt artifact. That path does not refund the tax you already paid. It stops the double charge.
One meeting, one smaller surface
Pick one upcoming invite — one you own or one you were added to. Apply the spotting rule. Status, FYI, assignment, input collection — or contested decision, co-creation, relationship?
If it is the first list, draft the written ask (or reply proposing one). If you want a guided pass, start at https://makethismeetingatext.site/interview. If it is the second list, keep the meeting — and walk in with a tighter surface: a pre-read, a decision question, a named owner.
The goal is not a life without talk. The goal is to stop using talk as the default container for work that writing can finish. Shrink the surface. Spend human presence on what only human presence can do.