The Process
Below we've assembled a basic DIY guide, including daily checklists, videos, and other resources.
Monday's structured discussions create a path for the sprint week. Start at the end and agree to a long-term goal, make a map of the challenge, ask experts to share knowledge, and pick an ambitious but manageable piece of the problem.
Focus on solutions with inspiration from existing ideas. Each person sketches following a four-step process emphasizing critical thinking over artistry. Begin planning Friday's customer test by recruiting target customers.
Critique each solution and decide which have the best chance of achieving your long-term goal. Take winning scenes from sketches and weave them into a storyboard: a step-by-step plan for your prototype.
Adopt a "fake it" philosophy to turn your storyboard into a prototype. A realistic facade is all you need to test with customers. Focus on the customer-facing surface to finish in just one day.
Interview customers and learn by watching them react to your prototype. This test makes the entire sprint worthwhile - you'll know how far you have to go and exactly what to do next.
What Are Sprints For?
Costs from switching context, communication barriers and other inefficiencies with exchanges over long development periods stifle the process. A Design Sprint removes these problems and provides a great ROI - teams channel in on the challenge to experience incredible results.
Build New Products
Solve Challenging Problems
Experiment with Ideas
Align Efforts
Develop a Roadmap
Drive Innovation
Develop a Successful Campaign
Learn from User Feedback
Churn Momentum
What Outcome Should You Expect?
After the 5-day Sprint, the prototype PlusInfosys helps you develop and user feedback clarifies the next steps. From here, you have the tools you need to refine the idea into a successful product.