We spend 45 minutes (tops) creating a passable map, which is easy enough by this point. In the book it takes half a day, but when it’s all built up like this you can do it in 45 minutes. You do NOT need longer to create a map that’s good enough. The Decider then chooses a target area on the map—and voilà! That’s Monday done in half a day. Time for lunch and a BIG coffee…
Tim Brown, CEO of the celebrated innovation and design firm IDEO, shows in his successful book Change by Design that Design Thinking is firmly based on generating a holistic and empathic understanding of the problems that people face, and that it involves ambiguous or inherently subjective concepts such as emotions, needs, motivations, and drivers of behaviors. This contrasts with a solely scientific approach, where there’s more of a distance in the process of understanding and testing the user’s needs and emotions — e.g., via quantitative research. Tim Brown sums up that Design Thinking is a third way: Design Thinking is essentially a problem-solving approach, crystalized in the field of design, which combines a holistic user-centered perspective with rational and analytical research with the goal of creating innovative solutions.
Google could learn a lesson from REALM Charter School in Berkeley, California, where students put the principles of good design thinking into practice. Emily Pilloton, teacher and Studio H founder, wrote that design should be “an active response to a context . . . a social act that builds citizenship in the next generation.” Students in her program have built a school library, a farmers’ market, and an outdoor classroom. But before diving into the projects, they conduct ethnographic research to identify their community’s (or, in the case of the library and classroom, their own) needs.
Use tricks that force users to make real—not hypothetical—decisions. The goal of any new product is to create something that people find valuable and are willing to pay for over other options in the market. But as designers, we know that often what consumers say they like is different from what they actually buy in the wild. One way we bridged this gap was by testing demand with potential Swell consumers: We gave them fake cash they could “invest” in one product or another. It was a great way to gauge whether the service had real value in the market.
The course materials take you through absolutely everything, start to finish, but if you’re already a Design Sprint facilitator then you probably won’t need to go through all the exercises, but things like the presentation slides, cheatsheet, and prototyping templates will probably be the most useful stuff, and maybe hearing some of our learnings throughout the videos will also help you avoid some common mistakes and learn some ‘hacks’
After a career in user experience design and research at companies like Microsoft and Nuance, Trace then became a developer at Pivotal Labs, and is now a Managing Director at thoughtbot. He has facilitated numerous product design sprints, and is an author and maintainer of thoughtbot's design sprint methodology repository. He's brought Lean and Agile methodology to many large companies and small startups, helping teams to focus, prioritize, and become happy and productive.
To help you understand Design Thinking, we have broken the process into five phases or modes, which are: 1. Empathise, 2. Define, 3. Ideate, 4. Prototype, and 5. Test. What’s special about Design Thinking is that designers’ work processes can help us systematically extract, teach, learn, and apply these human-centered techniques to solve problems in a creative and innovative way – in our designs, in our businesses, in our nations (and eventually, if things go really well, beyond), in our lives. Nevertheless, a great artist like Auguste Rodin, who created this famous sculpture called “The Thinker” and originally “Le Penseur”, would most likely have used the very same innovative processes in his artwork. In the same way, all great innovators in literature, art, music, science, engineering and business have practiced it and still practice it.
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?
While we assume you’re familiar with the original Design Sprint, here’s a quick recap: the Design Sprint is a five-day process to solve big problems and test ideas. A dedicated team discusses a challenge, designs potential solutions, and tests them with real users. You start with something vague, and finish with real feedback and something extremely tangible in just five days.