Yesterday, I attended two meetings.

Both were about making business decisions. Both involved experienced people, plenty of data, and a genuine desire to improve the business. Yet they unfolded in completely different ways.

The first meeting was about pricing. We were reviewing the retail prices of several products before launch. One item immediately stood out. Compared with the rest of the lineup, its price gap between two coutries was unusually small. We also compared it with competing brands and discussed whether the product still occupied the right position in the market.

Within twenty minutes, we decided to adjust the prices of several SKUs. The meeting ended, everyone knew what had been decided, and the next actions were clear.

Later that day, I joined another meeting.

This time, the topic was sales performance.

The Meeting That Had Data but Couldn't Decide

Sales had declined compared with the previous week. One idea was that we might be carrying too much slow-moving inventory, so perhaps we should allocate more inventory to our best-selling products. It sounded reasonable. In fact, everyone in the room probably agreed that it was worth considering.

Then someone asked a simple question.

How much of our A-ranked products have we allocated in the past?

Nobody knew.

Then came another question.

Did increasing allocation actually improve sales last time?

Again, nobody knew.

At that moment, the discussion changed. Instead of making a decision, we started discussing possibilities. Maybe the allocation wasn't large enough. Maybe the stores didn't display the products properly. Maybe demand had changed. Maybe another factor was responsible.

Eventually, the meeting ended—not because we had reached a decision, but because we had run out of time.

Why Did One Meeting Finish in 20 Minutes?

On the way home, I kept thinking about those two meetings.

At first, I assumed the difference was simply the topic. Pricing decisions are easier than sales decisions, I told myself.

But the more I thought about it, the less convincing that explanation became.

The pricing meeting wasn't faster because pricing is simple. It was faster because everyone already knew how the decision would be made.

There were clear decision criteria.

We weren't debating personal opinions. We were evaluating the same evidence against the same standards: international price positioning, competitor pricing, margins, and brand strategy.

Once the data met those criteria, the decision became almost inevitable.

KPIs Tell You What Happened. Decision Criteria Tell You What to Do Next.

The sales meeting was completely different.

We also had numbers. We had dashboards. We had KPIs. We knew whether sales were higher or lower than last week or last year.

But something important was missing.

We had measurements, but we didn't have decision criteria.

The KPIs told us that performance was below expectations, but they didn't tell us what decision should follow.

A decline in sales is a signal. It tells us something may need attention. But it does not automatically tell us whether to increase inventory, change the assortment, reduce price, increase marketing support, change distribution, or do nothing at all.

Every possible action depended on assumptions that nobody could verify during the meeting.

The conversation became longer because every new opinion was just as valid as the previous one. Without agreed criteria, the discussion had no natural endpoint.

Monitoring Metrics Are Not the Same as Decision Criteria

Organizations spend enormous effort defining KPIs.

Sales growth. Conversion rate. Inventory turnover. Forecast accuracy. Year-over-year growth. Week-over-week performance.

These metrics are valuable because they help teams understand reality.

But understanding reality is not the same as deciding what to do next.

A monitoring metric describes the current state.

A decision criterion creates a rule for choosing between actions.

That distinction may sound small, but in a meeting it changes almost everything.

What Happens When a Meeting Has No Criteria at All?

Some meetings are even harder.

Imagine a team trying to reduce product-code errors. Everyone agrees the current process isn't working. One person proposes additional training. Another suggests changing the workflow. Someone else recommends automation. A fourth person argues for another approval step.

Each idea has merit.

But how do you decide between them?

Is the priority implementation cost? Time? Accuracy? Ease of adoption? Employee workload? Long-term scalability?

Without agreeing on the criteria first, the meeting becomes a competition between opinions rather than an evaluation of alternatives.

That may be one reason operational-improvement meetings are often difficult to close. The team is trying to invent the solution and the decision criteria at the same time.

A Better Way to Start a Decision-Making Meeting

I'm beginning to think every important meeting needs two questions before the discussion begins.

Without those two questions, more data does not necessarily create more clarity. It can simply create more discussion.

This is also why a useful decision rule is different from simply tracking another KPI. The purpose of the rule is not only to observe what happened. It is to connect evidence to a decision.

Maybe We Don't Have a Meeting Problem

We often assume meetings fail because people disagree, because there is too much data, or because the meeting itself is poorly managed.

Those things certainly matter.

But perhaps the deeper problem is simpler.

Many meetings don't fail because they lack data. They fail because they lack decision criteria.

The pricing meeting had a clear decision and shared criteria, so the discussion had an endpoint.

The sales meeting had KPIs but no agreed rule for turning those KPIs into action, so the discussion continued.

The operational meeting had neither predefined criteria nor a clear way to evaluate competing solutions, so every opinion remained plausible.

These aren't simply different meeting styles.

They are different decision systems.