Every week I was spending 8-10 hours in meetings. Most of them were fine. But a significant portion were meetings that either didn't need to happen at all, or ran 30 minutes longer than they should have.
After some digging, I realized the root cause wasn't discipline or culture — it was a preparation problem. Most meetings failed before they started, because the agenda was unclear.
Here's the AI habit that changed that.
The Problem with Most Meeting Agendas
A typical agenda looks like this:
- Project status update (30 min)
- Q3 planning discussion (20 min)
- Misc / AOB (10 min)
This agenda is useless. It doesn't tell anyone what decisions need to be made, who is responsible for each item, or what success looks like. It's a list of topics masquerading as a plan.
The result: meetings where people talk until time runs out, then schedule a follow-up.
The Habit: AI Agenda Review, Every Time
Before every meeting I organize or attend, I run the agenda through this prompt:
Here's my meeting agenda: [paste agenda].
Review it and:
1. Flag any item that doesn't have a clear decision or outcome stated
2. Suggest which items could be handled async instead
3. Add a time box to each remaining item
4. Identify who should own driving each agenda item
5. Suggest one clarifying question I should ask before the meeting starts
Meeting details: [duration, attendees/roles, context]
What It Catches
Here's what this catches that humans routinely miss:
"Status update" items — 80% of the time, these can be a Slack message or email. AI will flag these consistently.
Decision items without a decision-maker — If there's no clear accountable person, you're setting up for a circular discussion.
Bloated agendas — A 60-minute meeting with 8 agenda items is a fantasy. AI will do the time math and tell you which items to cut.
Missing pre-work — Sometimes the right outcome is "get data from X before we can decide." AI catches when you're trying to make decisions without the necessary information.
Real Example
I recently had a sprint review agenda:
- Demo new features (15 min)
- Discuss sprint velocity (10 min)
- Backlog grooming (20 min)
- Team feedback (10 min)
- Planning for next sprint (15 min)
Running it through the prompt revealed:
- "Discuss sprint velocity" could be an async Slack post + reactions
- "Team feedback" had no owner or specific questions
- I was trying to do backlog grooming AND sprint planning in 35 minutes — impossible
The revised meeting was 45 minutes instead of 70, and we actually finished it.
The Bigger Picture
The goal isn't just shorter meetings — it's meetings where everyone knows why they're there and what they need to contribute.
When you arrive at a meeting and the agenda is crystal clear, you can prepare. When you prepare, you contribute better. When everyone contributes better, decisions happen faster.
That's how you get 30% of your meeting time back.
I write a weekly newsletter called Ahead of Schedule about practical AI habits for project managers and team leads. Every issue is one thing you can use this week.
Subscribe free: https://buttondown.com/marcustillerman
What's your biggest meeting pain point? Drop it in the comments — I'll cover it in a future issue.
This article was originally published by DEV Community and written by Marcus.
Read original article on DEV Community