Edtech, LMS Redesign

I started where I always start: who is involved, what do they need, where does the current system fail them. I mapped every platform in use, then ran interviews and questionnaires across all four user groups: students, faculty, admin, and management. Each group was failed differently, so I built personas and traced the pain points to their sources. The call that shaped the project: not to feature-match the existing tools. The easy version would have copied what the SaaS stack already did, minus the vendor bills. Instead I designed from the workflows outward: How Might We statements, workflows per user group, information architecture, and system maps showing how classes, tests, and records connect in one structure. The handoff had to survive without me, so the documentation went to developer depth: a full PRD with user flows, system architecture, and a phased roadmap the team could build against.