The Tyranny of the Average in Sales (Part 2)
When the map becomes more real than the deal
In Part 1, we looked at the first lie: the idea that your ICP describes a buyer.
It doesn’t. It describes a pattern.
The same lie shows up again - but this time it doesn’t live in Marketing.
It lives in your pipeline.
The substitution problem
Every sales organization needs a map.
Stages. Probabilities. Conversion rates. Average cycle time. Average deal size. Pipeline coverage. Velocity.
Without them, you don’t have a business.
You have a collection of stories.
And stories don’t forecast.
So you build models.
You build systems that turn uncertainty into numbers.
And then something subtle happens.
The model stops being a tool.
It becomes the reality.
The map becomes more real than the territory.
Averages don’t predict deals. They describe the past.
Your forecast model says deals at this stage close at 60%.
So you count it.
But the model doesn’t know that the champion just took a new role.
It doesn’t know the economic buyer is about to get reorganized out.
It doesn’t know procurement is introducing a new vendor review process that will add four months to everything.
The model only knows what happened across the last 200 deals.
It is backward-looking by design.
And you are trying to use it as if it were forward-looking.
That is the first substitution.
“This deal is moving too slowly”
Your pipeline review flags deals moving “too slowly” based on average cycle time.
So your manager pressures the Rep to accelerate.
But the deal isn’t slow.
It’s careful.
The buying committee is fractured.
The risk is political, not technical.
The internal alignment hasn’t happened yet.
Pushing doesn’t speed it up.
It kills it.
Because the buyer is not “delaying.”
They are protecting themselves.
And the average cycle time doesn’t capture self-protection.
It captures duration.
That is the second substitution.
“Engage five stakeholders”
Your account strategy playbook says “engage five stakeholders.”
Because across 200 deals, deals with five stakeholders closed more often.
So your Rep dutifully builds the list.
They schedule meetings. They do the rounds. They “multi-thread.”
And they waste three weeks talking to people who don’t matter.
Because in this account, there are two people who matter and seven people who perform the theater of inclusion.
The playbook sees “stakeholders.”
The deal has power.
That is the third substitution.
The dashboard is a comfort object
Pipeline analytics is not only about accuracy.
It is also about emotional management.
A dashboard creates the feeling of control.
It gives leaders something to look at when they don’t know what is actually happening in the deal.
And in Sales, the feeling of control is worth almost as much as actual control.
So the organization starts optimizing for what the dashboard can see.
Stage progression.
Activity counts.
Next steps.
Deal hygiene.
Forecast categories.
And what the dashboard cannot see - the real deal - gets deprioritized.
Influence.
Fear.
Internal conflict.
Political risk.
Career stakes.
Legitimacy.
You can’t roll those up into a weekly forecast.
So you pretend they don’t exist.
The stage is not the deal
Stages are abstractions.
They exist to make deals legible.
But in complex Sales, legibility is not the same thing as progress.
A deal can look healthy in Salesforce and be dead in the account.
A deal can look “early” in Salesforce and be close in reality.
A deal can be “late stage” and still have no internal buyer consensus.
A deal can have perfect MEDDICC fields and still be fundamentally unwinnable.
Because the stage tells you where the deal is in your process.
Not where the buyer is in theirs.
And those two are rarely aligned.
The average is not the territory
This is where Jung’s point becomes operational.
Statistics describe populations.
They do not describe individuals.
Your pipeline model describes what deals typically did.
It does not describe what this deal will do.
And the more complex the sale, the more the deal behaves like a person.
Unpredictable.
Context-dependent.
Shaped by fear, ego, status, and internal politics.
Capable of changing direction for reasons no dashboard can detect.
Your pipeline model cannot see that.
It can only measure the shadow of what already happened.
What the best Reps do differently
The best Reps don’t reject the model.
They refuse to be hypnotized by it.
They use the average as a starting hypothesis, not a conclusion.
They know what typically happens - and then they investigate what is actually happening.
They ask second-order questions.
They map influence, not org charts.
They listen for what’s unsaid.
They notice when behavior doesn’t match what the title “should” imply - and they get curious instead of confused.
They treat the deal like an individual, not a pipeline stage.
And this is the part that will make some leaders uncomfortable:
That work is not fully legible.
It doesn’t always produce neat stage progression.
It doesn’t always look like “momentum.”
Sometimes it looks like deviation.
Sometimes it looks like improvisation.
But what you call improvisation, they call adaptation.
The paradox
You need pipeline models.
You need averages.
You need dashboards.
But the moment you start managing the deal as if it were the dashboard, you lose the deal.
Because the deal was never the dashboard.
The dashboard was only a guess about what deals generally do.
Averages scale operations.
But deals are won in the present.
The cliffhanger
In Part 3, we’ll go one level deeper.
Because the tyranny of the average doesn’t just distort deals.
It distorts people.
It trains Reps to make their deals look like the model instead of understanding what is real.
It creates a culture where stage progression matters more than truth.
And once that happens, your sales organization becomes efficient.
Predictable.
And strangely fragile.
Part 3 will explore the leadership trap: how managing by averages erodes judgment, agency, and ultimately the ability to win non-average deals.
#B2BSales #EnterpriseSales #PipelineManagement #SalesLeadership #BuyerPsychology