BUILT BY GIRLS Registration
The original registration for BUILT BY GIRLS was not just long, but also lacked any clear purpose for our users and our beloved brand voice was all but missing. On the backend, our matching algorithm craved better inputs to create better matches.
The overdue overhaul of the registration process provided not only UX improvements, but an updated branding, and improved data used for matching pairs — the main utility of the program. It was also the first end-to-end development done by the internal product team of 3, myself, a product manager, and a single engineer.
The Process
1. Identifying user and business pain points
As mentioned above, there were 3 key user pain points, and 2 key business pain points addressed in this project.
User Pain Points
Too long - users didn’t see an end in sight when it came to registration. It was multi-paged without any expectation setting of how much time they needed to invest to complete.
Lack of purpose - signing up for a mentorship experience should feel inspiring, but users often felt confused about what their information was being used for. They also didn’t get excited for the experience through the registration process.
Confusing questions - questions utilized for an old matching algorithm felt confusing to users who were confused about what the information was being used for and how best to answer to fit into the provided categories.
Business Pain Points
Poor quality of data - original questions were created without user validation, and therefore users often answered in inconsistent ways. For example, a dropdown that listed job roles but didn’t have a category to fit theres, or topics of interest in tech fields that students did know the definition (like UX!).
Limited data - our matching algorithm utilizes the power of overlapping words to create strong matches, and with limited data and a majority of fields using multiple choice many matches were often weak.
2. Validate new registration questions
The bedrock of this new registration would be an audit of existing question, then validation of any new questions. As an expert in survey methodology and our users, I first took the opportunity to eliminate any questions we knew were not useful to our community or the business. Next, through collaboration with my product manager we brainstormed new categories and questions we wanted to cover. A quick survey launched to members yielded over 200 responses that helped validate some of the following questions and question types.
Long Answer Personal Questions
Since our algorithm loved more words to find overlap, and our users love connecting on personal topics we tested a the following “fun” questions:
If you could visit any place in the world, where would you choose to go and why?
What’s your favorite personal possession and why?
If you had a talk show, who would your first guests be?
If you could pick up a certain skill instantly, what would it be?
What's your favorite book, tv show, or movie?
In end the we kept questions 1-3 and eliminated 4 and 5. Question 4 produced a lot (like A LOT) of answers around knowing foreign languages. Not great for creating unique and personal matches. Question 5 did not produce rich answers after evaluating the survey compared to 1-3.
Role and Career Interests
A large pillar of our program used to be to match students with professionals in careers they are hoping to explore. We found this limiting, and an analysis I did of “unlikely matches” (through interviews) found that with strong personal interests overlap, a mismatch in career interests actually produced a rich relationship. In order to keep some element of matching on career interests, I recategorized our roles options by first analyzing the job titles of our mentors and creating a new selection of roles based on data. With these more inclusion and representative roles we sorted them based on percent representation in our community into 3 equal categories. With a survey to students we validated shared interest in these 3 categories.
Technical Roles aka "Building Tech" (roles like engineering, product management, and data/analytics)
Creative Roles aka “Creative in Tech” (roles like content, design, UX/UI, and marketing)
Business of Tech aka “Business of Tech” (roles like sales, HR, operations, finance, and customer support)
Personal Interests
The last category of questions I’d like to talk about are some of which I’m the most proud. Through user interviews with matched pairs, I discovered that most matches found deep personal connection on shared interests outside of careers. I myself have helped mentees create apps around microaggressions and creating inclusive spaces for trans folks. Two causes I care deeply about. After asking the following two questions as open-ended questions, we categorized the answers to create an inclusive and representative set of answers that spoke to our users’ interests.
What are some social causes you care about?
Accessibility Activism, Animal rights, Civic Engagement, Criminal Justice Reform, Diversity in STEM, Domestic violence, Education, Elderly Advocacy, Environmentalism, Gender Equality/Feminism, Gun Violence, Healthcare, Immigration, Income inequality, International development, LGBTQIA+ Rights, Mental Health, Poverty, Racial Justice
Do you have any hobbies or activities you like to do outside of work?
Arts and Crafts, Athletics and Sports, Eating and Cooking, Entrepreneurship, Friends and Family, Gaming, Home Improvement and Decor, Movies, TV, Theater, Music, Outdoors and Adventure, Pets and Animals, Reading and Writing, STEM and Coding, Travel and Language, Volunteering
3. Improve and validate new UX/UI
Now that we had our questions and content for registration, it was time to tackle the tactical UX. Based on user pain points, I had the following goals:
Users can see and preview all of the questions without being overwhelmed
Users can return to complete their profiles
Questions are grouped into categories with an explanation of why and how we use them
Based on these requirements, I mocked up 3 different options:
After testing them with over 10 students and professionals in user interviews, the overwhelming preference was for Option A.
4. Layer in new branding
Luckily, a rebranding of BUILT BY GIRLS aligned perfectly with this project. Seizing the opportunity, I built on the new brand colors and design elements to create a beautiful and seamless UI, and after I conducted two additional rounds of usability testing I was also confident it would delight our users.
Hello, World!