Storytelling as a Product Manager

One of the things I’ve been thinking about a lot lately is storytelling as a product manager — and specifically why it feels more important now than it used to.

This isn’t a new concept. Storytelling has always been part of the PM role. But I think something has shifted, and a lot of that shift is being driven by AI.

What’s changed is not that storytelling suddenly matters — it’s that the cost of unclear storytelling has gone way up.

As product managers, we already sit upstream of a lot of downstream work. The way we frame problems, explain decisions, and articulate intent flows into documents, tickets, roadmaps, and conversations that other people rely on. That was true before.

What’s different now is that those same artifacts are increasingly being consumed by AI systems — summarized, transformed, recombined, and reused in ways we don’t always see directly.

And AI doesn’t just read what we write. It extends it.

So whatever story is embedded in your artifacts — whether it’s clear or not — is going to travel further, faster, and with less opportunity for you to course-correct it later.

That’s the part I keep coming back to.

When I talk about storytelling here, I’m not talking about presentations, or persuasion, or being good at telling a compelling anecdote. I’m talking about the underlying narrative that explains what we’re doing, why we’re doing it, and how we’re making decisions along the way.

That narrative is often implicit. It lives between the lines of PRDs, decision docs, Slack threads, and tickets. And increasingly, it’s that implicit story that gets picked up and reused.

If the narrative is strong, AI can help reinforce it.
If the narrative is weak or inconsistent, AI amplifies the gaps.

That’s where ambiguity really enters the picture.

Most product work starts in a state of ambiguity. The problem isn’t fully understood yet. The constraints aren’t all known. Tradeoffs are still emerging. That’s normal. That’s not a failure of process.

But teams still need to move forward. Engineers still need to make decisions. Designers still need to explore solutions. And increasingly, AI tools are being used to accelerate all of that work.

Storytelling is what gives that work a spine.

It’s how you take an ambiguous situation and provide enough narrative structure that people — and systems — can reason about it without you being present to explain every nuance.

That’s especially important because so much of this work is asynchronous now.

People don’t just experience the story in meetings. They experience it later, through artifacts. And those artifacts often outlive the original context in which they were created.

If your story only works when you’re in the room, it doesn’t really work.

And AI exposes that very quickly.

A vague goal statement, an unclear decision rationale, or a poorly framed problem description might have been survivable before. Someone could ask a follow-up question. You could clarify in the next meeting.

Now, those same inputs might get summarized, reused, or fed into another system that produces output for someone else — without that opportunity for clarification.

So the question becomes: what story are your artifacts telling when you’re not there?

The product teams I’ve seen operate most effectively tend to share a common narrative. Not because everything is certain, but because there’s alignment on what matters, what’s still unknown, and how decisions should be made in the meantime.

That shared story shows up everywhere — in tickets, in prioritization discussions, in how tradeoffs are framed, and now in how AI-generated outputs are interpreted.

This is why I think storytelling is becoming less of a “soft skill” and more of a core product responsibility.

It’s not about being convincing. It’s about making your intent durable.

AI doesn’t replace judgment. But it does reveal whether that judgment was clearly encoded in the work to begin with.

If the story is there, AI can help scale understanding.
If it isn’t, AI accelerates drift.

That’s why, for me, storytelling isn’t just still relevant — it’s becoming more critical. Because the systems we’re building and using now depend on narrative clarity in ways they didn’t before.

And as product managers, we’re the ones most responsible for shaping that narrative.

This article has been copyedited from an audio transcript with assistance from ChatGPT. The header image was generated by ChatGPT.