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!
The big idea with the Design Sprint is to build and test a prototype in just five days. You'll take a small team, clear the schedule for a week, and rapidly progress from problem to tested solution using a proven step-by-step checklist. It's like fast-forwarding into the future so you can see how customers react before you invest all the time and expense of building a real product. 
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.

Cons: They likely haven’t facilitated nearly as many design sprints or training workshops compared to the firms listed above. As a result, it’s quite possible that you get a lesser design sprint experience at a higher cost. If you are trying to get organizational buy-in for the design sprint process and your innovation/design firm doesn’t have the expertise to deliver a great experience, you may leave your organization with a bad impression of design sprints, making it much more difficult to secure leadership buy-in for future sprints.
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).
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.
“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.”
Use the Tabata training method of product design. Tabata training is a workout method that focuses on 20 seconds of intense work followed by 10 seconds of rest. This is a great metaphor for sprint prototyping: It’s intense, and that means that rest is just as important as the creative bursts. Make a point of managing team energy by having intentional down days. With Swell, we made sure to keep our energy up by working in cafes, getting breather spaces when we needed to focus, and even hitting up museums or exercise classes to stay healthy and inspired.
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.
Design Sprints were once thought to be the exclusive province of startups and small organizations, but that is simply not the case. To the contrary, we are seeing massive organizations, public enterprises and government agencies rack up successes using this time-boxed method to overcome design and product roadblocks. Many of their stories are captured in the new book Enterprise Design Sprintsby Richard Banfield.
Design for a light-touch, full-product experience. Ask yourself: What’s the smallest set of features you can design that will still solve users’ problems? Start with the simplest version of your product, get user feedback, and then add features. As your sprint loops continue, you can move from simple prototypes to robust product directions. With Swell, we focused on creating a hero page for each key interaction (landing page, sign up, and invest). This meant we were testing the functionality of the full product experience, just in a light-touch way.
Why did we tell you this story? Telling stories can help us inspire opportunities, ideas and solutions. Stories are framed around real people and their lives. Stories are important because they are accounts of specific events, not general statements. They provide us with concrete details that help us imagine solutions to particular problems. While we’re at it, please watch this 1-minute video to help you get started understanding what Design Thinking is about.

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.
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.
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.

Another important criterion is the expertise of the trainers, both into the subject as well as in training and facilitating teams and individuals. As mentioned before, some providers have build experience by applying the framework themselves, while building digital products. Others have a background as trainers (for example in Agile, Scrum or Design Thinking) and added Design Sprint training to their curriculum.