These principles are precisely why Agile User Stories & BDD acceptance criteria are so effective as they cohesively & succinctly tell the whole story, starting with the plot:
As a Hero with X scenario I want to perform Y task So that I can achieve Z outcome
This second sentence carries a lot of weight. The dev team has to be invested in the needs of the user. So… get them out of the cave and into design thinking sessions, stores, factory floors, etc.
When I posted this to social media, I said:
I have come to believe that the “art of the story” is now THE most important skill set in business or in any endeavor in which you’re trying to persuade customers, specific constituents or the general public. And maybe it always has been, but we didn’t realize it quite so clearly.
Thanks so much for sharing, Shahed. You did such a good job of tying practical storytelling techniques to the world of PM & Design! Bookmarking and writing down some of these lessons to apply in my own day-to-day 🙌
I’ve always been drawn to the art of storytelling.
Your introduction reminded me of Simon Senek’s leadership principle of “Lead with the Why.” The stories you tell to the different stakeholders on the creation team serve as that “why” in an engaging, thoughtful way. Giving the why in a story format allows the engineers…
As someone who moved from UX into product management, my story structure so far was in 3 parts:
1. Finding a problem through research
2. Articulating and testing solutions
3. Implementation and evaluation of results
Hello, I found your article in my top recommend!
As much as I love your topic and it had some really good points, I am worried about the ‘Shrek’ image at the end.
I feel like showing another company’s product in an article focused on one specific company’s rule and great achievements seems a little……