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

Sprint your way to a prototype, just like Google

Sprint your way to a prototype, just like Google

With this deck, Africa's first Google Development Expert Johann du Toit took the I|O Powwow meetup group in Cape Town through a condensed, hour-long version of Google's Design Sprint methodology. The talk provides a basic overview of how to use this highly regarded methodology to save time and money in designing and developing new products - whether digital or not - but always to solve real-world problems. And no real-world problem could have been more apt an example than the one chosen by Johann for the group to solve: Cape Town's current water crisis. Participants were divided into random groups to bring together people from different skills sets and then each group employed the #GoogleSprint methodology to hammer out fast and furious creative solutions to the problem. Within an hour the room was filled with drawings and notes packed with imagination, insight, humour, new questions and novel ideas which could be further developed to create a real app or other product to help the citizens of the city to save more water.

I|O or invited speakers

February 24, 2017
Tweet

Other Decks in Design

Transcript

  1. We will • Firstly build up some teams • What

    a Design Sprint is, and why Google created it • We will run a very quick sprint ourselves while being guided through the phases
  2. We will • Firstly build up some teams • What

    a Design Sprint is, and why Google created it • We will run a very quick sprint ourselves while being guided through the phases
  3. We will • Firstly build up some teams • What

    a Design Sprint is, and why Google created it • We will run a very quick sprint ourselves while being guided through the phases
  4. • Efficient Failure=Learn and move on • Flawed Success=RUN MORE

    SPRINTS • Epic Win=Move to Production The sprint ends with 3 results
  5. We will • Firstly build up some teams • What

    a Design Sprint is, and why Google created it • We will run a very quick sprint ourselves while being guided through the phases
  6. PROBLEM SOLVING Cape Town is in trouble, we need to

    save as much water as possible. Build a service/app/web app that would allow: • People to monitor their usage • View the current dam levels and how many days are left
  7. PROBLEM SOLVING Cape Town currently has 127 days left of

    water left, with the dam sitting at 25%. Residents are currently advised to save as much water as possible, and we have 3B water restrictions in place since 1 February 2017 until further notice. This means various rules are currently in place:
 
 https://goo.gl/Ue1YMC
  8. Day 1: Part One • User Interviews • Lightning Talks

    • Building user profiles • How Might We's • Affinity Mapping
  9. Users are the ultimate judges of whether a product is

    good or not and it can be useful to start a sprint by finding and interviewing users.
  10. HMW’S How Might We? Write with a thick dark sharpie.

    Be succinct. One idea per sticky note. Not too broad, and not too narrow. If you don’t write it down it can’t be voted on. Good Example: HMW Use location to show relevant results?
  11. Affinity mapping Start grouping ideas into categories. Don’t worry if

    the categories aren’t immediately apparent. Look for overlaps or duplicates to get started. Revise or change the categories to create the most useful mapping.
  12. Voting • Each team member gets 3 dots. • It’s

    ok to vote on your own. • It’s ok to put more than one dot on the same note • We’ll pay more attention to notes that have multiple votes, so think strategically • We are not trying to get to one direction at this point in time
  13. Day 2 • Reviewing existing solutions • Rough Sketching using

    Crazy 8’s • Voting on the parts of the sketches that work • Creating prototype designs that could be built
  14. Solution Sketch Select what you think is your best idea,

    and best execution of that idea. Sketch it out, you can do multiple frames as needed, use real words, use words and pictures to create a sketch that can communicate on its own. Add a memorable title.
  15. Day 3 • Review existing solutions • Voting on solution

    sketches • Story boarding the solutions
  16. Vote Vote Give each person 3 votes to place on

    the elements within the design they find most compelling. This will highlight parts of an idea
  17. Prototype Your Sprint is an attempt to identify the solution

    to a problem. Your prototype is a chance to see how good the ideas from your Decide phase are. To do this you have to make it real enough that you can get a realistic response from a potential user when you’re in the Validate phase.
  18. Paper is fine too prototypes give you more feedback, but

    for short 2 . Paper is just fine, just talking to someone. Ensure that the design is quite clear. Paper is fine too Interactive prototypes give you more feedback, but for short 2 days sprint. Paper is just fine, just talking to someone. Ensure that the design is quite clear.
  19. Day 5 • Validate with users under recorded session •

    Stream session to team to watch reactions
  20. ESSENTIAL Remember 1. Manufacture time pressure 2. Prototype as fast

    as possible 3. Quick research by talking to users first