From our work
Muskoka Fund
The Muskoka Fund Collaborative Platform, Knowledge Sharing and Coordination for the Joint UN Mechanism on Maternal and Child Health
Continental
The coordination-substrate problem
Joint UN coordination mechanisms operate on a level of institutional complexity that single-agency platforms struggle to absorb. Four agencies with distinct mandates, distinct programming instruments, distinct internal cultures, and distinct accountability lines work together at country level, regional level, and headquarters level. The four agencies coordinate with the donor governments that fund the mechanism, with the host governments whose health systems the work strengthens, with implementation partners on the ground, and with the technical secretariats that hold the institutional governance together. The coordination work happens at every interface between these actors, and the institutional substrate beneath the formal governance is where the work either compounds productively or fragments quietly.
The default response to this complexity is to deploy a generic collaboration tool, the kind of off-the-shelf platform that promises to support any team in any organisation. The default response usually fails, not because the tools are technically inadequate, but because the institutional substrate they impose does not match the coordination taxonomy of the mechanism they are deployed for. Country-level inter-agency teams need different scopes than inter-country thematic exchanges. The regional Technical Committee operates differently than the bilateral country-to-regional channel. The Secretariat-Presidency interface has its own institutional logic. A platform that flattens these distinctions into a generic chat-and-channels metaphor degrades the coordination work it was meant to support.
What inter-agency platform design actually requires
The architectural answer is a platform whose substrate matches the coordination taxonomy. The subgroups, the access scopes, the document repositories, and the notification rules all reflect the actual institutional structure of the mechanism rather than imposing a generic team-and-channel metaphor on top of it. The single identity layer carries users across the platform according to their roles in the coordination, with their access scope reflecting the actual subgroups they are part of. The collaborative environment supports the working patterns the inter-agency teams already operate against, rather than asking them to learn a new pattern that does not match their work.
The discipline that makes the architecture work is institutional collaboration during design rather than after deployment. The subgroups that structure the platform have to be specified by the secretariat that runs the coordination, not invented by the technology partner. The access scopes have to align with the agency-specific data protection and information sharing policies that govern the four agencies' joint work. The notification rules have to reflect the actual cadence of the coordination cycles. The combination is what produces a platform that the coordination secretariat owns operationally rather than treating as a vendor delivery.
What we built for UNICEF and the Muskoka Fund
PANEOTECH delivered the Muskoka Fund Collaborative Platform for UNICEF on behalf of the joint Muskoka Fund mechanism. The platform serves the four UN agencies that coordinate the mechanism, the World Health Organization, UN Women, the United Nations Population Fund, and UNICEF, across the nine francophone beneficiary countries: Benin, Burkina Faso, Chad, Côte d'Ivoire, Guinea, Mali, Niger, Senegal, and Togo. Three architectural pillars consolidate the coordination work into a single environment: a multi-format documentary library, a collaborative working environment with subgroups scoped to the coordination taxonomy, and an operational tools layer with interactive maps, calendars, consultant rosters, and team directories.
The architecture respects the institutional reality of the Muskoka mechanism rather than imposing a generic collaboration metaphor on top of it. The MuskoTeams subgroups follow the actual coordination structure: country-level inter-agency teams, inter-country thematic exchanges, country-to-regional dialogue, the regional Technical Committee, regional-to-MEAE coordination, intra-agency working groups, and the Secretariat-Presidency interface. The platform is owned operationally by UNICEF and the Muskoka Fund secretariat, with capacity transfer designed to carry the platform forward through the renewal cycles France has committed to since the 2010 G8 commitment.
The institutional lesson
For inter-agency coordination platforms the choice is not between generic collaboration tooling and bespoke development. It is between an architectural substrate that matches the coordination taxonomy and a generic substrate that flattens it. Match the architecture to the institution, build the subgroups around the actual coordination structure, transfer ownership to the secretariat that runs the mechanism, and the platform becomes the institutional asset that long-horizon multilateral coordination actually requires.
We build the institutional platforms that long-horizon multilateral coordination actually requires.
Coordination-aware architecture, capacity transfer, and the engineering thinking that joint UN mechanisms demand.
