Meetings are part of leadership. We need them to align and understand. Yet, we often do it at the expense of action. The success lies in the milestones achieved. In essence, "Fewer Meetings, More Milestones" philosophy where action is more important.
Don't get me wrong. Communication is the backbone of any successful team. But let's be honest, how many times have you sat through a meeting thinking, "This could have been an email"? It’s exactly why we need to embrace a new approach. Here are a few angles I’d like to take.
Quick Huddles > Long Talks
Most meetings are endurance tests, not problem-solving sessions. You sit there for an hour, maybe longer, waiting your turn, half-listening while Slack pings in the background, and walk out with a fuzzy “action plan” that could’ve been written in two lines of text. That isn’t alignment. That’s time theft.
Now compare that to a five-to-ten-minute huddle. No slides. No ceremonies. No Scrum nonsense. You get in, say what's blocking you, clear the air, and get out. Think of it like a sports team huddle: quick reset, quick alignment, then back into the game.
Achieve more by meeting less
Prioritize Tools Over Talks
Most meetings exist for one reason: status updates. That is the worst way to spend human brainpower. You drag ten people into a call just to hear what could’ve been a Slack thread.
Make updates async by default. Status updates belong in Slack threads or project boards where everyone can check in when they actually have the bandwidth. That way nobody’s burning cognitive load listening to fifteen minutes of updates that don’t even apply to them.
Decisions? Same rule. Don’t schedule a meeting. Write a one-page doc with the context, the options, and the decision. Share it and let people comment. You do not have to replay the same conversation three times because someone missed the meeting. Writing also forces clarity. If you cannot explain the decision in a page, maybe you do not understand it yet. Over time, decision docs become organizational memory.
The tools are there to keep us out of rooms we don’t need to be in. Jira, Notion, Slack, Confluence. Pick your poison. The point isn’t the tool, it’s the principle: use software to do the repetitive communication so humans can do the creative work. Every meeting you replace with a doc or a thread is brainpower you free up for actual problem-solving.
Save Meetings for Friction
The conversations worth having live are usually the ones people avoid in writing. A dependency is failing, two teams want different things, or someone disagrees with a decision but writes polite comments. Async communication is good at moving information, but it's not very good at resolving conflicts.
That is when a meeting earns its place because you want to surface disagreement, force the trade-offs into the open, and leave with clear ownership. If the conversation cannot change the outcome, cancel it. But when the work is stuck behind politeness, ambiguity, or a decision nobody wants to own, another document will not save you. Sometimes you have to sit through the awkward fucking conversation until the real problem finally shows up.
The Meeting Is Not the Dependency
Cutting meetings does more than return time to the team. It exposes whether people have enough context, authority, and trust to move without asking permission. If every decision still requires you in the room, the meeting is not the real dependency. You are.
Look at your recurring meetings and ask what would break if you cancelled them. That answer tells you more about the team than the agenda ever will.