Case Study · Euroclear · September 2007 to January 2008
Project Manager · via ECL Management Consultants
Zero disruption is a governance outcome, not a technical one.
The Brief
It was very important to navigate fully around the tolerance for error: which was essentially zero, at a scale where error is systemic. ESES unified settlement across the Euronext-zone markets, and this migration moved cross-border regulatory custody onto the new platform against a European Central Bank compliance deadline, for an infrastructure on which 3,000 member participants depended daily. In market infrastructure, disruption is not a degraded experience; it is a settlement failure with regulatory and financial consequences for every member.
The Approach
The programme ran under PRINCE2 with Agile delivery inside it: formal stage gates and documented decisions where the regulatory weight demanded them, iterative working where it did not: governance proportional to risk, not maximal governance everywhere. Readiness was treated as a measurable programme property, not a feeling: tracked, tested, and improved 35% ahead of go-live through rehearsed cutover, verified fallback, member communication, and evidence at every gate that the organisation, not just the software, was ready.
Fig. 01 · Cutover governance to a fixed deadline
Zero disruption was rehearsed, not hoped for.
3,000 members depended on this date.It held.
Recreated from the programme's governance structure. No client-internal material reproduced.
Judgement Call
The deadline as a design constraint. An ECB deadline cannot be negotiated, so everything else had to be: scope was sequenced, decisions were forced to their latest responsible moment and no later, and the critical path was protected with the discipline of a programme that knows exactly which date it cannot miss. Fixed time, managed scope: the same shape later formalised in DSDM-based delivery elsewhere in this portfolio.
What Was Delivered
- Stage-gate governance refusing to pass unverified work, with a decision log that kept anyone from improvising at 2am
- A readiness programme improving measured readiness 35% before cutover
- Rehearsed cutover and real, verified rollback plans
- ECB-compliant go-live, on the regulatory deadline, with zero disruption for 3,000 participants
The repeat
The Outcome
The migration went live compliant, on time, with zero disruption. This is the engagement most responsible for the release-governance habits (approvals, test evidence, rollback planning, controlled windows) applied in every delivery since, including current Salesforce work. Delivering to a regulator's date, under a regulator's scrutiny, teaches a permanent lesson: it is not enough to have done the work; you should be able to show it.