A Global Partnership Fragmented Across Multiple Platforms
The Anti-Corruption Learning Center (ACLC)—a joint initiative between GIZ (the German international development agency) and Indonesia's KPK—had an ambitious mandate: deliver anti-corruption education and training to thousands of people across Indonesia. The audience was massive and diverse: KPK employees, civil servants, private sector professionals, NGO workers, politicians, and ordinary citizens.
But the ACLC's digital infrastructure was fragmented. Three websites existed in parallel, each serving different functions: ACLC (the main portal), LSP (certification platform), e-Learning (course delivery), and Aksesku Interaksi (community interaction). Theoretically interconnected. In practice, siloed.
A user wanting to take a course had to navigate between platforms. Someone seeking certification didn't know which portal to use. The community interaction space was disconnected from learning content. The fragmentation undermined the ACLC's core mission: making anti-corruption education accessible and integrated.
By 2021, GIZ and KPK recognized that technical improvements to each platform independently would fail. What was needed was not three better websites—it was one coherent ecosystem where learning, certification, and community formed a unified experience.
The Hidden Costs of Fragmented Digital Infrastructure
The ACLC's platform fragmentation created problems that went beyond poor user experience.
1. Users didn't know where to start their learning journey.
The ACLC had courses, certifications, and community features. But a new user arriving at the ecosystem had no clear entry point. Should they start at the main ACLC portal? The e-Learning platform? The certification site? Each platform assumed users already knew it existed and what it offered.
A civil servant wanting to complete anti-corruption training faced decision paralysis: Which platform had the content I need? Where do I apply for certification? How do these three sites relate to each other? The cognitive burden of navigating the ecosystem meant many potential learners never started.
2. Content and learning paths were disconnected from certifications.
The e-Learning platform hosted courses, but the certification platform (LSP) operated independently. A user could complete a course on the e-Learning site but wouldn't automatically be eligible for certification—they'd need to separately apply on the LSP platform, potentially repeating information already captured in the course.
This created friction and duplicate data entry. More importantly, it broke the learning logic: courses should naturally lead to certifications, which should lead to badges or credentials. Instead, these were three separate transactions on three separate websites.
3. The community space was isolated from learning.
Aksesku Interaksi was designed as a discussion and peer-learning platform. But it existed separately from both courses and certifications. A learner completing a course had no obvious way to connect with others on the same journey. A professional seeking peer advice on anti-corruption practices might not even know the community platform existed.
The network effects of community—where shared learning amplifies impact—were lost because the community was disconnected from the learning experience.
4. Different design languages created cognitive friction.
Each platform had been designed independently, sometimes at different times. They used different color schemes, different navigation patterns, different terminology. A user switching between them had to mentally recalibrate each time.
This wasn't just aesthetic inconsistency. It created usability friction: buttons looked different (were they clickable?), navigation patterns varied (where do I go next?), and terminology changed (is it called "courses" or "programs" or "learning paths"?).
5. Backend operations were invisible, creating support burden.
Administrators managing the three platforms couldn't see the complete user journey. Someone could be enrolled in a course on e-Learning, applying for certification on LSP, and asking questions on Aksesku Interaksi, but no single dashboard showed this complete picture.
This meant support staff couldn't diagnose problems holistically. A user stuck on their learning journey couldn't get help across platforms—they'd be redirected from one support team to another, each managing only their own platform.
Designing the Ecosystem as a Unified System
Suitmedia's approach treated the ACLC not as three websites that needed better design, but as one learning ecosystem that needed coherent architecture.
Foundational Research: Understanding Diverse Learner Needs
1. Internal stakeholder interviews with KPK and GIZ teams.
Suitmedia started by interviewing the teams managing each platform: course designers (who created e-Learning content), certification administrators (who managed LSP), community moderators, and leadership. Each team had different mental models of what the ACLC should be and how it should work.
The interviews revealed alignment gaps: was the ACLC primarily a certification body, a learning platform, or a community hub? Different teams prioritized differently. Resolving this required explicit conversations about the ACLC's core mission and which functions were primary versus secondary.
2. User research with learners across different backgrounds.
Suitmedia conducted interviews with actual and potential users: KPK employees (who needed mandatory training), civil servants (who sought voluntary upskilling), private sector professionals (who wanted certifications), and NGO workers (who needed community-based learning).
Each group had different needs. KPK employees wanted to understand compliance requirements. Civil servants wanted certifications they could add to their resumes. Private sector professionals wanted practical skills. NGO workers wanted to connect with peers facing similar challenges.
A single design couldn't serve all these groups equally—but the architecture could accommodate them. The key insight: the same learning content and certifications had different meanings depending on who the learner was and why they were learning.
3. Usage pattern analysis across the three platforms.
The existing platforms had user data: enrollment rates, completion rates, certification applications, community engagement. Suitmedia analyzed where users got stuck, which features were used most, and which pathways worked versus which ones leaked users.
The data revealed that users who started on the e-Learning platform often didn't complete the certification process. Users who discovered the community platform tended to stay engaged longer. Users who knew the ACLC existed often didn't know where to start. These patterns shaped the redesign priorities.
Creating Coherent Architecture Across Fragmented Platforms
Instead of redesigning each platform independently, Suitmedia created a unified design system and information architecture that could be applied consistently across all three platforms.
Five Principles That Guided the Integrated Design
1. One entry point that orients users to the complete ecosystem.
The redesigned ACLC homepage became the coherent entry point. Instead of three separate platforms, users saw one ecosystem with three functions: Learn, Certify, and Connect.
A user arriving at the ACLC was immediately oriented: "Take a course to develop anti-corruption skills," "Earn a certification to demonstrate competence," "Join the community to share experiences and learn from peers." Each pathway was visible but distinct, making it clear how the platforms related.
Most importantly, the entry point didn't force users to choose one pathway. It showed how they connected: complete a course → apply for certification → join the community for continued learning. The homepage communicated the intended learning journey.
2. A unified design system applied to all three platforms.
Suitmedia created a comprehensive design system: consistent typography, color palette, button styles, form layouts, and navigation patterns. This system was then applied to the e-Learning platform, the certification platform, and the community space.
The visual consistency made switching between platforms feel natural, not jarring. A user completing a course on e-Learning could navigate to the certification platform and immediately recognize the interaction patterns. The learning journey felt like one continuous experience, not three separate websites.
The design system also included behavioral patterns: how forms worked, how progress was displayed, how success was signaled. Consistency in these patterns reduced cognitive load—users could focus on their learning task, not on figuring out how the interface worked.
3. Unified user profiles that flowed across all platforms.
Previously, a user might have separate accounts on each platform, or information might be fragmented across systems. The redesign created a single user profile accessible across all three platforms.
When someone completed a course on e-Learning, their profile was automatically updated. When they applied for certification on LSP, the system could see their completed courses and automatically populate relevant fields. When they joined the community, their learning history was visible (if they chose to share it), helping peers understand their background.
This unified profile made the ecosystem feel integrated, not fragmented. Users didn't need to re-enter information as they moved between platforms. The system remembered their journey.
4. Learning pathways that guided users through all three platforms.
The redesign introduced explicit learning pathways: curated sequences of courses, certifications, and community engagement organized around specific anti-corruption topics or roles.
A civil servant might follow a pathway like: "Anti-Corruption Fundamentals" (course on e-Learning) → "Integrity Officer Certification" (certification on LSP) → "Integrity Officers Community" (community on Aksesku Interaksi). Each step had clear prerequisites and outcomes.
Learning pathways did more than organize content—they communicated intent. They showed users that the ACLC was designed as a coherent learning system, not three disconnected tools. Pathways also created natural progression: users weren't choosing randomly between courses; they were following a designed journey.
5. Community integrated into the learning experience, not separate from it.
The most significant shift was moving the community from a disconnected discussion space to an integrated part of the learning ecosystem. Courses now included community forums where learners could discuss concepts. Certifications included peer communities where certificate holders could share experiences.
This created two benefits: learning was richer (peer perspectives complemented course content), and community was more purposeful (discussions were grounded in learning content or shared credentials). A civil servant who completed an integrity course could immediately join others who'd completed the same course to discuss implementation challenges.
Redesigning Backend Systems for Admin Coherence
The user-facing improvements were visible, but equally important were backend changes that made the ACLC manageable for administrators.
1. Unified admin dashboard across all three platforms.
Previously, managing the ACLC required logging into three separate admin systems. A manager couldn't see the complete picture of user enrollment, course completion, certification status, and community engagement in one place.
Suitmedia created a unified admin dashboard that showed: total active users, enrollment trends across platforms, certification application pipeline, and community engagement metrics. Administrators could see which courses had high completion rates, which certifications had backlogs, and which community discussions were most active.
This unified view enabled strategic decision-making. If a course had low completion rates, the team could investigate whether the content was unclear or if the pathway integration was broken. If certifications were backing up, the team could see whether more reviewers were needed.
2. Content management that served all platforms from one place.
The three platforms had separate content management systems. A course instructor updating content on e-Learning couldn't easily see how that content related to certification requirements or community discussions.
Suitmedia implemented a unified content management system where courses, certifications, and community resources could be created once and deployed across appropriate platforms. This reduced duplication and ensured consistency.
A course update could automatically trigger a notification to the certification team: "The 'Corruption Reporting Procedures' course was updated. Does this affect the LSP certification requirements?" This coordination happened structurally, not through manual communication.
3. User journey tracking that revealed friction points.
With three separate systems, it was difficult to track complete user journeys. Did someone who enrolled in a course also apply for certification? Did they engage with the community?
The redesign implemented cross-platform journey tracking. The ACLC could see cohorts of users and track them through all three platforms. If a significant number of course completers didn't apply for certification, that indicated a friction point worth investigating.
This data-driven approach to improving the ecosystem meant changes weren't based on assumptions—they were based on observed user behavior.
Implementation: Phased Integration Without Disruption
Integrating three platforms while keeping them operational required careful sequencing.
1. Design system development and pilot testing happened first.
Suitmedia didn't launch changes across all three platforms simultaneously. Instead, the team developed the unified design system and piloted it on one platform (typically the e-Learning platform, which had the highest user volume).
The pilot revealed which design patterns worked well and which needed adjustment. Users of the e-Learning platform essentially helped test the design system before it was applied to the other platforms. Feedback from the pilot shaped refinements before full rollout.
2. Platform migrations happened sequentially with user communication.
The e-Learning platform was redesigned first, then LSP, then Aksesku Interaksi. Each migration was accompanied by user communication explaining why the change was happening and what benefits to expect.
The phased approach meant that when users migrated from platform to platform, they'd encounter increasingly familiar design patterns. A user who started on e-Learning (newly redesigned) and then visited LSP (redesigned with the same system) would recognize the patterns immediately.
3. The unified entry point launched last, after all platforms were updated.
The redesigned ACLC homepage—the coherent entry point showing all three functions—launched last. By that time, users who visited any of the three platforms would encounter consistent design and navigation.
The new homepage made the integrated ecosystem visible, but that visibility was backed by actual integration. The homepage wasn't just a marketing layer—it was the true entry point to a redesigned system.
Ecosystem Effects: When Integration Creates New Possibilities
The redesigned ACLC launched in 2022 and achieved results that went beyond improved user experience.
- Enrollment and completion rates improved across all three platforms.
Users who understood how the platforms connected were more likely to progress through the entire learning journey. Someone who started a course was more likely to apply for certification if the next step was obvious. Someone who earned a certification was more likely to join the community because it was integrated into the certification experience.
Completion rates for learning pathways—from course start to certification to community engagement—increased significantly compared to users navigating the old fragmented system.
1. The unified system enabled new learning models.
With integrated platforms, the ACLC could experiment with cohort-based learning: groups of learners progressing through courses together, then certifying together, then forming communities. The old fragmented system made this impossible—there was no way to track or facilitate cohorts across platforms.
Cohort-based learning had social benefits (peer accountability and support) and operational benefits (administrators could track group progress). The integrated system made this learning model viable.
2. Community engagement became more purposeful and sustained.
Previously, the community platform struggled with engagement—discussions often felt disconnected from any learning objective. With integration, community discussions were grounded in courses or certifications, making them more relevant and attracting higher-quality engagement.
Users who completed a course had context for community discussions. They could ask practical questions about implementing what they'd learned. More experienced practitioners could share real-world examples. The community became a continuation of learning, not a separate space.
3. The ACLC became measurable as a complete system.
With backend integration, GIZ and KPK could finally measure the ACLC's impact as a coherent program. They could track: How many people start the ecosystem? How many complete courses? How many pursue certifications? How many engage with community?
This data revealed the ACLC's true reach and effectiveness. It also revealed bottlenecks: if 80% of people started courses but only 20% applied for certifications, that was a friction point to investigate. The integrated system made measurement possible.
Lessons About Integrating Fragmented Digital Systems
1. The architecture precedes the interface.
Suitmedia could have redesigned each platform's interface independently, making each one beautiful but leaving them fragmented. Instead, the work began with creating a unified architecture and design system—work that isn't visible to users but determines everything they experience.
The lesson applies broadly: when integrating fragmented systems, fix the structural problems first. A unified design system applied to fragmented platforms creates coherence. Three beautifully designed but unconnected platforms remain fragmented.
2. User research must include the full ecosystem, not isolated platforms.
Traditional UX research tests individual platforms in isolation. But Suitmedia researched the complete user journey: how did learners move between platforms? Where did they get confused? What information would help them navigate the ecosystem?
This ecosystem-level research revealed integration problems that platform-level research would have missed. A learner struggling to move from course to certification isn't a course platform problem or a certification platform problem—it's an ecosystem problem requiring ecosystem-level thinking.
3. Backend integration enables frontend coherence.
Users experience coherence when moving between platforms. But that coherence is only possible if backend systems are integrated: shared user profiles, unified content management, cross-platform journey tracking.
A pretty interface on fragmented backend systems can't create true coherence. Conversely, integrated backend systems make beautiful, coherent interfaces possible. The backend work is invisible but foundational.
Strategic Insights for the C-Suite
1. Fragmented digital infrastructure reflects organizational silos.
The ACLC's three platforms didn't arise randomly. They existed because three different teams (e-Learning, certification, community) managed different functions. Each team optimized their platform independently without full visibility into the complete user journey.
This is a common pattern: digital fragmentation follows organizational structure. When you have separate teams managing separate platforms, each team optimizes locally without seeing system-level problems. Integration requires breaking down organizational silos, not just connecting platforms.
2. Integration unlocks new capabilities that fragmented systems cannot achieve.
The old ACLC had learning, certification, and community. But they couldn't work together strategically. Cohort-based learning was impossible. Community discussions were disconnected from learning objectives. Progress tracking across the user journey was invisible.
Integration didn't add new features—it enabled new possibilities by connecting existing features. This is the power of systems thinking: the value isn't in individual components but in how they work together.
3. Users don't experience the organization—they experience the system.
ACLC users didn't care that the organization had separate teams managing e-Learning, certification, and community. They cared about learning anti-corruption practices effectively. A fragmented system makes this harder; an integrated system makes it easier.
As a leader, you're designing systems that users experience as wholes. If your system is fragmented, users experience that fragmentation, regardless of how well each component is designed. Integration is invisible when it works, but fragmentation is always visible when it fails.
4. Backend coherence enables frontend simplicity.
The redesigned ACLC's user interface is simpler and clearer than before. But that simplicity is only possible because the backend is coherent. Unified user profiles, shared content management, cross-platform journey tracking—these backend systems allow the frontend to be simple because the system is doing work invisibly.
Conversely, if you try to create a simple frontend without fixing backend fragmentation, you end up with a confusing experience where users navigate disconnected systems through a unified interface. The fragmentation leaks through.
5. Measurement is the final driver of integration.
The old ACLC couldn't measure its impact as a system. Leadership didn't know how many people progressed from course to certification to community engagement. Data was trapped in three separate systems, making holistic analysis impossible.
Integration enables measurement. And measurement drives improvement. Once you can see that 80% of learners drop off between course completion and certification application, you have a data-driven reason to improve that transition. You can test changes and measure whether they work.
