For MDBs and DFIs, the strongest platform on paper is not always the right one. A risk platform must support – or deliberately improve – how the institution governs decisions, divides responsibility across risk, Treasury, operations and technology, and moves data between them. Functionality is easy to compare. Fit is harder, and it often decides whether the platform works in practice.
Selection should therefore start with the operating model: the one in place today, and the one the institution intends to run.
1. Understand the current state without preserving its weaknesses
A current-state view should set out who is responsible for what, where decisions are made, how data flows, which controls apply and where work passes between teams. Handoffs are often where friction sits. The risk is that mapping the current state quietly turns it into the target, and workarounds built around an old system get written in as requirements. The current state should inform selection, not define the future design.

Selection should move from current-state understanding through future-state choices to delivery readiness.
2. Translate operating needs into selection criteria
Requirements written inside one function describe that function’s screens. Requirements built across risk, Treasury, operations and technology describe the institution’s process, and they make better evaluation criteria. They also connect three things often kept apart: business requirements, operating needs and implementation strategy. A platform that scores well, but assumes an operating model the institution does not want or a delivery path it cannot staff, is not the safe choice it appears to be.
3. Evaluate cross-functional fit, ownership and handoffs
Functional coverage is only one dimension. Data and interfaces decide whether the platform can be fed and reconciled at reasonable cost. Ownership decides who maintains configuration and static data once implementation support steps back, which is easier to settle before selection than after. Operating-model fit decides whether responsibility sits where governance intends it. Gaps and assumptions should be recorded before a preferred solution is chosen; afterwards, they tend to become change requests.

Functional coverage is only one of four dimensions supporting a defensible selection.
4. Use selection evidence to prepare for delivery
Selection produces requirements, gap positions, assumptions, interface expectations and ownership decisions. Kept in order, that evidence gives implementation planning, testing, governance and delivery readiness a practical starting point, and it supports the value-for-money scrutiny that follows. Where it is lost, programmes often begin by rediscovering decisions already made. Selection evidence does not stop being useful once delivery begins.
Prodktr’s perspective:
A risk platform is bought as technology and lived with as an operating model. Prodktr works client-side with MDBs, DFIs and other financial institutions: setting out the current state honestly, agreeing what should change, turning that into criteria the whole institution recognises, and keeping the selection evidence defensible from evaluation through to delivery.
Contact us for more information.

