How leaders cut meetings without cutting collaboration

The distinction I use is simple. Does this meeting require both of us, or does it only require me?

When a recurring meeting consistently has one person teaching, advising, or solving while the other receives, that is not a meeting. That is a consultation. And consultations have a different structure, a different cadence, and often a different cost.

Once I started naming that distinction clearly, the calendar got easier to manage. Meetings where both people are actively contributing, thinking through something together, or making a decision that neither could make alone, those stay. They protect the work because they are part of the work.

The ones that felt more extractive, where my time and thinking were the primary resource being used, I restructured. Some became async. Some became shorter, scoped check-ins. Some I let go of entirely.

The rule that freed the most time was not a time-blocking strategy or a meeting audit. It was a clearer sense of what collaboration actually looks like. When you can tell the difference between a meeting and a consultation, you stop saying yes to the second one out of obligation.

That clarity also changed how I show up in the meetings I do keep. Less drained, more present. Which is the point.

I approach a crowded calendar the same way I approach any operational bottleneck, by auditing for ROI. Every recurring meeting gets evaluated against three filters: does it drive a clear decision, does it unblock execution, or does it create alignment that can’t be achieved asynchronously? If it fails all three, it’s either shortened, converted into an async update, or removed entirely. We also assign a “meeting owner” responsible for agenda, outcomes, and follow-ups. If that ownership is unclear, the meeting usually doesn’t deserve to exist.

One change that freed up significant time was implementing a strict “default to 25-minute meetings” rule instead of 60. That small constraint forced tighter agendas, faster decisions, and less filler discussion. As a result, we reclaimed hours each week without sacrificing collaboration. In fact, it improved it because conversations became more intentional and outcome-driven.

After reviewing my many appointments on my calendar, I realized that most of them were repeat meetings that did not correlate with productivity. These meetings were providing emotional reassurance for individuals who felt that attending would help maintain an alignment with someone else’s work. If a meeting is not generating decisions being made, assignments being given, or assignments being transferred from one participant to the other, then the meeting is a ritual rather than a productive use of time.

The first measure I implemented was to discontinue all weekly meetings unless those meetings had a specific agenda for discussion of an ongoing decision. In order to continue the meeting, a minimum of 2-3 bullet points must be present on the agenda the day before. I was very surprised to learn how often work became cooperative and effective after implementing this rule. I noticed many players began using Slack or sending a quick memo to provide a status report rather than attending the meeting; therefore, by using the meeting for conflict resolution or to work out team member issues, our total overall number of meetings decreased significantly.

In conclusion, the takeaway is to maintain meetings with the purpose of generating any decision-making by attendees, reduce the amount of time and frequency of meetings that serve only to provide visibility to each individual’s performance, and eliminate meetings designed solely to provide emotional comfort to someone uncomfortable with their ability to perform their job description as expected.

I decide which recurring meetings to keep by asking whether they require cross-company participation or can be handled by immediate team members during flow hours. Meetings that do not need cross-company input are shortened or canceled and handled within teams during the 1 PM to 5 PM PST flow window. The rule I implemented was company-wide communication hours from 9 AM to 1 PM PST and protected flow hours from 1 PM to 5 PM PST. That schedule freed meaningful blocks of uninterrupted focus time while preserving collaboration because cross-company meetings are confined to the communication window.

When my calendar is crowded with recurring meetings with employees, I decide which ones to keep, shorten, or cancel based on employee need. I generally do not have an issue with meetings tying up my calendar because I schedule one-on-one meetings monthly with each employee and one monthly staff meeting. After doing so, more of my time was freed up. Additionally, I implemented a chain of command with all of our vendors. No meetings are scheduled with me until they go through the chain of command.

The thing is that one hour meeting with five people is 750 dollars in output. We follow these losses on 150 accounts to cushion growth as big growth operations are characterized by 25% meeting tax that consumes margins. This happens in many ways because teams would choose to talk rather than act. In regards to all occurrences of invitations, I will question whether the client project would be a failure without me today.

We have been seeing recently that the most effective tweak is to have a fifteen minutes restriction on a single internal check-in. That move saved back ten hours per week of leadership time. In fact, as per Parkinson’s Law, the labor is increased to the optimum number of minutes that can be done. Meetings that are not written in the form of an agenda disappear off the calendar at once. As it happens, we saw a 20% jump in task completion rates after reducing these blocks.

I have always used two primary things to help me decide whether or not I need to be in a meeting. They both are rooted in the impact on the business and its people. Everything else and all other meeting types become secondary.

1) Decision impact – Is there a pivotal decision (M&A go/no-go, hiring/firing, product launch, pricing change, top 10 customer, etc.) to be made in the meeting that will have a significant impact on the business? If yes, then I need to attend.

2) Decision rights and capability – Am I the only one (and hence the bottleneck) who has the decision rights, or are there others who can make decisions and are capable of making them? If I am the bottleneck, then either I need to show up or I need to identify those who can make the decision in my absence. If I cannot find such alternatives, then I ask the question in #1 to determine the importance of this meeting relative to others.

Once I have successfully identified the highest and most important meetings I need to be part of, then I move on to secondary criteria for prioritizing the remaining meetings on my calendar.

Start by auditing which meetings actually require you. If you are there purely as a listener, that is the first category to exit immediately.

Then look at meetings where your presence is helpful but not essential. Those can be delegated. Brief someone else, hand over the responsibility, and trust them to handle it.

Finally, review the meetings you are running yourself. Does it have to be you leading it, or could someone else own it just as well?

Going through those three filters typically eliminates around 90% of calendar bloat. Most recurring meetings exist out of habit, not necessity.

Packed calendars kill actual business growth. I was taught early that busywork kills your deal flow, and that is what buyers are always complaining about. I experienced the same several years ago, and after examining more than 500 transactions on behalf of our holding company, I realized that all you need to do is to attend sessions with a strict decision agenda. I suspend all other things at once. Therefore, I trimmed down left-over calls by insisting on pre-reads in advance and retained only those sessions that require my direct financial sanction.

Meetings tend to help people evade difficult decisions, and, should you be a person who cares about efficiency, you are likely to have guessed it. Around year five I began to impose a strict 20 minutes work slot on each task to interrupt this cycle. This technique compels quick cooperation since the participants are aware that they have only twenty minutes to make a decision, which immediately halts the meandering. Our holding company manages all the acquisitions through this structure to safeguard our focus. After that we never looked back.

I ask myself whether a meeting actually results in making any decisions or it is a waste of time. In case of no improvement after three meetings in a row, I cancel it and switch updates to email. I also consider those who need to be there and inform people to miss meetings when the agenda is not related to their work.

The single change that liberated the real time was the blocking of three mornings in every week without any meetings. Only client work is done during those hours. At first, people attempted to book over those blocks, but I said no and they got accustomed to it. This helped my work as I was able to think without being interrupted.

I also made every 60-minute meeting 45 minutes and every 30-minute meeting 25 minutes. That will give me a couple of minutes between calls to relax and get ready for the next. Minor adjustment, but at least we would not have to jump all day long on a screen with no breaks.