The sprint is a five-day process for answering critical business questions through design, prototyping and testing ideas with customers. Developed at GV, it’s a “greatest hits” of business strategy, innovation, behavior science, design thinking, and more—packaged into a battle-tested process that any team can use.
- Monday: Monday’s structured discussions create a path for the sprint week. In the morning, you’ll start at the end and agree to a long-term goal. Next, you’ll make a map of the challenge. In the afternoon, you’ll ask the experts at your company to share what they know. Finally, you’ll pick a target: an ambitious but manageable piece of the problem that you can solve in one week.
- Tuesday: After a full day of understanding the problem and choosing a target for your sprint, on Tuesday, you get to focus on solutions. The day starts with inspiration: a review of existing ideas to remix and improve. Then, in the afternoon, each person will sketch, following a four-step process that emphasizes critical thinking over artistry. You’ll also begin planning Friday’s customer test by recruiting customers that fit your target profile.
- Wednesday: By Wednesday morning, you and your team will have a stack of solutions. That’s great, but it’s also a problem. You can’t prototype and test them all—you need one solid plan. In the morning, you’ll critique each solution, and decide which ones have the best chance of achieving your long-term goal. Then, in the afternoon, you’ll take the winning scenes from your sketches and weave them into a storyboard: a step-by-step plan for your prototype.
- Thursday: On Wednesday, you and your team created a storyboard. On Thursday, you’ll adopt a “fake it”philosophy to turn that storyboard into a prototype. A realistic façade is all you need to test with customers, and here’s the best part: by focusing on the customer-facing surface of your product or service, you can finish your prototype in just one day. On Thursday, you’ll also make sure everything is ready for Friday’s test by confirming the schedule, reviewing the prototype, and writing an interview script.
- Friday: Your sprint began with a big challenge, an excellent team—and not much else. By Friday, you’ve created promising solutions, chosen the best, and built a realistic prototype. That alone would make for an impressively productive week. But you’ll take it one step further as you interviewcustomers and learn by watching them react to your prototype. This test makes the entire sprint worthwhile: At the end of the day, you’ll know how far you have to go, and you’ll know just what to do next.
- Design Sprint – P1 – Intro
- Design Sprint Foundation P2 – Day one
- Design Sprint Foundation P3 – Day two
- Design Sprint Foundation P4 – Day Three
- Design Sprint Foundation P5 – Day Four
Research through Design is a term that is used primarily in academic work in the design communities, especially in interaction design and HCI, but it shares more than is usually discussed with other arts and engineering disciplines and with design pr...
A framework aligning task behaviors, beliefs, and emotions with product and service features. Can help you articulate root causes behind behaviors and develop solutions that deeply resonate with people. Diverse groups identified for study a...
Generative research is a more focused effort targeted at a deeper understanding of user needs and desires, and concept development through participatory design activities. Evaluative research combines more established methods to test emerging design ...
Diary studies are a form of longitudinal research(research that takes place over a long period of time with the same participants). Typically, users self-report their activities at regular intervals to create a log of their activities, thoughts, and ...
Value Opportunity Analysis (VOA) is an approach to identifying the aspirational attributes in a product or service, listing a set of value opportunities to help design teams focus on the key items to connect the target audience. Mapping the ...
Usability Report, When reporting results from a usability test, you should focus primarily on your findings and recommendations that are differentiated by levels of severity. Include the pertinent information from the test plan and present just en...