Challenge: Lido Labs conducts numerous in-person training and certification classes monthly, where students can purchase subscriptions for their digital training product. However, due to state insurance mandates, these transactions necessitate the use of paper applications, which must be filled out, collected, and manually processed. This traditional approach has led to various challenges, including difficulties in tracking, high data entry costs, and management inefficiencies. To address these issues, it's essential to implement a system that allows students enrolling in the digital training product during classes to be seamlessly subscribed, while also providing a platform for effective management, collaboration, and reporting of all student subscriptions derived from in-person sessions. Moreover, it's important to integrate this solution with the existing framework used by classroom trainers for both Lido Labs and the partner organization, who are already accustomed to entering class information and managing subscriptions through their training portal, to ensure a cohesive and efficient flow.

Opportunity: Build a new portal (web app) that will maintain familiarity and ease of use for classroom trainers, while simultaneously allowing Lido Labs to enter, manage, and report on subscription information for in-person student applications. This new tool will be designed to process, manage, track, and matriculate new students into the existing subscription enrollment engine.  In doing so, we would provide:

• Trainer classroom data entry: Trainers can enter their class information so that we can track and measure performance, and make strategic training decisions regarding future class events

• Digital application repository: Trainers will scan their class applications which we will store and retrieve at will applications for processing and review. 

• Application recovery: All recovery processes for incomplete applications will lead to this portal via application retrieval, alerts, and status. 

• Student subscriptions: Data entry personnel will subscribe users via the producer path so that automated processes will enroll the students in both CCU and FLP. 

• Commission tracking: Trainers and admins will be able to review classroom information (as it pertains to the trainer) to determine subscription history and payouts

• Trainer Login: This portal will serve as a place for trainers to receive communication and other information from CC/FLP

Product Strategy: We knew immediately that our stakeholders would fall into three camps, Lido internal, external (customers), and partners. A dual API integration would be necessary (internal/partner) and a refactor of the existing process/product to work with the new processor. 

Requirements were gathered, milestones determined, and critical path issues prioritized. From there, mockups were created, and we worked with UX to design a web app from the ground up with these unique requirements, detailing the user workflow via diagrams, and multiple iterations in design and UX. User stories were written for both front-end and back-end API work. We refactored the existing internal product to minimize the user interaction on the front-end and added new API endpoints to process the subscription and connect to the new portal. We built the new portal and connected the Lido processes, then completed the external API integration with the partner. 

Results: Due to the efficiency gained, overall subscriptions from this channel increased 15%, the need for manual data entry and commission tracking was reduced by 90%, and data flowed bi-directionally due to the integration so tracking vastly improved, reducing lost applications by 99%. Both companies were now compliant given that the physical storage of customer PII could be destroyed. Trainers and event admins now had access to data and reporting of their efforts, further reducing the need to contact management.