Day 5 - Test


To finish the Design Sprint, we will organize the ultimate test: neutral users will be invited to test our prototype. Based on the different target audiences (personas) that we have defined on the first day, we will select 5 testers to join us during the last day of the Sprint. Interviews are recorded and all the team will discover the results at once.

The tests take about 30 minutes per participant. Unlike some scientific practices performed by specialists of user research ( Eyetracking , AB testing , user panels ... ) our tests will be extremely simple and pragmatic.

We will put our testers in front of the prototype, in a real device and we will ask them to use the application . We will carefully observe their verbal and emotional reactions, "pain points," ergonomic problems ... We  will also question the purpose of the App: as potential users, would they use this product? how much would they pay for it? etc.

A few minutes of tests with non-biased users will often detect most of the bugs in the experience : remember, the prototype has no reason to be perfect, it must above all help you create the real product, and to avoid the pitfalls occurring in the creation of a new digital service.

 

What are the outcomes with a Design Sprint ?

Success!

By embarking on a Sprint, above all, what we want is users to love the application. If this proves to be the case at the end of Sprint, that is an ideal situation: you will have saved a lot of time developing your product and you will be able to build on the deliverables created.

The prototype will take the place of specifications and can be transmitted to developers who will know exactly what to make and will immediately understand your vision of the product. In this case, the benefit of the Sprint can be calculated in months.

Room for improvement

The prototype has confirmed interest in your product, but inconsistencies have been found during tests.

Good, now you know what direction to go. In such cases, either the problems that have been discovered can be solved naturally or a new Design Sprint can be launched a few weeks later. It is also likely that a new idea has appeared during the Sprint and be further developed.

Product Failure

The failure of the product during the tests does not mean the failure of Sprint : au contraire! An app that shows no interest in the outcome of Sprint, will not be developed. This is also in this case that the ROI of Design Sprint will be the most important: these few days have shown the product is irrelevant and stopped its development while there is still time. As stated by Ash Maurya (author of Running Lean) :

Life is too short to build something nobody wants.

In all cases

Design Sprint is a unique experience that will help you gather your team around a common vision of your future product. It is also a great introduction to the world of UX Design and User Centered Design. Do not waste time, it's time to organize your first Design Sprint.