User tests

To finish the Design Sprint, we will organize the ultimate test: we will invite unbiased users to test our prototype. Based on the different target audiences (personas) that we have defined on the first day, we will select five testers to join us during the last day of the Sprint. We will record interviews, and the whole team will discover the results.

The tests can be performed either face-to-face or remotely via Skype, for example. Each session is recorded and can be live-streamed if required.

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

We will put our testers in front of the prototype, and ask them to perform a few simple tasks, without guiding them too much. We will carefully observe their verbal and emotional reactions, “pain points,” ergonomic problems. By asking open questions, we will allow testers to express themselves as much as possible and to bring their thoughts. It is often in this way that the most interesting insights appear.

We will also ask them about the purpose of the concept to validate its business model.  As potential users, would they want to use this product or service? How much would they pay to use it? How could it be improved? etc

Design Sprint Ltd. team film interviews to allow all team members to see detail reactions to the prototype.

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.

Watching tests and filling-in Scorecard

Whether live-streamed or replayed in the afternoon, the whole team watches the tests. Using a Scorecard (an evaluation grid), everyone evaluates the testers’ reactions and answers. We have created this tool to allow everyone to capture their learnings and annotate their results in an unbiased way.


✅✅ Success!

A massive success: sometimes, most of the hypotheses are validated, and the testers are enthusiastic about the concept. In this case, it is possible to imagine launching the execution phase directly (product development, strategy deployment, or service implementation).

This is the ideal situation: you will have saved a lot of time on the development, and you will be able to capitalize directly on the deliverables created.

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

✅❌ Prospects for improvement

Ups and downs: sometimes, our results grid after the tests will contain as much red as green. In this case, we will identify what worked and what we can build on. What the testers didn’t like will either have to be removed from the concept or re-worked.

The prototype will have confirmed the interest of your concept, but we might have detected some inconsistencies. This is good, because now you know which direction to go in. 

In such cases, we can either solve discovered problems, or we can run a new Design Sprint a few weeks later.

It is also likely that a new idea has appeared during the Sprint and be further developed.

❌❌ Concept failure

We were wrong: sometimes, testers invalidate the concept. Paradoxically, this is probably the most useful result. It’s a clear sign that you shouldn’t continue with the concept. It’s better to get bad news after 5 days than after two years of development.

At the end of a Design Sprint, either we win, or we learn (fast)

Failure of the concept does not mean failure of the Sprint: quite the contrary!  An idea that turns out to be of no interest after a Sprint will not be developed. It is, in this case, that the ROI of the Design Sprint will have been significant. These few days will have allowed us to invalidate the concept and to stop its development while there is still time. As Ash Maurya (the author of Running Lean) says:

Life’s 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 or concept. It is also a great introduction to the world of UX Design and User-Centered Design. Don’t waste time, it’s time to organize your Design Sprint.

Agenda - Day 5

Morning: Design Sprint Ltd. will run 5 user tests
14:00 The whole team gathers to watch the videos of the Tests.
Discuss the strengths and weaknesses of the prototyped solution.
Answering Sprint Questions, Planning Next Steps
Sprint review
17:30 end of Design Sprint! 🎉

The Design Sprint day by day


Design Sprint - Day 0


Design Sprint - Day 1


Design Sprint - Day 2

Design Sprint Day 3 decide


Design Sprint - Day 3

Design Sprint rapid prototyping


Design Sprint - Day 4

Download a PDF proposal for a Design Sprint workshop

Please fill in this short form 👇

Wanna work with us?

If you have questions about the Design Sprint and how to integrate it into your company, contact Steph Cruchon, our lead UX Designer via or book a chat call.

Chat with Steph