Context

In January 2019, the Head of Product gave to one of the squads the mission to improve the boarding process of users on Plurall. Since the year before, the product was trying to solve a series of issues, such as bugs and bad user experience, but tech constraints were blocking them to refactor the solution in a scalable way.

Problems

• The school admin was enrolled manually.
• There were three different methods for inviting users.
• The conversion rate was low in two of the three methods.
• The boarding flow was long and inconsistent.

Goals

• Automate the access for the first school admin user.
• Simplify the enrollment process.
• Increase the conversion rate of users in the enrollment funnel.

Methodology

Understanding that the problem was critical, we decided to run a Design Sprint, a methodology that uses generative and evaluative methods, to tackle the challenge. So, after a few weeks of planning and preparation, we gathered a multidisciplinary team (Developers, QA, Customer Success Analysts, Designers, Product Owner, and Product Manager) for four days so we could get to the end of the week with a prototype validated with real users.

As the methodology suggests, the four days were divided as follows:

Design Sprint 2.0

Process

Day 1: Mapping and Sketching

The first day was dedicated to framing the problem and sketching alternatives of solution.

Day 2: Decision and Storyboard