We're using this design thinking mentality to run our sprints with clients. Visit our website to find out more.
“If I had an hour to solve a problem and my life depended on the solution, I would spend the first 55 minutes determining the proper question to ask… for once I know the proper question, I could solve the problem in less than five minutes.” - Einstein
What is a product design sprint?
A Product Design Sprint is a great way to tackle existing problems and launch new product ideas quickly and economically.
By applying a user centric approach over an intense period of time we are able to develop and validate ideas and solutions to problems much faster. This helps you learn quickly about the viability of an idea and make informed decisions on whether to invest in its development, or to instead focus your energy on something more impactful.
We take a human centered approach to our sprints, to ensure that whatever we create is designed with the user at the forefront. We take time to really learn about and understand the users as this allows us to develop solutions that address their needs.
Our Product Design Sprint methodology is based upon the design thinking and lean start-up approaches developed by the international design and innovation consulting firm Ideo, Google Ventures (for their Product Design Sprints), and the d.school Institute of Design at Stanford. We have built upon the great work that these teams have done, to create a methodology which is perfectly suited to our skills at Hanno, and the problems that our clients have brought to us to help them solve.
How does a Product Design Sprint benefit our clients?
By the end of a Product Design Sprint with Hanno, our client will have a validated prototype of a new or improved idea, product, or feature.
The best case scenario is that we are able to successfully validate the idea and assumptions, and set everything up so that the client is prepared to develop things further and work towards a fully functional product. Follow-up cycles of the Product Design Sprint will allow them to further develop things. It may take a few cycles to fully validate the idea, but the client should have a very good understanding by the end of the Product Design Sprint as to whether or not to commit more resources to the project.
But that subsequent development process doesn’t necessarily need to be done with Hanno. While many of our projects kick off with a Product Design Sprint and then morph into regular sprints conducted by the team, the Product Design Sprint can also work extremely well as a standalone process. Some clients come to us to ask for us to guide their team through their first Product Design Sprint, and then look to run the process by themselves next time around--and that’s perfectly okay with us!
And the worst case scenario at the end of a Product Design Sprint is that we learn that the idea doesn’t address a user need and that it would be better to kill it off early, or make a major pivot. That’s really not as bad as it sounds, because it avoids the waste of time and money building something that isn’t effective in fulfilling the needs of the user; and in the process of running the sprint and testing prototypes we learn a lot more about the product’s users and their motivations, which helps us to design better solutions. We may even discover something totally unexpected, which encourages us to pivot in a very different direction.
Regardless of the outcome, every Product Design Sprint will end with a validated hypothesis and clear learnings, and a significant step forward for the product’s design. We’ll end with a clear set of learnings, and a plan for where to head next.
- Do the hard work up front and the rest becomes easy.
- Show, don’t tell.
- The user is everything.
- Be inquisitive.
- Learn. Learn. Learn.
Chunks of content in this wiki are Creative Commons content, taken from the Stanford d.school site and learning resources.