diff --git a/src/content/posts/2026-08-01-engineering-an-agenda-culture.md b/src/content/posts/2026-08-01-engineering-an-agenda-culture.md new file mode 100644 index 000000000..d3da749a4 --- /dev/null +++ b/src/content/posts/2026-08-01-engineering-an-agenda-culture.md @@ -0,0 +1,169 @@ +--- +title: "Engineering an Agenda Culture for Better Meetings" +description: "Meetings without agendas create communications debt. Use a simple artifact rule to stop Groundhog Day syncs and capture real decisions." +published: false +--- + + +Over two years, I logged 143 meetings; only 17 had pre-reads, and 81% required a repeat. If your weekly sync feels like Groundhog Day, you're not imagining it. + +Same attendees. Same vague topic. Same twenty minutes of “quick updates” that could have been a comment on an issue. Then the meeting ends without a clear decision, nobody writes anything down, and three weeks later you're all back in the same room having the same conversation with slightly different nouns. + +That isn't collaboration. That's organizational amnesia. + +Engineers, of all people, should know better. We don't deploy to production without logs, version history, or some record of what changed and why. Yet a shocking number of teams still treat meetings—the place where priorities shift, tradeoffs get made, and commitments magically appear—as if they don't deserve artifacts. + +My stance is simple: if a meeting doesn't have a linked artifact, it probably shouldn't happen. + +## Meetings fail for the same reason undocumented systems fail + +A meeting without an agenda is bad enough. A meeting without notes or decisions is worse. But the real failure is that most teams don't see the cost. + +The cost isn't just sixty minutes times eight people. It's the follow-up meeting. It's the Slack thread trying to reconstruct what was decided. It's the new teammate who has no way to understand why the team chose option B over option A. It's the manager playing part-time historian because the only source of truth lives in three peoples' memory, which is to say, nowhere durable. + +This is [communications debt](https://ben.balter.com/2022/02/16/leaders-show-their-work/) in its purest form: near-term convenience that creates long-term drag. + +And like technical debt, you can take it on intentionally. Sometimes you do need to grab fifteen minutes and hash something out live. Fine. But pretending that debt is free because the meeting felt productive in the moment is how you end up re-litigating the same topic every month. + +I've watched this pattern play out enough times to spot it early. An invite shows up with a title like "Team sync" or "project touchpoint." No agenda. No linked issue or doc. No stated decision owner. You join anyway because declining feels rude. Forty-five minutes later, you've burned calendar time to discover that half the group came to get information, the other half came to give it, and nobody came prepared to make an actual decision. + +Then someone says, "Let's regroup next week." + +Of course you will. You built the meeting equivalent of a stateless service and now you're surprised it forgets everything. + +## The artifact is the work + +The fix isn't complicated, but it does require a cultural shift: treat the meeting artifact as the primary object, and the meeting as a temporary interface to move that artifact forward. + +That's just [showing your work](https://ben.balter.com/2022/02/16/leaders-show-their-work/) applied to meetings. + +The artifact can be an issue, a pull request, a shared doc, or even a one-page note in your wiki if that's what your team uses. I don't care much which tool you pick. I care that it exists before the meeting starts, that people can read it asynchronously, and that it gets updated with decisions and next steps before everyone wanders off to their next tab. + +This matters for the same reason async work matters. When you default to a durable artifact, you decouple progress from attendance. The people who couldn't make the meeting aren't punished. The people who need more time to think aren't steamrolled by the fastest talker in the room. And the organization gets a permanent record of not just what changed, but why. + +Or said more bluntly: if the only way to know what happened is "you had to be there," your process is broken. + +## The meeting artifact rule + +Here's the rule I wish more teams adopted: + +**Don't accept a meeting invite unless it links to an agenda artifact.** + +Not a title. Not a vague sentence in the description. A real artifact. + +That artifact should answer, at minimum: + +- Why are we meeting? +- What decision, discussion, or outcome is expected? +- What should attendees read or review beforehand? +- Who owns the decision? +- Where will notes and follow-ups live? + +If the organizer can't spend five minutes setting that up, the odds that the meeting deserves thirty or sixty minutes from multiple people are low. + +Yes, this sounds rigid. Good. A little friction up front prevents a lot of waste later. + +And no, this doesn't mean every meeting needs a ten-page memo. Most meetings deserve a page, not a novel. The point isn't ceremony. The point is memory. + +## A copy-pasteable one-page meeting template + +If you want to make this easy for your team, give them a default. People are far more likely to adopt good habits when the blank page disappears. + +Use this: + +```md +# Meeting title + +## Purpose +One sentence describing why this meeting exists. + +## Desired outcome +What should be true by the end of the meeting? + +## Decision owner +@[TEAM OR PERSON] + +## Attendees +Who needs to participate, and who is optional? + +## Pre-reads +- Link 1 +- Link 2 + +## Agenda +- Topic 1 — [OWNER] — [5 min] +- Topic 2 — [OWNER] — [10 min] +- Decision / review point — [OWNER] — [10 min] + +## Notes +- + +## Decisions made +- + +## Action items +- [OWNER] — [TASK] — [DATE] + +## Open questions +- +``` + +That's it. One page. Copy, paste, fill in the blanks. + +The hidden benefit is that the template forces the organizer to think. Do we actually need this meeting? Is this a decision meeting or a status update? Who owns the call? What do people need to read before they show up? Those are healthy constraints. They flush out bad meetings before they happen. + +## What to do when the invite has no artifact + +You don't need to be dramatic about it. Just be consistent. + +Reply with something like: + +> Happy to join. Can you add a linked agenda or issue with the purpose, pre-reads, and desired outcome? If it's helpful, here's the template I use. + +That's polite, but it changes the norm. You're signaling that your time—and everyone else's—deserves at least a minimal level of structure. + +If you're the manager or team lead, go one step further: make this the default expectation for recurring meetings. No artifact, no meeting. If the recurring sync keeps happening without updates to the agenda or notes, cancel it until there's a reason to bring it back. + +Recurring meetings are where this goes off the rails fastest. Because the calendar event already exists, teams stop justifying it. The meeting becomes a standing tax. Nobody remembers why it was created, but everybody keeps paying it. + +That's how you get a weekly sync that survives three reorganizations and still produces nothing except mild resentment. + +## The obvious objection + +Sometimes the right answer is to talk live. + +Of course it is. Brainstorming can be easier in real time. Sensitive feedback usually deserves a human conversation. Some decisions are blocked on a fast back-and-forth that would take days over comments. + +I'm not anti-meeting. I'm anti-meeting-without-memory. + +A good meeting can accelerate a decision. A bad meeting just hides indecision behind calendar invites. + +The artifact rule doesn't ban synchronous collaboration. It makes synchronous collaboration accountable to the rest of the organization. That's the difference. You're not just getting eight people into a room. You're producing a record others can build on. You're [working in the open](https://open-and-async.com/) enough that the value survives the hour. + +And if the topic can be resolved in comments on the artifact without meeting at all, even better. That's not a failure of collaboration. That's the system working. + +## Start with one meeting + +You do not need an enterprise-wide meeting reform initiative—there's a phrase no one has ever said over coffee. + +Start with one recurring meeting that annoys you the most. + +Add the template. Ask for pre-reads. Write decisions down in the same place. At the end, capture action items with owners and dates. Next week, begin by reviewing the open actions and unresolved questions from the artifact, not by asking everyone to remember what happened last time. + +That one change does two things. + +First, it improves the meeting itself. Second, it creates a visible example others can copy. That's usually how culture changes anyway—not through proclamations, but through a better default people are relieved to adopt. + +If you want a placeholder to make the pain concrete, use your own numbers: [NUMBER: e.g., "I answered the same question 40 times in six months because the decision lived only in meetings"] or [NUMBER: e.g., "our weekly sync spawned 12 follow-up meetings in one quarter"]. Most teams don't have to invent the evidence. They're swimming in it. + +Meetings still suck because too many organizations treat conversation as the output. It isn't. + +The output is the shared understanding, the decision, and the durable record. Everything else is just people talking. + +Engineers know better. Your meeting culture should, too.