How we used Google Ventures Design Sprint to accelerate innovation at SEEK.
We discuss the key ingredients, practical tips and some important deviations from the Google Ventures process.
A detailed blog post describing our process can be found here:
https://medium.com/seek-user-experience/using-design-sprint-to-accelerate-innovation-part-i-of-ii-f643ad42cf60
One of the practical tips is described in detail here:
https://medium.com/seek-user-experience/4-simple-steps-to-improve-your-ui-sketches-4ad2f1433373
_______________________
Originally presented at melbournegeeks.com meetup in July 2015
http://www.meetup.com/Melbourne-Geek-Night/events/223730061/?comment_table_id=452258090&comment_table_name=event_comment
_______________________
If you are interested in having this presented at your workplace or Meetup, get in touch via Twitter @ThatBaldUXGuy
Intro:
Rob and I were lucky enough to…
we’ll talk to you about how we locked up 12 people in a room for a week and got them to come up with some novel ideas on tackling an important business opportunity
The sprint is a five-day process for answering critical business questions through design, prototyping, and testing ideas with customers.
Accelerate the design process (outcome within a week, not 6 weeks). Earlier user and business input
Developed by Google Ventures for internal projects.
It’s a “greatest hits” of business strategy, innovation, behavior science, design thinking, and more.
Practice is the general reason
Then, talk about why we specifically wanted to do it and the fact that we have to remain innovative. Being at the top is hard - you are constantly being attacked by competitors.
Talk about the fact that we identified a market opportunity that we wanted to act on quickly
1. time, pre-scheduled user testing
2. x-functional, gender mix, size, facilitator, decision makers
3. Keep it visual - space, supplies (no PowerPoint!!). Also motivating at the end of each day to see what you’ve achieved
earlier feedback means you waste less time on ideas not worth developing. Google Venture suggests doing this on day 5
After 5 days you are exhausted. Having the weekend to recharge and reflect is good
2. because of earlier user engagement, we had more time to test multiple ideas. Google Ventures suggests testing with one idea
Tested individual ideas, not end to end flows during the week.
3. The key was to agree on scope up-front and have the decision makers involved. The benefit is the whole team feels empowered. No parking lot.
Call out pricing
Focus on
1. The difference at which point you have to make a decision
2. Empathy
3. Involving users in the design and decision making
4. Making a more informed decision
Decision was on what to prototype, not what to build
Focus on
1. The difference at which point you have to make a decision
2. Empathy
3. Involving users in the design and decision making
4. Making a more informed decision
Decision was on what to prototype, not what to build
Talk about
Two diferent types of exercises. One to get you into the problem space and one to get you thinking wide
Call out Mars Rover example
2. Everyone started presenting on day 1
3. Everyone forced to pay attention from day 1 and contribute (note taking routine)
Talk about
1. the four steps
2. the benefit of sketches looking the same
3. building confidence for those who are not used to drawing
Talk about
1. Would have been easy for the experienced facilitators to do this
2. No passengers - everyone involved
3. Building empathy personally
Talk about
1. Experiencing your users’ world first hand
2. more critical feedback
Talk about
1. Speed to develop an idea
2. Difference to normal inception process
3. ownership by the whole team
4. exec team impressed and willing to keep going
5. small team forming around this and looking how we can develop a lean product, test early
Point out that we have described this process in detail on Medium and there is a growing library of articles on the SEEK User Experience Medium account