SchoolMint Enroll streamlines the student enrollment process for schools and families all across the United States. It provides an extensive set of features that allow schools to manage their enrollment efficiently and families to easily apply to the school programs of their choice.
The process of enrollment and school choice is cumbersome. Organizations with hundreds of schools have different needs than single site schools and existing platforms offer limited flexibility. Administrators often have to switch between several platforms to achieve their goals.
For families, the struggle is even greater. The lack of an intuitive platform that lets them navigate the school choice process and stay informed about deadlines, application statuses and events results in confusion and frustration.
Adding to this complexity, this initiative followed the merger of two legacy enrollment products. The challenge was not only to rebuild the experience, but to evaluate and consolidate the strongest capabilities from both platforms into a single, cohesive product. This required identifying the most effective features from each system, determining gaps and unmet user needs, and defining a roadmap that prioritized the most impactful additions.
I led the design, user experience & accessibility of SchoolMint Enroll from January 2020 to February 2026, including prototyping with AI tools and user testings.
In addition, I worked alongside Product Managers on strategy and discovery, while collaborating with engineering to deliver dozens of features.
As a Sr. member of the product team, I also collaborated with leadership, marketing, sales, onboarding and support teams on all major releases.
The v1.0 web app launched in July 2021 and we’ve consistently shipped improvements and new features (v3.2 as of February 2026).

The discovery and research phase is arguably the most important step in the process, during this phase we focused on the following goals:
We were fortunate to have access to enrollment admins from various organizations which were active users of our legacy enrollment products. This allowed us to gain a deep understanding of the intricacies and challenges involved in various stages of the process. We also engaged in weekly meetings with colleagues with diverse backgrounds. This group consisted of former school admins, implementation managers and sales professionals who regularly interact with current and potential clients.
In these collaborative sessions we created an environment that encouraged open dialogue and the sharing of ideas. The collective knowledge and experience within the team allowed us to gain valuable insights into our clients' requirements, leading to more tailored solutions.
___________
First-Principles Thinking: While working on the discovery phase it is important to understand the user's problems and goals. Then work on ways to improve the experience while keeping innovation in mind. Not merely improving existing processes but completely rethinking new intuitive ways to help users achieve their goals.
Based on all research, competitor analysis, and strengths and weaknesses of our legacy enrollment products, the team prioritized the following key features as the MLP “Minimum Lovable Product” for Enroll:

Flexible configuration options are key to meeting the diverse needs of districts, charter networks, and private schools across the country.
The requirements may vary from state to state also, creating an even bigger set of challenges in the enrollment process.
The following is a high-level summary of admin feature priorities for Enroll 1.0
Families need the most intuitive and consistent experience (across iOS, Android, Chrome) as possible to navigate school choice. They need to spend time thinking about what is best for their children and not how to use an enrollment product.

To make sure v1.0 accomplishes family needs, we prioritize the following items:

Clear status tracking and action steps on applications and registrations are essential for both families and admins. To make sure we provide the best experience we prioritized two essential features:
03 Design and Prototyping
This is where research and strategy begin to take shape. I want to highlight the importance of UX/UI design on any product. This is what the users see and interact with, all the research, strategy and backend work is not apparent to the user and they rarely think of many of those more time consuming steps in the process. What they do think about is how to easily go from A to B using the provided UI. The effectiveness of this is what creates a great user experience.
I created flows for each key feature mentioned above to help visualize the individual steps a user takes to complete tasks. This process is essential to think through all the different scenarios, edge cases, pain points, details, and turn them into testable items.
After identifying the UI requirements for each key feature I started with low and mid fidelity mockups to help define the visual direction. Of course product development is not a linear process, so at this stage we would go back and get more feedback and validation and make adjustments as needed without much effort before going to the design stage.
Based on SchoolMint’s predefined brand, which I created a couple of years earlier, I applied styles to the mockups, and began building a design system. Consistency and well defined UI elements are very important for UX. I also worked with a UX copywriter to find the best way possible to be clear and concise from small things like field labels and tooltips to bigger items like user guides. Once key feature designs were complete, I created prototypes and moved the product into its next stage.
Before testing it is important to set up objectives and usability test plans to help us measure results. To ensure effectiveness and usability, Enroll underwent alpha and beta testing phases.
Internal testings, including accessibility, were conducted by the product team to identify and address any major issues. We also were able to test family flows with colleagues that have school age children and have been through the School Choice enrollment process.
A group of schools admins, from big and small organizations, were selected to test the platform and provide feedback on its usability, performance, and features. We developed Beta sites where admins were able to test with their own data. This is, in my opinion, the most helpful type of testing for our products. We had biweekly sessions to give them assignments and get feedback from previous testings.
The team focused on addressing usability issues and enhancing configuration options based on user suggestions. Also, performance issues were found using big sets of data by our Beta testers. This clearly demonstrated the importance of testing in our process.

SchoolMint Enroll is currently serving more than 11 million students and 16,000 schools across the country. Over 1 million student applications and 17,000 lotteries are processed annually.
This has been an incredible experience for myself as I led UX and product design and worked closely with the team on discovery, strategy, testing and all other important steps in the product development process. We worked on this project using Agile with multiple scrum teams, two and three week sprints, then change to Kanban, lots of QA, regressions and more.
But it was not all perfect. As we balanced user needs with business goals and timelines, key trade-offs were made that shaped the scope of the MVP. Version 1.0 received mixed reviews as it was missing essential parts from the original road map, such as, conditional fields, document verifications or a more robust report builder. Users quickly raised concerns and only after the release of v2.0 in 2022 did Enroll begin receiving strong positive reviews and industry recognition.
Now, ongoing feedback and iteration cycles continue to refine and enhance the platform, ensuring it remains responsive to user needs and evolving requirements.
