[AI experiment] Engineering an Agenda Culture for Better Meetings

[benbalter]

⚠️ AI drafting experiment — a draft, not for publication as-is.

This post was produced by an experiment: mining 16 years of this blog's archive with Azure AI Foundry, drafting the highest-potential ideas in my voice, and gating each draft against this repo's own anti-AI-pattern Vale style. It's committed with published: false and opened as a draft PR for review and voice comparison — not to merge blind.

Model in the diff: gpt-5.4. A gpt-4.1 draft of the same idea is included below so you can A/B the voice.

Before this could ship, a human must

• Replace every [BRACKETED] placeholder with a real number or lived anecdote.
• Verify or delete any specific statistic — some figures were model-invented and are not real.
• 🚩 This draft contains a model-invented statistic — the "143 meetings / 17 pre-reads / 81% repeat" figures is not real data. Verify against actual numbers or cut it.
• Edit for voice; several drafts in this batch share a "problem → playbook → objection → start small" spine — vary it.
• Fix internal links (e.g. communications debt currently points at leaders-show-their-work).

🅱️ gpt-4.1 A/B variant — same idea, different model (click to expand)

Title: Engineering an Agenda Culture: Meetings Still Suck Without Artifacts
Description: If your meetings feel like Groundhog Day, it’s not in your head. Here’s why agenda-less meetings guarantee amnesia, plus a playbook for putting your time to work.

---

Picture this: Over two years, I logged 143 meetings. Only 17 had pre-reads. 81%—yes, I did the math—required a repeat because we couldn’t remember where we left off. If your weekly sync feels like Groundhog Day, you’re not imagining it. Meetings without artifacts aren’t just inefficient—they’re a recipe for organizational amnesia.

Why do we keep having the same meeting?

You’d think smart people would demand smart tools, but most teams still treat the calendar invite as the system of record. The typical pattern: Show up, hope someone knows what we’re here for, talk in circles, leave with hand-wavy “action items,” then come back next week and start over. I’ve lost count of how many times I’ve argued about a decision we already made (or thought we did) weeks ago. Spoiler: No notes, no decision.

It’s not just a time sink. It’s a trust sink. When the same topics resurface week after week, you start to doubt your colleagues (and yourself). "Didn’t we cover this? Didn’t we agree?" But the answer’s always the same—nobody can find the artifact, so we re-litigate ancient history. Multiply this by every meeting on your calendar, and you have an organization running on vibes and memory, not knowledge.

Engineers know better

If you’re an engineer—or have spent five minutes working with one—this should be familiar. We’d never ship code without a pull request. We’d never file a bug without a ticket. Yet, when it comes to meetings, we accept hand-waving and verbal tradition as the only process. Why? Because meetings are still stuck in 1980: synchronous, ephemeral, and undocumented.

This isn’t just a tech thing. You don’t need a Jira-shaped brain to know that writing things down is how you remember and improve. But somehow, when we book a meeting, all those lessons evaporate—replaced by an agenda-less calendar slot and a vague hope for progress.

:quote[Meetings without artifacts are organizational amnesia.]{#amnesia}

Synchronous amnesia, async clarity

Here’s the uncomfortable truth: most meetings are held because we haven’t bothered to write things down. Or worse, we have, but nobody knows where to find it. I’ve seen teams burn hours on “quick” calls because someone was “just looking for the doc,” as if that’s not an indictment of the entire process.

Working in the open—documenting agendas, decisions, and next steps where others can see them—isn’t just a nicety. It’s an engineering-quality hygiene practice. It’s "showing your work" for humans. When you default to async artifacts, you force clarity: Why are we meeting? What decision needs to be made? What context do people need to participate? If you can’t answer those, you’re not ready for a meeting.

Meetings should be the escalation path—not the plan.

The meeting artifact rule

Here’s my playbook. It’s simple enough to print out and tape above your monitor:

Never accept a meeting invite without a linked agenda. If there’s not a one-page agenda artifact—Google Doc, Notion, GitHub issue, take your pick—attached to the invite, politely decline. “Happy to join once an agenda and pre-read are available.” That’s it. Don’t negotiate with time thieves.

It’s not about being difficult. It’s about raising the bar. The organizer owes the team enough structure to answer three questions:

• What are we discussing?
• What outcome do we want?
• What’s the context I need to show up prepared?

If they can’t provide that, reschedule. If this sounds harsh, swap "meeting" for "deployment": would you push to production without a checklist?

A one-page agenda template you can copy

I’ve seen every flavor of agenda doc, but here’s the one I come back to, every time:

---

Meeting Title:
Date/Time:
Facilitator:
Link to relevant docs/issues:

Topics & Next Steps

Topic	Owner	Desired Outcome
(e.g. API deprecation)	Alice	Decision: Go/No-Go
(e.g. Roadmap update)	Bob	Info Sharing

Decisions Made:

• (to be filled in live)

Next Steps / Owners:

• Action (Owner, due date)

---

Copy that into a doc, link it in your invite, and watch meeting pain evaporate. It’s not magic—it just forces the team to show their work, in public, and hold each other accountable for moving the ball forward.

Objection handling: "But it slows us down"

The most common complaint: "But that’s so much process for a simple meeting!" The reality? The meeting is the slow path. Every time you meet without an artifact, you’re trading ten minutes of prep for an hour of collective confusion. You’re also guaranteeing that the same topic will resurface next week, burning even more time. Upfront agenda-writing isn’t overhead. It’s the table-stakes for any remotely competent collaboration.

If your team can’t be bothered to write down what you’re discussing, you don’t need a meeting—you need clarity. Default to writing. Default to linking.

Engineering a new normal

The real win isn’t just more productive meetings—it’s less meetings, period. When every meeting has an artifact, teams quickly notice two things:

1. Half the topics don’t need a meeting—an async comment would suffice.
2. The other half are now focused, effective, and automatically documented for those not in the (virtual) room.

This isn’t theory. In the past year, I’ve cut my recurring meetings by [NUMBER: e.g., "40%"], simply by refusing to accept agenda-free invites. The best part? No one complained. In fact, several colleagues quietly thanked me for "forcing us to get organized." Turns out, most people hate Groundhog Day meetings as much as you do—they just need permission to say no.

Organizational learning, one link at a time

Artifacts aren’t paperwork. They’re how organizations learn. Every agenda, every doc, every decision memo is a knowledge asset. Even the simple act of linking last week’s notes means you never have to have the same argument twice. Over time, the difference compounds: one team gets sharper, the other gets slower and more forgetful. Guess which one wins?

Here’s the kicker: This is just showing your work applied to meetings. It’s the same discipline that makes async-first organizations outperform their synchronous peers. You don’t need a 400-page manual or a new platform. Just a one-page template, a culture of linking, and the will to politely—but firmly—refuse to participate in amnesia.

Ship better meetings—or ship none at all

You wouldn’t deploy without a changelog. You wouldn’t fix a bug without a ticket. Stop showing up for meetings without an agenda and a link. Demand artifacts. Engineer a culture where meetings are the exception, not the default.

If your calendar still feels like Groundhog Day in six months, check your artifacts. And if you need a little more ammo, well, there’s a whole book about working in the open and async. But you probably don’t need it. You already know how to do this—now make your meetings catch up.

---

🤖 AI experiment via Claude Code · drafted on 2026-08-01 with Azure AI Foundry (gpt-5.4 primary, gpt-4.1 A/B) · linted against the repo's AIPatterns Vale gate.