The Map Is Not the Territory

One of the most useful—and most misapplied—mental models in business comes from Alfred Korzybski:

The map is not the territory.

In pricing, we forget this constantly.

Pricing structures, ERP records, customer segments, dashboards, and margin reports are maps. They are clean, static, mathematical representations of how the world should work.

The market—the territory—is dynamic, emotional, political, and messy.

Problems begin when we confuse the two.

When Measurement Replaces Understanding

When leaders confuse measurement with understanding, they stop learning.

Pricing data is often treated as a verdict:

• “The data says this price is right.”

• “Sales just needs to follow the model.”

• “Overrides are high, so discipline is low.”

But data should provoke curiosity—not compliance.

When pricing data and sales behavior disagree, that tension is often treated as resistance. More often, it’s a signal that the model is missing important context.

A Familiar Pricing Conversation

Not long ago, I sat in a meeting with a sales leader and a pricing leader at a mid-sized distributor.

The sales leader made an observation that felt obvious to anyone close to customers: buyers grouped into a single customer segment on paper behaved very differently in practice.

OEM customers buying for one industry purchased differently than OEM customers buying for another. Application mattered. Market context mattered. Treating them all the same forced salespeople to override system pricing just to reflect reality.

As the conversation explored more nuanced customer segmentation, the pricing leader interrupted with a reasonable concern.

Expanding customer segments would significantly increase the number of pricing records. System complexity would rise. Governance would get harder.

He wasn’t wrong.

But neither was the sales leader.

You Can’t Eliminate Complexity—Only Move It

This is the question pricing teams rarely ask directly:

Where do you want complexity to live?

You have two choices:

• Absorb complexity in the pricing structure (more segmentation, more nuance, more governance)

• Push complexity into human behavior (overrides, exceptions, judgment calls, workarounds)

When pricing structures don’t reflect how customers actually buy, overrides aren’t a failure of discipline.

They’re a signal that the map is missing important terrain.

Keeping the map simple doesn’t eliminate complexity. It just relocates it.

When Clean Models Create Dirty Outcomes

This is how pricing initiatives quietly fail.

From pricing’s perspective:

“We built a rational, consistent model.”

From sales’ perspective:

“The model doesn’t reflect how customers buy.”

Both sides are acting rationally. Trust erodes anyway.

Overrides become the shadow system—sales compensating for nuance the map can’t express.

The system stays clean. Confidence in system pricing does not.

Understanding Model Limits Matters

Every pricing model has an intended use.

Some pricing models are designed to optimize repeat, everyday transactional business. They were never meant to be the basis for large, competitive, project-driven quotes.

Using a model outside its design intent doesn’t make it wrong.

It makes it dangerous.

Pricing models don’t fail. They get blamed for problems they were never designed to solve.

Respecting the Territory (Without Worshiping It)

There’s an important nuance here.

When the map disagrees with the territory, the territory is always right—but that doesn’t mean we blindly accept every piece of feedback at face value.

As a former buyer, I know how easy it is to end an unwanted conversation by saying, “Your price is too high.”

Price objections require investigation, not automatic acceptance:

• Who did we lose to?

• Was it the same product?

• Domestic vs. import?

• Was price the issue—or trust, availability, or preference?

Reality matters.

But it must be interpreted, not merely echoed.

The Goal Isn’t Better Maps

The goal isn’t perfect pricing models.

The goal is better navigation.

That requires leaders who:

• Treat dashboards as prompts for inquiry, not verdicts

• Talk to sales about confidence, not compliance

• Follow up on lost deals beyond “price was too high”

• Revisit pricing structures as markets evolve

Maps are tools—not truth.

When mistaken for truth, they enable poor decisions made with a high degree of confidence.

And in pricing, confidence applied to the wrong model is often more dangerous than uncertainty handled thoughtfully.