Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Learn How to Lead a Design Sprint...by Participating in a Design Sprint

Jimmy Chandler
November 08, 2019

Learn How to Lead a Design Sprint...by Participating in a Design Sprint

Design sprints don’t have to be 5 days — they can be done in as little as a few hours and still be a useful tool. Learn all about design sprints by doing shortened versions of several activities that are core to the experience.

Includes a list of resources on design sprints at the end of the deck.

Jimmy Chandler

November 08, 2019
Tweet

More Decks by Jimmy Chandler

Other Decks in Design

Transcript

  1. Jimmy Chandler
 
 DCUX 2019
 November 8, 2019 Learn How

    to Lead a Design Sprint…by Participating in a Design Sprint • Twitter @uxprinciples • https:// www.linkedin.com/in/ jimmychandler • [email protected]
  2. AGENDA Intro and overview Scenario Interviews Form Groups + Affinity

    mapping Sketching Critique + Prototype Break Usability testing Analysis and wrap up 9:00 AM 9:15 AM 9:20 AM 9:35 AM 10:05 AM 10:15 AM 10:30 AM 11:40 AM 12:15 PM
  3. ANDREW WHITIAK CO-FACILITATOR PRINCIPAL UX DESIGNER UX research, design engineering

    for global enterprise [email protected]
 https://www.linkedin.com/in/andrew-whitiak/
  4. WHAT IS A 
 DESIGN SPRINT? • Workshop • Time

    boxed • Entire process • Individual steps • Build and test a prototype • 5 consecutive days
  5. PHASES Source: Sprint by GV 1. Understand 2. Diverge 3.

    Converge 4. Prototype 5. Test 6. Analyze + 
 recommend 7. Iterate 0. Prepare
  6. PHASES 1. Understand 2. Diverge 3. Converge 4. Prototype 5.

    Test 6. Analyze + 
 recommend 7. Iterate 0. Prepare Design Sprint 2.0:
 Combine into Day 1
  7. WHY CONDUCT A DESIGN SPRINT? • Solve a big problem

    • Innovation • Efficient: One week or less instead of weeks-months
  8. TEAM OF 5-8 • Designer • Developer • Product manager

    • Marketer • Subject matter expert / stakeholder • Executive
  9. TEAM OF 5-8 • Decision maker 
 (ideally the product

    owner) • Facilitator • Facilitator ideally is not contributing any work / designs / decisions • Aka “neutral”
  10. SKILLS TO LEARN • Interviewing • Affinity mapping • Sketching

    • Prototyping • Usability testing • Synthesis
  11. SCENARIO • Less time: must be something all participants use

    or are target audience for • More time: start the Sprint with an “understand” or mapping activity • Ex. Pre-Mortem + group persona + expert interviews
  12. • 1 person ask questions (facilitator) and takes notes using

    post-it notes and black sharpie • Other person answers questions (participant) • Notes: document problems, successes • 1 note per post-it • Make a pile of notes • Note anything you think is valuable data • Think of this as a conversation, and the written questions as your guide • 4 minutes to chat • Wait for instructions on next step • Only the facilitator is asking questions • Facilitator tips: listen, don’t interrupt or help them finish, avoid leading questions
  13. AFFINITY MAP • Goal: share and synthesize research data •

    Determine what problem(s) you are trying to solve when designing your prototype
  14. AFFINITY MAP • One person reads off the text of

    a sticky • If anyone else has the same/similar note, combine • Go through all notes, grouping items into columns • Find the patterns / themes • Decision: what are you going to prototype
  15. WHY SKETCH • Brainstorms don’t work • Structured, facilitated activities

    much more effective • People are more effective in generating ideas solo
  16. CRAZY 8S • Think about one or more ideas you

    want to work on from the affinity map exercise • Sketch 8 ideas in 8 minutes • Use provided 8-ups • Pen, not pencil • 1 in each box • These sketches can be multiple steps • You can sketch multiple variations on one idea • No sketch needs to be perfect -- just enough to demonstrate a concept
  17. PRESENT YOUR SKETCHES • Divide into groups of 3 •

    1 person in group presents their 8 sketches at a time • 2 minutes to present • Others: listen (NO TALKING) take notes on post-it • 1 thought per post-it • Only write down ideas you like • Don’t share your critique yet
  18. CRITIQUE • One at a time, share what you liked

    about each of the other team members sketches • 1 minute per person
  19. CASE STUDY # Name of case study • 1 person

    in group presents their 8 sketches at a time • 3 minutes to present • Others: listen (NO TALKING) take notes on post-it • 1 thought per post-it • Only write down ideas you like • Don’t share your critique yet • One at a time, share what you liked about each of the other team members sketches • 1 minute per person Present Critique
  20. PROTOTYPE • Paper version of your interface • Prototype only

    what you need to test your idea • If mobile app as scanner: what will you be scanning? • One at a time, each person presents their top 2-3 ideas from sketching/critique • Goal is to learn • What works, what doesn’t, and why • Arrange your screens for the test
  21. COMPUTER INSTRUCTIONS • You are responsible for showing the user

    the screen • When the user points to something and says they would tap or swipe, change the screen
  22. NOTE TAKER INSTRUCTIONS Write down observations of the participant •

    Problems • Doesn’t understand • Frustrations • What they say • One note per post-it
  23. FACILITATOR INSTRUCTIONS • Your goal is to see if someone

    can use this [product/service], and if they understand • Don't ask for their opinions on the design 
 (if they offer opinions, that's fine) • Give a brief scenario / intro • Ask: what would you do here? • Request that they speak their thoughts aloud • You can ask follow up questions, probe why they do something or if they seem confused • They can point to the prototype and tell you they would tap there, you then change the prototype to the appropriate “screen" • React neutrally: try not to influence
  24. WRAP UP 1. Briefly describe: • What your product does

    • Something you learning from testing 2. Something you learned about design sprints
  25. LEARN MORE ABOUT DESIGN SPRINTS Jake Knapp/Google • GV Sprint

    • The Sprint Book • Intro videos • Design Sprint Kit • 5 design sprint questions I hear the most AJ & Smart • The Design Sprint 2.0: What is it and what does it look like? Richard Banfield
 For people who want more choices in how to conduct a design sprint, or want alternatives to the Google Ventures process
 • designsprintbook.com • Enterprise Design Sprints Remote design sprints • Running Global Virtual Design Sprints: Webinar Recap Affinity Mapping • The KJ-Technique: A Group Process for Establishing Priorities • Affinity Diagramming for Collaboratively Sorting UX Findings and Design Ideas • Gamestorming
  26. Jimmy Chandler
 
 DCUX 2019
 November 8, 2019 Learn How

    to Lead a Design Sprint…by Participating in a Design Sprint • Twitter @uxprinciples • https:// www.linkedin.com/in/ jimmychandler • [email protected]