Before changing how a sales organization works, it is worth understanding what is actually preventing it from working better.

A company's sales results have been disappointing. The pipeline contains plenty of opportunities, but too few turn into orders. Quotations remain open for months, forecasts are unreliable, and management struggles to explain why promising projects repeatedly lose momentum.

Something needs to change — and initiatives are rarely in short supply. A new sales methodology is proposed, CRM reporting requirements are expanded, the team receives additional training, and management introduces more frequent pipeline reviews.

These initiatives may be useful. But an important question usually remains unanswered: what exactly was causing the problem?

Similar symptoms, different causes

Commercial organizations can experience similar difficulties for very different reasons.

Consider a low quotation conversion rate. It may indicate that salespeople are insufficiently qualifying opportunities. It may equally indicate that the company is targeting customers whose requirements do not match its capabilities. Perhaps the technical offering is competitive, but delivery times are preventing customers from committing. Perhaps the team is spending considerable time on smaller, low-probability opportunities while more attractive accounts receive insufficient attention. Or perhaps conversion is acceptable within the company's strongest segments, and a recent expansion into a new market is simply pulling down the overall average.

Each of these situations might produce the same headline problem: too many quotations and too few orders. But the appropriate response to each could be very different.

The danger of treating symptoms

Imagine a company where management believes salespeople are not following up consistently enough. The CRM contains numerous quotations without recent activity, and several opportunities have remained open longer than expected. Management introduces a stricter follow-up procedure: salespeople are now required to contact customers at fixed intervals and document every interaction.

Activity increases. CRM compliance improves. Yet conversion remains largely unchanged.

Further investigation reveals that many of those customers were still comparing possible technical solutions internally. Some had no approved investment budget. Others were requesting quotations primarily to establish preliminary project costs. The follow-up procedure had addressed a visible symptom, but did little to change the circumstances that were preventing those customers from making decisions.

That does not mean follow-up discipline was irrelevant. It means the intervention was not sufficient to address the wider problem.

Looking at how the process actually works

Understanding a sales process requires more than studying its formal structure. A company may have a clearly defined sequence of stages, documented procedures and an extensively configured CRM. But the way people actually work may differ considerably from the process on paper.

Salespeople may bypass particular stages because those stages do not fit the customers they encounter. Technical support may become involved too late, and quotations may require approvals that introduce avoidable delays. Different account managers may approach similar opportunities in entirely different ways. Some of these differences are productive adaptations to customer needs; others create inconsistency or inefficiency.

The useful question is therefore not simply whether everyone follows the process. It is whether the process helps the organization make better commercial decisions.

Combining data with the people behind it

Sales data can reveal patterns: where opportunities typically slow down, which customer groups convert most successfully, how long it takes to move from technical evaluation to quotation, and whether particular products or applications are consistently associated with stronger results.

These observations provide useful starting points, but the numbers rarely explain themselves. The people involved in the process often understand circumstances that are not visible in the CRM. Salespeople may know why certain quotations are difficult to convert. Technical colleagues may recognize recurring application problems. Management may understand commercial or strategic constraints that influence how the team operates.

One caveat: conversations produce interpretations too. What colleagues describe is shaped by their position, their preferences and their memory of what happened. The value of combining perspectives is not that people are right and data is wrong — it is that each can test the other. Brought together, they can reveal explanations that neither the data nor the individual conversations would establish alone. And sometimes the result is the discovery that an apparent problem was not a problem at all.

Understanding before changing

Analysis should not become an excuse to postpone necessary action. Organizations rarely have complete information, and waiting for absolute certainty can be just as unproductive as acting too quickly. The objective is to develop enough understanding to choose a reasonable intervention, identify what improvement would look like, and evaluate whether the change produces the intended effect.

That last step deserves its own discipline. Before implementing a change, state what effect is expected, on which measure, and when the result will be reviewed. Without that, a busy intervention and a successful one look identical from the inside.

Sometimes the answer will be training. Sometimes it will be a different process, better customer selection, improved technical support or a change in commercial priorities. And sometimes the most useful conclusion is that the organization should stop investing time in activities that contribute very little to its results.

The point is not that every improvement requires an extensive study. It is that improvement is a loop, not an event: a grounded diagnosis, a chosen intervention, and the discipline to check the result against the expectation. Change a process without understanding the problem, and you risk improving the wrong thing.

From the book

Organizational navigation - understanding what is actually preventing a sales organization from working better - is explored in more depth in Chapters 16 and 17 of Sales Between the Lines, alongside the wider role of observations, context and recurring patterns in making sense of complex commercial situations.