Contents
- 1 Is sprint design effective?
- 2 What is not a design sprint?
- 3 What’s the difference between design thinking design sprints and agile sprints?
- 4 When should I not design sprint?
- 5 How does a Design Sprint work?
- 6 Who should be in a design sprint?
- 7 Who are the companies we work with at GV?
- 8 When did Jake Knapp start the design sprint?
Is sprint design effective?
Design sprints are a safe way to explore bold solutions to risky problems. When facilitated properly by experts, every sprint team wins. Organizations are becoming increasingly aware that good design is good for business.
What is not a design sprint?
There might already be a validated product design concept that’s agreed to and all the team needs to do is execute it. A design sprint to implement functionality without exploring improvements, reductions, or changes isn’t a design sprint.
What’s the difference between design thinking design sprints and agile sprints?
Agile follows naturally, giving us the means to implement these solutions efficiently. Quite simply, it is a project management mindset. Design Sprints are purely a problem-solving method. Typically, the biggest misuse of Design Sprints is when teams try to use them to define or decide what problem to solve.
What is the purpose of a design sprint?
Design sprints are an intense 5-day process where user-centered teams tackle design problems. Working with expert insights, teams ideate, prototype and test solutions on selected users. Google’s design sprint is the framework to map out challenges, explore solutions, pick the best ones, create a prototype and test it.
Who should run a Design Sprint?
Design Sprints are run by teams. If you don’t have a team, the Sprint doesn’t really happen. It’s essential to have a group of people coming together from different disciplines (e.g. product management, design, engineering). To facilitate a Design Sprint, you need two specific roles — the facilitator and the decider.
When should I not design sprint?
Design Sprints are not for you if…
- The problem is too small.
- The problem is unclear.
- You want to replace Agile Sprints with Design Sprints.
- You want to change the Design Sprint process completely.
- You can’t do User Testing with 5 users.
How does a Design Sprint work?
The sprint is a five-day process for answering critical business questions through design, prototyping, and testing ideas with customers. Instead of waiting to launch a minimal product to understand if an idea is any good, you’ll get clear data from a realistic prototype.
Who should be in a design sprint?
The sprint should include a cross-functional team of seven people. The key idea when filling out the team is to draw from different areas of the organization to get different perspectives. For example, if you’re looking at a product, you should have someone from the engineering team, design team, and sales team.
How does the design sprint work at GV?
Developed at GV, it’s a “greatest hits” of business strategy, innovation, behavior science, design thinking, and more—packaged into a battle-tested process that any team can use. Working together in a sprint, you can shortcut the endless-debate cycle and compress months of time into a single week.
What do you need to know about the design sprint?
The sprint is a five-day process for answering critical business questions through design, prototyping, and testing ideas with customers. Developed at GV, it’s a “greatest hits” of business strategy, innovation, behavior science, design thinking, and more—packaged into a battle-tested process that any team can use.
Who are the companies we work with at GV?
On Thursday, you’ll hammer out a high-fidelity prototype. And on Friday, you’ll test it with real live humans. At GV, we’ve run sprints with companies like Nest, Flatiron Health, and Medium —to help them enter new markets, design new products, develop new features for millions of users, define marketing strategies, and much more.
When did Jake Knapp start the design sprint?
Former GV design partner Jake Knapp began running design sprints at Google in 2010. He worked with teams like Chrome, Google Search and Google X. In 2012, Jake brought sprints to GV, and the rest of the team chipped in their expertise to perfect the process.