Learnings of a Design Sprint Maverick

The new rage in the space where Agile meets Design is the Design Sprint.

What are design sprints and how can you adapt them to apply them at your startup? In this talk Allard will discuss this and the best practices he has learned from his experiences at Google and his subsequent companies.

=======================

Performed at Design Thinking Stammtisch @Axel Springer, Berlin, 12 February 2015

www.vanhelbergen.com
www.twitter.com/vanhelbergen

Slides with speaker notes: http://goo.gl/MywT4L

Google Ventures Design Sprint Book: http://www.gv.com/sprint/

Brandwatch Blogpost on Design Sprints: http://engineering.brandwatch.com/accelerating-design-solutions-with-design-sprints/

=======================
Speaker Notes:
LEARNINGS OF A
DESIGN SPRINT MAVERICK
Allard van Helbergen @vanhelbergen vanhelbergen.com
The Challenges!
WebBuilding products has changed
Web is starting to appreciate design

Give Design a seat at the table
We need to change the mindset
The perfect design will emerge overtime
NOT upfront that will scale to any future requirementand do sth with that seat
HOW?

Design Sprints!

How many people know?

Why
What
How

@vanhelbergen
Hi, I’m Allard.
UX Designer @ Brandwatch
My background
Freelance: Kanban
Started at Accenture: Waterfall
Google: Scrum and design thinking around it,
Startups: Scrum and ‘Intrapreneuring like a Maverick’!

Idea
Launch
Build
Measure
Agile/Lean
ideate, build, launch, measure, iterate, repeat
Good:
Ship early shift often
Resource control
Iterative cycle
Bad:
Design dependencies too tightly coupled
No input from prototyping into

Launch
Build
Measure
Idea
Design Sprint
from Google Ventures
Daniel Burka
Jake Knapp

Getting feedback before dev

Idea
Launch
Build
Measure
Run it a few times

Idea
Launch
Build
Measure
Learn early, learn often; ship with confidence

HOW DO THEY ACHIEVE THIS?

Empathise
Define
Ideate
Prototype
Test
Everyone know this right?

Loosely map steps
Implement Standford Design thinking into Scrum cycle
Prep
0 - prepare
Real
Choose big problem
collect people team
block a week + agendas
Schedule user studies
Considerations
Prepare well - Set deadlines for learning
Stretch it to fill a sprint
Half days vs full days
Know what to tackle
Get the right people, mix it up

Understand
1 - understand
Real
Show and tell everything you know
Competitors, Own app
Get all people on the same line
Define metrics for success
Considerations
30 min Interviews
3 pp for 15 - 20 min
3 * 4 or 5 = 12 - 15 in under 90 min
Use business tools
Business Model Canvas
Empathy Map
Javellin Board
Metrics
HEART
Pirate Metrics

Diverge
2 - diverge
Real
Create lots of ideas individually
Notes, mindmap, crazy 8s, storyboard
Critique and Vote
Considerations
Use exercises to do this (User Journey)
Keep it fun
Force the decision maker, to counter groupthink

Decide
3 - Decide
Real
Choose solutions, set solutions up against each other
Draw large storyboard together
best shot, battle royale
Considerations
Keep everything together
People
Deliverables
Assets
block enough time
Getting back into the flow is hard

Prototype
4 - Prototype
Real
build prototypes for testing
goldie locks fidelity
Considerations
The most critical path, exactly what you need to learn
Prototype with subset of team, worst case on your own
Iterative work here REALLY helps

Validate
5 - Validate
Real
Show to customers in 1:1 interviews
Considerations
Mix internal and external users
Get team to make notes

Empathise
Define
Ideate
Prototype
Test
Under-
stand
Prep
Diverge
Decide
Prototype
Validate
Works? Great! Doesn’t work? Learning the hard way

Google Ventures Book

Brandwatch Blog
More info
Google Ventures blog: http://www.gv.com/sprint/
Brandwatch blog: http://engineering.brandwatch.com/accelerating-design-solutions-with-design-sprints/

@vanhelbergen
https://speakerdeck.com/allardvanhelbergen/learnings-of-a-design-sprint-maverick

The perfect design will emerge overtime
Earn seat at the table