Why Are Your Executives in the Room?

Executives are busy.

That statement probably does not require research.

Look at almost any senior leader's calendar and the evidence is sitting right there.

Meeting.

Meeting.

Meeting.

Ten minutes to answer emails.

Meeting.

A working lunch.

Meeting.

Something gets added at 4:30 because an issue came up that "needs attention."

Then the actual work starts after everyone else goes home.

It has become so normal that we rarely question it.

We talk about executive time management. We talk about meeting efficiency. We introduce meeting free Fridays, artificial intelligence assistants, automated notes, calendar optimization, delegation frameworks, and every other solution designed to give leaders a few hours back.

Maybe some of those things help.

But I think we may be looking at the wrong problem.

Instead of asking:

Why does this executive have so many meetings?

What happens if we ask:

Why does the organization need this executive in so many meetings?

Those questions sound similar.

They are not.

One examines the executive.

The other examines the organization.

And the difference between the two may tell us something important about how organizations are actually operating.

The calendar is telling us something

There is evidence that modern work has become increasingly fragmented.

Microsoft's 2025 Work Trend Index found that employees in its dataset were interrupted by a meeting, email, or chat roughly once every two minutes during the workday. More than half of leaders, 52 percent, described their work as chaotic and fragmented. Microsoft also reported that meetings beginning after 8:00 PM had increased 16 percent year over year, while 30 percent of meetings were crossing multiple time zones. [1]

The problem is not restricted to executives.

McKinsey studied middle managers and found that they spent only 23 percent of their time on strategy focused work and 28 percent on talent and people management. The remaining 49 percent went toward administrative and individual contributor work. [2]

Asana reported that senior leaders estimated losing approximately 3.6 hours every week to unnecessary meetings. [3]

None of this proves that meetings are inherently bad.

In fact, research on CEOs suggests exactly the opposite.

Harvard Business School professors Michael Porter and Nitin Nohria tracked 27 CEOs for nearly 60,000 hours. Their research demonstrated just how interaction dependent the CEO role actually is. Executives have to integrate strategy, people, customers, investors, operations, external constituencies, decisions, and unexpected events. Leadership at that level cannot happen from behind a closed door. [4]

So the problem cannot simply be that executives spend too much time with other people.

That would be too easy.

The better question is:

What requires their involvement?

Look at the meeting differently

Imagine opening the calendar of a senior executive.

There are 35 hours of meetings scheduled this week.

Some of them make perfect sense.

Capital allocation.

Strategy.

Enterprise risk.

Major talent decisions.

Customer relationships.

Acquisitions.

Cross functional priorities with material business implications.

There are decisions that should occur at the executive level because the authority, context, and consequences belong there.

Now keep looking.

A department needs help deciding how to respond to a customer.

Two functions disagree about priority.

A manager wants confirmation before making a decision.

Someone needs the executive to speak with Finance.

A project has stalled because nobody is certain who owns the next step.

A team wants the executive's opinion before moving forward.

Another meeting exists because the last meeting did not produce clear accountability.

A follow up meeting gets scheduled to make sure everyone completed what they previously agreed to complete.

Those meetings look different.

The executive is still working.

People are still talking.

Problems are still being solved.

Decisions are still being made.

The calendar still appears productive.

But the function of executive involvement has changed.

The executive is no longer operating primarily as an executive.

They are becoming part of the organization's operating mechanism.

What role is the executive actually playing?

Look closely enough and the executive may be functioning as several things at once.

Decision maker.

Conflict resolver.

Information router.

Permission structure.

Alignment mechanism.

Quality control system.

Escalation point.

Accountability mechanism.

Organizational memory.

None of those activities necessarily looks dysfunctional in isolation.

In fact, each one may be entirely reasonable.

A problem appears.

The executive gets involved.

The problem gets solved.

That is what leaders are supposed to do, right?

Maybe.

But something else happened at the same time.

The organization learned that executive involvement works.

That matters.

Because the next time a similar problem appears, what happens?

Someone escalates it.

The executive provides guidance again.

The problem gets resolved again.

Another situation appears.

Another escalation.

Another meeting.

Another decision.

Another successful intervention.

Eventually the organization can begin organizing itself around executive availability without anybody deliberately designing it that way.

The executive becomes busier.

The organization feels supported.

Problems continue getting solved.

Everyone appears responsive.

Yet something underneath the activity may be moving in the opposite direction.

What if successful intervention creates dependency?

This is where the problem becomes uncomfortable.

Executive involvement can simultaneously solve today's problem and preserve tomorrow's dependency.

Think about that.

A leader sees a problem that could cost the organization money, damage a customer relationship, delay an important project, or hurt performance.

Of course they intervene.

The immediate business case is obvious.

But what happens if intervention becomes the normal response?

The organization starts learning where decisions actually get made.

People become less willing to take risk without confirmation.

Managers become accustomed to upward validation.

Cross functional disagreements migrate vertically instead of being resolved laterally.

Employees learn that difficult decisions are safer when shared with someone more senior.

Eventually the organization may become extremely effective at escalation.

That does not necessarily mean it has become effective at decision making.

Those are different capabilities.

And now we arrive at a strange organizational contradiction.

Executives are expected to drive results through other people.

But those same organizations can gradually consume more executive involvement in order for those people to produce the results.

So what exactly is being scaled?

Guidance can quietly replace leadership

There is nothing wrong with guidance.

People need context.

Managers need coaching.

Complex decisions deserve discussion.

Leaders should absolutely remain connected to their organizations.

The issue is frequency and purpose.

If an executive regularly has to explain what to do next, align functions that cannot align themselves, resolve decisions that should live elsewhere, check whether commitments were fulfilled, or personally push work through organizational resistance, something is being revealed.

Not necessarily about the executive.

About the system.

That is an important distinction.

Because organizations often respond to an overloaded executive by attempting to improve the executive.

Delegate more.

Protect your calendar.

Say no.

Block focus time.

Use AI.

Hire an executive assistant.

Reduce meetings.

All potentially useful.

None necessarily addresses why the demand exists.

You can make an executive incredibly efficient at managing dependency.

The dependency remains.

The same problem may exist below them

This is where the McKinsey findings become interesting.

Middle managers in its research spent almost half their time doing administrative or individual contributor work rather than strategy, talent management, coaching, or development. [2]

Think through the possible organizational consequence.

Executives are too busy solving problems.

Middle managers are too busy doing work.

Frontline managers are too busy managing daily execution.

Everyone is busy.

Everyone can point to a full calendar.

Everyone has legitimate demands.

And the work of increasing organizational capability gets squeezed into whatever time remains.

Then we wonder why the next level is not ready.

We wonder why managers struggle with decisions.

We wonder why everything escalates.

We wonder why the organization cannot operate without constant leadership involvement.

When exactly was that capability supposed to have been built?

If leaders continually absorb the work created by capability gaps, but lack the time to develop the capability that would close those gaps, the system can sustain itself while simultaneously increasing its future dependency.

The operation continues.

The debt accumulates.

And because today's problems keep getting solved, the condition can remain nearly invisible.

Busyness can hide organizational weakness

This is what interests me most.

An overloaded executive can look like evidence of importance.

They are involved in everything.

Everyone needs them.

They know what is happening.

People trust their judgment.

They are constantly solving problems.

Organizations often reward that behavior.

We describe them as responsive.

Committed.

Hands on.

Indispensable.

But "indispensable" deserves more scrutiny than we usually give it.

Sometimes indispensable means extraordinary value.

Sometimes it means the organization has not developed the capability to function without a particular individual.

Those realities can exist simultaneously.

The question is not whether the leader provides value.

The question is whether their involvement creates additional organizational capability or substitutes for it.

That distinction changes everything.

Start with the calendar

There may be a very simple way to begin looking at this.

Do not cancel any meetings.

Do not redesign the organization.

Do not start another transformation initiative.

Take two weeks of an executive's calendar.

For every meaningful meeting, ask one question:

Why was executive involvement required?

Then classify the answer.

Authority

Was there a decision that legitimately required this level of authority?

Good.

That belongs here.

Strategy

Was the executive applying enterprise context, setting direction, allocating resources, or shaping the future?

Good.

That is leverage.

Development

Did the executive's participation increase somebody else's ability to handle a similar situation in the future?

That matters enormously.

Coordination

Was the executive primarily connecting people, functions, or information that could not connect without them?

Now we should become curious.

Escalation

Did the issue reach the executive because it could not or would not be resolved at the appropriate level?

More curiosity.

Assurance

Was the executive checking, validating, approving, or following up because confidence in execution was insufficient?

Keep looking.

One coordination meeting proves very little.

So does one escalation.

So does one approval.

Organizations are messy.

But patterns tell us things individual events cannot.

What percentage of executive time is creating leverage?

What percentage is compensating for organizational friction?

How many decisions reach this level because they should?

How many arrive because nobody below it believes they can make them?

How often does executive involvement increase future capability?

How often does it merely resolve the immediate problem?

And perhaps most importantly:

What happens when the executive is not available?

The calendar may be the symptom

Microsoft's recent research describes a workforce experiencing significant fragmentation, with leaders reporting particularly high levels of chaos. [1]

Technology will undoubtedly help.

Artificial intelligence will remove administrative work.

Automation will improve coordination.

Meetings will become easier to summarize.

Information will become easier to find.

Executives will gain new tools for managing their workload.

But there is a risk hidden inside that progress.

If technology simply allows an executive to participate in more decisions, answer more questions, review more work, and process more escalations, we have increased the capacity of the bottleneck.

We have not necessarily removed it.

A more efficient dependency is still a dependency.

Which brings us back to the beginning.

Executives really are busy.

Many probably do need fewer meetings.

Some certainly need to delegate more effectively.

But before reducing the calendar, I would want to understand what created it.

Because the calendar might be telling us something.

It might be showing us where authority actually lives.

Where confidence breaks down.

Where functions fail to connect.

Where managers lack capability.

Where accountability requires executive reinforcement.

Where decisions routinely migrate upward.

Where the organization has learned that the safest path forward is to wait for someone more senior.

If that is what the calendar reveals, then the executive does not have a time management problem.

The organization has a dependency problem.

And removing three meetings from Thursday afternoon will not fix it.

The question worth asking is much simpler:

Why are your executives in the room?

Then keep asking until the calendar gives you the answer.

References

[1] Microsoft, 2025 Work Trend Index Annual Report and "Breaking Down the Infinite Workday." Microsoft reported employees being interrupted roughly every two minutes during core work hours, 52 percent of leaders describing work as chaotic and fragmented, increased late evening meetings, and greater cross time zone collaboration.

[2] McKinsey & Company, "Stop Wasting Your Most Precious Resource: Middle Managers." McKinsey's survey of 706 middle managers found 23 percent of time spent on strategy focused work, 28 percent on talent and people management, 18 percent on administrative work, and 31 percent on individual contributor work.

[3] Asana, Anatomy of Work Global Index 2023. Research conducted by GlobalWebIndex for Asana surveyed more than 9,600 knowledge workers across six countries and found senior leaders estimated losing 3.6 hours per week to unnecessary meetings.

[4] Michael E. Porter and Nitin Nohria, Harvard Business Review, "How CEOs Manage Time" and "What Do CEOs Actually Do?" The underlying Harvard Business School research tracked 27 CEOs for approximately 60,000 hours and examined how executive time was distributed across meetings, constituencies, decisions, strategy, and other responsibilities.