My competitive analysis revealed important directions moving forward. I wanted to focus on product features that could get out the door quickly, and really test the lens of safety.
1) Refine the information architecture flow around the concept of safety.
2) Allow for customizable and transparent metrics that are easy to interpret.
3) Focus on public school only, since private school choice implicitly deals with safety.
From the qualitative research, I found that school safety was the #1 data priority of parents. Thus, I made an onboarding function for the app were I broke down safety into different categories, physical and mental. Once a user selects the metrics important to them, they will be able to see schools rated by their personal definition of safety.
From the qualitative research, I found that all parents valued classroom size and school distance. Thus, I highlighted this data on the school search dashboard.
I tested these concepts with 5 users.
The biggest find was discovering just how controversial the topic of safety could be. Everyone seemed to define safety differently. What was beneficial to one user was viewed as harmful to another user. While I refined the over-all concept, I made sure to give users more transparency and agency into how safety would be and could be measured in the app.
User testing relieved the very concept of school safety may be controversial, so I chose to lean into it, with the style of a serious cartoon.
It’s a school search app, based around the concept of safety. Why? A safe and supportive environment is a huge factor in student academics, but everyone defines safety in different ways. As a user, after you answer a few questions, Safe & Sound will help you find the safest school for your child to attend, designed around how you define safety.
For a user, it doesn’t matter what their politics are, how old their child is, or what part of the country they live in. Everyone values safety–just in different ways.
After onboarding, when users search for schools, they can see a personalized safety rating that means more to them, since they were part of it’s creation.
And of course, as they click through the safety rating, they’ll see data about education. But it will be through their lens of safety.
The key choices made on the app's dashboard all refer back to the initial stages of research. User's can see at a glance the student teacher ratio, the commute time (based on their transportation preference) and the safety score (based on how they define safety).
This is an MVP, designed to get the product out quickly. More features and data streams can be added later, making the app more robust. But the new features will be built UP, from the ground floor, THROUGH the lens of safety, which resonates with everyone, in one way or another.
This project was a mixture of new learnings and new frustrations for me. I thoroughly enjoyed the research methods. Creating the affinity diagram felt very familiar. In fact, it was almost exactly like pulling selects and structuring a scene for a documentary film, something a have tons of experience with. The survey I sent out proved to be useful, as well. However, I believe I relied too much on this quantitative method, in the end.
I probably leaned too heavily on the lens of safety. Yes, safety was important to my users, but in an effort be unique, I probably emphasized safety slightly above it's proper setting. Meaning, I would have liked to have more time designing the app and exploring the concept of safety beyond simply the onboarding phase. Also, I felt a little uncomfortable drilling down into a heated political topic like school safety.
I did learn some things in the project, however. Filter, sort, search, and mapping--all good, standard issue, UX techniques that I was exposed to in this project. I'm sure it won't be the last time I employ these techniques.