Product Management · EdTech · Learning Design
Flipt(ed)
A mastery-based learning platform that reimagines how students see and understand their own progress.
TL;DR
Existing mastery-learning tools left students in the dark about their own performance. I built, piloted, and iterated on a gamified student dashboard to close that gap — and let the data tell me what to cut.
- Identified a student-facing visibility gap ignored by every major competitor
- Ran a semester-long pilot with 70 students to validate desirability before investing in engineering
- 74% of students said the dashboard clarified their academic trajectory
- Cut competitive features (leaderboards, marketplaces) when data showed they created anxiety, not engagement
- Repositioned the product from a standalone LMS to a modular layer on top of existing tools
- Pivoted from async self-pacing to teacher-facilitated guardrails after a 69% target-completion drop-off
The student-facing home dashboard, showing mastery targets, progress indicators, health and EXP feedback mechanics, and links to external tools.
The Problem: The Student-Facing Visibility Gap
Existing software solutions supporting mastery-based educational models optimize strictly for the administrative persona — teachers and administrators — leaving the primary user, the student, completely isolated from their own performance metrics.
For secondary students (ages 11–18), this lack of transparent data architecture triggers a critical drop-off in student agency. Learning science indicates that academic success at this developmental stage heavily relies on building a student's feedback literacy — their capacity to understand, reflect upon, and self-regulate their response to learning targets. When students cannot visualize their immediate trajectory toward an objective, it creates an "invisibility of engagement" gap. Without transparent, real-time insight into the why and where of their progress, secondary learners fail to develop the metacognitive habits required to sustain motivation in mastery-based environments.
Flipt(ed) was built to cross this gap by turning performance data into a transparent, student-centered interface.
Competitive Landscape & Market Opportunity
A comprehensive market analysis of the mastery learning space revealed a clear product gap between administrative utility and user engagement:
| Competitor | Primary Persona | Core Strength | Product Limitation / Market Gap |
|---|---|---|---|
| MasteryConnect | Teachers / Admins | Robust standards-aligned backend reporting | Poor UX/UI for students; dashboard treated as a low-priority afterthought |
| Khan Academy | Students | Strong gamified progression mechanics | Rigid, closed ecosystem; zero customization for district-specific curricula |
| Classcraft | Students | High engagement via generic game mechanics | Extrinsic motivators (points/levels) decouple from actual learning objectives |
No solution on the market combined curriculum-agnostic mastery tracking with intrinsic gamification mechanics designed to keep learning objectives — rather than superficial point accumulation — at the center of the student experience.
Validating Assumptions via a Low-Code MVP
To de-risk the product concept without engineering overhead, I executed a dual-phase validation strategy.
Phase 1: Alpha Testing & Persona Validation
I put an early prototype in front of four mastery-learning educators to test the value proposition — validating seller/user desirability and uncovering immediate workflow friction. The core feedback mechanism resonated strongly, validating the underlying value hypothesis. However, this phase also exposed a critical infrastructure bottleneck: a Google Sheets backend would introduce severe scalability risks in a live classroom environment.
Phase 2: The Live Pilot
Accepting the technical debt of a low-code infrastructure as a calculated risk to prove user demand, I prioritized speed-to-market. I launched a semester-long pilot with 70 secondary students across four distinct cohorts. Rather than optimizing for technical architecture, this pilot was instrumented strictly to measure user behavior, dashboard usability, and student motivation — tracked via pre-, mid-, and post-pilot surveys throughout the lifecycle.
Post-Pilot Results
User Desirability — The Success Signals
Pilot data also served as a feature-prioritization matrix. 66% of users prioritized intrinsic mastery feedback and 54% valued experiential progression (EXP). Competitive mechanics like leaderboards cratered at 29% engagement — providing a clear, data-driven mandate to deprecate them entirely.
Technical Feasibility — The Failure Signals
While the Google Sheets backend confirmed it was non-viable for production, it served its purpose: it proved user demand before allocating engineering capital. The 69% target drop-off — amplified by remote pandemic learning — forced a critical rethink of who the product was really designed for.
Four Core Product Decisions
Decision 1
Prioritize the Student Persona Over Administrative Utilities
Context: Legacy mastery platforms optimized for district-level admins, relegating the student dashboard to a secondary, data-dense view.
Decision: Treat the student as the primary user. Funnel all engineering resources into an intuitive, gamified student progression dashboard. Keep administrative tools to a bare-minimum ingestion script.
Impact: 67% of students actively preferred our interface over their primary LMS.
Decision 2
Ruthlessly Deprecate Low-Value Gamification Mechanics
Context: Early ideation included leaderboards, marketplaces, EXP, and objective tracking.
Decision: When pilot telemetry showed competitive features engaged only 29% of users — and actively introduced anxiety — I cut them from the roadmap entirely. Development focus shifted to progress-visualization (66%) and experiential progression (54%).
Impact: Optimized the development runway, stripped cognitive noise, and ensured game mechanics reinforced learning objectives rather than distracting from them.
Decision 3
Reposition From Standalone LMS to Integration Layer
Context: The long-term vision was a comprehensive standalone LMS. But school districts mandate specific enterprise tools, creating immense switching costs and adoption friction.
Decision: Reposition Flipt(ed) as a modular optimization layer that sits on top of the incumbent LMS — turning a technical constraint into a friction-reduction strategy.
Impact: Dramatically lowered adoption barriers, proving that operating within a mandated ecosystem is a faster path to product adoption than fighting it.
Decision 4
Replace Asynchronous Autonomy With Synchronous Guardrails
Context: The platform was designed for fully asynchronous, student-paced navigation. User outcomes showed a 69% drop-off in target completion driven by the developmental limits of a middle-school demographic in remote environments.
Decision: Abandon the pure async roadmap. Refactor the PRD to introduce structured, synchronous pacing guardrails managed via a centralized teacher control panel.
Impact: Acknowledged a hard environmental truth: in K–12 EdTech, software cannot substitute for operational human guardrails. The product was redesigned to empower teacher intervention, not bypass it.
Retrospective
If executing this initiative again under similar constraints, I would shift from full-scale product development to a highly targeted, modular discovery process — isolating a single high-impact friction point (progress-visualization) and building a bulletproof integration layer for existing LMS ecosystems.
My subsequent experience leading a cross-functional squad of university engineering and UX design students validated this approach. Managing the product team required translating qualitative pilot insights into clear technical requirements, running agile sprint structures, and facilitating design sprints. It reinforced my approach to leadership: a PM's highest leverage activity is not building, but ruthlessly prioritizing the roadmap so that cross-functional talent can execute without friction.
What Came Next: The Mastery Quiz Game
The clear signals extracted from the Flipt(ed) pilot pointed to an unaddressed market opportunity: what if a standalone, gamified formative assessment tool could instantly map student performance to mastery criteria for both learners and educators simultaneously?
By deprecating the complex, low-retention aspects of the original ecosystem and isolating the highest-value feature — immediate feedback tied to clear learning targets — I initiated development on a spin-off product: the Mastery Quiz Game. This strategic pivot scales down technical risk, fits cleanly into existing classroom operational models, and directly captures the market gap identified during the MVP phase.