Why prototyping?

We should see a website or a mobile application as complex machinery. When developing a digital product, a number of choices must be made, technological and artistic or ergonomic .

The digital is still a very young field that is evolving extremely rapidly. We are in the experimental phase.

Take for example the heroic days of early aviation : the first successful flight was preceded by hundreds of prototypes, most of which didn't take off more than a few feet from the ground:

Developing an app and running it without first being tested , is comparable to launching a brand new aircraft over a cliff : to see if it will fly.

An entrepreneur wishing to create an application, will put together a team of a product manager, and marketing specialists ... who will often call an external agency. A designer from the agency will then work on the application without having the direct relationship with the customer, without understanding of the business , without contact with the future users. In the end, a lot of time lost , endless round trips and frustration , both on the client side and that of the agency.

The Design Sprint aims to simplify all this, to bring together a multidisciplinary team around the same table and achieve in a few days a clickable prototype that will align all stakeholders around a common vision.

The prototype will allow you to project your future product and your team together around a common vision.

At the end of a sprint , it is possible that after testing, the prototype is considered good and that the development phase can begin.

If necessary  we will identify opportunities for improvement and a new Design Sprint can be scheduled. In the event that the prototype demonstrates that the product is not suitable and that the tests reveal it won't find its audience , it is better to stop here. You don't want to push forward and invest a fortune in an idea without a future .

Discover more about the return on investment (ROI) of a Design Sprint.