Case Study:

Better School Choice

The challenges of choosing an elementary school for your kids

Better School Choice wanted to create a product to help caregivers pick schools for their children. The product would also cater to schools wanting to advertise to their target demographics.

To start my research, I analyzed interviews with six parents talking about their school search experience.

6 interviewees had different research processes lasting from overnight to more than 5 yearsResearch methods were similar, starting with online first or word of mouth and ending with a school tour

These were my early insights listed by importance:

  • Caregivers started their search online and ended with an in-person tour of the school
  • Search time varied widely, ranging from overnight to several years

I also noticed that there was limited data coming from lower income households. How do I make this experience more accessible for people who don't have the time or financial means to conduct the research they feel is necessary to make an informed choice?

I conducted a competitive analysis to see what services were already available.

Competitive analysis table of key features showing competitors either had a good interface or comprehensive school information but not both

Each competitor had either an intuitive user interface or comprehensive school information, but never both. Together, they reveal a gap in the market where Better School Choice could make the biggest impact.

Streamlining features, reducing complexity

My goal was to engage users in the preliminary stages of their search with the intention of covering the entire research journey in future iterations. I conducted a feature prioritization exercise to determine what my MVP would require.

A feature prioritization matrix categorizing features into quick wins, big projects, fill ins, and time wastersA list of critical features such as search, comprehensive school info, search filters, school comparisons, etc.

In defining my MVP, I focused on streamlining the school search experience to make it more accessible for users.

Making school search more accessible

My early iterations were inspired by set and forget search preferences. The onboarding process allowed users to establish search presets, defining the baseline scope for searches each time the user opened the app. Users could customize their search further by selecting additional specifications to focus on.

Lo-fi mockup of the profile page showing how users are encouraged to set their school preferences

The onboarding flow included steps for the users to enter basic information and create a profile with their baseline preferences. These search presets included school types (public, private, charter, etc), price, class size, among other filters.

Diagram of the onboarding flow showing the steps from creating an account to setting school preferences

Once the preferences are set, users can access the search page at any point and it would update the results for them automatically depending on which factor they wanted to emphasize.

Examining Feedback

The usability test supported my hypothesis. While there was more work to be done to optimize the app, it seemed like I was on the right track.

Graphic of usability test results with over 60% success rate for both time on task and error success rates

A number of participants requested a feature to let them weigh baseline filters by importance.

I initially thought this feature would be a good way to give users more control over each search and began prototyping ideas for weighing search filters.

Sketch of a prototype for weighing search filters with togglesSketch of a prototype for weighing search filters with sliding scalesSketch of a prototype for weighing search filters with drag and dropSketch of a prototype for weighing search filters with checkboxes

But if more complex features were being used to increase the app's usability, then the search process was not being streamlined. I was on the wrong path.

I revisited my research and one quote from a parent stood out to me:

“In the beginning, one school was at the bottom in terms of price and location, because it was the furthest away from us. But the way the meeting went, I was just so amazed and impressed with the way they treated our boys”

I realized that the priorities of users will change over the course of their research journey. Because they weren’t fixed, the set and forget system would not be able to keep up. I had to pivot.

Streamlining the school selection process

I decided to rework the entire app from the lo-fi wireframes I started with. Throughout this project, I returned to the question: Would this decision simplify the experience?

Key changes

I streamlined the comparing schools flow by giving the compare feature its own page. The initial flow had too much bloat and moving the profile/accounts page to settings makes the overall app simpler and easier to navigate.

Diagram of user flow for the entire app before changes showing how users had to go through other pages to access the compare featureDiagram of the user flow after changes that streamlines the user flow significantly by making the comparison feature a main page

When I streamlined the user flow, I realized that I could apply the same principle with how information was presented. I focused on succinctly synthesizing data while designing the individual and school comparison pages. This would cater primarily to users who are beginning their journey by making information more scannable.

Lo-fi comparison page mockup with a side-by-side comparison styleHi-fi comparison page with a chip style comparison

I used the same information chunking concept on the individual school pages to keep the patterns consistent and reduce cognitive load.

Lo-fi school page mockup with information grouped into cardsHi-fi mockup with grouped information accessible through a drop down menu

Smaller changes

I separated filter and search features into two different pages to make it easier to find schools depending on what kind of searching users preferred

Lo-fi search page mockup with filters
Hi-fi search mockup with sort featureHi-fi filter mockup with drop down for filters

Next steps

I need to conduct two or more rounds of usability testing to get feedback on the new features and make adjustments before handoff.

Learnings

The concept of negative space is an important consideration when designing visually pleasing layouts as well as conducting research and getting feedback. I found that it is valuable to take a step back from the data, identify what is missing, and why those gaps exist.