That Meeting Could Have Been
an AI Workflow.

Somewhere in your calendar this week is a meeting that is, structurally speaking, an information-retrieval task dressed up as a collaboration. Twelve people join. One person talks for 20 minutes. Everyone else waits politely for their 30 seconds of acknowledgment. Then everyone leaves and goes back to doing what they were actually going to do anyway.

This meeting did not need twelve people. It needed a workflow, a summary, and a Slack message.

I am not here to tell you meetings are bad. Some meetings are irreplaceable — the ones involving genuine ambiguity, conflicting priorities, and the kind of judgment calls that require reading a room. Those meetings earn their calendar slot. I’m here to talk about the other ones. The ones that exist because nobody sat down and asked: what information is actually being exchanged here, and what’s the cheapest way to exchange it reliably?

The Automation Audit

Before you build anything, the most useful thing you can do is spend one week tracking the purpose of every recurring obligation on your calendar. Not what it’s called — what it’s actually for. For each one, ask a single question:

Is a human judgment being made here, or is information being relayed?

The answer is more revealing than it should be.

The weekly standup at most organisations is, in practice, three Jira queries summarised verbally by people who haven’t looked at Jira since the last standup. This is a job for a cron job and a Slack bot, not a recurring calendar invite.

Information relay does not require synchronous human presence. It requires accurate, timely, well-formatted information. Which is something an AI workflow handles better than a meeting, because the workflow doesn’t forget to mention the blocked ticket, doesn’t run over time, and doesn’t schedule itself on a Friday afternoon.

What Actually Needs a Human

The meetings that genuinely require humans are the ones involving:

• Ambiguity about what to build, not how to build it — requirements that need negotiation, not implementation
• Interpersonal complexity — conflict resolution, team dynamics, motivation conversations
• Novel decisions — architectural choices without precedent, where the right answer isn’t yet knowable
• Accountability — decisions that need a named human to own them

If your meeting doesn’t involve at least one of these, it is a workflow wearing a calendar invite.

The Practical Playbook

You don’t need to rebuild your entire organisation to reclaim your calendar. Start with one meeting. Pick the most obviously automatable one — the standup is usually the easiest target.

Step one: Identify what information is actually being exchanged. For a standup it’s typically: what did each person do, what are they doing today, what is blocked. Three Jira queries and a template.

Step two: Build the workflow. Jira API → LLM summary → Slack message. This is an afternoon of work, not a project. If you’re in a .NET shop it’s maybe 200 lines. If you use Python with an existing framework, significantly less.

Step three: Run it in parallel with the meeting for one sprint. Show the team that the automated summary contains everything the meeting was surfacing. Then cancel the meeting.

Step four: Bank the recovered time. Use it for the architecture review, which is where human presence actually earns its keep.

This is not about eliminating human collaboration. It’s about using human time where it’s irreplaceable and using automation where it’s interchangeable. The two are not in conflict. They are complementary — provided you’re honest about which category each obligation falls into.

The goal is not a world with no meetings. The goal is a world where every meeting that exists is there because a human being genuinely needed to be in a room with another human being, and there was no cheaper way to get the same outcome.

Most organisations are a long way from that world. The distance is mostly a workflow backlog. Start building.