Every Monday morning, the meeting looked productive.

The dashboard was already on the screen by the time everyone settled into their seats. Revenue was slightly behind plan. Pipeline coverage had weakened in one region but improved in another. Several key opportunities had slipped into the following month. The discussion moved steadily from one market to the next, and each sales manager explained what had happened. The explanations were thoughtful. Questions were asked. Assumptions were challenged. Nobody seemed distracted, and nobody seemed confused. If someone unfamiliar with the business had walked into the room, they would probably have concluded that this was exactly what an effective sales review was supposed to look like.

That was precisely what made the following week so puzzling.

When the team gathered again, the dashboard looked different in small ways but strangely familiar in larger ones. A few numbers had moved, but several of the same accounts were still being discussed. Many of the same explanations returned. Even some of the proposed actions sounded familiar, as though they had been carried over from the previous meeting without ever quite becoming reality. It wasn't that the team lacked ideas. If anything, there were too many of them. What seemed to be missing was any clear sense that the previous discussion had changed how the organization behaved.

Most sales managers know this feeling well.

It isn't the frustration of working with people who don't care. Quite the opposite. Teams often understand the business remarkably well. Ask why a customer delayed an order, why conversion weakened in a particular channel, or why a retailer reduced purchases, and someone in the room can usually provide a thoughtful explanation. The meeting leaves everyone with the reassuring sense that the situation has been understood.

And yet understanding has an odd habit of disappearing somewhere between Monday's meeting and Monday's dashboard.

For a long time, I assumed this was simply an execution problem. It seemed like the obvious explanation. If everyone understood what needed to happen, then surely the remaining challenge was making sure people followed through. Like many managers, I found myself thinking about accountability, ownership, and discipline.

Then two meetings on the same day made me question whether I had been looking in the wrong place.

Two Meetings on the Same Day

The first meeting wasn't about sales.

It was about pricing.

One product immediately became the centre of the discussion because something about it looked unusual. Compared with the rest of the assortment, the price difference between Japan and the United States had narrowed considerably. Competitor pricing was projected onto the screen. Historical sales after previous price adjustments were reviewed. A handful of questions followed, but they all seemed to move in the same direction. Less than half an hour later, several SKUs had new prices.

The meeting ended with surprising confidence. Nobody asked for another week of analysis. Nobody suggested gathering additional data before deciding. Nobody argued that the business was too uncertain to act.

At the time, none of that seemed particularly remarkable.

It only became remarkable a few hours later.

That afternoon I joined the weekly sales review.

In many ways, it felt like a better meeting. There was more information, more discussion, and a much deeper understanding of the business. Someone suggested increasing the allocation of our highest-performing products. The proposal sounded sensible. It was exactly the kind of action everyone would expect after reviewing the dashboard.

Then someone asked a simple question.

“How much did we allocate last time?”

The room became quiet.

Another question followed.

“And what happened after we increased allocation?”

No one was certain.

The discussion changed almost immediately. Instead of deciding what to do, the meeting began exploring possibilities. Perhaps the increase hadn't been large enough. Perhaps stores hadn't displayed the products properly. Perhaps customer demand had shifted. Each explanation sounded plausible, yet every new possibility made the original decision feel slightly harder to make.

By the end of the meeting, there were more ideas than when it had begun.

There was no decision.

Why Did One Meeting Decide While the Other Kept Thinking?

Driving home that evening, I found myself thinking less about the sales meeting than about the contrast between the two meetings.

At first, I dismissed it. Pricing decisions, I told myself, are simply easier than sales decisions. It sounded reasonable for a while.

Then the explanation began to fall apart.

Pricing isn't simple. It involves competitors, margins, brand positioning, channel relationships, and long-term customer behaviour. If complexity explained why meetings struggled to reach decisions, the pricing discussion should have been every bit as difficult as the sales review.

Yet it wasn't.

The more I replayed both meetings in my mind, the less interested I became in the decisions themselves and the more interested I became in the process that produced them.

Eventually, I noticed something that hadn't stood out while I was in the room.

In the pricing meeting, nobody spent time deciding how they were going to decide.

That work had already been done.

The discussion wasn't about inventing a decision-making process. It was about asking whether reality had crossed a threshold the organisation already recognised.

The sales meeting felt fundamentally different.

There was no shortage of information. Revenue trends, pipeline coverage, forecast accuracy, conversion rates, customer updates—if anything, the sales meeting contained more information than the pricing meeting ever had.

What it seemed to lack wasn't analysis.

It lacked a shared understanding of what evidence would actually be enough to justify changing course.

When Understanding Becomes the End of the Meeting

Once I began looking for that distinction, I started noticing it elsewhere. Different companies, different industries, different dashboards, yet remarkably similar meetings. People understood the business exceptionally well, but returned to the same discussion week after week. Meetings produced thoughtful analysis but very little commitment. Organisations measured performance with extraordinary precision while remaining surprisingly vague about what performance was supposed to change.

Perhaps we've become so accustomed to measuring performance that we've quietly assumed measurement and decision-making are part of the same process.

They may not be.

The dashboard succeeds in helping people understand the business. But understanding does not automatically reveal the moment when an organisation should stop analysing and start changing what it does.

That distinction is close to what I have come to think of as the difference between an insight and a business signal. An insight helps us understand what may be happening. A signal goes further: it represents a condition that the organisation has already decided deserves a response. I explore that distinction more fully in Insight vs Signal.

Once viewed this way, the familiar frustration of the weekly sales review starts to look slightly different.

Perhaps the meeting is not failing because people ignore the data.

Perhaps the organisation has never decided what the data would need to say before people are expected to behave differently.