DEV Community

Cover image for The Startup Meeting That Should Have Been an Email
👉 Peesh Chopra | Startup Mentor
👉 Peesh Chopra | Startup Mentor

Posted on Fully Autonomous

The Startup Meeting That Should Have Been an Email

TL;DR

As startups grow, meetings multiply faster than clarity. The problem is not meetings themselves. The problem is using meetings to solve issues that require ownership, preparation, or a simple decision.

It starts with a good reason

A startup begins with five people.

Everyone sits together.

Questions get answered quickly.

Decisions happen in minutes.

Nobody worries about scheduling.

Then the company grows.

Five people become fifteen.

Fifteen become thirty.

Suddenly, the calendar is full.

Monday planning meeting.

Tuesday product meeting.

Wednesday leadership meeting.

Thursday project meeting.

Friday review meeting.

The company is talking constantly.

But is it actually moving faster?

Meetings can hide a leadership problem

When something is unclear, the easiest response is often:

"Let's have a meeting."

Someone sends an invite.

Everyone joins.

The topic gets discussed.

People leave with slightly different interpretations.

Another meeting is scheduled.

This can continue for months.

The real problem is often not communication.

It is unclear ownership.

Who actually owns the decision?

Consider a simple product decision.

Five people are invited to discuss it.

Everyone gives an opinion.

The conversation becomes longer.

Eventually, someone says:

"Let's revisit this next week."

Why?

Because nobody knows who has the final call.

A meeting cannot fix unclear accountability.

Someone needs to own the decision.

Not every decision needs consensus

This is especially important as a company grows.

Founders sometimes believe everyone should agree before an important decision is made.

That sounds collaborative.

It can also become painfully slow.

Good teams know the difference between:

Input

and

Approval

You can ask five people for input.

That does not mean five people need to approve the decision.

One person should usually be accountable for making the call.

The hidden cost of unnecessary meetings

The obvious cost is the time spent in the room.

The less obvious cost is context switching.

A developer preparing for a deep technical task may lose momentum because of three unrelated meetings.

A sales leader may spend an hour discussing a problem they could have answered with a five-minute message.

A founder may spend half the day in meetings and then work on important decisions late at night.

The calendar looks productive.

The output tells a different story.

Try this before scheduling another meeting

Ask four questions:

What decision needs to be made?

Who owns that decision?

What information do they need?

Could this be resolved asynchronously?

If the answer to the last question is yes, skip the meeting.

Write it down.

Share the relevant information.

Let the owner decide.

Some meetings are absolutely worth having

This is not an argument for eliminating meetings.

Some conversations need real interaction.

Difficult customer problems.

Strategic planning.

Team conflicts.

Complex decisions with significant consequences.

These situations benefit from discussion.

The goal is not fewer meetings at any cost.

The goal is better meetings.

A simple rule for founders

Every recurring meeting should have a reason to exist.

Ask:

"If we stopped this meeting for the next three months, what would break?"

If nobody can answer clearly, the meeting deserves another look.

You may discover that the meeting is no longer solving the problem it was created to solve.

Replace meetings with ownership

One of the strongest changes a startup can make is moving from:

"Who should attend?"

to:

"Who owns this?"

That small shift changes how teams operate.

People stop waiting for group approval.

Managers stop becoming communication bottlenecks.

Decisions become clearer.

Execution gets faster.

The calendar tells you something about the company

Take a look at your team's calendars.

If they are packed with meetings, ask what the calendar is revealing.

Maybe the company has grown.

Maybe responsibilities are unclear.

Maybe managers do not trust teams to make decisions.

Maybe information is scattered.

The meeting problem may actually be a symptom of a deeper organizational problem.

Final thought

Meetings are not the enemy.

Unnecessary meetings are.

A healthy startup creates enough space for people to think, build, sell, serve customers, and make decisions.

The next time someone suggests another meeting, don't reject it automatically.

Just ask one question:

"What decision will be different when this meeting ends?"

If nobody knows the answer, you probably don't need the meeting yet.

Top comments (0)