Previous Lecture Complete and continue  

  The GV Model in a Nutshell

Jake Knapp published the Google Ventures model in his book “SPRINT - How to Solve Big Problems and Test New Ideas in Just Five Days” (2016). The GV model, as we will be calling it from now on, inherits most of its techniques from Design Thinking. Although the book was launched in 2016, the GV model’s most known sprint “The Blue Bottle Case” took place around 2013. Since then, the Google Ventures team has been sprinting with numerous startups and companies. You can read many of those case stories here:

Day 1

The team defines the challenge, makes a map, defines target customers, and talks to experts from inside and outside the team.

Day 2

Starts with a benchmark research on great solutions for the team to get inspired from, use, remix, and improve. The team then defines a “How Might We” question (don’t worry about this right now, we’ll cover it extensively later). Finally, the team moves into idea generation mode.

Day 3

Team decides on the best solutions and moves on to create a storyboard.

Day 4

The team will build a realistic prototype using the storyboard as a basis, then do a trial run.

Day 5

Test the prototype with users, watch and learn from them.

Pros: Inherits tools from Design Thinking. Easier to recruit users since user sessions take place only on the last day. Great if you have high-quality raw input coming into the sprint and can put together a very diverse and creative team.

Cons: Very little exploratory research. No co-creation with users, which may silence serendipity by turning off the gathering of user insights and user generated ideas at early stages. The team builds first and learns from users last.