The design sprint was a critical process in delivering the solution that allowed us to validate ideas, communicate effectively, prototype quickly, and test with real users. This five-day process helped us develop a complete prototype that was tested with real users to produce real data. The design sprint eliminates endless discussions and makes the product development process both fast and productive. After the sprint, the data can be analyzed ensuring a final decision can be made and the development process can begin.

The solution entails developing a B2B platform that boasts a simple and user-friendly UX/UI design, making it easy for recruiters to access their B2B dashboards and invite customers to utilize the tests. The product is tailored to meet the specific needs of recruiters and offers a range of tests and packages, including numerical reasoning and verbal analogies, customized for job seekers worldwide. B2B efficiently connects business organizations and their recruiters to potential job candidates, making it an ideal solution for those seeking talented employees.

Want to know more about the Design Sprint process?

Planning the sprint

Once Making Moves B.V proposed the business idea, it needed to be validated before being developed. The best way to organize our teams was to run our very own version of Google Venture's Design Sprint.

Our design sprint took place in Sarajevo over the course of three days and the other two days were executed remotely with the client back in their Amsterdam office. We combined the skills of developers, designers, and product owners. A facilitator was assigned to oversee the events of the design sprint.

Design Sprint Week

After welcoming Making Moves B.V in our office in Sarajevo and introducing the process, we began the design sprint.

The following schedule outlines the series of events that were followed during the five-day sprint:

Mapping Monday (In the Office)

• Welcome the Making Moves B.V team in our office space located in Sarajevo and explain the design sprint process.

• Conduct interviews with the client’s team and get to fully understand the business idea.

• Set up long-term goals and questions.

• Encourage each participant to create a map of users' experiences.

• Organize the "How Might We" (HMW) wall by categorizing the stickies into different themes and having each participant vote on a target.

• Choose a target to focus on for the following day of the sprint.

Tuesday Sketches (In Office)

• Organize the lightning demos to inspire the participants by evaluating a range of solutions. 

• Dive it up-Decide who will sketch which part of the map.

• Sketching & more sketching- Everyone takes the opportunity to sketch, conveying their solutions and idea.

• Planning out the recruitment of users for Friday's testing procedure.

Wednesday Decisions (In Office)

• Sticky decisions- Review, analyze, and discuss each presented solution.

• Note & Vote-Quickly gather ideas from the group and narrow them down to one final decision.

• Create a storyboard to plan the prototype.

Thursday Prototyping (Remote)

• Based on the storyboard, the team spent the day developing a realistic prototype.

• Share the prototype with the client's team and seek approval.

Friday Testing (Remote)

• Making Moves B.V organizes the testing process bringing real customers (HR recruiters and businesses) to the office in Amsterdam and having them test the web platform. The testing is video and audio recorded.

• The client measures, analyzes, and organizes the data presenting it to the RUBICON team.

• Both teams analyze the data and MVP product deciding what further steps to take.