A particular company was in the initial stages of building a new software to solve the problem of improving collaboration between Claims Professionals at an Insurance Company, Attorneys of an Injured Claimant, Attorneys representing the Insurance Company, and Consultants who specialize in financial solutions for injured parties.
Because the problem was complex, we used a Design Sprint to tackle the first iteration of a low fidelity solution.
Preparation: We organized a 5 day design sprint where participants from across the US gathered in a *conference room. We brought in experts of all different personas, including video clips of interviews of Claims Professionals.
Design Sprint Week:
Day 1: We defined as a group the objective of what we were trying to solve. Provided time where experts presented their knowledge of the existing problem.
Day 2: We created journey maps to describe the problems. We went through the Design Sprint exercises to build rough sketches.
Day 3: We voted on ideas that we liked most and defined the direction we wanted to test out.
Day 4: We built out a prototype based on our sketches.
Day 5: We got feedback of the prototypes from our internal team. We then got user feedback from Consultants and Claims Pros of the prototypes through moderated usability studies.
Take aways: At the end of the 5 day Design Sprint, we had an initial wireframe of a direction. I met with the Project Manager and Project Owner to help identify what would be initially built. After finalizing the branding, we were able to build the MVP version of the software.
* Note since COVID hit, I’ve been running design sprints remotely using Mural with relative success.
