Your new post is loading...
I would like to propose an alternative to Design Sprints : Cover Story.
This is not an official “Process” and it is not intend it to be so. This is an experiment to find the best way to facilitate early, fast discovery of problems and solutions. This is an experiment that might work well or fail miserably.
The Cover Story starts off as a design sprint, but progresses in a different manner. The idea is to get something functioning reviewed by the customer and to discover the true scope and direction of the feature.
I love the idea behind design sprints, but I dislike design sprints.
I love the fact that design sprints get people to iterate with the customer.
I love that people try to understand that they should be figuring out how to best satisfy the customer’s needs.
I hate the fact that most teams do it without the customer(s) being present.
I hate that, from a lean perspective, it is almost complete waste.
There is no value produced (I should say no value added to the product) at the end of whatever time period has been spent coming up with the best design. The part I love is the day 5 user validation piece, there is so much to gain from this. What I hate is that it is happening with a prototype. The whole experience for the user(not UI, but UX) could be very different when the feature is a part of the product.
A design Sprint can very easily set you on the path to a modernized waterfall. However you try to sell it, a Design Sprint is BUFD(Big Up Front Design). At the end of it there is no customer validated product, at best there is customer validated design. If it takes a long time to build the feature out, customer’s needs, design preferences or even the customer themselves can change. The eventual, integrated experience might be very different from the perceived design as well. If your process looks a bit like Joshua 스크람 Partogi’s diagram below, your Design Sprints might be setting you up for “A More Agile Waterfall”.