The Data storytelling gap

Every product team I work with has more data than it knows what to do with. Dashboards are sharper than they have ever been. A junior PM can pull a cohort retention analysis today that would have required a dedicated data scientist three years ago. But the decisions are not moving.

This is the quiet crisis at the centre of every product review that ends with polite nods and zero commitments. The analysis is rigorous. The charts are clean. The conclusions are correct. And yet the room does not shift. The budget does not move. The roadmap does not change. The data was presented. The story was not.

I call this the narrative gap: the distance between what the data says and what the audience actually hears.

The spreadsheet defence

Most product people, when pressed on why a recommendation failed to land, retreat to what I think of as the spreadsheet defence. The data was right. The analysis was thorough. The conclusion was obvious to anyone paying attention. If leadership did not act, the problem must sit with leadership.

But the problem is almost never with the data. It is with the delivery.

At Freshworks, I watched a product lead present one of the most rigorously constructed analyses I had seen that quarter. She had done everything by the textbook. Usage data broken down by segment. Churn correlation mapped to feature adoption curves. A clear, defensible recommendation to sunset a feature that was haemorrhaging maintenance cost while generating negligible retention value. The slides were precise. The methodology was clean. Every single chart supported the argument.

The room thanked her. And then nothing happened. For three months.

She came to me afterwards, visibly frustrated. "The numbers are right there," she said. "What else am I supposed to show them?" That word, show, was precisely the problem. She had shown them data. She had not told them a story. She had walked into a room full of busy people who were juggling twelve competing priorities and expected them to do the interpretive work themselves. Data does not speak for itself. It never has. Someone has to speak for it.

Data without a narrative is noise with a spreadsheet attached.

And, But, Therefore

The structure that separates data which moves decisions from data which gets filed is older than product management. It is arguably the oldest narrative structure humans use: And, But, Therefore.

And: here is the world as it currently stands. Our product serves 14,000 active accounts. Engagement is stable. Revenue is growing at 8 percent quarter over quarter. Things are, on the surface, fine.

But: beneath that stability, a specific pattern is forming. Our highest-value customer segment is showing a 22 percent decline in feature adoption over the past two quarters. They are not churning yet. They are disengaging. Slowly, quietly, and in exactly the segment that funds our expansion revenue.

Therefore: if we do not address the engagement decline in this segment within the next two quarters, we will likely see churn acceleration in exactly the accounts that represent 40 percent of our expansion pipeline. Here is what we recommend.

That is the same data the Freshworks product lead had. But it is wrapped in a structure that gives the audience a reason to care before they see the numbers, a reason to worry before they see the recommendation, and a reason to act before they leave the room. Most product people skip straight to the problem because the problem is what excites them. But senior stakeholders lack the context to understand why the problem matters unless you first establish what normal looks like. You need the "And" so the complication lands as a disruption, not a complaint.

The "And" is not throat-clearing. It is load-bearing.

What happened the second time

The lesson crystallised for me at Adobe. I was presenting to a leadership group about a product direction that had been stuck in limbo for months. The first time I presented, I did what most product people do. I led with the analysis. Usage patterns, competitive positioning, a clear case for investing in a specific capability. The work was rigorous. Nobody disagreed with any of it. But nobody acted on it either.

The numbers were right. The story was missing. Nothing moved.

A colleague pulled me aside afterwards. He was not a product person. He was in marketing, of all places. And yet he understood something about that room that I did not. "You gave them a report," he said. "Give them a reason."

So I rebuilt the presentation. Same data. Same recommendation. Same room, three weeks later. But this time I started differently. I opened with a specific enterprise customer who was using our product in a way we had not anticipated, and whose usage pattern represented a broader trend we were ignoring. I named the customer. I described what they were doing. I showed what would happen if we ignored the pattern and what would happen if we leaned into it. Then I brought in the data, not as the argument, but as the evidence supporting a story the room already cared about.

Same stakeholders. Same data set. Entirely different outcome.

The decision that had stalled for months was approved in that meeting. Not because I found better data. Because I found a better frame.

Why the gap keeps widening

The narrative gap persists because product culture rewards analysis, not storytelling. We train product people to be rigorous. We teach them to think in hypotheses, to validate with evidence, to present findings with statistical precision. But we do not teach them to build a narrative arc around those findings. We do not teach them that the audience's emotional state matters as much as the data's confidence interval.

This is not a soft skill. It is possibly the hardest skill in the room.

I have watched data-fluent teams lose funding to less rigorous teams who could tell a better story about what they were building and why it mattered. The team with the stronger narrative won the budget. The team with the stronger data did not. There is an uncomfortable truth lodged in that pattern. Being right is not enough. Being right and being compelling are different skills entirely, and the second one determines whether the first one matters.

Senior stakeholders do not read data the way product people do. They are making decisions across dozens of competing priorities with limited attention. The product team that expects leadership to do the interpretive work is the product team that keeps losing budget reviews. But the team that walks in with a three-minute story supported by data, a story with a beginning and a complication and a clear recommendation, that team gets the resources.

Every time.

Product teams right now have more analytical capability than any prior generation of builders. The tools are better. The data literacy is higher. The dashboards are genuinely impressive. But the ability to shape all of that into a story that lands with a person who controls a budget has not kept pace. Not even close. Teams trust the data to speak for itself, and the data sits on a slide, mute, waiting for someone to give it a voice.

The best product people I have worked with are not the ones with the deepest analytical chops. They are the ones who can take a complex data set and compress it into a story a senior leader remembers three days later when the actual decision gets made. The analysis gets you into the room. The narrative is what stays after you leave.

Learning to tell that story is not a nice-to-have sitting adjacent to the real work. It is the real work. It always was.