This talk is about understanding the team dynamics at play on a Design Sprint. It briefly explains what is a Sprint, when to do one and who should be in it, as well as its structure. Then, it explains what makes it so successful, by understanding the mechanics that make it work. I gave this talk at a local meetup, called Braga.Product. I hope to have the video of this talk available soon.

1. I’m João
Hi!
@jferreiradzn

3. Deconstructing
the Design Sprint
Understanding the team dynamics at play

4. What’s a Design
Sprint?

5. What’s a Design Sprint?

6. A five-day process for answering
critical business questions
through design, prototyping,
and testing ideas with users.
What’s a Design Sprint?

8. Highly flexible and accessible
What’s a Design Sprint?
Timeboxed activities
Success by preventing failure

9. When should I
run a Sprint?

10. When should I run a Sprint?
When stakes are high
When there’s not enough time
When you’re plain stuck
When you’re starting a new project

11. Who should be
in the Sprint?

12. Who should be in the Sprint?
Facilitator
A Decider (CEO, PM, PO, Client)
Designer
Developer

13. Also…
Marketing
Customer Support
Sales
CFO, CTO, CCO (all C’s basically)

14. The Sprint
Structure

15. The Sprint Structure
Understand
Diverge
Converge
Prototype
Test

16. The Sprint Structure
Understand
Diverge
Converge
Prototype
Test
Monday
Identify and clarify the problem at hand.
Talk to your users and understand their
needs and workflows, so you can be
equipped to formulate a solution.

17. The Sprint Structure
Understand
Diverge
Converge
Prototype
Test
Tuesday
Explore a range of possibilities that may
solve the identified problem.

18. The Sprint Structure
Understand
Diverge
Converge
Prototype
Test
Wednesday
Collaboratively curate and narrow down the
suggested ideas into one or two solutions to
move forward and test.

19. The Sprint Structure
Understand
Diverge
Converge
Prototype
Test
Thursday
Build a realistic prototype so you can put
your solutions in front of the users and test
them.

20. The Sprint Structure
Understand
Diverge
Converge
Prototype
Test
Friday
Run interviews and usability tests with
users, which will provide you with
invaluable findings.

21. Interpret the results, capture
your findings and integrate
them with your workflow.
The Sprint Structure

22. What makes the
Sprint a success?

23. The Design Sprint hacks team
dynamics and mixes it with a
profound knowledge of design
thinking techniques
What makes the Sprint a success

24. The Design Sprint hacks team
dynamics and mixes it with a
profound knowledge of design
thinking techniques
What makes the Sprint a success

25. The 1980’s
paradigm

26. 1980’s Paradigm
Group Brainstorming
Polarization in group decision making
Groupthink
Unchallenged, poor-quality
decision-making

27. J. Richard
Hackman

28. He started by focusing his work
on real-time performance teams,
with no chance for “do overs”

29. Why teams
don’t work

30. Team empowerment rarely comes from
long and seemingly democratic
discussions about what teams' purposes
should be. It comes instead from
establishing a direction for the team that
is clear, challenging (with no guarantee
of success!) and highly consequential for
the organization or its clients.
J. Richard Hackman

31. Team empowerment rarely comes from
long and seemingly democratic
discussions about what teams' purposes
should be. It comes instead from
establishing a direction for the team that
is clear, challenging (with no guarantee
of success!) and highly consequential for
the organization or its clients.
J. Richard Hackman

32. Why teams don’t work?
No room for individuality
Unknown/undefined goal
No accountability
No clear leadership
“Too many cooks in the kitchen”

33. Most teams leave enormous
pools of member talent
untapped.

34. How to make
teams work

35. The challenge for a leader is to
find a balance between
individual autonomy and
collective action.
J. Richard Hackman

36. Making teams work
Develop ideas individually
Clearly defined leadership & roles
All necessary skills represented
An inescapable deadline
A challenging, clearly defined goal

37. What makes the
Sprint a success

38. What makes the Sprint a success
A “high risk, big reward” goal
Focus on individual work
Small teams, with diverse skills
A Facilitator and A Decider
Testing day

39. What makes the Sprint a success
Efficient feedback and ideation techniques
Real-world validation of assumptions
Focus on people and valid data
Team-shared insights

40. Want to know
more?

41. Want to know more?
gv.com/sprint
github.com/thoughtbot/design-sprint
sprintstories.com

43. Design Sprint Workshop @
Subvisual
July, 8th

44. Thank you!
@jferreiradzn