An integral part of the Design Thinking process is the definition of a meaningful and actionable problem statement, which the design thinker will focus on solving. This is perhaps the most challenging part of the Design Thinking process, as the definition of a problem (also called a design challenge) will require you to synthesise your observati...
No special previous knowledge is required. The Design Sprint Master course builds on the Google Ventures Framework and Jake Knapp's SPRINT book. It is further developed by drawing on our trainers' experience of many sprints in large and small businesses. Although reading SPRINT is not a prerequisite, it will offer advantages in being better prepared for the individual steps of the process.
Jake Knapp describes Design Sprints as a greatest hits of productivity, decision making, innovation, creativity, and design — and I think that’s true. But I recently took part in a sprint which modified this “greatest hits” formula heavily. My gut feeling was that these modifications were not beneficial, but since I was unfortunately not in a position to change the process, I chose to view it as an opportunity to gather data, and do a comparative analysis between this sprint, and the GV process outlined in the book — to learn, and to be more prepared for the next time around. https://i1.wp.com/s3.amazonaws.com/production-wordpress-assets/blog/wp-content/uploads/2016/11/23155646/RAD.png?fit
Once everyone is BFFs, we introduce design sprints as a practice. We talk about how they fit into the bigger picture of business innovation, design thinking, and product development. We help attendees understand the work your team will need to do before the sprint, to ensure we’re connecting business value to the sprint, as well as choosing the right/best challenge.
What I Find Noteworthy: They have a certification program and a mentor program. If you pass their Sprint Master certification exam, you can serve as a mentor to other students in future classes, and join their online community of Sprint Masters. Students learn not one, but two different approaches to design sprints (Jake Knapp’s sprint model and Tenny Pinheiro’s MVS service start-up model).
In 2012 and 2013, the Google Ventures team published a how-to series about Design Sprints, and the process started to spread. The Sprint book came out in 2016, and today, thousands of teams around the world have run sprints in startups (like Slack and Airbnb), big companies (like LEGO and Google), agencies (like IDEO and McKinsey), schools (like Stanford and Columbia), governments (like the UK and the UN), and even museums (like the British Museum and the Smithsonian).
“Sprints begin with a big challenge, an excellent team — and not much else. By Friday of your sprint week, you’ve created promising solutions, chosen the best, and built a realistic prototype. That alone would make for an impressively productive week. But Friday, you’ll take it one step further as you interview customers 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.”
In theory you probably could, and we’ve always been advocates for making the Design Sprint as open as possible, and our aim is to get as many people as possible using it (as long as they do it properly!) however to get all the information in a structured way, and all the toolkit and materials for free, would be really hard and would take hours of piecing bits of information together. Also, most of the information that’s readily available is on the internet (including our own) speaks to a total beginner audience, whereas the material in our course, while suitable for beginners, will give you a deep-dive into the Sprint and all the process and materials around it. The toolkit we provide as part of the course is the actual ‘live’ stuff we’re currently using with our Sprint clients, and we’ve never made it readily available, and to our knowledge, there isn’t anyone else putting this stuff out there.
Understand: the team maps out the problem to focus on, and unites under a shared brain; this phase involves lightning talks, which are 10- to 15-minute sessions given by knowledge experts, as well as the “How might we” note-taking method, and affinity mapping; the team puts himself in the shoes of the user with user journey mapping, user interviews, empathy building exercises, and success metrics;
The outcome of a Design Sprint is not an end result, but rather a starting point. The goal of a Design Sprint is not to end up with a perfect solution after just one week, but to get feedback on one or two possible solutions. What we usually see is that the direction is so big (because your problem is big), you need to further split your solutions into chewable chucks to for prioritization and phasing. So don’t focus too much on building exactly what you come up with in the Sprint, the result of a successful Design Sprint is better understanding of the problem, better alignment within the team and feedback on potential solutions you can further research and design on.
Before consumers even had the opportunity to purchase the digital eyewear, Google announced in January it would pull Google Glass off the market. The company isn’t completely shattering Glass, but rather it’s putting an end to the “Explorer” program, which allowed curious developers to try out the product for $1,500. Google insists this is hardly the company’s last foray into wearable technology, but the original Glass has fielded overwhelming criticism since it was launched to the elite crowd in 2012. Glass’s (at least temporary) demise is a cautionary tale for technologists. In another light, it’s a ringing endorsement of design thinking.
Some of the scientific activities will include analyzing how users interact with products and investigating the conditions in which they operate: researching user needs, pooling experience from previous projects, considering present and future conditions specific to the product, testing the parameters of the problem, and testing the practical application of alternative problem solutions. Unlike a solely scientific approach, where the majority of known qualities, characteristics, etc. of the problem are tested so as to arrive at a problem solution, Design Thinking investigations include ambiguous elements of the problem to reveal previously unknown parameters and uncover alternative strategies.
In just one exciting and eye-opening day, Sprintmaster Stéphane Cruchon will take you and your team through this revolutionary way of working. You’ll come away from this specialized condensed training program confident in your ability to facilitate your own Sprints, recruit the ideal team, and have a clear vision about testing and prototyping tools.
For our first dispatch of 2019, we’ve assembled enough Google Design goodies to put a spring in your step. Our roundup includes a big story on Waymo—exploring how the company’s designers built a brand new UX playbook to foster user trust; an artful interview with technologist John Maeda on agile leadership; and deep insights from UX Director Margaret Lee, who penned an essay on how her immigrant upbringing shaped her take on leadership. We also compiled a fresh selection of “5 Things to Love Right Now”—curated by San Francisco-based designer Shannon May. Dig in for a new bloom of insights and inspiration.Subscribe to the Google Design Newsletter