Google Sprint 411
We recently completed a Google Design Sprint for a SAAS technology company that I consult for and it was a very constructive experience.
Before we get into that, here’s the 411 on the Google Design Sprint Process:
- Week Before: Preparation, Team and Availability, Product Availability for User Feedback, User Studies, Identify key measures
- Week of:
- Monday – Mapping the challenge, reviewing your expert’s feedback, picking a target for the Sprint
- Tuesday – Solutions also known as the diverge phase as the team pours in the ideas in a structured process
- Wednesday – Converge, narrowing these ideas and creating storyboards to decide what to prototype
- Thursday – Prototyping and preparing for Friday’s Test
- Friday (and sometimes into the next week) – share the prototype with users for feedback
- Week After: Take everything you have learned and translate to product requirements and roadmap. Start your development. Set up the measures and tracking intervals.
Here are some other great resources for learning about the Design sprint process:
We had so many variations of things we thought we wanted to work on and this process really helped us focus on what matters.
Getting on the Same Page
Many times the Sprint Process is the first time an organization has been able to lay out all of their features and discuss how they may tackle them. Sure there Product idea funnels and Jira Stories till the cows come home, but does the organization have visibility. Better yet, are they aware of the scope and actively contributing to prioritization? Diverge and then Converge was a crucial part of the team activities.
Get Quality Feedback Before and After
User feedback is key, it can help to reduce the natural biases that the various organization groups bring into the process. Users/Customers are the ultimate decision maker.
Set Goals and Create Measurements
Be ultra clear about your goals and create relevant measurements, metrics and timelines, so you can really know what effect your new design produces.