If you don’t think through the experience you want customers to have, who will? If you have to make a few guesses along that way, that’s OK. Being right isn’t as important as being explicit and making your ideas testable. Neglect your imaging of the customer experience, and you’re leaving your success to chance.
Agile user stories are a great solution to this problem. Always popular in software engineering, I’m increasingly seeing companies use them for projects in other areas, like marketing. That said, agile stories are not a silver bullet. They encourage good storytelling but don’t guarantee it. Supplementing your major storyboards will help you avoid arbitrary stories, disconnected from (even hypothetical) customer realities.
Quick Review of Agile User Stories
(Freely skip this section if you know stories up and down.) First off, agile user stories have this format:
“As a [persona],
I want to [do something]
so that I can [derive a benefit]”
Second, to help stay organized and coherent, stories are often nested within ‘epic stories’. If you’re new to product development, you’ll probably find yourself writing stories that turn out to be epic stories as you get into their particulars. Finally, ‘test cases’ are a good way to layer additional detail against your stories. (see agile user story examples for more).
Storyboard are a great way to humanize and describe epic stories:
Creating an Epic User Story
Let’s take a look at an example epic. I use a (fictional) company called Enable Quiz in my book. They offer lightweight technical quizzes. Managers use the quizzes to screen new candidates and also assess the skill sets of their existing teams so they can plan training, etc. Let’s say the persona ‘Frank the Functional Manager’ wants to assess one of his teams so he can plan a skills development program. The ‘epic user story’ might be:
‘As a functional manager, I want to administer a skills audit so that I can understand the capabilities of my staff and plan training.’
The storyboard below summarizes a few agile user stories that sit within that epic story:
Create a Copy
Extracting User Stories out of An Epic
The story above an epic story, meaning it had multiple sub-stories within it to flesh out the details. You may find a table helpful for unpacking the detail you’re narrating with your epic storyboard. Here’s an example for the epic story above. This epic assumes Frank and his company have already successfully onboarded with Enable Quiz, using it for screening new recruits.
|This epic assumes Frank and his company have already successfully onboarded with Enable Quiz, using it for screening new recruits.Frank’s first goal is to set up a quiz to complete a skills audit for his team. He has the employees he wants and it’s part of his job to help them make time to develop a holistic skill set.This first step covers these two stories:
A) “As a functional manager, I want to browse the quiz banks [of available questions] so I can make sure I’m subscribed to all the necessary topics for my skills audit.”B) “As a manager, I want to purchase additional quiz banks so I can add additional technical topics to me quizzes.”
|Frank has some topics specific to their internal products, processes and technologies that he’d like to use for his internal staff. After that, he’s ready to send the quiz. This panels deals with the following two stories:C) “As a manager, I want to create a custom quiz banks so I can add my own questions to the quiz.”D) “As a manager, I want to create a quiz so I can use it with my staff.”|
|Now Frank has to get all his staff into the systems so they can get invitations and their individual results tracked. He might want to do this in bulk and/or on a one by one basis.E) “As a manager, I want to create a list of students [employees] from an Excel file so I can invite them to take the quiz.”F) “As a manager I want to create a list of students [employees] online.”G) “As a manager, I want to invite a set of students [employees] to take the quiz so I can see their scores.”|
|Now the employees/students come into play. They need to get a notice that Frank can customize where he communicates what this is about and when he’d like to have them finish the quiz. Suggestions show him how to communicate that the purpose of the quiz is creation of tailored professional development/training vs. micromanagement/big brothering.H) “As a student, I’d like to understand the objectives and content of the quiz as well as when I need to do it by so I can understand and prioritize it.”|
|People get busy, etc. Frank needs to see who’s finished vs. not so he can send automated and/or human reminders to finish up the quiz.I) “As a manager, I want to see which students have completed the quiz and which have not so I can send them a reminder.”|
|Now he has his result. The objective was to tailor training programs for his team so they’re able to broaden their skill sets in the context of their business schedule.J) “As a manager, I want to see how the students scored on the test so I can put in place a skills improvement program.”|
Why user stories? Storyboards?
Here are a few more reasons I like the user of stories:
- They dovetail with design thinking outputs like personas, problem scenarios and value propositions.
- They are highly consumable by developers, designers, and other creators who are helping you execute, balancing structure and description; specificity and objectives.
- They’re robust and ‘nestable’, scalable even for large, complicated projects.
Storyboards are a great way to keep agile user stories from mimicking the dull, context-free requirements definitions they were meant to replace. They help avoid myopia, making sure you’ve thought through the whole story. They’re also a great way to engage your audience.
What have you tried to improve the quality of your agile user stories? What worked? Didn’t? Have you tried storyboards? Would you? Post a comment, respond on Twitter, drop me a line, post on LinkedIn- we’re in this together!