Data-Driven Decision Making: Which Numbers Should Decide
Most companies that say they practise data-driven decision making are not lying. They have dashboards, a weekly report, and more numbers than anybody has time to read. What they often cannot produce is a single decision from the last quarter that went differently because of any of it.
That gap is the subject here. Not whether you collect data, because you already do, but whether the collecting ever changes an answer. The blunt version is worth sitting with. Name the last decision where a number told you something you did not already believe, and say what you did next.
What Data-Driven Decision Making Actually Means
Data-driven decision making means choosing on evidence rather than instinct: collecting the numbers that bear on a decision, working out what they say, and letting that shape the call. Every definition you will read says roughly that. They are all correct, and none of them is much use, because the definition was never the hard part.
The test that matters is whether the data could have changed the answer. A decision is data-driven when you named the number before you looked, said out loud which result would send you the other way, and then went that way when it did. A chart on the screen while a decision is announced proves nothing.
That distinction explains why two companies with almost identical reporting get completely different value out of it. The reporting is not the variable. The order of operations is.
It also explains why the honest version of this is uncomfortable rather than technical. Anybody can install reporting. Very few teams will say, in front of each other and before the number arrives, what result would make them change their minds.
Why Dashboards Are Not Decisions
The evidence that this pays is older and better than most of what gets quoted in this field. In 2011 Erik Brynjolfsson, Lorin Hitt and Heekyung Kim studied 179 large publicly traded firms and found that the ones practising data-driven decision making had output and productivity 5% to 6% higher than their other investments and their technology use would predict.
That last clause is the whole finding. They were not measuring who owned the best analytics, because the analytics had already been accounted for. They were measuring what happened when a company actually decided this way. You can buy every piece of the tooling and get none of this.
It is also why buying something rarely helps. A new dashboard arrives on a date, has a price, and can be shown to a board. A change in how a team decides has none of those properties and produces nothing visible until the second or third decision. So the tool gets bought, the habit does not follow, and a year later the company has better reporting and the same meetings.
The figure on the other side comes from BARC, whose 2015 study of big data use found an average 8% increase in revenue and a 10% reduction in costs. The qualifier is more interesting than the numbers: those were the organisations able to quantify their gains at all. Being able to say what a decision was worth is not a reporting nicety, it is the same discipline pointed backwards.
Hold both loosely. One is from 2011, one from the big data era, and neither was measured on a company your size. What they establish is direction and mechanism, which is more than most figures on this subject can claim.
Numbers That Explain, and Numbers That Only Describe
Most dashboards are mostly description. Revenue this month, total pipeline, traffic, meetings booked, headcount. All of it true, all of it worth knowing, and almost none of it able to tell you what to do differently, because a number that only describes has no action attached to it.
An explaining number is one where a change forces a decision. It is usually a rate, a ratio or a comparison rather than a total, because totals move for too many reasons at once to be read.
| Describes what happened | Explains it well enough to act | |
|---|---|---|
| Revenue | The number for the month | The share of it from customers you already had |
| Pipeline | Total value in the pipeline | Conversion between two named stages |
| Marketing | Traffic, impressions, followers | Win rate by where the lead came from |
| Selling | Meetings booked | Deals that needed the founder in the room to close |
| Cost | Total spend | What it costs to serve the next customer |
| Forecast | The number submitted | How wrong the last four forecasts turned out to be |
The right-hand column is the decision agenda. The left-hand column belongs in the report that gets circulated beforehand, and the mistake most leadership teams make is spending the meeting on it, because it is easier to discuss and nobody has to be wrong in front of anybody.
Movement between funnel stages is the clearest case of the difference. The total is a fact. The rate between two stages is an instruction, because it names the place where the work is going wrong.
Where the Numbers Break Before the Decisions Do
The failure is hardly ever an absence of data. It is that one word means two things in two places, so two people arrive at the same meeting with different numbers for the same week and spend it reconciling rather than deciding.
A qualified lead means one thing to the team generating it and another to the team working it. A closed deal is a signature in one system and cash in another. The gap stays invisible until the two numbers meet.
The cure is boring and it is written work: one definition per term, recorded, with a name against it and a rule for changing it. Owning that is most of what revenue operations is for.
Where the disagreement is specifically between the team that generates demand and the team that closes it, it is the subject of sales and marketing alignment, and it is far cheaper to settle before the second team exists than after.
When Judgement Should Win
This is where most writing on the subject goes quiet, because the honest answer is that plenty of decisions have no useful data behind them and never will.
The variable is how often the decision repeats. A pricing call you will make forty times a year builds its own record. Entering a market you have never sold into, hiring the first person into a function that does not exist yet, taking an offer for the company: each happens once, and the data available is mostly other people's circumstances wearing a chart.
For the rare ones the discipline is different rather than absent. Write down what you expect to happen and why, before you act, and read it back afterwards. That turns a one-off into evidence for the next one, which is the only way the thin end of the scale ever thickens.
The two failure modes are opposites and both are common. One is the company that overrides every number with a feeling. The other is the company that will not move until the evidence is conclusive, which for a decision made twice it never is.
The Four Questions That Make a Decision Data-Driven
None of this needs a platform. It is four questions asked in order, and the order is the part that does the work.
Which decision is this, and when does it have to be made? Unnamed decisions cannot be evidenced. Most meetings are about topics rather than decisions, which is why they end without either.
Which number would change it, and in which direction? Said out loud, before anybody looks. This is the question that separates the two panels in the first diagram.
Do we agree what that number means? Definitions get settled before the data arrives, not after, when everybody has acquired a stake in a particular reading of it.
Was the reasoning right, separately from whether it worked? Good calls lose and bad calls win. A team that reviews only outcomes learns superstition, and it learns it quickly.
Most companies ask the first and skip the rest. The second question alone, asked consistently for a quarter, will change more than a reporting project will.
What Changes, and How Long It Takes
Expectations matter here, because the early part of this feels like going backwards, and that is exactly when it tends to get abandoned.
| Roughly when | What actually changes | What it feels like from inside |
|---|---|---|
| First month | Definitions get argued over and written down | Slower, and faintly bureaucratic |
| One quarter | Meetings shorten, because the numbers now agree | The first noticeable relief |
| Two quarters | The forecast starts being roughly right | Quiet confidence, hard to attribute to anything |
| A year | Decisions get delegated, because the rule is written | You are needed less, which was the point |
The forecast row is the one to watch. Forecast error is the cheapest honest measure of whether any of this is working, and it is difficult to argue with. If you are as wrong in October as you were in March, the reporting improved and the deciding did not.
One thing is worth protecting in the first month. Settle the definitions for the decisions you actually make, not for the whole business. A company that tries to define every term before it decides anything has started a documentation project, and documentation projects are abandoned at about week six with nothing decided differently.
Where that review sits in the year, and how often it happens, is as much a strategic planning question as a data one. A number nobody is scheduled to look at is not a measure, it is a file.
Frequently Asked Questions
What is data-driven decision making?
Making a choice on evidence rather than instinct: naming the decision, naming the numbers that bear on it, agreeing what they mean, and letting the result shape the call. The working test is whether the data could have changed the answer. If it could not, the exercise was reporting.
What is the difference between data-driven and data-informed?
Data-driven usually means the number decides within an agreed rule. Data-informed means the number is one input and a person still decides. Most companies need both, sorted by how often the decision repeats, and the trouble starts when a team claims the first while practising the second.
Which metrics should a leadership team actually run on?
The ones where a change forces a decision. Conversion between two named stages, win rate by lead source, what it costs to serve the next customer, and how wrong the last four forecasts were. Totals like revenue and pipeline belong in the circulated report rather than on the agenda.
How do you start when the data is a mess?
Do not start with the data. Start with one decision you make every month, name the single number that would change it, and fix the definition of that one number only. Cleaning everything first is the project that never finishes and never changes a decision.
Does this replace executive judgement?
No, it sorts it. Judgement carries the decisions you make once or twice, where no useful evidence exists or ever will. Data should carry the decisions you make every week, where instinct is mostly a slower way of being wrong. Knowing which one you are holding is the skill.
How do you know it is working?
Forecast error over time is the cheapest honest signal, because it is hard to argue with and nobody can flatter it. Alongside it, count how many decisions were delegated without coming back. Both improve for the same reason, which is that the rules are finally written down.
Final Thought
Data-driven decision making gets sold as a tooling problem and it is almost always a habit problem. The companies that get value from it are not the ones with the most instrumentation. They are the ones where somebody says, before the meeting, what would change their mind.
The rest follows from that sentence and very little of it follows without. If you want one place to start, start there, on a single decision, this week.
Ready to build a revenue engine that runs without you?
Mark works alongside founders as a player-coach — not a slide deck.
Book a 30-minute call