I’ve written about stories as frameworks for customer engagement and their specific applications to product management. I also dig deeper into different parts of the story framework; the first is about the heroes and their needs.
In this post I focus on three of those elements from the Hero’s Journey:
and map them onto the customer journey. (I will deal with them out of sequence, because I’ll be writing more about the Refusal of the Call in a future post.)
It’s a necessary milestone in just about…
In an earlier entry, I wrote about the inherent qualities that made stories the magic things that they are. Stories are shared forms of human creativity and expression. Stories create empathy on the part of the listener, whether a potential customer or product team member; stories are far more persuasive and memorable than statistics. They open doors to worlds; they create wonder.
So how can you use stories in product management? The word “use” is deliberate: stories can also be seen as tools that serve a purpose. While that sentiment may sound terribly utilitarian and anti-poetic — I mean, I…
Storytelling is at the heart of product management. Whether referring to assembling the nuts and bolts of product delivery, crafting a product strategy, or selling a product vision, stories are key to both successful product development and customer engagement as a whole. I’d even argue that stories — and no, I’m not just talking about user stories — are also integral to the execution of projects. A story — that simplest of frameworks — serves as a musical counterpoint, if you will, to the formal project management phases.
Consider below some general reasons for using stories (and prepare yourselves for…
Sometime last year I was conducting a storytelling and product management workshop at work. I had instructed the participants, who were Information Technology managers and officers, to come prepared by thinking of fictional characters. (For an icebreaker, create an anonymous poll and ask, “Which fictional character do you (secretly) identify with?” Then watch the team have fun guessing who wrote what.)
I asked them the question: what was the principal thing the protagonist(s) had to accomplish?
I gave them some examples:
(A small disclaimer: a lot of thinking out loud is about to follow, with the caveat that I may revise and update this later for something slightly more polished. Sometimes I write more crafted entries (as with my movie / book / game posts on my personal blog), but it feels like a burden to have to deliver than just messily laying my thoughts out on the screen. So consider this a living document.)
The other week I told my colleagues they needed to be more like Yoda. It was part of a two-hour Design Thinking and Storytelling class I…
So this radioactive spider accidentally got loose in a lab and — ahh, who am I kidding. But my interests in the intersection of storytelling and product management do have an origin story of sorts.
Most people keep the different spheres of their life completely separate: there’s the day job, and there’s the stuff they do for fun. By day I’m a senior product manager, working with development teams to build software applications for internal customers at the Federal Reserve.