Cut Your Design Sprint Time in Half
Traditionally, design sprints involve developers, designers, product managers, and other stakeholders coming together over the course of 5 days with the purpose of prototyping ideas, gathering insights on users, and validating them before building solutions with company resources. Like most start-ups, we are always extremely busy, and getting people to work for 5 days felt like a lot, even 2 days was a stretch for some so we decided to see if we could come up with a way to get the same results in a fraction of the time.
Cut Your Design Sprint Time in Half
Traditionally, design sprints involve developers, designers, product managers, and other stakeholders coming together over the course of 5 days with the purpose of prototyping ideas, gathering insights on users, and validating them before building solutions with company resources. Like most start-ups, we are always extremely busy, and getting people to work for 5 days felt like a lot, even 2 days was a stretch for some so we decided to see if we could come up with a way to get the same results in a fraction of the time.
What a design sprint CAN’T do (for enterprise teams)
The original design-sprint format popularized by the Google Ventures team has been interpreted by some as a one-size-fits-all model. This was never the intention, and it’s definitely not the case for enterprise-level projects.