During design sprints, teams spend 5 days building functional prototypes and testing them on live customers to solve big challenges.
Rebuilding months later
Opportunities + gaps spotted in 1 week
Driven by ego
Driven by customer insights
Spec documents + RFPs
Functional prototypes + product roadmaps
Pick your big challenges to solve, assemble your sprint team and then aggregate all existing info (research, metrics, surveys).
Map the customer journey as they experience this challenge. Talk to experts, enhance your map, and decide which part you'll focus on this week.
Individually (but together) gather inspiration from existing ideas, take notes, and sketch up solutions.
Vote on the best solution and then add additional details so that it’s a complete storyboard, start to finish.
Divide and conquer to build and refine the prototype(s) you'll be testing on your live customers tomorrow.
Test your prototype(s) with 5 customers while the rest of the team captures reactions that will validate or invalidate your solution.
This may be a mocked up website or mobile app. It may be a presentation. It depends what we’re trying to test for and the reactions we’re after from your customers.
A report that recaps the sprint, summarizes customer reactions and includes recommended next steps; e.g. build / rebuild features, run another sprint, pivot.
A list of user stories that have been prioritized by product release, and assigned with forecasted budgets and timelines.
A professionally designed investor pitch deck that contains all of the most critical slides, plus the insights and traction attained within the sprint.