What Google learned from their research is similar to what developed within IDEO over the course of 30 years where trust, purpose, and impact have evolved to become central to IDEO’s culture. There’s a focus on establishing trust and building relationships by designing intentional moments, which we call rituals. For example, IDEO’s weekly tea time ritual was designed as a way to encourage collaboration and “casual collisions”—a time when people step away from what they’re working on and connect with each other. Small, consistent moments like tea time are a prime way to deepen relationships and trust over time.
Day 3 sees us kick off prototyping, and we do this pretty much exactly as stated in the book, so nothing new to report here. It’s noise-cancelling-headphones-on mode for our resident Prototyper, and we’ll have a couple of huddles throughout the day to make sure we’re all on track. We’ll also update the client at the end of the day to keep them involved and show them what we’ve been doing throughout the day.
“Design Sprints proved to be a valuable tool for accelerating our early-stage, service-driven innovation initiatives. The Design Sprint School team and approach have been instrumental in helping us create the environment and the internal capacity to run our Service Design Sprints for internal Ventures and for running Co-innovation at our Cisco Innovation Centers around the world” https://www.tatvasoft.com/blog/wp-content/uploads/2015/12/feature_driven_development.jpg
Learn fast, fail fast. The sprint helps to obtain a clear vision of the goals upfront. It forces you to make critical decisions and solve complex problems fast. This means that you and your team can save months of design, engineering and development costs. The bonus? You’ll be able to get your product to market faster because you focussed on the right thing.