The Hidden Assumptions Founders Make When They Look at Metrics
Two founders can look at the exact same dashboard and walk away with completely different decisions.
Same numbers.
Same charts.
Same week.
Different conclusions.
I’ve seen this happen repeatedly.
And it has very little to do with intelligence or experience.
It has everything to do with assumptions.
Same numbers.
Same charts.
Same week.
Different conclusions.
I’ve seen this happen repeatedly.
And it has very little to do with intelligence or experience.
It has everything to do with assumptions.
We don’t look at metrics neutrally
Founders like to believe we’re objective when we look at data.
We’re not.
We bring context, pressure, goals, ego, and recent conversations into the room with us. All of that quietly shapes what we see.
If I’m worried about runway, I’ll zoom in on costs.
If I’m thinking about growth, I’ll focus on top-line movement.
If I’ve just had a difficult customer conversation, I’ll scrutinise churn.
The dashboard hasn’t changed.
But my mental frame has.
We’re not.
We bring context, pressure, goals, ego, and recent conversations into the room with us. All of that quietly shapes what we see.
If I’m worried about runway, I’ll zoom in on costs.
If I’m thinking about growth, I’ll focus on top-line movement.
If I’ve just had a difficult customer conversation, I’ll scrutinise churn.
The dashboard hasn’t changed.
But my mental frame has.
We assume movement equals meaning
One of the most common hidden assumptions is that change automatically requires action.
Conversion rate dips slightly.
Traffic spikes unexpectedly.
ROAS fluctuates.
The instinct is to intervene.
But not every movement is a signal. Some of it is noise. Some of it is seasonality. Some of it is simply variance.
When founders assume that every shift demands a response, they end up reacting instead of thinking.
Conversion rate dips slightly.
Traffic spikes unexpectedly.
ROAS fluctuates.
The instinct is to intervene.
But not every movement is a signal. Some of it is noise. Some of it is seasonality. Some of it is simply variance.
When founders assume that every shift demands a response, they end up reacting instead of thinking.
We assume metrics explain themselves
Another quiet assumption is that numbers are self-explanatory.
They aren’t.
A 3% increase in conversion could mean:
– Better targeting
– A pricing shift
– A temporary promotion
– Or random distribution effects
Without context, the metric is incomplete.
But founders often move straight from number to conclusion without interrogating the story underneath it.
They aren’t.
A 3% increase in conversion could mean:
– Better targeting
– A pricing shift
– A temporary promotion
– Or random distribution effects
Without context, the metric is incomplete.
But founders often move straight from number to conclusion without interrogating the story underneath it.
We assume our interpretation is rational
This one is uncomfortable.
We assume that because we’re looking at data, our conclusion must be logical.
But interpretation is shaped by:
– What we want to be true
– What we fear might be true
– What we’ve already committed to
– What narrative we’ve been telling investors or the team
Two founders can see the same dashboard and act differently because they’re optimising for different things.
Security.
Growth.
Validation.
Control.
The metrics are the same.
The priorities aren’t.
We assume that because we’re looking at data, our conclusion must be logical.
But interpretation is shaped by:
– What we want to be true
– What we fear might be true
– What we’ve already committed to
– What narrative we’ve been telling investors or the team
Two founders can see the same dashboard and act differently because they’re optimising for different things.
Security.
Growth.
Validation.
Control.
The metrics are the same.
The priorities aren’t.
The real work isn’t collecting data
It’s exposing the assumptions sitting underneath it.
What am I assuming this number means?
Why does this metric feel urgent?
What story am I attaching to it?
That’s where better decision-making begins.
Inside Nudge, this is something we think about constantly. Not just surfacing metrics, but helping founders slow down enough to question their interpretation.
Because better dashboards don’t automatically produce better decisions.
Clearer thinking does.
What am I assuming this number means?
Why does this metric feel urgent?
What story am I attaching to it?
That’s where better decision-making begins.
Inside Nudge, this is something we think about constantly. Not just surfacing metrics, but helping founders slow down enough to question their interpretation.
Because better dashboards don’t automatically produce better decisions.
Clearer thinking does.