The necessary material for the sprint must have been prepared beforehand (post-it notes, boards, markers,...)

A sprint master and a decision maker should be appointed among the participants to orchestrate the sprint.

The first step of the Sprint Design is the understanding phase.
After having gathered all the participants to this sprint, they will answer different questions about the project as an introduction:
- What is the context of the project? A reflection on the customer account.
- What is the project's problem? 
- What is the main objective of the project? There are 3 objectives: increase the number of accounts created, orders connected, migration connected
- What are the expected benefits?
- Who is the target?
- What is the technical environment of the project?
- Are there any particular constraints?

Then they need to define the long-term objective to keep it in mind throughout the sprint (it can be written at the top of the whiteboard for example).

To help define this objective, an interesting exercise can be set up: The idea is to imagine a year after the start of the project that ends in a huge failure, what would be the causes?

Then the team will be asked to sketch the experience map of the future solution by drawing a diagram. Then the team will have to define the keys to success of the project. Finally, the team will have to benchmark the project as future inspiration for the rest of the sprint.

At this stage of the design sprint, it would be interesting for the progress of the project if the team could take stock of everything that has been produced so far so that they can better refocus on the project.

The next step will be the last step of the understanding phase and will have as objective to focus on the user.
The idea is to interview the users who will use the service.

We will therefore start by setting up an interview grid centered around different points (but it is important to leave some freedom for the team to create this grid). Here are some interesting elements to include in this grid:
- Introductory questions to identify the user in front of you
- Questions related to the user's needs.
- Questions about the user's use of the service (recurrence, fears, barriers, the ideal experience he/she would like to have, etc.)

After completing this grid, we need to interview the users.
Ideally, two people are needed to conduct an interview (a speaker who asks the questions and a "scribe" who transcribes everything into writing). The idea is to ask open-ended questions and to bounce as much as possible off the interviewee's answers.
After having conducted the interviews, a formalization work is necessary to continue.

This work will be done through an analysis grid that will allow the team to detect trends within the users.

Now the team can enter the second phase of the Sprint Design with the Divergence Phase.
The objective of this phase is to open as many doors as possible without setting barriers to be as creative as possible.

The idea here is to alternate between phases of divergence (where the team is led to open up to generate ideas) and phases of convergence (where the team is led to refocus on the ideas produced).

Several exercises will be set up for this phase.
First the flash presentation can open doors (the idea is that each team member prepares a 3 minutes presentation to present an idea related to the project).
Then the Crazy 8s exercise will allow the team to produce a large number of ideas in a short time. The idea is that each person will take a sheet of paper with a grid of 8s and write 8 ideas on it in 10 minutes. Then each person will give his or her ideas back to the whole team.

These exercises will lead the team to come up with an outline of the solution.
Their job now is to create a story board to present their solution to the project.

The idea here is to get the team to converge on a common idea in order to continue in the sprint.

This phase will start with a review of all the work done so far
Then we will have to integrate the scenarios imagined by the team to integrate them into the experience map created at the beginning of the sprint.

Then the team will move on to phase 4, the prototyping phase.
The idea here is to design a product that is as functional as possible in order to be able to test it with users using tools such as the Marvel App

Once the prototyping is done, phase 5 can begin.
It is about testing the solution to see if it suits the users.
Before going to do the tests, it is important to prepare them first.
First you have to recruit the testers, then prepare the interview guide (which defines the context of the test, the execution conditions, the scenarios and the tasks to be performed by the tester)
During the test, you need a person who will assist the user in case of blockage or misunderstanding and an observer who will transcribe the interview

At the end of the test session, the solution prototype can be modified to reach a more relevant V2 of the solution.

The last step of the Sprint Design is the Restitution of the team's work.
This feedback is done in 2 steps:
The analysis of the lessons learned from all the work done
The Pitch of restitution which will be used as report for the Sprint.