During the four-week boot camp, we present a balance of theory and practice aimed to build up your confidence and set you up to run (and sell) your own Design Sprints. Get ready to deep dive in one of our rich scenarios and design solutions using our unique canvas-to-canvas approach. This approach was designed to make your experience learning about Design Sprint a smooth sailing one. You can take as much time as you want to go through the Boot camp, usually students complete the course in two months. That being said, it is possible to finish the core-program in just one month. Here is a suggested breakdown structure for that.
This should be a no-brainer, but do NOT, under any circumstances start revising the foundation of the sprint, which was defined at the beginning of the process. In our case, assumptions, questions, goals and problems were literally revised on the last day of the sprint, rendering much of the process pointless, since everything in the sprint is built on top of this foundation. Mess with the foundation — and the whole house comes crashing down.
is one of the pioneers of Design Sprint methodology in Europe. Based in Switzerland, he works with startups and big companies in the regions of Lausanne (EPFL), Geneva and France. Passionate about digital, he has more than 15 years of experience in agencies, crafting website and designing apps. He will accompany you throughout the process: from idea to prototype.
Design sprints can help prevent you from building the wrong thing even when your customers say it’s the right thing. Larissa Levine, from the Advisory Board Company, believes that a design sprint is successful if it guides you toward building the right product feature. As she explains, “Product marketing wants to sell this one feature and says, ‘let’s build XYZ because we heard that the user said they wanted XYZ,’ when actually, that’s not the problem at all. They think they want XYZ, but it’s not it at all. So you end up building the wrong thing.”
There are many variants of the Design Thinking process in use today, and they have from three to seven phases, stages, or modes. However, all variants of Design Thinking are very similar. All variants of Design Thinking embody the same principles, which were first described by Nobel Prize laureate Herbert Simon in The Sciences of the Artificial in 1969. Here, we will focus on the five-phase model proposed by the Hasso-Plattner Institute of Design at Stanford, which is also known as d.school. We’ve chosen d.school’s approach because they’re at the forefront of applying and teaching Design Thinking. The five phases of Design Thinking, according to d.school, are as follows:
It’s often difficult for us humans to challenge our assumptions and everyday knowledge, because we rely on building patterns of thinking in order to not have to learn everything from scratch every time. We rely on doing everyday processes more or less unconsciously — for example, when we get up in the morning, eat, walk, and read — but also when we assess challenges at work and in our private lives. In particular, experts and specialists rely on their solid thought patterns, and it can be very challenging and difficult for experts to start questioning their knowledge.
Since we've pioneered Service Design Sprints in 2014 we've been busy teaching both the MVS and the GV Design Sprint models to product developers around the globe. Our diverse community of alumni Design Sprint Masters includes startups in Silicon Valley, small businesses in Latin America, innovation powerhouses like Cisco in the USA, government agencies in Malaysia, tech giants in Japan, and the list goes on. The Design Sprint School is a direct result of these learning and teaching experiences collected during such complexity-rich and culturally diverse engagements. https://res.cloudinary.com/practicaldev/image/fetch/s--MRTtA0aB--/c_fill,f_auto,fl_progressive,h_50,q_auto,w_50/https://thepracticaldev.s3.amazonaws.com/uploads/user/profile_image/27744/7899f8c6-aa40-4cd6-ab30-833593220321.jpg
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.
The First principle incorporated in regular science is the "Design Thinking Cycle", which is new to the method. The cycle starts with you, envisioning the lives, dreams and anxieties of your customers. Then you define the problem you want to solve. After that you try to figure out as many solutions to that problem as you can imagine. Then you choose the most likely solution to be successful, you make a prototype of that solution and test its acceptance with your customers. Only after you have found a successful solution, you will invest in executing your business.
This is a relatively new practice in the business world, and there are different definitions of what exactly constitutes ‘Design Thinking’. While some call it a ‘problem-solving protocol that helps you achieve big results by focusing on the solution’, others say it is a ‘core strategy that creates an organisational culture focused on solving problems for the end user.’ There are also those who talk about design thinking as a factor that can impact the greater good and change life for the better.
In the end the design effort and research should lead to an "Fact Based or Evidence Based Business Design". The design can have many forms, ranging from a business plan to a company website, but we advise that the design should at least contain a substantiated Value Web, a substantiated Business Model Canvas and a substantiated Value Proposition Canvas.
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.
Yes! Our goal is to provide you with all the knowledge, information and the toolkit you need to confidently facilitate a successful Sprint. Everything included in this course are what we wish we had known before we started doing Sprints, and also stuff we’ve built up over time and loads of real-life experience doing Sprints with a range of different companies. Something you feel like you’re missing at the end? Just tell us and we’ll make it happen!
Organizations can often take months to create a new product concept…and many times that product concept was not validated by customer need or designed for what is most important to the business and customers. A design sprint can significantly shorten that timeframe into an intense 5 day period that is very productive. Five full days for a team dedicated to a design sprint is still more than many organizations or professionals can allocate. Our design sprint training workshops will show you this approach and how you can have more of a design sprint mindset and be able to get started with key activities.
In Design Thinking Peter Rowe provides a systematic account of the process ofdesigning in architecture and urban planning. He examines multiple and often dissimilar theoreticalpositions whether they prescribe forms or simply provide procedures for solving problems - asparticular manifestations of an underlying structure of inquiry common to all designing. Over 100illustrations and a number of detailed observations of designers in action support Rowe'sthesis.Peter G. Rowe is Raymond Garbe Professor of Architecture and Urban Design at HarvardUniversity and Chairman of the Department of Urban Planning and Design at the Harvard GraduateSchool of Design, Harvard University.
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.