I recently participated in a 'design sprint' for a new feature our team is building. Start with my synopsis of Day 1 of this 3-part series.
This series assumes you're already somewhat familair with what a design sprint is, but perhaps have never actually participated in one. If you're NOT familiar, read this 2-minute overview first.
This post describes the second day in our abridged (two-day) design sprint.
1 - Define the Ultimate Goal (30-60 min)
Look at all of the use cases that the group marked as 'most important' in yesterday's session, and come up with a singular sentence or phrase that describes the goal of the product. This is difficult, and it can take a while. The facilitator should elicit ideas from the team and write them down on the whiteboard until the perfect 'north star' phrase is found.
2 - Team Storyboarding (60 - 90 min)
Now that your ultimate goal has been defined in a single sentence or phrase, the team can start storyboarding the user journey. Each team member should receive some paper and pen (or a whiteboard) and draw the ideal user journey.
In our session, there weren't a lot of parameters or instructions given around storyboarding, and everyone came up with something a little different. Each storyboard should represent the user journey, from the problem they're trying to solve, how they solve that interacting with the productI, and the end (ideal) result.
Tape all of the storyboards to the wall (or a whiteboard) and have each participant explain theirs. At the end, have the team vote on the storyboard that best represents the customer problem and best solution.
3 - Create Paper Wires (90-120 min)
Now that you have a storyboard to guide you, it's time to dive deeper and create actual paper prototypes with more detail. Each team member should again receive paper and pens (or a whiteboard) and should draw wires for what they expect the feature to look like. If your session is anything like ours, the UX participants should excel at this portion of the day!
Once everyone has completed their wires, tape them up on the wall or whiteboard (just like you did with the storyboards), and have each participant explain their wires. As a group, decide which set of wires is the best solution, OR take pieces from more than one participant's wires to develop the best solution.
4 - Validate the Chosen Wire Against Use Cases + Discussion (60 min)
Take the chosen solution - chosen by the group - and validate it against the use cases. Do you need to add anything to the wires to make the solution comprehensive? As a group, go through all use cases and make sure they're covered.
- The facilitator (or some other appointed team member) should make sure all use cases, storyboards, wires, and other notes are documented.
- UX should take the wires and formalize them/ detail them out further.
- Take the detailed wires to other stakeholders to socialize them and make any other needed changes before proceeding with a full scoping exercise.