The Meeting That Replaces 10 Other Meetings

Most teams don't have a productivity problem—they have a meeting architecture problem.

You can feel it happening. Someone schedules a sync to discuss the output of last week's planning meeting. That sync spawns three follow-up one-on-ones because the group couldn't align. Those one-on-ones create action items that require a separate working session. The working session reveals gaps that demand a stakeholder check-in. By the time you've attended all of this, you've spent eight hours in rooms (or Zoom windows) to accomplish what could have been a 45-minute conversation with the right people in the right format.

The instinct is always to add structure. Teams respond by creating more meetings—a weekly standup, a biweekly planning session, a monthly all-hands, a quarterly strategy review. Each one feels necessary. Each one solves a specific problem. But collectively, they create a system where the meeting schedule becomes the actual work, and the work itself gets squeezed into the margins.

What actually works is the opposite: one meeting that does the work of ten.

This isn't about combining unrelated topics into a bloated agenda. It's about identifying the core decision or output that everything else orbits around, and building a meeting structure that makes that decision inevitable. Everything else becomes optional context.

Consider how this works in practice. A product team might have a weekly meeting that is nominally about "roadmap review." But if that meeting is designed correctly, it's also where prioritization happens, where technical constraints get surfaced, where customer feedback gets weighed against capacity, where the next sprint gets locked in, and where individual contributors understand how their work connects to strategy. You don't need a separate prioritization meeting. You don't need a separate capacity planning session. You don't need a separate strategy alignment call. They're all embedded in the structure of one meeting that has a real output: a locked roadmap.

The meeting that replaces ten others has three characteristics. First, it has a non-negotiable output. Not "discuss the project status"—that's vague and endless. But "leave with a decision on which three features we're shipping next quarter" or "leave with a clear understanding of who owns what." The output is specific enough that you know when the meeting is done.

Second, it brings together the people who actually need to be in the room. Not everyone who might have an opinion. Not everyone who could theoretically benefit from the information. The people whose input is required to make the decision, or whose buy-in is required to execute it. Everyone else gets the output asynchronously.

Third, it's scheduled with enough time and frequency that it can absorb the work that would otherwise spawn satellite meetings. A 90-minute weekly meeting can do more than a 30-minute weekly standup plus three 30-minute one-on-ones. The longer format allows for actual problem-solving, not just status reporting.

The resistance to this approach is usually about fear of missing information. Leaders worry that if someone isn't in the room, they won't know what's happening. So they add them to the meeting. Then they add someone else. Then the meeting becomes so large that it can't make decisions anymore, so they schedule a smaller meeting to actually decide, which spawns follow-ups to communicate the decision.

The antidote is radical clarity about what information needs to be synchronous and what can be asynchronous. Most of what people think needs to be discussed in real-time doesn't. It can be documented, shared, and absorbed on individual time. What actually requires synchronous time is the part where people with different perspectives collide and have to resolve something together.

When you design meetings this way, something shifts. People stop dreading the calendar. The meeting becomes the place where work actually happens, not where you talk about work that happens elsewhere. And paradoxically, by having fewer meetings, you end up with better communication—because the meetings that exist are doing real work, not just broadcasting information that could have been an email.