The myth of Data-Driven Product Management
E.H. Carr and the Myth of Data-Driven Product Management.
Why Product Managers Are Really Interpreters
One of the most influential books I read during my history studies was What Is History? by E.H. Carr. It is not really a book about kings, battles or dates, although historians naturally end up dealing with all three. It is a book about evidence, and more importantly, about what evidence actually means once someone begins to interpret it.
For product managers working in a world of dashboards, analytics platforms, customer feedback tools and AI-generated insight, Carr’s ideas feel surprisingly modern. Perhaps they are more relevant now than ever, because the central problem has not changed. We are surrounded by facts, but facts alone do not tell us what to do.
Facts Do Not Speak for Themselves
Carr challenged the popular idea that historians simply collect facts and allow the truth to reveal itself. His argument was more uncomfortable than that. Facts are everywhere, but meaning is rare. The historian’s job is not merely to gather information; it is to decide which information matters, how it should be understood, and what kind of story it helps to explain.
As Carr famously wrote:
“Study the historian before you begin to study the facts.”
His point was that every historian interprets evidence through a particular lens. The same applies to product managers. We like to claim we are data driven, but data rarely gives us complete answers. More often, it gives us clues that need to be tested, challenged and placed into context.
Suppose usage falls by 15%. One team may conclude the product needs more features, another may decide onboarding is broken, and a third may argue that pricing is the real issue. The data has not changed, but the interpretation has. That is where product management begins to look much less like administration and much more like historical analysis.
The Dashboard Delusion
Modern organisations are obsessed with dashboards. There are dashboards for usage, revenue, churn, support tickets, customer satisfaction and productivity. In many companies, the assumption seems to be that if enough data is collected, better decisions will naturally follow.
Carr would probably disagree. History shows that organisations rarely suffer from a shortage of information. They suffer from a shortage of understanding. The challenge is not gathering facts, because most organisations already have more facts than they can sensibly process. The challenge is deciding which facts matter, which ones are misleading, and which ones are being overvalued because they are easy to measure.
That is the dashboard delusion. It is the belief that visibility and understanding are the same thing. They are not. A dashboard can show that something has happened, but it cannot automatically explain why it happened or what should happen next.
Product Managers as Historians
A good historian builds a narrative from evidence. A good product manager does something very similar. Product managers work with fragments: customer interviews, market trends, usage data, competitor activity, financial performance, support feedback, sales conversations and operational constraints. None of these fragments explains the product on its own.
The product manager’s role is to connect those fragments into a coherent explanation. In that sense, product management is less about technology than we sometimes pretend. It is about interpretation. It is about understanding why a product is behaving in a certain way, why customers are responding as they are, and why the organisation is struggling to make progress.
Both historians and product managers are trying to answer the same basic questions. Why did this happen? What does it mean? What should happen next? That is the real work. It is not staring at a dashboard until strategy magically appears, like some kind of corporate Magic Eye picture.
The Veep Problem
Modern analytics can sometimes feel like an episode of Veep: a room full of intelligent people, all staring at the same information, somehow reaching completely different conclusions, and then trying to turn those conclusions into a strategy before anyone notices the logic has fallen over.
That is the trap. Organisations often assume that if the numbers are visible, the meaning will be obvious. But Carr would argue that evidence does not work like that. Facts do not arrive with labels attached saying, “This is the important bit.” They have to be interpreted, challenged and placed into context.
The Veep problem is not a lack of information. It is the frantic conversion of partial evidence into confident-sounding decisions. One metric is treated as proof. One customer comment becomes a trend. One dashboard movement becomes a strategic emergency. Before long, everyone is reacting to the noise rather than understanding the signal.
That remains highly relevant to product management. A product manager has to resist the organisational urge to turn every data point into a dramatic plot twist. The job is not to perform certainty. The job is to create understanding.
A dashboard can tell you what has changed. It cannot tell you whether the change matters, why it happened, or whether the correct response is to build, stop, simplify, investigate or wait. That requires judgement, context and interpretation — the exact territory Carr was writing about.
What This Means for Product Managers
The lesson from Carr is not that data is unimportant. That would be ridiculous. Data matters, evidence matters and facts matter. Without them, product management becomes opinion dressed up as strategy, which is basically how you end up building whatever the loudest stakeholder asked for after a tense meeting and three coffees.
But facts do not remove the need for judgement. A strong product manager does not simply ask what the dashboard says. They ask why something might be happening, what evidence supports that interpretation, what evidence contradicts it, what is missing from the picture, which facts are being overvalued and which facts are being ignored.
That is where real product thinking starts. It begins when the product manager treats data not as an answer machine, but as evidence. Evidence has to be interpreted carefully, challenged honestly and connected to a wider understanding of customers, markets, constraints and organisational behaviour.
Final Thoughts
E.H. Carr reminds us that facts are only the beginning. The real challenge lies in interpretation, and that is a lesson product managers should take seriously. Data is valuable, evidence matters and dashboards help, but insight emerges only when someone connects the dots.
The dashboard tells you what happened. The product manager must explain why it happened, what it means, and what should happen next. That is why product managers are not just delivery coordinators, feature owners or backlog gardeners. At their best, they are interpreters of evidence.