Learn to Win
Product Overview
Traditionally, athletic teams have their plays in a physical binder, meaning limited modes of studying and untraceable learning progress. Learn to Win saw this gap and created an incredible micro-learning tool that is the epitome of teaching re-envisioned. The platform offers customized, engaging and interactive micro-learning lessons and quizzes delivered directly to athletes. Instructors can use the web application to rapidly create content and instantly collect learning data to understand knowledge gaps. For athletics, this platform revamped the traditional way of teaching and unleashed unlimited opportunities for teams.
Key Metrics
Team designed and built two web apps and one mobile app in 6 months
Within two years of my involvement through Hyperspace Ventures, Learn to Win went from ideation to being a multi-million company
Partnered with 5 collegiate and professional athletic teams within 3 months
My Role as Learn to Win’s Product Manager
Learn to Win (L2W) is one of the fastest growing digital software that I have worked with: within 1.5 years of my involvement, it was valued as a multi-million venture. It was incredibly exciting to work directly with the founders from the development phase to its MVP release and post MVP rapid enhancements. I led a team of four engineers and designers who were in the U.S. and India to deliver L2W’s product suite:
Mobile application for athletes to learn on the go
Web application for coaches to develop lesson plans, quizzes and plays
Web application for L2W’s management
During my involvement, I was in touch with the founders on a daily basis to discuss product features. I collected product feedbacks and translated business goals into product features for our product team. I facilitated the product vision by developing detailed user stories, technical targets, setting work breakdown structures and prioritized the development pipeline. To maximize efficiency, I created wireframes on Figma to confirm new features and UX enhancements to all stakeholders before handing over clear OKRs to our design team. I also led the intensive quality assessment efforts prior to MVP and feature launch, where I debugged and reported issues to our development team.
With its rapid expansion and VC demands in 2019, L2W’s management decided to transition to building their in-house engineering team. With this, I established detailed hand-over documentation (user stories, readme files, github, branches explanation, etc.) and held briefings with their new internal engineering department to ensure a smooth transition.
Key Takeaway
Always, always, always build products with sustainability and expansion in mind.
L2W was the fastest growing product from my early Product Management career, it instilled in me the importance of product scalability and sustainability.
A few months into MVP release, L2W had a number of major teams, such as UMich Football and Under Armour All-America Games active on the platform. It was incredibly thrilling for a sports fan like myself but I was soon stressed out by the constant unpredictable app downtimes. I worked with my team night and day to understand the situation and found out we were storing user uploaded content to AWS EBS (block storage) instead of AWS S3 (scalable storage). This means that our applications would be unavailable as soon as EBS is maxed out and the quickest solution would be to add additional EBS storage when we are close to the limit. However, it’s almost impossible for us to constantly monitor available storage level and considering L2W is a content heavy platform, I soon realized we needed a better plan moving forward.
This motivated me to quickly familiarize myself with AWS offerings and how to build sustainable infrastructures. Since then, I have participated more heavily in infrastructure design for every application I manage. This ranges from identifying AWS services that allows us to easily scale, to making sure the database structure is capable of intaking new data types if needed.