DEV Community

Kinetic Goods
Kinetic Goods

Posted on

Why Your Meetings Produce No Decisions (And How to Fix It)

You've been in this meeting. Everyone talks.Opinions are shared. Concerns are raised. The conversation goes in circles. And then the meeting ends with no clear decision.

Sound familiar?

The problem isn't your team. The problem is the meeting structure.

Why Discussions Don't Produce Decisions

Discussions are divergent. They explore ideas, surface concerns, and generate options. That's valuable.

Decisions are convergent. They narrow down to a single choice and commit to action. That's also valuable.

Most meetings stay in discussion mode the entire time. They never make the transition to decision mode. So nothing gets decided.

The Three Question Test

Before your next meeting, ask: "What decision needs to be made?"

If you can't answer that question, you're not having a decision meeting. You're having a discussion meeting. And discussion meetings don't produce outcomes.

How to Make Decisions in Meetings

Name the decision out loud. "By the end of this meeting, we need to decide X." Put it on the screen. Everyone needs to know what they're deciding.

Limit the options. If you have 8 options, you'll discuss forever. Narrow to 2-3 realistic options before the meeting. "We're deciding between Postgres, MongoDB, and DynamoDB. Not other databases."

Identify the criteria. "The 3 things that matter most are: cost, latency, and team expertise." This focuses the discussion on what actually matters.

Assign a decision maker. Sometimes it's a vote. Sometimes it's a manager. Sometimes it's the person most affected. But someone needs to make the final call. Without this, you get analysis paralysis.

Document it. "DECISION: We're using Postgres. REASON: Best fit for team expertise and reliability requirements. TIMELINE: Implementation starts Monday." If it's not written, it didn't happen.

What to Do When You Can't Decide

Sometimes you genuinely don't have enough information. That's fine. The decision is: "We need more information before we can decide."

Schedule a follow-up meeting to get that information. Set a deadline for when the information will be available. And make sure someone owns getting it.

The System Behind It

I use a Meeting Mastery System that makes decision-making the default:

  • Pre-meeting template that forces you to name the decision before you meet
  • Decision criteria checklist
  • Decision log template that captures outcomes and reasons
  • Follow-up tracker that ensures decisions get implemented

The goal isn't to have fewer discussions. It's to have decisions that actually get made.

[Link to Meeting Mastery System in bio]

Top comments (0)