The Capability Bridging Framework exists because the standard approaches were not working. This is the story of how it came to be, why it matters, and where it is going.
Before a single line of architecture was written for The Gambia's national Higher Education Management Information System, we brought everyone into the same room. Representatives from across the entire higher education ecosystem. Public universities, private universities, tertiary institutes, government ministries. Well-resourced and severely under-resourced. All in the same space.
What happened in that room changed everything.
Institutions described their operational realities to each other for the first time. Some were talking about cloud ERPs and API readiness. Others quietly admitted they managed everything in Excel. A few acknowledged they were still largely paper-based. Nobody had asked them all to be honest about this together before.
And instead of embarrassment, there was relief. Everyone could see the diversity was real, shared, and nobody was alone in their constraints. That collective honesty became the foundation of the Capability Bridging Framework.
Instead of embarrassment, there was relief. Everyone could see the diversity was real, shared, and nobody was alone in their constraints. That collective honesty became the foundation of everything we built.
The HEMIS Context
Digital transformation that assumes uniform technical capability perpetuates the very inequality it promises to solve. Governments and development partners spend billions on systems that exclude the very stakeholders they were designed to serve. The Capability Bridging Framework exists to change that.
Every stakeholder deserves a pathway into the system, not a promise to be included later. The framework makes inclusion permanent, not provisional.
No stakeholder gets lesser quality. What differs across pathways is the validation mechanism, not the standard. Every organisation contributes data of equal integrity.
The framework is freely available for any organisation to adopt, adapt, and build upon. It belongs to everyone who needs it, not to a vendor or a licence.
The Capability Bridging Framework was developed and validated during the implementation of The Gambia's World Bank-funded HEMIS platform, implemented under the leadership of the Ministry of Higher Education, Research, Science and Technology. What began as a solution to a specific implementation challenge has become a transferable methodology applicable across any public sector context where stakeholders have unequal technical capabilities.
The same design problem exists everywhere. The same framework solves it.
Applicable Across Sectors
Olawale Fabiyi is a Strategic Technologist with 17+ years of experience leading digital transformation across Southeast Asia and West Africa. PRINCE2 Agile-certified, he specialises in large-scale project implementation and the application of TOGAF frameworks to design scalable, inclusive systems.
He currently serves as Technical Advisor for the HEMIS Project at The Gambia's Ministry of Higher Education, Research, Science and Technology, where he leads architecture, stakeholder alignment, and sustainable capacity building for a World Bank-funded national higher education management platform.
He is also an AI and deep learning researcher focused on safety optimisation and database performance, combining academic work with hands-on implementation to bridge policy, education, and technology. He is pursuing a PhD in Computer Science and Information Systems, developing a pre-procurement diagnostic framework for predicting and preventing digital transformation failure in resource-constrained public sector environments.
The Capability Bridging Framework is his original contribution to the field of inclusive public sector digital transformation, developed through direct implementation experience and validated at national scale.
Current Role
Position
Technical Advisor, HEMIS
Organisation
Ministry of Higher Education, Research, Science & Technology
Country
The Gambia
Project
World Bank RISE Initiative
Two audiences. One tool. Platform operators use it to design inclusive integration architecture. Individual institutions use it to understand their current digital capability and chart a path to improvement.
