Meetings Are Symptoms

Most teams don't have a meeting problem. They have a systems problem that meetings paper over.

When nobody knows who owns a decision, you schedule a meeting. When status is trapped in people's heads, you schedule a standup. When the roadmap lives in a slide deck nobody trusts, you schedule a planning session to renegotiate reality.

The calendar fills up. Everyone feels busy. Throughput drops. Then leadership asks for more “alignment” — which, predictably, becomes another recurring invite.

👉 A meeting is often a tax you pay for missing documentation, unclear ownership, or weak feedback loops.

What Meetings Quietly Hide

I've sat in rooms where the same three questions got asked every week:

• What are you working on?
• Are we blocked?
• When will it ship?

Those questions aren't wrong. Putting eight people on a call to answer them live is wrong — especially when a ticket board, a short written update, or a shared runbook would answer them better.

Meetings also reward the loudest voice. Quiet engineers with the best context get interrupted. Decisions get made by whoever can stay online longest. The system selects for presence theater, not judgment.

And there's a cost that never shows up on the invite: context switching. A one-hour meeting rarely costs one hour. It costs the half-hour before (you can't start deep work) and the half-hour after (you can't restart it).

Replace Rituals With Written Defaults

The first system upgrade is boring on purpose: write down how work moves.

Written defaults feel slow the first week. They feel like freedom by week four — because people stop re-negotiating the process in every conversation.

You don't need a wiki novel. You need a living page that answers the questions people currently ask in meetings.

Draw an Ownership Map

Ambiguity is expensive. If two people think they own a service, both wait. If nobody owns it, everyone pings everyone.

Make ownership visible: who decides, who implements, who must be informed. Keep it lightweight. A simple table beats a RACI theater deck.

When ownership is clear, most “alignment meetings” disappear. People know who to ask, and that person can answer in writing without assembling a committee.

👉 If a decision requires six people in a room, either the decision is huge — or ownership is broken.

Async That Actually Works

Async fails when it becomes a chat dump. It works when it has structure.

• Proposals get a short written brief before anyone debates them.
• Reviews happen in pull requests and docs, not screenshare walkthroughs by default.
• Blockers get named early, with an owner and a next action — not a vague “we'll sync.”
• Time zones are treated as a feature: write so the next person can move without waking you.

The goal isn't to never talk. The goal is to reserve live time for work that only live time can do: conflict resolution, messy design trade-offs, mentoring, and moments where tone matters.

Keep the Few Meetings That Earn Their Slot

I'm not anti-meeting. I'm anti-default-meeting.

A meeting earns its place when:

• You need real-time negotiation, not status reporting.
• You're unblocking a stuck decision with incomplete info.
• You're building shared mental models that writing alone can't create yet.
• You have an agenda, a decision owner, and a written outcome afterward.

Everything else can usually be a doc, a ticket comment, or a short recorded walkthrough. If the invite has no agenda and no owner, it isn't a meeting — it's a calendar placeholder for anxiety.

Closing

Engineering teams don't get faster by stacking more syncs. They get faster by making the invisible visible: ownership, status, decisions, and the path from idea to shipped.

Cut the meetings that exist because systems are missing. Then build those systems. The calendar will look emptier. The work will look better.