Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Five parallel design sprints What possibly can go wrong? Den Tserkovnyi @dtserkovnyi
24 million users per year 2 000+ universities 140 000+ programmes
Mindset
How we work 5 days of Design Sprints
March 2014
Now
me
+ More creative solutions + Easier cooperation + Speed of development - Long term planning - Style consistency
Sprint planning Standup Testing on devices Testing on devices Backlog refinement Showcase Stakeholder feedback
Sprint planning Standup Testing on devices Testing on devices Backlog refinement Showcase Stakeholder feedback Sprint alig...
Removed picture of the designer, developer and researcher observing the users On the other end, people are observing. Anyo...
It is also how you get there
Slide from thesprintbook.com/tools
You’re gonna build & test a realistic prototype in 5 days. Slide from thesprintbook.com/tools
Get the team From the notes: Before we could start our first ever sprint, we created the team and picked the date. This st...
Presentation and check list PDF thesprintbook.com/tools
Now, some quick ground rules Slide from thesprintbook.com/tools
1. The Facilitator is in charge of the schedule.
2. The Decider makes all tough decisions.
3. No devices in the room. (You can use them at breaks. Or step out of the room any time.)Slide from thesprintbook.com/too...
4. Timebox everything.
Schedule
Slide from thesprintbook.com/tools
Explain the sprint
Set the long-term goal
Enable easy selection of study programmes based on the most relevant information
Too vague Well defined makes it less creative Not an actual graph
Make a map This will be a simple diagram with around 5-15 steps. Slide from thesprintbook.com/tools
Time to call the experts
Prepare expert questions to avoid stress
Pick a target Choose a customer type and a focus on the map. Slide from thesprintbook.com/tools
Recruit Users
Slide from thesprintbook.com/tools
Group brainstorms don’t work, so you’ll sketch alone. Slide from thesprintbook.com/tools
Sketch Notes 20 minutes Ideas 20 minutes Crazy 8s 8 minutes Solution sketch 30–90 minutes Slide (partially) from thesprint...
Divide or swarm Slide from thesprintbook.com/tools
Shorter day?
Slide from thesprintbook.com/tools
You’ll make fast decisions without groupthink or sales pitches Slide from thesprintbook.com/tools
Sticky decision Choose the best sketches with silent review and structured critique. Slide from thesprintbook.com/tools
Art museum Heat map Speed critique
Straw poll Supervote
Turn the winning sketches into a storyboard Slide from thesprintbook.com/tools
Slide from thesprintbook.com/tools
A realistic façade is all you need to learn from users. Slide from thesprintbook.com/tools
If your product is on a screen, try tools like Keynote or PowerPoint and InVision or Marvel. Slide from thesprintbook.com/...
If it’s on paper, design it with Keynote, PowerPoint, or Word. Slide from thesprintbook.com/tools
If it’s a service, use your sprint team as actors. Slide from thesprintbook.com/tools
Maker, Stitcher, Soldier, Spy
Maker, Stitcher, Soldier, Spy Writer, Asset collector, Interviewer
Longest day? • Storyboard refinement • Pending decisions
Slide from thesprintbook.com/tools
5 interviews are enough to reveal big patterns.
Decide on the note taking format
Prepare for “no-shows”
At the end of the sprint, you’ll know what to do next.
We added retrospective
Slide from thesprintbook.com/tools
Often, it’s helpful to fix the prototype and test it again. Slide from thesprintbook.com/tools
FM T W T If you do 3 sprints in a row… FTWT FT …they won’t all take 5 days. Slide from thesprintbook.com/tools
Conclusions
Cross-department alignment
Championing UX
Robust framework
Enough time to think things through, but not enough to procrastinate
Regular work during the sprint
Deciders alignment
Follow up can be difficult
Design methods toolboxhttps://designsprintkit.withgoogle.com
Next steps
Follow-up
Timeline on how to pick things In the future (blurred)
Hack day/UXD day
Combining designers from different teams in less sprints
Living style guide
Hybrid design team
Slide from thesprintbook.com/tools
Ask me anything @dtserkovnyi or LinkedIn or visit us in Eindhoven
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Five parallel design sprints. What possibly can go wrong?
Upcoming SlideShare
Loading in …5
×
Internet
1,153 views
Jun. 08, 2017

Five parallel design sprints. What possibly can go wrong?

Slides from my UXcamp Berlin presentation.
We, at StudyPortals, experiment a LOT with different design methods.
This time I talked about design sprints, a methodology introduced by Google. As a quick process to define the future of your product.
This year we challenged ourselves to run 5 design sprints at the same time, virtually occupying half of the company for a week of UX activities. How did we do it? What went wrong?

no profile picture user

  • Be the first to comment

Five parallel design sprints. What possibly can go wrong?

  1. 1. Five parallel design sprints What possibly can go wrong? Den Tserkovnyi @dtserkovnyi
  2. 2. 24 million users per year 2 000+ universities 140 000+ programmes
  3. 3. Mindset
  4. 4. How we work 5 days of Design Sprints
  5. 5. March 2014
  6. 6. Now
  7. 7. me
  8. 8. + More creative solutions + Easier cooperation + Speed of development - Long term planning - Style consistency
  9. 9. Sprint planning Standup Testing on devices Testing on devices Backlog refinement Showcase Stakeholder feedback
  10. 10. Sprint planning Standup Testing on devices Testing on devices Backlog refinement Showcase Stakeholder feedback Sprint alignment UX Standup UX Day or Usability testing (once a month)
  11. 11. Removed picture of the designer, developer and researcher observing the users On the other end, people are observing. Anyone can drop by to see user tests.
  12. 12. It is also how you get there
  13. 13. Slide from thesprintbook.com/tools
  14. 14. You’re gonna build & test a realistic prototype in 5 days. Slide from thesprintbook.com/tools
  15. 15. Get the team From the notes: Before we could start our first ever sprint, we created the team and picked the date. This step was not easy as it demanded 35 hours of time in one week. With a little bit of magic and meeting rescheduling we managed to clean up agenda of the future team. Which finally consisted of 8 members of 6 nationalities from 5 different departments. On the other 7 sprints every team facilitator contacted main stakeholders outside of Engineering department to get them on board.
  16. 16. Presentation and check list PDF thesprintbook.com/tools
  17. 17. Now, some quick ground rules Slide from thesprintbook.com/tools
  18. 18. 1. The Facilitator is in charge of the schedule.
  19. 19. 2. The Decider makes all tough decisions.
  20. 20. 3. No devices in the room. (You can use them at breaks. Or step out of the room any time.)Slide from thesprintbook.com/tools
  21. 21. 4. Timebox everything.
  22. 22. Schedule
  23. 23. Slide from thesprintbook.com/tools
  24. 24. Explain the sprint
  25. 25. Set the long-term goal
  26. 26. Enable easy selection of study programmes based on the most relevant information
  27. 27. Too vague Well defined makes it less creative Not an actual graph
  28. 28. Make a map This will be a simple diagram with around 5-15 steps. Slide from thesprintbook.com/tools
  29. 29. Time to call the experts
  30. 30. Prepare expert questions to avoid stress
  31. 31. Pick a target Choose a customer type and a focus on the map. Slide from thesprintbook.com/tools
  32. 32. Recruit Users
  33. 33. Slide from thesprintbook.com/tools
  34. 34. Group brainstorms don’t work, so you’ll sketch alone. Slide from thesprintbook.com/tools
  35. 35. Sketch Notes 20 minutes Ideas 20 minutes Crazy 8s 8 minutes Solution sketch 30–90 minutes Slide (partially) from thesprintbook.com/tools
  36. 36. Divide or swarm Slide from thesprintbook.com/tools
  37. 37. Shorter day?
  38. 38. Slide from thesprintbook.com/tools
  39. 39. You’ll make fast decisions without groupthink or sales pitches Slide from thesprintbook.com/tools
  40. 40. Sticky decision Choose the best sketches with silent review and structured critique. Slide from thesprintbook.com/tools
  41. 41. Art museum Heat map Speed critique
  42. 42. Straw poll Supervote
  43. 43. Turn the winning sketches into a storyboard Slide from thesprintbook.com/tools
  44. 44. Slide from thesprintbook.com/tools
  45. 45. A realistic façade is all you need to learn from users. Slide from thesprintbook.com/tools
  46. 46. If your product is on a screen, try tools like Keynote or PowerPoint and InVision or Marvel. Slide from thesprintbook.com/tools
  47. 47. If it’s on paper, design it with Keynote, PowerPoint, or Word. Slide from thesprintbook.com/tools
  48. 48. If it’s a service, use your sprint team as actors. Slide from thesprintbook.com/tools
  49. 49. Maker, Stitcher, Soldier, Spy
  50. 50. Maker, Stitcher, Soldier, Spy Writer, Asset collector, Interviewer
  51. 51. Longest day? • Storyboard refinement • Pending decisions
  52. 52. Slide from thesprintbook.com/tools
  53. 53. 5 interviews are enough to reveal big patterns.
  54. 54. Decide on the note taking format
  55. 55. Prepare for “no-shows”
  56. 56. At the end of the sprint, you’ll know what to do next.
  57. 57. We added retrospective
  58. 58. Slide from thesprintbook.com/tools
  59. 59. Often, it’s helpful to fix the prototype and test it again. Slide from thesprintbook.com/tools
  60. 60. FM T W T If you do 3 sprints in a row… FTWT FT …they won’t all take 5 days. Slide from thesprintbook.com/tools
  61. 61. Conclusions
  62. 62. Cross-department alignment
  63. 63. Championing UX
  64. 64. Robust framework
  65. 65. Enough time to think things through, but not enough to procrastinate
  66. 66. Regular work during the sprint
  67. 67. Deciders alignment
  68. 68. Follow up can be difficult
  69. 69. Design methods toolboxhttps://designsprintkit.withgoogle.com
  70. 70. Next steps
  71. 71. Follow-up
  72. 72. Timeline on how to pick things In the future (blurred)
  73. 73. Hack day/UXD day
  74. 74. Combining designers from different teams in less sprints
  75. 75. Living style guide
  76. 76. Hybrid design team
  77. 77. Slide from thesprintbook.com/tools
  78. 78. Ask me anything @dtserkovnyi or LinkedIn or visit us in Eindhoven

×