In the past, product ideas were often implemented without prior testing, as time was short and investors were easy to find. First experiences with the application could only be made after the launch. This traditional approach involves a high risk, as many improvements affect the development of the code and can therefore only be applied with great effort and cost. The design sprint solves this problem and offers an abbreviation: with the help of fast prototypes and user tests it can be proven whether an idea reaches the customer – without the product having already been implemented at this point in time.
First of all, the business idea is analysed both technically and economically. Then the target groups, the performance bound, the success criteria and the competitors are defined.
In a second phase, various solution approaches for the application are collected and evaluated.
The best solutions are combined and it is determined how the prototype should look and function.
The agreed prototype is implemented. Code is not developed, but only clickable graphics are used. This «dummy» is now presented to potential customers so that they can check the usability and other aspects of the idea.
The user tests give a well-founded first impression of the application: How do end customers react to the use? Do they like the solution? In this last phase, the first important improvements and adjustments to the product can be made.
The effort for the development of a web application is high, so it is all the more important to test a vision for its feasibility, efficiency, economy and user-friendliness. The design sprint is an approach that has been used by large companies for a long time. A prototype of the vision is created without programming and presented to potential customers for testing and feedback. Numerous learnings are collected before the actual development of the product has begun.
Interesting blog posts about Prototyping: