How I use design sprints
Design sprints are a proven method for generating new ideas and identifying unmet user needs.
There are several pros and cons associated with this method, which is why I've customized it to better suit my work within product teams:
- Pro: Design sprints facilitate the collaboration of individuals from different departments, fostering collective thinking. This is a unique value that is often lacking otherwise.
- Con: Duration is a drawback. In day-to-day business, obtaining buy-in for a 5-day sprint can be challenging, and energy levels tend to wane quickly.
- Pro: The most valuable aspect of the format for me is researching the market using screenshots, enabling team members from all departments to gather insights from the broader landscape.
- Con: Design sprints often promote a greenfield approach, assuming a starting point from scratch. While this approach is suitable for exploring new business areas, it can be excessive when enhancing existing features.
- Con: A notable shortcoming is the lack of execution, which frequently results in unrealistic outcomes.
I prefer to condense design sprints into shorter durations, even as brief as 4-6 hours, and integrate them with execution, such as a 1-day hackathon. This approach ensures that ideas are not merely conceptualized but also tangibly pursued.