惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
T
The Blog of Author Tim Ferriss
博客园 - 司徒正美
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
有赞技术团队
有赞技术团队
量子位
S
SegmentFault 最新的问题
博客园 - 聂微东
博客园 - 【当耐特】
J
Java Code Geeks
美团技术团队
Hugging Face - Blog
Hugging Face - Blog
H
Help Net Security
V
V2EX
人人都是产品经理
人人都是产品经理
博客园 - Franky
罗磊的独立博客
Engineering at Meta
Engineering at Meta
A
About on SuperTechFans
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
酷 壳 – CoolShell
酷 壳 – CoolShell
云风的 BLOG
云风的 BLOG
Y
Y Combinator Blog
Apple Machine Learning Research
Apple Machine Learning Research

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
How I Reduced Meeting Time by 30% Using This One AI Habit
Marcus · 2026-04-28 · via DEV Community

Marcus

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]

Enter fullscreen mode Exit fullscreen mode


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.