Stop! Collaborate & Strategize: Part 4
0 likes269 views
This document provides an overview of design sprints, which are a five-phase framework that helps teams answer key product questions through collaboration, rapid prototyping and user testing. The phases are understand, sketch, decide, prototype and validate. Design sprints allow teams to reach goals quickly, encourage user-centered thinking and faster product launches. Research findings can be turned into a sprint challenge to action results. Activities include lightning talks, user sessions, how might we brainstorming, crazy 8 sketching, dot voting and prototype testing.
Stop! Collaborate & Strategize: Part 4
- 1. STOP! COLLABORATE & STRATEGIZE Craig Spencer Part 4: Design Sprints UXPA 2017 TORONTO
- 2. DESIGN SPRINTs▪ XFN in nature ▪ Great for actioning research
- 3. My journey with sprints ▪ I had been part of sprint’s prior to joining Google. Some were successful some not so. ▪ Completed the Google Sprint Master Training, based on the Google framework. ▪ Sprints have been a very valuable tool to getting research findings actioned.
- 4. Where did Sprints come from? ▪ The Google Design Sprint framework was created in 2010. ▪ The methodology has evolved over time and continues to be refined and tested. Remember it’s a framework, it’s up to you to apply it sensibly to your challenge.
- 5. Introduction to Design Sprints ▪ A design sprint is a five-phase framework that helps answer key product/design questions through teamwork, rapid prototyping and user testing. ▪ Sprints let your team reach clearly defined goals and deliverables and gain key learnings, quickly. ▪ The process helps spark innovation, encourage user-centered thinking, align your team under a shared vision, and get you to product launch faster. WIN!
- 6. Design Sprint process Understand PrototypeSketch Decide Validate
- 7. What is involved at each stage? ▪ Understand - create a shared understanding of the problem ▪ Sketch - think and sketch ideas ▪ Decide - as a team what should we prototype ▪ Prototype - build what you need to validate your ideas ▪ Validate - feedaback from users Typically sprints are 2,3, or 5 days in length. As your team gains experience and is used to sprinting often you can reduce the time needed.
- 8. Why are design sprints useful to researchers? ▪ Action your findings - you convert the research findings into a “Sprint Challenge” and have the team work on this. ▪ Steer the product - by it’s nature the sprint will be heavily rooted on your research, and will reference research throughout. ▪ Get XFN team to work together - utilising the whole team to action the research is very powerful, and will result in a practical way forward. ▪ Use when the answer is not clear, where it will take consensus to move forwards, and the problem is medium-large.
- 9. Constructing a Sprint Challenge Clarity is important : ▪ It needs to contain the timeframe e.g. in the next year, in the next quarter. ▪ It needs to contain the channel/platform e.g. Mobile App, Website. ▪ It needs to be clear & understood by the team. ▪ This is where we can rephrase a user need as a sprint challenge
- 10. Activity time As a team, construct a sprint challenge based on the user needs mapping you have conducted ▪ Timeframe, channel, clarity 5 mins
- 11. Pre Sprint A lot of the Sprint Master’s role is about organising the sprint and ensuring it is setup for success. ▪ Decide who should attend the sprint (Eng, PM, UX, Mkting) ▪ Who should give lightning talks? ▪ Create a pre-read list of materials sprinters need to consume (especially your research) ▪ Set the sprint challenge & set expectations / deliverables. ▪ See here for planning advice
- 12. Understand Phase Lightning Talks : Bring in speakers who can illuminate the topic, have important perspectives to be considered. This is where you need to utilise your research. User sessions : Bring in users to illuminate your research. How Might We’s : As the talks are happening get your sprint team to create HMW, and cluster them after the lightning talks are over. Understand PrototypeSketch Decide Validate
- 13. Understand Phase What does a How Might We look like? We then share & cluster HMW’s to highlight areas of opportunity. How Might We Make finding out about what is on at the UXPA conference super simple
- 14. Sketch Crazy 8’s : Crazy 8’s is a core sprint method. It’s a fast sketching exercise that challenges people to sketch 8 ideas in 8 minutes (not 8 variations of 1 idea or 8 steps of 1 idea, but 8 distinct ideas). May also require storyboarding Voting : After everyone has finished the Crazy 8’s exercise, it’s time for each team member to share the ideas they have generated and discuss with the group. Understand PrototypeSketch Decide Validate
- 15. Activity time Create 8 individual ideas, that will help answer your sprint challenge 10 mins
- 16. Share your crazy 8’s with your team Sharing : take your teammates through your ideas. 2 mins per person
- 17. Dot vote Individually dot vote on the 3 most compelling ideas by voting on the specific sketches (not the entire paper). 5 mins
- 18. Decide Decision matrix : If the team can’t come to a clear consensus after Dot Voting, you can use a Decision Matrix. The matrix is a simple table or diagram that helps the team judge all the ideas based on a set of criteria that is most useful for the goals of the sprint. Feasability Impacttotheuser Understand PrototypeSketch Decide Validate
- 19. Prototype & test Prototype : You are building just the minimum of what you need to make the prototype real enough to take into testing with users. Validate : Watching your users try out the prototype is the best way to discover major issues with your design, which in turn lets you start iterating immediately. Understand PrototypeSketch Decide Validate
- 20. Recap Understand PrototypeSketch Decide Validate Crazy 8’s Dot votingUser needs mapping
- 21. Resources ▪ Google Design Sprint KIT which includes case studies ▪ Google ventures Design Sprint
- 22. End of part Contact: craigwspencer@googlemail.com 4