Meetings Are Where Execution Goes to Die

A lot of teams think they have a speed problem.

What they usually have is a meeting problem.

Not because meetings are evil.

Because most meetings are badly designed, overused, and completely disconnected from forward motion.

That is how smart companies slowly become sticky.

Everyone is talking. Nobody is really moving.

According to Atlassian’s 2026 meetings research, meetings are the number one barrier to productivity for the 5,000 knowledge workers it surveyed. Atlassian says meetings are ineffective 72% of the time, 78% of people feel they are expected to attend so many meetings it is hard to get work done, and 54% frequently leave meetings without a clear idea of next steps or who owns what.

That is brutal.

Asana sees the same drag from a slightly different angle. In its 2025 work-about-work research, knowledge workers spend 60% of their time on work about work, including 103 hours a year in unnecessary meetings.

That is not collaboration.

That is organizational sludge.

Most meetings exist because the system is weak.

People tell themselves the meeting is necessary because:

Sometimes that is true.

A lot of the time, the meeting exists because:

That is why “having fewer meetings” is only half the fix.

The real fix is to stop using meetings as duct tape.

I use one blunt test:

Is this meeting the fastest way to get to a better decision, clearer commitment, or lower risk?

If not, it probably should not happen live.

That immediately kills a lot of junk.

Examples of things that usually do not need live meetings:

The default should not be: “let’s hop on.”

The default should be: “what is the lightest format that moves this forward?”

I think every company should classify meetings into four buckets.

Used when tradeoffs need to be resolved live.

Used to inspect metrics, risks, and outcomes against a standard.

Used to improve a person’s thinking, not to move a project.

Used intentionally, not disguised as operational work.

Anything else is suspicious.

A lot of teams try to solve this with calendar hacks.

That helps a little.

The deeper fix is structural.

I would redesign meetings using five rules.

Atlassian says 62% of workers often attend meetings that do not even state a goal in the invite. That is ridiculous and very fixable.

Not one “facilitator.” One owner.

They are responsible for:

Atlassian’s async research makes a good point: live meetings can increase groupthink and bias, while writing before meeting helps people think more clearly.

This is one of the simplest upgrades available. Ask for pre-read comments or written options before the call.

No vague “we’ll circle back.”

Leave with:

Atlassian found 80% of workers think most meetings could be done in half the time.

I believe them.

Let’s say a GTM team has:

That feels normal.

It is also how execution dies politely.

I would rebuild it like this:

That is enough to recover real time quickly.

One of the things older operators understand is that meetings feel productive because they simulate progress.

Everyone showed up. Everyone talked. Everyone heard each other.

But execution does not care how many people attended.

It cares whether anything got clearer, faster, or safer.

The good news is that this is fixable without drama.

You need:

Do that, and the company gets a little quieter.

Which is usually a sign it is finally getting faster.