The Root Cause — Issue 01

There is a meeting that happens inside almost every enterprise technology company. You have probably been in it. A product manager, an engineering lead, and someone from marketing are sitting at the same table. The product team has built something real. The technology works. The roadmap is solid. And they need marketing to turn what they built into something the market will actually buy.

This is where it starts to go wrong.

The product team explains the features. The marketer takes notes. Someone converts features into benefits. Someone else adds a customer quote. A positioning doc circulates. A launch deck gets built. The product goes to market.

And the market doesn't respond the way anyone expected.

Not a product problem. A diagnosis problem. And it is the most expensive mistake in technical marketing.

In 2018, I was handed a blank page. Enterprise AI wasn't a category yet. It was a promise most organizations had no infrastructure to keep. A peer and I were tasked with building AI best practices for a market that didn't have any, because the market itself was barely a year old.

The product team came in loaded with use cases. Workflows. Automation scenarios. Business logic dressed up in ML branding. They weren't wrong about the technology. They were wrong about where the actual problem lived.

Customers weren't failing at AI because of bad use cases. They were failing because of bad data.

Dirty data. Siloed data. Data that nobody inside the organization trusted enough to act on. We said it then and it holds up now: garbage in, garbage out. You can't build a prediction model on a foundation nobody believes in. You can't automate a workflow that has never been consistently documented. The most sophisticated ML pipeline in the world collapses against corrupted input.

The product team was looking at the solution. We were looking at the root cause.

So we built the narrative around the data problem, not the AI capability. And it landed in a way the feature list never could, because it spoke to something the customer already knew was broken, even if they couldn't put words to it.

That was 2018. It is still true now. Six years of GenAI announcements, agentic AI launches, and LLM integrations later, the number one reason enterprise AI fails in production is still data quality. The root cause hasn't moved. Most marketing keeps ignoring it.

The product team's problem is proximity. They've been with the product since day one. They know every capability, every architectural call, every edge case that shaped the roadmap. That intimacy makes them the worst possible narrator of their own product. They explain what it does. Customers need to hear what it solves.

The customer's problem is the opposite. They're overwhelmed. They describe symptoms, not causes. They tell you about the ticket backlog, the failed deployment, the executive pressure, the compliance audit they just failed. They're not being evasive. They genuinely can't always see the root cause from where they're standing. They are too deep inside the problem to see its shape from the outside.

The technical marketer's job is to sit in that gap. Translate inward toward the product team: here is what the customer actually needs, and here is why the roadmap should be framed around it. Translate outward toward the market: here is the story that makes this product impossible to ignore, because it names the problem the customer already feels.

That requires listening between the lines. Not to the stated problem but to what's underneath it. A customer who says their ITSM process is broken might actually be telling you their teams don't trust the data their tools produce. A customer who says they need better automation might be telling you they've never had consistent process documentation to automate against in the first place.

The diagnosis is the work. The feature list is just the evidence.

There's a version of this challenge that doesn't get discussed openly in marketing circles, because it requires admitting something uncomfortable: the narrative is a strategic asset you manage deliberately. It is not just a reflection of what exists.

In the years after that 2018 AI push, several enterprise software categories were being invented in real time. Digital Portfolio Management. Digital Employee Experience. Intelligent automation at scale. These weren't established markets with defined buyer budgets and clear competitive sets. They were territories that had to be claimed before anyone else got around to naming them.

Building narrative for an unclaimed category is one of the hardest things a technical marketer can do. You have to name the problem before the buyer even knows they have a budget for solving it. You have to show enough to be credible without showing so much that a half-baked feature promise becomes a public commitment you can't keep. And you have to do all of this while competitors are watching and taking notes.

Most marketing organizations get this wrong in the same direction every time. They disclose too much, too early. They announce capabilities before they're ready to deliver them because the pressure to show momentum is real and constant. In doing so they hand competitors a roadmap they didn't have to earn.

The skill is building a story that is completely true, genuinely compelling, and strategically incomplete in exactly the right way. Not deceptive. Selective. There's a real difference. You're not hiding the product. You're sequencing the revelation.

What you say, when you say it, how specific you get, and which audience hears it first — that's narrative architecture. Not a communications exercise. A strategic decision with competitive consequences.

After twelve years building narrative for enterprise AI across organizations as different as CERN, the US Army, Japan Railways, and Disney, one thing is consistent across all of them.

Stop listening to what is being said. Start listening to what is being avoided.

The product team avoids the limitations. The customer avoids the root cause. The truth is almost always in what neither side wants to name first.

From there, the translation. The product's strongest attribute is rarely the one the product team leads with. It's usually the one that directly addresses the root cause the customer couldn't articulate. Finding that intersection is the actual work. Everything else is packaging.

Then the sequencing. What do you say at launch? What do you hold for three months out? What do you let a competitor announce first, because you'll be positioned to demonstrate superiority when it actually matters to the buyer?

This is what ThinkRoot is built on. Not a framework out of a business school case study. A diagnosis model built from the front lines of the most consequential period in enterprise AI history, from the first ML use cases in 2018 through the GenAI wave to the agentic systems being deployed across enterprises right now.

The root cause of a product that can't find its market is almost always a narrative written by people who were too close to the product to see it from the outside.

That's the problem. The Root Cause is where we work on it.

Chad Corriveau is the founder of ThinkRoot, a technical marketing strategy and AI narrative practice built on twelve years inside enterprise AI at ServiceNow. The Root Cause is published when something is worth saying.

Read the work at thethinkroot.com. Subscribe to stay in it.