Multi-College Learning Management Platform
A digital transformation project aimed at modernizing an existing learning management environment and bringing multiple colleges under one platform, while preserving the ability of each college to manage its own operations independently.
My role covered the analysis journey from understanding the existing system and eliciting requirements to translating them into a comprehensive prototype spanning 11 different user roles.
The Challenge
Unifying multiple colleges without removing their operational independence.
The project involved more than replacing an old system with a newer interface.
The new solution needed to support a shared administrative structure across multiple colleges, while still allowing each college to operate independently within its own responsibilities and processes.
This meant understanding the existing environment first, identifying what should be retained, improved, or automated, and then translating a large set of interconnected requirements and user roles into one coherent product vision.
My Contribution
From understanding the current system to shaping the future one.
Established the Current-State Baseline
I started by studying the existing system and documenting how its processes worked, creating a clear baseline before defining the future solution.
This helped distinguish between existing behavior, operational needs, and opportunities for improvement rather than treating every current process as a requirement for the new platform.
Elicited & Structured Requirements
Collected requirements through stakeholder collaboration, analyzed the business needs behind them, and organized them into a clearer structure that could guide the future platform.
The work involved connecting requirements across different colleges, processes, and roles while maintaining a consistent understanding of the overall system.
Turned Requirements into a Multi-Role Prototype
Translated the analyzed requirements into a comprehensive prototype covering 11 distinct user roles.
The prototype helped make the proposed solution tangible by showing how different users would navigate the platform, interact with processes, and access functionality based on their responsibilities.
Rather than relying on documentation alone, it became a shared visual reference for discussing and validating the intended system behavior.
Used the Prototype to Drive Stakeholder Discussions
Presented analysis outcomes and prototype flows during stakeholder sessions, using the visual solution to clarify requirements, collect additional needs, and refine the proposed experience.
This made discussions more concrete: instead of reviewing requirements only as written statements, stakeholders could see how they translated into actual workflows and screens.
- Requirements
- Prototype
- Discussion
- Refinement
Structured the Handover
When analysis ownership transitioned to another team member, I documented the current project status, completed work, open areas, and relevant context needed to continue the analysis.
I also supported the transition to reduce the loss of knowledge and provide a clearer starting point for the next phase.
Key Deliverables
Turning analysis into artifacts the team could use.
Current-State Analysis
Documented the existing system and its processes to establish a reliable baseline for the transformation.
Requirements Documentation
Structured business and functional needs across multiple processes, colleges, and user roles.
Multi-Role Interactive Prototype
Created a connected representation of the proposed platform across 11 user roles, making requirements easier to review and validate.
Project Handover Documentation
Captured the project status and analysis context to support continuity when ownership changed.
Skills in Practice
What this project allowed me to practice.
- Current-State Analysis
- Requirements Elicitation
- Requirements Analysis
- Process Analysis
- Stakeholder Communication
- User Flows
- Interactive Prototyping
- Knowledge Transfer
Takeaway
A requirement becomes much easier to discuss when people can see how it will work.
This project strengthened my understanding of prototypes as more than a design deliverable.
When many roles, processes, and organizational levels are involved, translating requirements into a visible experience can uncover questions that are difficult to identify from documentation alone.
For me, the prototype became a bridge between analysis and shared understanding, helping stakeholders discuss the intended solution in a much more concrete way.