There are many reasons to do a design sprint: you have a complex issue that needs solving; a particular project has stalled and is in analysis gridlock; or maybe you’re bored and can’t think of anything else to do. Whatever your reason, a design spring is a very quick way to develop ideas around a particular issue to solve.
“Great! Does that mean I can sprint a solution on how to make a ham sandwich?”
Well, no. Design sprints are meant for complex issues that require abstract thinking. There are some guidelines on what you can do a design sprint on.
Impact: Design sprints are usually done to solve medium or high impact problems where there’s usually higher risk.
Complexity: The sprint is meant to breakdown complexity and help define what the needs of the collective are. This also means that there is potential for many groups with differing opinions are likely involved.
No Idea: A sprint is more effective when there is no idea of a solution. You might have parts but if you have an idea with a reasonable probability of success, then you don’t need a sprint. Sprint generate new ideas, learnings, perceptions, and insights.
References
Knapp, J., Kowitz, B., Zeratsky, J. (2016). Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days. Simon and Schuster. doi:1501121774, 9781501121777
Recent Comments