You can’t change what you can’t measure, right? One of the biggest questions we initially faced when implementing design sprints in our organizations was “How do you measure the success of a design sprint?” In our experience, it was often the absence of something that we were trying to measure. For example, how do you measure the amount of time you won’t spend on bad product development? How much money will you save by not investing in a product that will make less ROI? Those questions point toward future gains by not spending some difficult-to-calculate amount of time or money. How do you measure the absence of a failed product?
Once we have an understanding of the foundation we all need to run a successful design sprint, we kick off by working through the sprint’s Monday exercises — setting a proper long term goal based on our sprint challenge, determining our sprint questions, creating a map, interviewing experts, connecting our personas to the map, and selecting a target.
During the first day, we’ll do a bunch of really fun exercises to help break the ice and build trust with the group of strangers you’ve literally just met. Without team chemistry, you will never get through a design sprint. So we try to model the same requirement in our training environment — bond with your team and then get to work solving problems together.
Tenny Pinheiro lives in Silicon Valley, CA. He pioneered Service Design Sprints by publishing in 2014 his book The Service Startup: Design Thinking gets Lean (2014 Elsevier/ Altabooks / Hayakawa). In the book, Tenny proposed the MVS model, a Service Design Sprint methodology based on the integration of Lean Startup and Service Design Thinking. The MVS was the first methodology to suggest an Agile Sprint approach to Design Thinking projects. The book was published two years before Google Ventures launched the book Sprint.
The drawback of a design sprint is that it is a serious undertaking. Many organizations shy away from dedicating the energy of a team or even one individual for a full week straight. They tend to not take a focused approach and rather opt with weekly meetings, etc. A true design sprint will take a week! The good news is that you can involve another firm in helping you to run the sprint and many of these people will bring an outside perspective and experience with this sort of design thinking innovation approach.
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
Have a group and want to save more? Groups always save with Coveros Training! Groups of 3–5 save 10% on Public and Live Virtual training, and groups of 6 or more save 20%. Group discounts are automatically applied when registering multiple attendees with the same initial path. For groups choosing a mix of classes, contact our Client Support Group at 929.777.8102 or email [email protected]. https://www.tatvasoft.com/blog/wp-content/uploads/2015/12/rapid_application_development.jpg
To make your Design Sprint more efficient, Google suggests a few preparation tips, like writing a Sprint brief, collecting User Research, assembling a cross-functional team, planning Lightning Talks, creating a Deck, finding the right Space, getting the Supplies, setting the stage, the ground rules for Sprinting, and choosing a good ice-breaker! Innovation fortune only favors the prepared mind.
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 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.
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.
IDEO typically uses lots of different research techniques to generate insights around the needs of people including, but not limited to, observation, interviewing, immersive empathy, and exploring extreme users. Generally, the types of research you can do fall into three buckets. Generative research helps identify new opportunities and explore needs. Evaluative research gathers feedback on experiments and helps you iterate forward. These two types of research are focused on the future and new ideas. Traditional market research is known as validating research—intended to understand what is currently happening. Balance your research approach to focus on what’s happening now and what could be in the future.
With a solid foundation in science and rationality, Design Thinking seeks to generate a holistic and empathetic understanding of the problems that people face. Design thinking tries to empathize with human beings. That involves ambiguous or inherently subjective concepts such as emotions, needs, motivations, and drivers of behaviors. The nature of generating ideas and solutions in Design Thinking means this approach is typically more sensitive to and interested in the context in which users operate and the problems and obstacles they might face when interacting with a product. The creative element of Design Thinking is found in the methods used to generate problem solutions and insights into the practices, actions, and thoughts of real users.
The design sprint reduces the risk of bringing a new product, feature or service to the market. The process helps teams to gain direct feedback from customers quickly, meaning new solutions and experiences can be iterated and improved before they are built and launched. The Design Sprint book was written and published by Jake Knapp, John Zeratsky and Braden Kowitz. Designer Jake Knapp invented this successful 5-day process at Google. Since then the methodology has been accepted not only by Google ventures but by hundreds of successful brands across the globe.
Thanks to timeboxing, the Design Sprint takes a process that can sometimes drag on for months, and condenses it into just 5 days. The client is actively involved in the first days of the sprint (workshops). Day 4 is devoted to Prototyping and can be performed remotely. On day 5 we will invite users to test our prototype and take advantage of their feedback to assess the potential of your product.
Einstein was certainly right — we can’t solve problems by using the same kind of thinking we used when we created them. In addition, with the rapid changes in society, the methods we have previously used to solve many of the problems we face are no longer effective. We need to develop new ways of thinking in order to design better solutions, ser...