A CRM can contain accurate information while still presenting a misleading picture of what is happening.

A pipeline dashboard mixes two kinds of content. Some fields describe things that actually happened: a quotation date, a meeting, a confirmed technical requirement. Others contain judgments rather than records — some about the future, such as an expected closing date or a probability, others about the past, such as the reason a deal was lost.

On screen, both types look identical — same font, same color, same apparent authority. The dashboard may not show which is which.

Where interpretations enter the record

A factual field can usually be filled in close to the event it describes. An interpretive field depends on judgment — and one common setting for that judgment is the end of a process, under time pressure, choosing from a fixed list of options.

Consider the loss reason. A customer requested a discount and then selected another supplier, so the salesperson selects "price." That may be exactly right. It may also be that the customer left for delivery reliability, and the discount request was simply the last objection raised. Unless the underlying reason was confirmed with the customer, the field records an interpretation — and the CRM does not distinguish a verified explanation from a plausible one.

The record captures the classification. Whether the classification captures the cause is another question.

When interpretations become organizational knowledge

The stakes become clear the moment those fields are aggregated.

A company analyzes lost opportunities and finds that 40 percent were attributed to price. Management concludes pricing is a competitive weakness and starts investigating lower margins.

The arithmetic is perfect. But how were the classifications made? Did customers confirm price as the deciding factor, or did salespeople select the last objection from a dropdown? If the categories were inconsistent or weakly supported, the analysis measures sales behavior more than market reality — and the margin decision rests on it.

The distinction worth protecting

The solution is not automatically more fields and more reporting, which tends to add administration rather than understanding. It is keeping three things visibly separate:

• Observations — things that happened, verified.

• Interpretations — plausible explanations, unconfirmed.

• Customer-reported explanations — reasons provided by the customer, offering stronger evidence of their perspective without necessarily establishing the underlying cause.

A CRM is valuable because it simplifies complex commercial reality into a usable structure. But structure always simplifies, and the simplification is invisible in the dashboard. An opportunity can have an accurate value, quotation date, and contact history while containing considerable uncertainty about the customer's priorities and decision process.

The CRM may be up to date. The organization's understanding of it may not be — and no report flags the difference.

From the book

Assumptions, interpretations and the uncertainty that keeps them honest are explored in more depth in Chapters 10 and 12 of Sales Between the Lines, alongside the wider role of ambiguity in understanding what commercial information is actually worth.