Mohammed Baobaid
Learning-platform screens for content, progress, and administration.
A product concept focused on clearer course operations, simple progress visibility, and admin tools that can scale beyond a single cohort.
Role
Prototype lead
Outcome
Mapped the core user flows before implementation decisions were locked.
Education platforms often prioritize content delivery over operational clarity. Instructors and administrators needed a system where managing courses, tracking progress, and handling enrollments felt as intuitive as the learning experience itself.
I started with user flow mapping in Figma, identifying the critical paths for three roles: learner, instructor, and admin. From there, I built interactive prototypes in Tailwind that validated the UI patterns before any backend work began. The data model was designed to support multi-cohort scaling from day one.
Each role was mapped through its core journey: learners from enrollment to completion, instructors from content creation to grading, and admins from cohort setup to reporting. Edge cases and error states were documented at each decision point.
Before writing any backend code, interactive Tailwind prototypes were built and tested with potential users. This approach caught three major usability issues that would have been expensive to fix after implementation.
The database schema was designed with future scaling in mind: courses can belong to multiple cohorts, content can be versioned independently of enrollment data, and progress tracking supports both automated and instructor-assessed milestones.
I build systems like this for teams that need reliable engineering, clean interfaces, and measurable outcomes.