Design Sprint at école Moser

Following a first collaboration, we were commissioned by École Moser to assist them in the design of a new digital tool. It is obviously not possible for us to communicate on the purpose of the tool, however we wish here to present the course of the Design Sprint week that we shared.

The team dedicated to Design Sprint is extremely important. With École Moser, we had the chance to work with really motivated and motivating professionals. The group was composed of teachers, administrative staff, IT staff and managers.

Having been able to gather as many different people was a real benefit for the Design Sprint.

The direction of Moser gave the project outline, while leaving freedom of creation to the Sprint team. During the first day, we set the long-term goal to keep it in mind throughout our design week.

Through collective and individual activities, we managed to map the project, establish the desired results and especially share the knowledge of each participant and explore opportunities from all angles. We had the momentary participation of external experts, including Me Capt (a recognized specialist in media and technology law).

The various exercises that make up this day allow, in addition to the aspects mentioned above, to create a group cohesion while allowing everyone to express themselves, verbalize and contribute to the definition of the problem, which has a very positive psychological impact on all participants.

During the second day, we guided the participants through the creative process. It was to analyze and study existing solutions and possible improvements in order to sketch ideas individually. The goal was to prepare the exhibition of ideas that will be analyzed and challenged during the day 3.

This kind of individual proposals can generate a lot of ideas without the participants drowning in endless debates. During this day, the goal is mainly about producing content, which will be analyzed and sorted out later.

Part of the group has, among other things, had the task of recruiting test users. This is important because it is these testers who will provide the first feedback during the day 5 tests.

The morning started smoothly with the visit of the sketches exhibition from the previous day. Through specially designed activities, we were able to criticize and vote on imagined solutions without ever having to debate.

This allowed the team to create the Storyboard of the imagined tool in a harmonious way by gathering the ideas of all (or at least voted by all). The Storyboard will serve as a base for the next day.

It was a decisive day ... all the participants particularly appreciated this day. It was at this point that the team realized the value of the work they were doing.

The 4th day is dedicated to the creation of the prototype of the tool imagined during the previous 3 days. A prototype consists of producing a product model that is relatively close to a finished product. Digital mockups can be easily made using software like Keynote, PowerPoint, Google Slides, InVision, Adobe XD or others.

The group divided the tasks according to their abilities and preferences. Some have formalized the script in writing, others have created the prototype using Google Slides or have created some content to make the prototype as realistic as possible.

A member of the team has been designated as the user testing manager. This person had the task of understanding the validation method, writing the interview and training by doing a first test of the prototype. It will be that person who will pass all user tests during the 5th and final day of the Sprint.

Intense day, but very exciting, because it really concretizes the work done so far.

The 5th and final day of this Sprint is dedicated to user testing. The use of the prototype created during day 4 makes it possible to directly test the new digital product with future users without the need to wait for the development of the MVP. This step is essential because it ensures the alignment between the expectations of the users and the tool imagined.

In the case where the user feedbacks are negative (which was not the case for the Moser school), the team can simply modify the prototype instead of the application itself. Therefore, the financial risks associated with poor design are considerably reduced.

During the day, the rest of the team observed the test progress remotely, which allowed them to analyze the results in real time and thus have the necessary information to define the next steps.

The main advantage (except for the prototype and the test results) of day 4 and 5 is that the team has all the necessary knowledge to repeat the days 4 and 5 in a loop until the imagined product fully meets the expectations of their users.

Finally, all the participants of the Design Sprint gathered for a round table to conclude this week of co-creation.

On a personal note, we are delighted with this Design Sprint at École Moser. The challenges were numerous, a good part of them were overcome thanks to the contributions of the members of the team as well as the direction of the school.

Some barriers have been identified. It's now time for the École Moser to imagine the solutions to overcome these issues, but we are confident that the Sprint team has all the keys in hand to do so.

We are looking forward to see the final version ready to start the development.

We sincerely thank École Moser for their trust and also congratulate the entire team who participated in this great Design Sprint.

You think that such workshop could boost your project?

Want to know more about the Design Sprint methodology?

Feel free to visit our dedicated page

or fill out the form below to request a meeting.