Meet Alex Cowan, entrepreneur (5x), intrapreneur (1x), author, and instructor at General Assembly. He’s also the author of ‘Starting a Tech Business’. When he’s not teaching at GA, he’s often found advising companies and posting instructional materials for innovators and instructions on alexandercowan.com. This is the second post in Alex’s series on Storyboarding. Click here to read his introductory post.
Outstanding products are the accumulation of many thoughtful details. Particularly in more mature categories, consistently thoughtful execution is probably more important than grand inspiration.
Agile’s primary input, user stories, have always been a great way to get that consistency. Sadly, they’re not a silver bullet and their impact is often marginalized because of weak stories. Quality stories that really represent users should thread back to personas & problem scenarios, meaning that you have a vivid depiction of who this user is and what underlying need the story’s addressing. Without this, the user stories may end up as a specification for something thought up ‘inside the building’ as opposed to out in the market. Furthermore, the story will end up in out there in the real world without a clear trail back to why you thought it was a good idea and a ready criteria for whether or not it’s delivering the outcome you intended.