It was a 15-minute meeting. We covered three topics, made two decisions, assigned three action items, and everyone left knowing exactly what was happening.
Here's the exact format that made it possible.
The Setup
Before the meeting, I sent a single page to all participants:
Topic: Q2 Planning - Mobile App
Goal: Decide on MVP scope
Time: 15 minutes
PRE-MEETING NOTES:
- I've reviewed the technical estimates
- I've talked to the top 3 customers about their priorities
- I have a recommendation but I'm open to alternatives
That's it. Three lines. Everyone came prepared because they knew exactly what we were solving.
The Format (15 Minutes Total)
Minutes 0-2: The Context
I spent exactly 2 minutes setting up the problem. Not presenting — just framing. "Here's what we're deciding, here's the context, here's my recommendation."
This is not a presentation. It's a frame job. You're telling people how to think about the problem before you ask them to think.
Minutes 2-8: The Discussion
6 minutes of actual discussion. Not "any questions?" — real back and forth. Concerns, alternatives, trade-offs.
The key: if someone raises a concern I hadn't thought of, I write it down. We don't solve it in this meeting. We park it.
Minutes 8-12: The Decision
4 minutes to make the actual decision. Sometimes this is me deciding. Sometimes it's a vote. Sometimes it's "we need more data and we'll decide next Tuesday."
Whatever the decision is, we write it down clearly:
DECISION: We will ship feature set B (notifications + offline mode) for MVP, with feature set A (search + sharing) as a post-launch sprint.
REASON: Customer priority data + technical risk assessment
OWNER: Sarah to update the project plan
Minutes 12-15: The Wrap
3 minutes to assign action items and confirm next steps. Every action item needs:
- What
- Who
- Due date
If we couldn't assign it in the meeting, it doesn't get done.
Why This Works
It respects everyone's intelligence. You're not treating the meeting as a lecture. You're bringing context and asking for input.
It creates urgency. 15 minutes is short enough that people stay focused. They're not checking email under the table because there's no email under the table to check.
It produces outcomes. Decisions get made. Action items get assigned. Things happen.
It ends on time. Which means the next meeting starts on time. Which means people trust that the meeting will actually end when it's supposed to.
The System Behind It
I've been using a Meeting Mastery System that makes this kind of meeting the default instead of the exception:
- Pre-meeting template that forces you to clarify the goal
- Time-boxed agenda templates
- Decision log that captures outcomes
- Action tracker that follows up automatically
It takes 5 minutes to prepare for a meeting using this system. It saves hours of follow-up meetings.
[Link to Meeting Mastery System in bio]
The goal isn't short meetings. It's meetings that produce results.
Top comments (0)