The Google sprint ideology to software development radically shifted the way we rolled out new updates to the the interfaces being designed for all new Chrysler vehicles. Their approach was radical for the automotive industry and produced results that were able to be tested in front of a maximum amount of users while maintaining a cohesive core of stake holder requests and user must haves.
What is A Google Design Sprint?
A sprint is a tenant of Agile development. Agile development; for those who don’t know, is the way software developers and savvy hipsters alike communicate to build the digital interfaces most of us take for granted…If they’re doing it right..
This process is how software advances. It’s how designers and stake holders and developers talk to each other to create the interfaces we all interact with. Google’s approach is to take an idea from brass tacks inception to a viable concept in a week. These concepts are further honed in weeks to come in consequent sprints that all come from the initial design.
Why A Google Design Sprint?
From the beginning of the design experience one starts with inspiration that could be conveyed either via print outs or white board sketches. At this point, you’re just collecting ideas that would be core must-haves.
Nice to have items and imagery that inspires new user features. At the genesis, of any sprint you’re trying to inspire innovation and knock loose any ideas that might be shoe-horned in and try to come up with the initial game plan for your project.
This may seem trivial, but ends up creating a quick list to work with when rapidly designing your user interface.
