Yayasan Penguatan Partisipasi, Inisiatif, dan Kemitraan Masyarakat Indonesia (YAPPIKA), also known as Yappika ActionAid, works to strengthen public services and build a more equitable society. Founded in 1991, the nonprofit organization focuses on education, disaster response, poverty, injustice, and civil society development.
As part of its education initiatives, YAPPIKA wanted to help Indonesian universities improve digital learning. Many institutions still lacked a reliable Learning Management System (LMS) for managing course materials, assignments, assessments, and communication.
Suitmedia partnered with YAPPIKA since 2024 to develop a user-friendly and scalable LMS tailored to higher education. The project combined platform development with training and technical assistance, helping universities improve academic management while giving students more consistent access to learning resources.
Universities Needed More Than Digital Content
1. The education gap was also a systems gap
Universities increasingly depend on digital tools to support learning beyond the classroom. Lectures, course materials, assignments, assessments, feedback, and student communication often need to continue across different channels.
However, many Indonesian universities still lacked a single platform to manage these activities. Educators might rely on email, messaging applications, shared folders, or separate tools for different courses.
This created unnecessary work and made information harder to manage. Students could miss announcements, lose track of deadlines, or struggle to locate the latest learning materials.
The issue was not simply a lack of digital content. It was the absence of a connected system that could organize learning in one place.
2. Students needed more reliable access to learning resources
When academic information is scattered, students experience unequal access to course materials and instructions.
Some may receive updates quickly, while others may miss them. Assignment requirements can become unclear when instructions, deadlines, and submissions are handled through different platforms.
An LMS could create one consistent reference point. Students would have a clearer place to review materials, understand assignments, submit work, and follow academic activities.
This flexibility was important for students who needed to access learning outside scheduled class hours. But the system also needed to be simple enough for users with different levels of digital confidence.
3. Educators needed a practical way to manage courses
An LMS must support the daily work of lecturers, not add another administrative burden.
Educators need to organize course materials, distribute assignments, review submissions, manage assessments, and communicate with students.
If these activities are difficult to complete, lecturers may continue relying on familiar but disconnected tools. The platform therefore needed to reflect real academic workflows instead of forcing universities to adapt to an inflexible system.
The goal was to create a shared structure while allowing educators to manage different teaching styles and course requirements.
4. Universities needed a flexible and scalable system
Higher education institutions do not all operate in the same way. They may differ in academic structures, course formats, assessment processes, user roles, and administrative procedures.
YAPPIKA needed an LMS that could accommodate these differences without requiring a separate system for every institution.
Flexibility was therefore important from the beginning. The platform needed to support current requirements while allowing more courses, users, content, and activities to be added over time.
5. Adoption mattered as much as development
A technically sound LMS can still fail if users do not understand how to use it or why it matters.
Educators and administrators may hesitate to adopt a new platform if they lack confidence, do not see how it fits into their work, or receive insufficient support during implementation.
YAPPIKA recognized that the project required more than software delivery. Universities needed training and technical assistance to use the platform effectively and sustain it after launch.
The project therefore had two objectives:
- Build a capable learning platform.
- Develop the confidence and skills required for long-term adoption.
Designing the LMS Around Real Academic Work
1. We started with requirements, not assumptions
Suitmedia began with a detailed requirements-gathering process to understand how participating institutions managed teaching and learning.
The team examined the needs of students, educators, and administrators. The YAPPIKA team participated in defining workflows and user journeys, helping ensure that the system reflected actual academic conditions.
The research focused on practical questions:
- How are courses organized?
- How do lecturers distribute materials?
- How are assignments submitted?
- How are assessments managed?
- What information do students need first?
- Which activities require administrative oversight?
- Where do current processes create delays or confusion?
These findings shaped the platform’s structure and reduced the risk of building a system that looked complete but failed to support daily work.
2. We mapped different users within one connected platform
Students, educators, and administrators use an LMS for different purposes.
Students need to find courses, review materials, complete assignments, and monitor learning activities. Educators need to create content, manage assignments, review submissions, and assess student performance. Administrators need to manage users, courses, permissions, and institutional settings.
Suitmedia mapped these different journeys so each role could access relevant functions without creating separate or disconnected systems.
The aim was not to make every user see the same interface. It was to give each user a clear path through one shared academic environment.
3. We designed for clarity and routine use
An LMS is used repeatedly throughout an academic term. This makes ease of use especially important.
The interface was designed to help users understand where they were, what information was available, and which action they could take next.
Clear navigation and consistent page structures reduced the effort needed to move between courses, materials, assignments, and assessments.
The platform was designed to support users with different levels of digital confidence. Completing a routine academic task should not require users to learn a complicated system first.
4. We brought course management into one structure
The LMS provided a central environment for organizing courses and learning materials.
Educators could manage course content and activities within a consistent framework, while students could access course information through a familiar structure.
Centralization reduced the need to use separate tools for different classes or activities. It also gave institutions a clearer record of how courses were organized and managed.
The system created common ground without forcing every course to follow exactly the same teaching method.
5. We connected learning materials with assignments
Learning resources were organized alongside the academic activities they supported.
This helped students understand how course materials related to assignments, lessons, and assessments. They could move from reviewing content to completing the relevant task without searching through unrelated channels.
For educators, the structure reduced repeated distribution of instructions and files across different systems.
The result was a more continuous learning process. Students could see not only what they needed to read, but how that material connected to their academic responsibilities.
6. We integrated assignments and assessments
Assignments, submissions, and assessments were managed within the same platform.
This gave students clearer information about requirements, deadlines, and submission processes. Educators could review work and manage assessment activities through a more organized workflow.
Integration reduced the risk of lost files, missed instructions, and uncertainty about whether work had been submitted correctly.
For institutions, it also created a more consistent record of academic activity and reduced dependence on informal communication channels.
7. We built for institutional flexibility
The LMS was designed for Indonesian higher education institutions with different requirements and workflows.
Its structure could accommodate different course arrangements, user roles, learning activities, and assessment needs.
This flexibility made the platform more suitable for broader adoption. YAPPIKA could support universities without requiring each institution to start from the beginning.
Scalability was considered both technically and operationally. The system needed to support growth while remaining manageable for the institutions using it.
8. We tested the platform before deployment
Testing helped identify technical issues, usability problems, and gaps between intended workflows and the actual platform experience.
This was important because an LMS affects several user groups at once. A feature that works for administrators may still be confusing for educators or students.
Testing provided an opportunity to refine the experience before launch and increase confidence in the system’s reliability.
The objective was not to eliminate every possible issue. It was to ensure that the core academic journeys worked effectively from the beginning.
9. We treated training as part of implementation
Suitmedia provided training to help users understand the platform and apply it to their work.
Training helped educators and administrators learn how to manage courses, materials, assignments, assessments, and other academic activities.
It also helped users understand how the LMS fit into existing processes and where it could reduce manual work.
This was essential for adoption. A system becomes valuable only when people use it consistently and confidently.
10. We provided technical assistance after deployment
Technical support helped universities address questions and issues that emerged under real academic conditions.
This reduced the risk that small problems would cause users to return to disconnected tools.
Support also helped the institutions develop greater ownership of the platform. The goal was not to deliver software and leave users alone with it, but to help them build the capability to manage digital learning over time.
From Fragmented Learning Activities to a Connected Academic Environment
1. Universities gained an integrated LMS
The platform brought course materials, assignments, assessments, and learning activities into one environment.
This created a more structured experience for educators and students. Academic information could be accessed through a consistent system instead of being distributed across multiple tools.
The integration also improved institutional oversight. Universities could manage learning activities through a shared framework rather than relying on disconnected records.
2. Students gained more consistent access to course information
Students could access materials, assignments, and assessments through one platform.
This reduced uncertainty and made it easier to understand what they needed to complete and when.
The LMS also supported more flexible learning. Students could review content and manage academic tasks beyond the classroom and according to their own schedules.
3. Educators gained a more organized workflow
Lecturers could manage course content, distribute assignments, review submissions, and conduct assessments in a more structured way.
This reduced some of the administrative friction created by using different tools for different activities.
A more organized course environment also helped educators communicate expectations more clearly and maintain better records of student work.
4. Academic management became more efficient
The platform helped universities coordinate academic activities through one system.
This could reduce repeated manual work, improve information consistency, and make it easier to monitor how courses and assessments were managed.
The benefit was not only operational efficiency. A clearer system can also improve accountability between educators, students, and academic administrators.
5. Collaboration between educators and students improved
An integrated LMS gives educators and students a shared source of information.
Students can access the materials and instructions provided by lecturers, while educators can review student activity within the same platform.
This supports clearer communication and reduces the need to reconcile information from separate applications.
6. Institutions became better prepared for digital education
The LMS helped universities strengthen their ability to deliver and manage learning through digital systems.
The project’s impact extended beyond the platform itself. Through training and support, institutions developed greater confidence in adopting technology as part of their academic operations.
This prepared them to respond more effectively as student expectations, teaching methods, and education technology continued to change.
7. YAPPIKA gained a model that could support more institutions
The combination of a flexible LMS, user research, training, and technical assistance created a scalable approach for YAPPIKA’s education initiatives.
The platform could be adapted to different universities while maintaining a consistent foundation.
This allowed YAPPIKA to contribute to broader improvements in public education services rather than limiting the benefit to one institution.
8. The project created room for future improvement
Once a university has an integrated LMS, it can continue improving how it organizes courses, supports students, evaluates learning, and manages academic information.
The platform creates a base for future developments, such as additional integrations, new content formats, learning analytics, and more specialized support for educators and students.
The initial implementation therefore created value beyond the launch period.
What YAPPIKA Reveals About Digital Learning Transformation
1. An LMS is an institutional change project
Technology provides the platform, but adoption depends on workflows, training, ownership, and leadership support.
Universities need to understand how the system changes daily academic work and why consistent use matters.
2. User research reduces implementation risk
Different institutions and user groups have different needs.
Understanding those needs before design and development helps ensure that the LMS supports real teaching and learning rather than imposing an impractical structure.
3. Integration improves access and control
When course materials, assignments, and assessments work together, students gain clearer access and institutions gain better oversight.
Integration reduces fragmentation and creates a more reliable academic record.
4. Training is part of the solution
Users judge a platform by how confidently they can use it in practice.
Training and technical assistance bridge the gap between software delivery and real adoption, especially when the system affects educators and administrators.
5. Scalability includes people and processes
A platform may support more users technically, but adoption will not scale without institutional capability.
Long-term growth requires systems that universities can understand, operate, and maintain.
6. Digital learning must balance flexibility and structure
Students need convenient access to learning resources, while institutions need consistent academic processes.
An effective LMS provides both: flexibility for learners and structure for educators and administrators.
Strategic Insights for the C-Suite
- Treat education technology as organizational change.
An LMS succeeds when users, workflows, and leadership align around its use. Software deployment without adoption planning will not improve learning outcomes. - Design around the work educators and students actually do.
Requirement gathering and user research reduce the risk of building a platform that looks complete but fails in daily academic use. - Integrate learning activities to reduce institutional friction.
Course materials, assignments, assessments, and communication create more value when they work within one connected environment. - Invest in training and support as seriously as development.
User confidence determines whether a platform becomes part of institutional practice or remains an underused system. - Build public-service technology for long-term flexibility.
A platform intended for multiple universities must accommodate different requirements, growing adoption, and changing educational needs.
