The sprint is a five-day process for answering critical business questions through design, prototyping, and testing ideas with customers. Developed at GV, it’s a “greatest hits” of business strategy, innovation, behavior science, design thinking, and more packaged into a battle-tested process that any team can use. After reading Jake Knapps “Sprint: How to solve big problems and test new ideas in just five days”, I was inspired to use this methodology throughout my workflow. The huge success of the book across so many different industries such as to ‘access the viability of a new business, to make the first version of a mobile app, to improve products with millions of users, to define marketing strategies, to design reports for medical tests” p16. This method makes perfect sense to use, especially when approaching different industries who will have different needs, audiences and business goals.
He also references Lean Development, Design Thinking and Agile Processes.
The reasoning behind using the GV sprint method is that the sprints have been tested and refined for almost any task, any industry. Knapp lists three challenging sitations where sprints help:
- High Stakes – facing a big problem which will require alot of time and money
- Not enough time – up against a deadline, the sprint is built for speed
- Just Plain Stuck – Hard to start projects, booster rocket for ideas and problem solving (p27)
Points 2 and 3 apply to this project as time is a factor with 3 mini projects into one. The other issue is the goals required by the companies themselves, at this point I feel stuck in deciding. Hence why the sprints are set into weeks with a week either side to do industry research and testing.
The Monday – Friday breakdown will have to be rearranged and spread out slightly due to work commitments. However, I am using Teamweek to organise the sprints accordingly. A week for a sprint and a week either side to refine and get industry feedback.
An issue with the GV Sprint is that, like recommended, I do not have a team of 7 to complete this task, I did further research into solo sprints and the book does suggest you can work solo if you refine the process, however, the results will differ (p253). Knapp suggests a team of 7 (or fewer) including Finance expert, Marketing Expert, Customer Expert, Tech, logistics and design experts (p35). The article below details how an individual managed the GV process as a solo project.
Working together in a sprint, you can shortcut the endless-debate cycle and compress months of time into a single week. Instead of waiting to launch a minimal product to understand if an idea is any good, you’ll get clear data from a realistic prototype. The sprint gives you a superpower: You can fast-forward into the future to see your finished product and customer reactions, before making any expensive commitments.
Creating trello board for Google Design Sprint could be very useful in start ups and hackathons. Please check it out below’s link for trello board (Bhojak, 2019).
Bhojak, M. (2019). Trello Board for Google Design Sprint. [online] UX Collective. Available at: https://uxdesign.cc/trello-board-for-google-design-sprint-57b051bc60b7 [Accessed 1 Jun. 2019].