Coordinating an enterprise treasury and risk implementation means managing decisions that never stop multiplying. On Africa Finance Corporation’s Murex MX.3 programme, that means 11+ interlocking workstreams, spanning Front Office, Risk, Operations, Finance, Technology, Data Migration, Interfaces, Collateral Mgmt, and Reporting, each with its own experts, timelines, and dependencies, all moving at the same time.
Insyt Solutions is the PMO and project management partner on this programme. The firm responsible for making sure every part of the delivery connects and stays connected through every phase.
That distinction matters more than most organisations realise when they start.
What we see when we get inside a programme
Every complex implementation carries the same fault lines. They show up at different times and in different forms, but they’re consistent enough that we’ve stopped being surprised by them.
Decisions go unowned. On a multi-party programme, a decision made in one meeting rarely survives to the next unless someone documents it, assigns it, and tracks it. Without that discipline, the same conversation happens three times and the delivery drifts between them.
Problems reach leadership too late. By the time an issue escalates, it’s already expensive. The window to course-correct has closed. A consistent reporting cadence, the same format, the same rigour, every cycle, gives leadership visibility when it can still change the outcome.
Workstreams solve different versions of the same problem. When teams operate without a shared picture of the programme, effort multiplies and outcomes diverge. A Risk team and a Finance team can spend weeks solving what they each believe is the same issue and arrive at incompatible answers. Coordination isn’t overhead. It’s what keeps that from happening.
These aren’t failure modes unique to difficult clients or underprepared vendors. They’re the default on any programme without a strong delivery structure holding the centre.
What it actually takes to hold it together
On the AFC programme, our role is to be that centre. We maintain one source of truth for every open item, decision, and action. We run formal design sign-off gates so scope is agreed before build begins, not assumed during it. We surface risks before they become blockers and manage the dependencies between workstreams so a decision in one doesn’t quietly derail another.
That requires more than project management experience. It requires domain fluency, understanding the difference between a scheduling problem and a valuation problem, between a data issue and a design gap. On a treasury platform, the PMO has to speak the language of the work, not just the language of delivery.
It also requires presence. There’s a difference between advising on a programme and being inside one. Frameworks don’t hold programmes together. People do, showing up week after week, gate after gate, making the coordination actually happen.
The question your programme needs answered
Every organisation planning a complex implementation has a version of the same problem. Multiple workstreams. Multiple vendors. Decisions that need to be made, owned, and tracked across all of them. A leadership team that needs to see risk in time to act on it.
The platform you choose matters. The internal team you assemble matters. But neither is enough without someone whose sole responsibility is holding the delivery structure together from the first gate to the last sign-off.
That’s the question worth asking before your programme begins, not just which platform, but who holds it together.
If you’re planning a complex implementation and want to talk about what the right delivery structure looks like, book a consultation with our team.