Every Monday morning at nine o'clock, the sales team gathers for its weekly business review. Nobody is late. Laptops are already open, last week's sales figures fill the screen at the front of the room, and everyone has a fairly good idea of what is coming. The numbers were circulated days ago, so there are few genuine surprises left. What remains is the conversation about why the business performed as it did and, more importantly, what everyone intends to do next.

The Sales Director studies the screen for a moment before asking the familiar question. “Sales are down. Walk us through what's happening and tell us what you're going to do differently.” The first salesperson promises to reduce stock-outs of the best-selling products. Another wants to strengthen product education at retail. A third suggests improving product knowledge across the team. Each answer is entered into the meeting minutes as an action item, nobody objects, and the discussion continues until the meeting finishes almost exactly on schedule.

Seen from the outside, there is very little to criticize. The team reviewed the numbers, discussed what had happened, and left with a list of things to improve. Many organizations would describe exactly this kind of meeting as data-driven management: performance is visible, people are accountable for their business, and every discussion produces an action plan. Yet meetings like this always left me with a faint sense that something important had been skipped, even though for a long time I couldn't explain what it was.

When a Good Action Plan Feels Strangely Incomplete

Consider one of the most common answers: “We need to improve product knowledge.” There is nothing inherently wrong with it. Product knowledge is valuable, better-informed salespeople usually have stronger customer conversations, and almost no manager would argue that the team should know less about what it sells. The interesting question is not whether product knowledge matters, but how it became the action that deserved the team's attention at that particular moment.

Had anyone actually concluded that weak product knowledge was the primary reason sales declined? Perhaps pricing had become less competitive, perhaps the assortment no longer matched the customer visiting those stores, perhaps repeated stock-outs had already pushed demand toward another brand, or perhaps the channel itself was simply becoming less productive. Any of those explanations might have been true, but the meeting rarely spends much time comparing them. “Improve product knowledge” enters the minutes, and everyone moves on as though an important choice has just been made.

Occasionally, a manager does push a little further. “Do you really think product knowledge alone will improve sales?” The salesperson pauses, looks back at the numbers, and adds another initiative: “We've also had stock-outs over the last two weeks, so we'll focus on alternative products until inventory improves.” The additional answer usually satisfies the room. It is sensible, difficult to oppose, and easy to add beneath the first action item.

That was the moment I began paying less attention to whether the individual actions were reasonable and more attention to how easily they appeared. The suggestions seemed to emerge not because the meeting had worked its way toward them, but because the meeting required an answer. Once an answer sounded responsible enough, the curiosity disappeared.

The Meeting Looks Different From the Hallway

One of the most revealing parts of these meetings often happens after everyone has left the room. People return to their desks noticeably quieter than when they arrived. Someone sighs. Someone else says, “Let's see what happens next week.” Occasionally there is a brief complaint about inventory, pricing, or the market before everyone gets back to work. From the front of the conference room, the meeting appeared constructive. From the hallway outside, it can feel strangely unfinished.

Managers may reasonably interpret that atmosphere as disappointment about the sales results themselves. After all, nobody enjoys missing a target. But over time I started wondering whether at least part of that heaviness came from somewhere else: the quiet recognition that an hour of discussion had produced several new tasks without giving anyone much confidence that tomorrow's business would actually be different.

For years, I treated this as an execution problem. Perhaps salespeople weren't following through consistently enough. Perhaps managers needed to push harder on accountability. Perhaps the team simply lacked discipline. Those explanations were attractive because they placed the failure after the meeting: the discussion had produced the right answer, and the organization had simply failed to execute it.

The more meetings I watched, however, the harder that explanation became to maintain. The salespeople were already working hard. Many knew their customers better than anyone at headquarters, understood which accounts were losing confidence long before a dashboard showed it, and spent far more time solving customer problems than a weekly report could ever capture. If effort were the missing ingredient, there should have been much less repetition from one review to the next.

Actions Are Easy When Nobody Has to Choose

Eventually, a different pattern became difficult to ignore. “Improve product knowledge.” “Communicate more closely with stores.” “Reduce stock-outs.” Each is a perfectly respectable initiative, but they also share a useful characteristic: almost nobody needs to disagree with them. They do not force the organization to abandon one path in order to pursue another, and they rarely require someone to explain why this intervention deserves priority over everything else the team could do.

A genuine decision feels different. “This product is no longer right for this channel.” “We should stop discounting.” “We should reduce allocation to these stores and move the inventory somewhere else.” Statements like these create friction because they close one possibility while opening another. They invite questions, require evidence, and carry the possibility that six months later the organization may discover it made the wrong call.

That difference matters when a salesperson is sitting in a room with disappointing results projected behind them. There is a large psychological gap between proposing an idea that might visibly fail and promising to improve something that nobody could reasonably oppose. Over time, people do not need to be told which kind of answer is safer. The meeting teaches them.

A meeting can quietly train people to give answers that are easy to accept rather than decisions that are worth testing.

This does not require bad managers, timid employees, or a dysfunctional culture. In fact, it can happen among thoughtful people who genuinely want the business to improve. Each person is simply responding rationally to the environment around them. The salesperson wants to demonstrate ownership. The manager wants to leave the meeting with a credible plan. The organization wants evidence that something is being done. A broadly agreeable action satisfies all three needs, even if nobody has established that it is the best response to the underlying problem.

Perhaps We Have Been Looking at Execution Too Late

Once I began viewing the meeting this way, the repeated conversations made more sense. The organization had no shortage of actions. It had no shortage of people willing to work on them either. What it often lacked was a visible connection between the problem being observed, the alternatives available, and the reason one path had been chosen over the others.

This is where an action plan and a decision begin to diverge. An action tells someone what to do. A decision explains why the organization believes that action is worth taking instead of another one. The distinction may sound academic until the following week, when sales remain weak and everyone needs to decide whether the previous initiative should be continued, changed, or abandoned. Without knowing what the action was expected to change, there is very little to learn from the result.

“Improve product knowledge” may still be exactly the right decision. But if that is the case, the meeting should be able to explain what observation led the team there, what competing explanation it chose not to pursue, and what would eventually convince everyone that the hypothesis was wrong. At that point, the conversation is no longer about pushing a salesperson harder. It is about giving people a clearer way to learn from what happens next.