
Storyboard


The Storyboard method unifies the entire Design Sprint team on the prototype concept and helps the group make critical decisions during the prototyping process. A Storyboard maps out each step of the experience that you want to test and clarifies the pieces you need to prototype.
At this point in the Design Sprint, the team often begins to brainstorm aspects of the product, some of which might be outside the scope of your Sprint questions and prototype. Capture these ideas for later, but keep the team focused on exactly what needs to be built for successful user testing.
Script writing is important at this stage as it helps align the storyboard to the user interview and clarifies the structure of what mocks or experiences will be needed in the testing. The script can also help create a plan for the Validate phase.
Directions
- The facilitator draws the Storyboard on the whiteboard or poster in a grid
- Narrow in on four or five key moments that will help illustrate the solution
- You don’t need to sketch out every single user flow or use case. Just focus on what you need to create to get accurate user feedback
- Map out the flow you’ll use in the user-interview script
- Figure out which moments can be rough, and which need to be well-defined