At Paidy, we wanted to focus on the next big project that we had in the pipe and before any requirements or decisions were to be made we needed to do research.
This was the perfect time to suggest doing the Google Design Sprint.
This was the first Google design sprint for the company and having done the design sprint before at my previous company, I volunteered to be the facilitator and organizer for the sprint.
The design sprint book recommends that only 7 people participated but our sprint consisted of 13 people from various departments including the Founder, CEO, Product, Engineering, Design, Risk, Marketing and Sales. Making sure that everyone was free during these 5 days took a lot of negotiating and planning.
Also having more people meant that the allocated time for each of the activities needed to be recalculated and the schedule would need to change to accommodate for everyone.
Another problem we were facing was the goal for the project was not decided. Without having a big goal to test meant that the project could be swayed into many different ways. Facing this issue, I contacted Jake Knapp and John Zeratsy who were 2 of 3 Authors of the Google Ventures Design Sprint book for some help and advice.
How ever the biggest problem we were facing was that some members in the design sprint felt that we should use a proper testing agency to conduct the tests which meant that our day 4 and day 5 would be over 2 - 3 weeks long.
Setting a Long Term Goal
Defining Sprint Questions
How Might We’s
Creating a Map
Divide And Conquer
Given that we decided to use an agency for the testing, we had about a week to create our prototype. As a minimum requirement we created an invision clickable prototype as a back up but at the same time we utilized our iOS developer skills to create a real working prototype on an iPhone to simulate our idea.