The OneLern Connect revolutionizes school success management by empowering the S3 Lead to efficiently oversee School Success Specialists (S3s). Addressing manual tracking and decentralization challenges, the app offers real-time calendar access, geolocation tracking, journey step insights, document availability, instant notifications, and streamlined ticket management. Replacing Excel-based methods, it elevates oversight and data analysis. Scalable for team expansion, the app promotes collaboration, propelling improved educational outcomes.
Each member brought their unique skills and experience to the table, and we collaborated effectively to ensure the project's success. I am grateful for the opportunity to have worked alongside such a talented and dedicated team.
I played the role of a product designer throughout this design process. I oversaw and contributed to various crucial steps in the journey, ensuring the product's conceptualization and visual representation align with its intended user experience.
We conducted two rounds of in-depth user interviews to gain a comprehensive understanding of the needs, challenges, and expectations of key individuals within our user base. These interviews were instrumental in shaping our approach and guiding our design decisions.
The S3 lead faces challenges managing School Success Specialists (S3s) due to inefficient manual tracking methods, reliance on Excel sheets, communication difficulties within the existing management system, and the need to reduce costs associated with using multiple external applications. These issues contribute to inefficiencies, inaccuracies, and a lack of centralized coordination, ultimately impeding effective team management and hindering the expansion of S3s and schools by OneLern.
S3 Lead
After thorough data collection and analysis, we crafted a detailed persona representing the S3 Lead. This persona, named Kishan, embodies the characteristics, responsibilities, and challenges faced by a typical S3 Lead in the field.
The map was crafted to comprehensively capture the tasks and sub-actions undertaken by our S3 lead in completing their responsibilities, highlighting pain points encountered, and ultimately pinpointing opportunities for enhancement.
Following the completion of the user research phases, where we gained a deep understanding of our users' needs, challenges, behaviors, and goals, we developed a list of tasks for our application. We also created task flows for each task to ensure seamless usability and effectiveness.
After creating individual task flows, we integrated them into a comprehensive workflow that illustrates the entire application from start to finish.
We carefully crafted the application's information architecture, diligently planning each screen and its elements to ensure seamless navigation and intuitive user journeys. Our approach prioritized clarity and organization, ultimately enhancing user engagement and satisfaction.
During the project planning phase, we've set up Module Prioritization & Timelines by dividing modules with another product designer. This collaborative approach ensures effective coordination and progress as we work together. Following are the tools we have used to facilitate this collaboration:
In order to materialize our design concepts and ideas, we created pen and paper wireframes as a foundational step in our design process. These preliminary sketches served as a rapid and visual way to explore different layouts and arrangements of interface elements.
To crystallize our design vision and direction, we embarked on the creation of mood boards. This crucial step served as a visual exploration of aesthetics, themes, and emotions that we aim to evoke through our design.
We have developed new components and scaled our existing design system to incorporate them. After testing these components and variants, we have integrated them into our design system for use in UI creation.
After prioritizing the modules, we proceeded to work on our assigned modules and later integrated them into the complete product. In total, we developed over 140 screens for this product.
These prototypes serve as dynamic representations of the application's functionalities, enabling us to test and refine our design solutions before implementation.
This document serves as a structured guide to facilitate usability testing sessions with S3 Leads, allowing us to gain invaluable insights into their interactions with the application.
After conducting comprehensive usability testing with a diverse group of stakeholders, we have compiled a Usability Test Report that provides valuable insights into user interactions, perceptions, and the overall user experience.
Our design journey was marked by a series of iterative steps, each fueled by valuable user-centric feedback. This iterative approach ensured that we continuously refined our design, aligning it more closely with the needs and preferences of the S3 Lead users.
1. Notification icons not reflecting new notifications, S3s, schools, and
region counts not being highlighted, potential issues with displaying task counts in circles as they
grow, and the unclickable appearance of task count blocks.
Solutions:
2. Display the time gap between S3's previous and next school visits within a 40-day timeframe, and
include the previously completed task with its date in the task list.
Solutions:
3. Move sorting to filters, enhance S3 cards with location and previous tasks, and add numbered labels
to S3 names.
Solutions:
4. Show the location of S3, provide contact details for S3 lead, and ensure consistent use of task
status cards on the dashboard.
Solutions:
5. Provide task filtering, enhance task date identification, and resolve the issue of mixed status
cards.
Solutions:
6. Tasks should clearly show when they're overdue, include school logos on task cards, display the year
name, and indicate the days until a school visit.
Solutions:
7. Streamlining S3 assignment on this screen, simplifying school discovery for S3 leads, and
identifying schools lacking S3 support pose challenges.
Solutions:
8. The growing task count on tabs presents an issue by expanding the tab's size, and there's a need for
a streamlined method to identify task card statuses.
Solutions:
To initiate the handoff, we conducted a demo for the tech team on Microsoft Teams and gathered feedback. After approval, we created handoff documents (process, logic, notification, data requirements) in Word and Excel. Screens were transferred from Figma to Zeplin, and Figma access was granted to developers. User stories from the product manager were also validated before development began.
Following the completion of each module, developers conducted product demos. As product designers, we provided feedback on the development progress and assisted developers in resolving any uncertainties they encountered.
After resolving all development and design issues, the final product was launched and adopted by S3 leads. To validate our solution, we conducted Product Adoption Surveys and received a positive response.
This gallery showcases snapshots of our team at work, engaging in user research, design discussions, prototyping, and usability testing.