Storytelling for
Product Managers

For a product manager to succeed, storytelling is not optional. It is critical and load-bearing. Despite recent advances in AI streamlining much of a PM’s day-to-day production work, storytelling remains mostly untouched. This matters because storytelling was always the actual job: taking a pile of incomplete, contradictory information, collapsing it into a direction you are willing to defend, and then holding an organization aligned around that direction long enough to build something.

This seminar is about the craft of that work. Those who use it will leave with a more deliberate approach to a skill that forms the bedrock of career success — and that remains stubbornly resistant to delegation to AI.

My target audience is advanced product managers who want to be the model others learn from. You already ship impactful products by influencing effectively and you know how much communication matters. But you may be less aware of the structure and mechanics behind communication that actually works, or the places where the craft is genuinely hard.

How the seminar is built

The first session introduces a framework of five load-bearing elements — audience, intent, stakes, structure, and through-line — that sits underneath every product narrative that holds. Everything after it is either a deeper treatment of one element or a specialized application of the whole. You can read the eight in order, which is how they are designed to build, or you can drop into the one that maps to the problem in front of you.

A word on what this is not. It is not a bag of delivery tricks, and it is not a case for spin. The through-line of the whole seminar is that a story has integrity only when the interpretation it offers is one you actually believe and would defend under hostile scrutiny. Credibility is the compound interest of storytelling, and this seminar is, in the end, about earning it.