Case Study: SearchASchool

Case Study: SearchASchool

Helping parents choose the best school for their family based on word of mouth recommendations

UX Design, UI Design | 3 week timeline

The Ask

Understand how parents decide where to send their children to school and create a digital product to help them simplify the school search process.

The Challenge

Understand how parents decide where to send their children to school and create a digital product to help them simplify the school search process.

The Solution

A hifi prototype of a school search and community app that helps parents personalize their search results to align with their location, budget, and educational approach preferences, and connect with fellow parents who can offer real life testimonials and support

Helping parents choose the best school for their family based on word of mouth recommendations

Helping parents choose the best school for their family based on word of mouth recommendations

UX Design, UI Design | 3 week timeline
(Flatiron School Project)

UX Design, UI Design | 3 week timeline
(Flatiron School Project)

The Ask

Understand how parents decide where to send their children to school and create a digital product to help them simplify the school search process.

Understand how parents decide where to send their children to school help simplify the school search process.

The Users

Parents of school age children between 3-17 who: 

  • live in the New York Metropolitan area

  • are tech savvy, busy professionals

  • are skeptical of reviews from strangers & marketing copy

The Challenge

Find a way for parents to access trustworthy word of mouth school recommendations from fellow parents.

The Solution

A HiFi prototype of a school search and community app that helps parents personalize their search results to align with their location, budget, and educational approach preferences, and connect with fellow parents who can offer real life testimonials and support.

The Solution

A hifi prototype that helps parents choose a school that aligns with their location, budget, and educational approach preferences, that also comes recommended by people they actually know in their community

Design Process & Agile Sprints

Design Process & Agile Sprint Timeline

Sprint 1
domain research
competitive analysis
user research
synthesis
feature prioritization
Sprint 2

rapid sketching

low/midFi prototyping

user flow diagramming

user testing & evaluation

Sprint 3

visual ideation

hiFi prototyping

wireframe annotation

stakeholder presentation

Competitive Analysis

I looked to competitors to compare features and establish industry standard for user expectations. All of the competitors:

Filters are necessary to customize results to suit family's constraints around location, budget, and teaching methods

Parents were lacking a comprehensive database including both private and public school information

Matching quizzes help parents begin their search from scratch

User Research

In order to further understand our audience, I conducted five 1:1, 60 minute interviews via Zoom.

Audience

Parents searching for schools

NYC residents

Parents of kids

between 3-17

Post interviews, I created an affinity diagram together to synthesize the insights pulled from each interview.

Key Participant Pain Points:

“It’s frustrating that there isn't one centralized and reliable database of information about schools”

“Talking to parents with children at the school was the most valuable resource”

“I wish there was somewhere to go to talk to parents with my same values instead of just reading reviews”

Resulting Insights: Parents don't trust marketing copy on school websites or reviews from strangers and rely heavily on word of mouth recommendations.


The actual problem to be solved is not a mere database of schools, but a community group that connects parents to share recommendations about each one.

Resulting Insights: The common denominator for most parents was that they don't trust marketing copy on school websites or strangers making school reviews, and therefore, they rely heavily on word of mouth from people they trust. Unfortunately, word of mouth isn’t always easy to come by if you don’t know anyone at the school you’re interested in.

The Ideation Process To MidFi

I rapid sketched a potential task flow that guides users to a space to talk with other parents.

User Opens App->User Signs Up->App Loads->User Skips Onboarding Screens (School Matching Quiz/Adv Search/Search For Parent Groups)->User Arrives At Dashboard

Default Home Screen With Search->Results->Filter Results->School Profile-> Parent Group

Default Home Screen With Search->Results->Filter Results->School Profile-> Parent Group

I streamlined the user journey from app launch to parent group with a user flow diagram.

Job: A new user needs to ask fellow parents about a school that they are considering for their child

I brought the user flow diagram into a mid fidelity prototype to validate the pathway in usability testing.

Validating MidFi Concepts With Usability Testing

The Participants

Parents of kids 3-17

NYC residents

Parents who have completed school search

I met with potential users in person, one on one and asked them to think through their process out loud as they completed the following task scenario:

“You are at home researching potential schools for your two year old. You need to find a school for under $20k a year within 20 minutes of your home, that other parents have a high opinion of. Use the product to research schools and ask another parent about their opinion of the school.”

“You are at home researching potential schools for your two year old. You need to find a school for under $20k a year within 20 minutes of your home, that other parents have a high opinion of. Use the product to research schools and ask another parent about their opinion of the school.”

What I learned from testing:

Key Insights:

"One parent group per school could get spammy and result in a ton of unwanted notifications"

"Separate sections for enrolled parents and prospective parents would help me find the right contact faster."

"It's redundant and busy for info I filtered for show up again on the results page. I know the age range of the school because I just filtered for it."

How I iterated based on user feedback:

I created subgroups for prospective parents and enrolled parents within each parent group to avoid cluttering the main feed.

I created subgroups for prospective parents and enrolled parents within each parent group to avoid cluttering the main feed.

I created subgroups for prospective parents and enrolled parents within each parent group to avoid cluttering the main feed.

I created subgroups for prospective parents and enrolled parents within each parent group to avoid cluttering the main feed.

I distilled the school preview stats to the essentials to ease eye strain and information overload.

I distilled the school preview stats to the essentials to ease eye strain and information overload.

I distilled the school preview stats to the essentials to ease eye strain and information overload.

I distilled the school preview stats to the essentials to ease eye strain and information overload.

Visual Ideation

During interviews, participants repeatedly communicated feelings of overwhelm, stress, and distrust which greatly informed the visual direction of the product.


  • I leaned into childhood nostalgia and academia for the header font and logo to inspire trust and a simple body font for legibility.


  • I opted for school bus yellow for its mood boosting brightness, green to echo vintage chalkboards and reliability, and red to establish authority.


  • I used abstract illustrations in the launch sequence so all families could relate and photos of schools to give an accurate preview.

HiFi Prototype Version 1

My first HiFi prototype takes the user all the way through their main objective, to meet and connect with other parents that can help support them in their school search decision making.

HiFi Prototype Iteration

Upon finishing my Flatiron program, I conducted an additional round of usability testing with 3 senior product designers and 1 frontend developer to validate the visual design choices I made.


I used the same task scenario as my first round of testing and asked them to think out loud not just about the task flow but the visual design choices as they navigated my hi fidelity prototype.


Key Insights:

"The use of cards is cluttered, hard to read, and distracting from the photo content"

"The red CTAs give the impression of an error message"

"It's hard to read group comments and figure out how to post comments"

I revised my color application (10% red, 30% yellow, 60% green) so that green was now the CTA color to imply action and movement to help users flow through the product and updated the logo and illustrations to align with new color application.

I removed the cards from the school result page and the group pages and utilized subtle dividers instead.

I decluttered the text under each school on the results page even further and enlarged the image so the user could let their eyes rest on the image of the school and click into the school profile if they needed more information.

I made the header font Work Sans in a heavier weight to provide appropriate hierarchy and limited my use of Arvo to the logo font only to make headings more legible and make the entire product feel more modern and current.

I removed the cards from the school result page and the group pages and utilized subtle dividers instead.

The Final HiFi Prototype