2026-05-08
May 8, 2026
The decision happens in writing. The meeting is the rehearsal. Most teams have it backwards — and pay for it in calendar burn.
The instinct when something feels stuck is to schedule a meeting. The result is a calendar that looks like a Tetris game, decisions that get re-litigated weekly, and engineers who do their actual work between 6 PM and midnight. The problem isn't the meetings — it's the assumption that meetings are where decisions happen.
Senior TPMs and tech leaders who run on docs flip the model. The decision happens in a written artifact — a DACI sheet, an RFC, a working-backwards memo. The meeting, if it happens at all, is a 25-minute structured review of that artifact. No artifact, no meeting. The standing 60-minute weekly sync is the most expensive piece of furniture on your team's calendar.
Today's deep dive is the case for replacing recurring synchronous ceremonies with three written ones — and what to give up to make space.
The argument for async-first isn't that meetings are bad. It's that recurring meetings are a tax on the highest-leverage time your team has — uninterrupted blocks for thinking. Engineers do their best work in stretches of two to four hours. A 10am standup, a noon design review, and a 3pm planning sync don't add up to 90 minutes of meetings — they add up to a destroyed day.
The replacement isn't fewer meetings. It's three written ceremonies that compound:
1. The decision doc (replaces "let's hop on a call"). When someone says "we need to talk about X," the answer is "write a one-pager with the options and your recommendation, share it Friday, we'll review it Monday." DACI on the doc: one Driver, one Approver, named Contributors, listed Informed. The Approver's job is to read, comment, and decide — not to sit in a room and be persuaded. Effect: decisions get faster (because the meeting was the rate limit), and they stay decided (because the rationale is written down).
2. The weekly written status (replaces the standup, replaces most 1:1 prep). Each engineer posts a Slack thread or Notion entry every Monday: what shipped last week, what's planned this week, what's blocked. Two minutes to write, scannable in 30 seconds. Effect: the manager who actually wants to know what's happening reads ten of these in five minutes, instead of attending five 30-minute syncs and getting half the picture.
3. The pre-read for the only meeting that survives (replaces unprepared discussion). The one synchronous meeting you keep — usually a weekly leadership review — runs on a six-page memo, Amazon-style. First fifteen minutes is silent reading. The remaining time is real argument. Effect: the people who showed up unprepared either prepare next time or stop showing up. Both are wins.
What you give up: the social contact of standups, the hallway-conversation feeling of design reviews, the sense of "alignment" you got from being in the same Zoom. These are real losses for some teams (small, high-trust, co-located, early-stage). For larger teams (8+ engineers), distributed teams, or teams across more than two time zones, the data is consistent: async-first beats sync-default on every measurable dimension that matters — throughput, satisfaction, retention.
The pushback you'll hear: "people won't write." That's not a writing problem; it's a culture problem. You can't make engineers write by mandate. You make them write by making the written artifact the only path to a decision. When the doc is the meeting, the doc gets written.
The pushback you'll hear from yourself: "I lose touch with my team without the recurring sync." Replace it with one 30-minute walk-and-talk per direct report per week. You'll learn more in 30 minutes of unstructured conversation than in an hour of round-robin status.
Try this week. Identify one recurring meeting on your calendar that has met three times without producing a decision or a written outcome. Cancel it. Replace it with a Slack channel and a Friday written summary. Watch what happens. If something genuinely breaks, reinstate it — but with an explicit decision-doc requirement attached. Most don't break.
What it is. Before any new product, feature, or major initiative, write a one-page press release describing the launched outcome — as if it were already shipped — followed by 3-5 pages of FAQs. The PR/FAQ becomes the design doc, the alignment artifact, and the kill criterion. If you can't write the press release, you don't understand the customer enough to build the thing.
When to use it. New initiatives where the right answer isn't obvious; cross-org programs that require alignment before commitment; any project where "what does success look like?" doesn't have a one-sentence answer.
How to run it:
When NOT to use it. Small, well-understood features where the cost of writing the memo exceeds the cost of just shipping. Use it when the decision is irreversible, the cost is high, or the alignment matters across more than 4-5 people.
Example: Amazon Prime, AWS, and the Kindle were each born from a working-backwards memo years before any code was written.
Honeycomb: "Stand-Up Meetings Are Dead (and What to Do Instead)" — Charity Majors' team's case study on going async-first. The line worth quoting in your next standup: "We didn't kill the standup. We let it die from neglect, and it didn't come back."
Async-first manifesto trending across remote eng leaders — Distributed teams reporting 25% more meetings than co-located peers and pushing back. Useful reference if you're making the case to a sync-default leadership chain.
Atlassian Team '26 (last week): Rovo agents now draft meeting summaries from doc + chat — The agentic version of "did we decide anything?" Useful for the meetings that survive the cull. Less useful as an excuse to keep the ones that shouldn't.
"If you think without writing, you only think you're thinking."
— Leslie Lamport
Don't miss what's next. Subscribe to Critical Path: