Margo Yoon is pixelated.

Orion's University CRM

Organizing Complex Family Relationships

Introduction

Orion's University was a growing social enterprise geared towards offering afterschool programs for students. Due to their growth, their sales teams needed a standardized system to organize and manage leads information. Already existing customer relationship management software was regarded too bulky for the needs of Orion's University. Also, because OU sales associates communicated with families, multiple relationships existed. Each relationship requiring documentation. A customized CRM system seemed to be the best solution for OU's needs.

My Role

I designed a customized CRM to improve sales operations for Orion's University. Utilizing their use case research, I created wireframes that suited the needs of the company. I was also responsible for the visual aesthetic of the platform and worked closely with the development team on the build.

Use Case

The need for a universal organizational system to collecting, recording, and sharing of contact leads for Orion's University
The system needs to represent the complexity of OU students' family relationships
Define the roles of adults in connection to students
Build a comprehensive system that information can be easily read and digested quickly

Family First

An important aspect to tackle while designing was the complicated nature of the students' family structures. My approach was to have the overview to be organized by families instead of individuals. At a glance, a user could then view the total amount of adults, students, their relationships and roles.
The app was built to have infinite scrolling so the user can look through as many of the contacts as quickly as possible. If one needed quick access to information, the search bar and filter are options fixed at the top of the page.

adding_contact

Adding a Family

When designing the adding and editing features of the CRM, it was important to put into consideration the ease of those actions for the user. Instead of a user clicking a button that would take them to a separate page to add a family, the "add family" feature inconspiciously slides out from the side of the page.

editing_contact
contact_notes

Card Edits

In continuity with ease of the app, the info can be edited by simple selection of a contact's respective card.

Card Notes

If there was any additional information on a contact, a simple click on the bottom-right area of the card would reveal any information.

adding_interaction

Adding an Interaction

Every interaction with the family needs to be recorded for the sales teams. To composed an interaction event, a user can directly select the Interactions section. When selected, the Interactions section expands to reveal a form to record the event in a efficient manner. Rather than a scrollbar, the user can read through a set of three events at a time.

Conclusion

While this project was quite a challenge, I learned a lot about how databases and sales operations function. Although having a customized CRM accomplishes only one area of sales management for the company, the creation of a standardized system designed for ease and quick comprehension will for certain increase productivity. Also, because of the design of the layout, it will improve sales associates understanding of their leads and their connections.
The next steps are to test the product with the sales teams, get feedback, and make any other adjustments or additions accordingly. In the future, a mobile application of the CRM for sales associates to use onsite would be a goal.