We've all heard it: "Hey, can we hop on a quick call?" That word "quick" is a trap. It makes the meeting feel low-cost, which makes it easy to call, easy to pad, and easy to waste everyone's time.
Here's what actually works.
The Quick Meeting Problem
When someone says "quick call," they're implicitly asking for a low-commitment interaction. But meetings aren't low-commitment. They require:
- Everyone being online at the same time
- Context switching (which costs 15-25 minutes of focus)
- Synchronized schedules across time zones
The "quick" framing makes it socially acceptable to call a meeting that should have been an email. Or a Slack message. Or nothing at all.
The 12-Minute Rule
My rule: if it can be a meeting, it gets 12 minutes maximum. Not 30. Not "however long it takes." Twelve minutes.
Why 12? It's short enough that wasting time feels expensive. It's long enough to cover most topics. And it's not the default "30 minutes" that Google Calendar assumes.
This constraint forces preparation. If you know you have 12 minutes, you come with a clear agenda. You don't meander. You don't let sidebar discussions expand.
Agenda or No Meeting
Before accepting any meeting invitation, ask: "What's the agenda?" If the answer is "just catching up" or "figuring it out as we go," decline. Politely. With a counter-proposal.
Sample response:
"I'm not sure I can add value without a clear agenda. Could you share what you'd like to cover so I can prepare? Happy to hop on 12 minutes if there's a decision needed."
This isn't being difficult. It's being respectful of everyone's time.
The三种 Types of Meetings That Actually Need to Happen
Not all meetings are bad. These three types justify the cost:
1. Decision meetings — You need input from multiple people to make a decision. The key word is DECISION. Not "discussing" or "brainstorming." If there's no decision to make, there's no meeting.
2. Collaborative problem-solving — When you're genuinely stuck and need real-time back-and-forth. Whiteboarding sessions, architecture discussions, debugging calls. These benefit from synchronous interaction.
3. Relationship building — Team retrospectives, 1-on-1s, vision alignment. These are about humans connecting, not information transfer.
Everything else? Async.
The Meeting System I Use
I track meetings in a simple system:
- Agenda template (so I know what we're covering before we start)
- Timer visible on screen (so we actually stop at 12 minutes)
- Decision log (so outcomes don't get lost)
- Action tracker (so things actually get done)
It's the Meeting Mastery System — everything I wish I'd had years ago.
[Link to Meeting Mastery System in bio]
The goal isn't fewer meetings. It's meetings that justify the cost of having them.
Top comments (0)