You’re the product person in your organization. You may have no one reporting to you. You might have 50 people in your product group. You might be responsible for the entire product. Maybe the design team doesn’t report to you, nor do the developers or marketing and sales teams. Maybe you’re in a startup without all those defined roles, and you wear a lot of hats. Maybe you’re in a large enterprise organization that has each one defined to the nth degree. Maybe you are a product design freelancer. You might work in an agency as a consultant. You probably have read a blog post about this process. Maybe you even tried one yourself. You’re very likely wondering how your unique needs will work with design sprints and are seeking more information than you can find in a few blog posts. https://res.cloudinary.com/practicaldev/image/fetch/s--gk0eqZrY--/c_imagga_scale,f_auto,fl_progressive,h_100,q_auto,w_100/https://thepracticaldev.s3.amazonaws.com/uploads/user/profile_image/64057/722ec19f-029b-479d-a34b-33cf27a5fe79.jpg
The “Design Sprint” is one of the fastest trending innovation and design thinking approaches I’ve seen in the past decade. It is now a part of our language to describe a specific kind of innovation session. This design sprint training article shares an overview of the process and resources you can use throughout. The design sprint concept has been made famous by Google Ventures in the book Sprint by Jake Knapp, John Zeratsky, and Braden Kowitz. It is a 5 day approach with specific activities each day of the week and each part of the day. I like it because it is something fun to learn and experience with a design sprint training workshop. The design sprint process seems like a combination of design thinking, lean startup, and agile for an approach to innovation that is rapid. You may have already heard about the Sprint book and the 5 day approach. BUT, did you know that there is also a 3 day design sprint kit from Google as well?
Humans naturally develop patterns of thinking modeled on repetitive activities and commonly accessed knowledge. These assist us in quickly applying the same actions and knowledge in similar or familiar situations, but they also have the potential to prevent us from quickly and easily accessing or developing new ways of seeing, understanding and solving problems. These patterns of thinking are often referred to as schemas, which are organized sets of information and relationships between things, actions and thoughts that are stimulated and initiated in the human mind when we encounter some environmental stimuli. A single schema can contain a vast amount of information. For example, we have a schema for dogs which encompasses the presence of four legs, fur, sharp teeth, a tail, paws, and a number of other perceptible characteristics. When the environmental stimuli match this schema — even when there is a tenuous link or only a few of the characteristics are present — the same pattern of thought is brought into the mind. As these schemas are stimulated automatically, this can obstruct a more fitting impression of the situation or prevent us from seeing a problem in a way that will enable a new problem-solving strategy. Innovative problem solving is also known as “thinking outside of the box”.
The design sprint is an important approach to innovation and quickly developing new products and services that customers want. It is becoming a popular trend in organizations and with designers and developers. It is also relevant to people of other roles since innovation is everyone’s business. Scroll through this article for a quick design sprint training guide. Consider getting the book (or at least the free toolkit and resources), participating in a design sprint workshop, or running your own sprint to learn through experience.
Page 72 - ... of power and electricity transformer (66, 93); also the most efficient place for the poultry and dairy farming which require road access (58); the bus stop is the natural arrival place for incoming wedding processions (10). C2: 5. Provision for festivals and religious meetings. 6. Wish for temples. 20. People of different factions prefer to have no contact. 21. Eradication of untouchability. 24. Place for village events — dancing, plays, singing, etc., wrestling. 84. Accommodation for panchayat...
On Thursday, you'll build a realistic prototype of the solutions in your storyboard so you can simulate a finished product for your customers. Design Sprint prototyping is all about a "fake it till you make it" philosophy: With a realistic-looking prototype, you'll get the best possible data from Friday's test, and you'll learn whether you're on the right track.
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.
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.
“On Monday, you and your team defined the challenge and chose a target. On Tuesday, you’ll come up with 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. Later in the week, the best of these sketches will form the plan for your prototype and test.”
Learn fast, fail fast. The sprint helps to obtain a clear vision of the goals upfront. It forces you to make critical decisions and solve complex problems fast. This means that you and your team can save months of design, engineering and development costs. The bonus? You’ll be able to get your product to market faster because you focussed on the right thing.
After you have a big and vague problem that your team decided to run a Sprint on, the next step is further defining the problem so that it’s concrete and manageable. Instead of a too vague statement like “How to reduce food waste in New York City”. You and the team need to do some pre-work to further define the problem — Who are the users? What’s your product focus/technology/strength? What are the constrains? Believe it or not, your team usually already know a lot about the problem. Someone in the organization probably already done some research or had some ideas. If your team has nothing, then look outside your organization, chances are that there is a competitor somewhere already doing something similar.
Couldn’t have said it better than the big man himself. As Tim says, Design Thinking is an approach to innovation that draws from a toolkit. This toolkit is vast and full of numerous exercises that can be pulled out at different points in the design process. Learning about Design Thinking is learning the philosophy and mindset of innovation along with the tools you could use to make your way there. Here’s everything you really need to know about Design Thinking.
With a small team and a clear schedule for the week, you’ll rapidly progress from problem to tested solution. On Monday, you create a map of the problem. On Tuesday, each individual sketches solutions. Then, on Wednesday, you decide which sketches are the strongest. On Thursday, you build a realistic prototype. And finally, on Friday, you test that prototype with five target customers.
The primary cause of concern? Privacy. The camera feature caused discomfort among unwitting passersby who couldn’t tell whether they were being quietly photographed or filmed. “Glass is easy to ignore” for the person wearing it, but “Google’s challenge in making the device a successful consumer product will be convincing the people around you to ignore it as well,” wrote Simson Garfinkel in the MIT Technology Review. Other Explorers complained that Glass was no more useful than existing devices—only much more conspicuous. New tech gadgets are often praised for their sleekness and style, but Glass just looks like a pair of geeky spectacles, wrote Jake Swearingen in the Atlantic.
Ah, Tuesday morning. A leisurely stroll around the gallery of concept sketches, coffee cup in hand, taking it all in. We spend the whole morning deciding what to prototype, starting with the Heat Map, where people place multiple votes on inspiring parts of sketches so that clusters can form. These clusters are then highlighted in the solution presentations, where the moderator walks the room through each individual sketch, followed by the straw poll (where everybody puts one vote on the one solution they want to push forward). The morning is rounded off with the Decider’s vote, where they pick one or two concepts that they want to prototype.
With more than 500 new apps entering the market every day, what does it take to build a successful digital product? You can greatly reduce your risk of failure with design sprints, a process that enables your team to prototype and test a digital product idea within a week. This practical guide shows you exactly what a design sprint involves and how you can incorporate the process into your organization.
“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.”
Page 36 - ... them because of the difficulties of going back and starting afresh. From his case studies of architectural design, Rowe (1987) observed: A dominant influence is exerted by initial design ideas on subsequent problem-solving directions . . . Even when severe problems are encountered, a considerable effort is made to make the initial idea work, rather than to stand back and adopt a fresh point of departure.
Prototype only what you need to validate your ideas in a very short time; hammer out a realistic prototype, a facade of the experience you have envisioned in the sketch phase. Design a barest minimum but usable prototype, taking advantage for instance of of Pop App, an app that transforms pictures of a story board into clickable UI; think of your prototype as an experiment in order to test out hypothesis;
The Design Sprint has been developed and popularised by Jake Knapp, John Zeratsky and Braden Kowitz, who together published the book ‘Sprint- How To Solve Big Problems and Test New Ideas in Just Five Days’ (2016). Designer Jake Knapp created the five-day process at Google. The methodology has been adopted by many Google Ventures and highly successful startups such as Uber, Blue Bottle Coffee, Slack, and Shopify.
The Sprint method allowed the team to start prototyping quickly, collect immediate user feedback, and make small mistakes early. We conducted multiple design sprints in quick loops—folding the learning from week one into the structure of week two, and so on. We learned a lot in the process. Here are a few quick tips we picked up for running successful and energizing design sprints.
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.
Braden Kowitz added story-centered design, an unconventional approach that focuses on the customer journey instead of individual features or technologies. Michael Margolis took customer research—which can typically take weeks to plan and often delivers confusing results—and figured out a way to get crystal clear results in just one day. John Zeratsky helped us start at the end, and focus on measuring results with the key metrics from each business. And Daniel Burka brought firsthand expertise as an entrepreneur to ensure every step made sense in the real world.
Access to all the course videos, that not only describe the process in a great deal of detail, but also the mindset and very concrete tactics that you can put to work immediately. You also get access to all the bonus materials, including the Design Sprint cheatsheet, the preparation checklist, and facilitators toolkit, and lifetime access to the AJ&Smart Design Sprint community. As a student on the course you'll get lifetime access to all course improvements (we’re a big believer of continuous improvements, and you’ll get to benefit from this!)
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.