Skip to main content

No agenda, no meeting

2 min read

Summary: A meeting without an agenda hasn’t even bothered to justify its own existence. Write first, meet second, and if you do need a meeting, include an agenda, attach a read-ahead, and state the decision you’re trying to make. Next time you get an invite without an agenda, decline it, or reply asking for one.

Table of contents

You get the invite. No description. No agenda. No attached document. Just a title like “Quick sync” and a 30-minute calendar hold. You accept it anyway. What else are you going to do, decline a meeting with your skip-level?

I’ve written before about how meetings should be a point of escalation, not a starting point. But the agenda-free meeting is an even more fundamental failure mode: it’s a meeting that hasn’t even bothered to justify its own existence.

I made a site about it: noagendanomeeting.net.

The cost of no agenda

A meeting without an agenda is like calling a function without documentation. Sure, it might do what you expect, but you’re forcing every caller to read the implementation to find out. Meetings without agendas force everyone to context-switch twice: once to figure out what it’s about, and again in the meeting itself when they arrive unprepared.

The average knowledge worker already spends 40% of their workweek in meetings. Without clear goals, those meetings drift, no decisions get made, and everyone leaves wondering if that could’ve been an email. (It could’ve.)

Start with a document

The site’s core argument is that writing scales; meetings don’t. Before you send that invite, ask yourself: can this start as a document instead?

If the answer is yes (and it almost always is), write first, meet second. If you do need a meeting, include an agenda, attach a read-ahead, and state the decision you’re trying to make. This isn’t radical advice. It’s basic async-first communication hygiene.

What to do about it

Next time you get a meeting invite without an agenda, try something wild: decline it. Or better yet, reply asking for one. You can even send them the link. noagendanomeeting.net is a lot more diplomatic than “I’m not attending your agenda-free ambush.”

If you manage like an engineer, you already know that undefined inputs produce undefined outputs. Meetings are no different. Define the problem before you schedule the standup.

Keep reading

  • How to one-on-one

    Most 1:1s waste your team's only protected synchronous time on status updates. Here's how to run ones worth showing up for.

  • Merge by committee

    Reviewing pull requests in weekly committee meetings kills open source projects. Decentralize governance and reduce information imbalance.

  • How to derail any meeting

    How a WWII field manual can help modern knowledge workers identify those inadvertently sabotaging your organization today.

Ben Balter

I'm Ben Balter, and I write here about developer platforms, product and engineering leadership, open source, and showing your work. I'm a principal product manager for API (developer) experience at Cloudflare, where I work on making it an even better place to build, for developers and their agents. Before that, I spent over a decade building developer platforms at GitHub. For five years I was a product manager for trust and safety, shipping 500+ features and policies to 50M+ developers, plus github.com API endpoints for trust and safety workflows. I also led a bottom-up rewrite of GitHub Pages, maintained Jekyll, and wrote the plugins most GitHub Pages sites run on. My open source projects have hundreds of millions of downloads. I wrote Open and Async, the playbook for remote and distributed teams. More about the author

Follow along: Bluesky LinkedIn

Originally published April 6, 2026 View revision history

This page is open source Help improve this article on GitHub

Keyboard shortcuts

Search

  • / or ⌘ K Open search
  • ↓ or j ↑ or k Move through results
  • Enter Open the selected result
  • Esc Close search

Go to

  • g then h Home
  • g then p All posts

This page

  • y Copy link to this page
  • ? Show this list

Turn off if you use voice control or keep triggering them by accident. ⌘ K still opens search, and this list stays under "Keyboard shortcuts" in the footer.