You are developing a new product. You validated that your idea meets the needs of your users, for example by means of a Design Sprint. But is it also technically feasible? And how complex are the desired functions? We will investigate this during a Prototyping Sprint. The development process of the prototype gives you the first insight into the technical possibilities and costs. A proven approach with which we validated new ideas with companies such as Mentos, Medkit and Sita.
When do I need a prototype?
A prototype is an ideal tool to investigate the feasibility or your idea and to convince colleagues, investors or stakeholders. With a relatively small investment you convert your idea into a working product. At the end of this sprint you will have a better understanding of the size of your project:
How complex are the desired functions?
Which technical choices do you have to make?
How much time does it take to translate the prototype into a working product?
How does a Prototyping Sprint work?
We turn your idea into a (technical) prototype. We will go through the following steps:
During the kick-off we discuss your plan and determine the scope of the prototype: which functions are a must and what can be moved to the wish list? Of course, we will give lots of input. We come up with smart solutions that we can develop quickly.
Then we build your prototype. We will keep in touch about the progress so that you can make adjustments if necessary.
At the end of the week, we present our work to you and your team
What happens after the Prototyping Sprint?
At the end of the week, we collected lots of insights. The next step can go in three directions.
Your product appears to be technically feasible, but there is another technical solution direction that you want to test. In that case we continue with a second validation round during an Iteration Sprint.
The second option is that your idea has been positively validated with users, for example during a Design Sprint, and we know at the end of the Prototyping Sprint that it is also technically feasible. In that case we will make a plan for the development phase. We discuss what your team should look like and estimate how many sprints you need until the launch. This way you have all the input to convince your stakeholders of your idea. Have you received the approval? Then our team is ready to develop your product!
It may also happen that the outcome of the Prototyping Sprint is that the chosen technical solution is not feasible or too complex. We are testing of course. In that case, we can test a second technical approach or it is time to go back to the drawing board first.
I've already done a Design Sprint, is this still necessary?
If you have already completed a Design Sprint, then you have a design prototype as the result. A prototyping tool such as Invision allows users to click around the design. With the Prototyping Sprint we are taking the next step. We are investigating whether the technical assumptions in the prototype are feasible. For example, we make a real (test) link with the back-end services or read real (test) data. This is how we validate the technical feasibility of your idea.
Why a Prototyping Sprint with De Voorhoede?
By testing the technical feasibility early, you can determine with more certainty whether you want to invest in the development of your product.
From our team of 15 developers, the right experts connect, for example about AI, privacy, SEO or data visualisation.
We are ready to continue developing your product quickly and seamlessly. Your entire development team is already up to speed through this exploration.