Case Study Platform Transformation Financial Infrastructure Pre-Launch H1 2026

Leading the Rebuild of the Platform That Processes Every U.S. Options Trade

As Program Manager and Technical Product Owner for the Design and Development team, I have led the OCC Renaissance Initiative: a multi-year transformation replacing a 20-year-old monolithic clearing system with Ovation, a cloud-native clearing, settlement, and risk management platform targeting a H1 2026 production launch across 16 exchanges.

$24T
Daily notional value Ovation is designed to process
40+
Cross-functional team members led across four product streams
H1 2026
Target production launch, first SIFMU cloud-native platform
16
Exchanges coordinating for cutover
Oct 2022
SEC Notice of No Objection secured
0
Critical defects in initial external testing
Q4 2025
External testing scheduled to resume
Jun 2026
Portfolio revaluation changes go live
Role
Program Manager / Technical Product Owner
Team
Design and Development
Organisation
Options Clearing Corporation - Chicago, IL
Programme
Renaissance Initiative (ENCORE to Ovation)
Duration
Dec 2022 to Oct 2024
📌
Programme Status (mid-2025): OCC paused external testing in June 2025 to prioritise internal readiness initiatives. Testing is scheduled to resume Q4 2025 or early Q2 2026. Production launch remains targeted for H1 2026, with portfolio revaluation changes on June 30, 2026. This case study documents completed work and the programme approach.

ENCORE processed every U.S. options trade. It was also a 20-year-old single point of failure that blocked every attempt to modernise it.

OCC clears 100% of listed U.S. options trades. Its ENCORE system required full-platform regression testing for every feature change, creating 6 to 12 month deployment backlogs. The 2020 pandemic exposed how badly the architecture had aged: volatility surged, remote operations became mandatory, and a system designed for stable on-premise conditions could not adapt. A failure at a Systemically Important Financial Market Utility does not stay local. It cascades across the entire U.S. derivatives ecosystem. The problem was not whether ENCORE needed replacing. It was that no safe path to replace it existed.

01
Monolithic Architecture at Breaking Point
Every feature touched every system. Adding one new capability required testing the entire platform, stretching cycles to 6 to 12 months. OCC was not failing in production. It was prevented from responding to market evolution at any speed regulators or clearing members found acceptable.
02
No Safe Modernisation Path
Incremental patching increased technical debt. Big-bang replacement was impossible: OCC cannot tell 16 exchanges the market will be offline. Parallel operations create multi-year synchronisation overhead. A fourth path was needed: complete redesign with zero downtime, coordinated across 16 independent organisations and three regulators simultaneously.
03
No Regulatory Precedent for SIFMU Cloud
No Systemically Important Financial Market Utility had received SEC approval for cloud infrastructure. The regulatory pathway did not exist. Securing it required a multi-year coordination process with the SEC, CFTC, and Federal Reserve before production cloud code could run. This was a programme management challenge before it was a technology one.

Outcomes first. Technology second. Regulatory approval as a product milestone.

Most technology transformations begin with platform or vendor choices. I began with outcome clarity: feature deployment in weeks not quarters, real-time risk visibility, 10x volatility surge capacity, and instant regulatory data access via API. Every technical and team decision cascaded from those four goals.

01
🎯
Outcomes-Led Architecture Decisions
North Star outcomes established before any infrastructure decisions. Architecture choices, vendor selection, and team structure all traced back to specific, measurable goals. Teams that start with technology choices rebuild when requirements shift. This programme did not.
02
👥
Lead Through Expertise, Not Control
As Program Manager and Technical Product Owner for Design and Development, my role was outcome clarity and blocker removal. Designers iterated without approval gates. Developers chose stacks based on requirements. I intervened on regulatory conflicts and cross-team dependencies, not implementation detail. Product leaders who control implementation become bottlenecks.
03
⚖️
Regulatory Engagement as Product Work
Coordinated the multi-year SEC advance notice process, managing review cycles across SEC, CFTC, and Federal Reserve. Translated regulatory concerns into specific architecture requirements the engineering team could build against. The October 2022 Notice of No Objection unlocked the entire cloud-native development phase.
04
🔬
50+ Member Interviews Before Any Design
Research team conducted 50+ stakeholder interviews with clearing members before development began. Findings drove specific design decisions: single sign-on saved 20 minutes of daily login friction. Self-service reporting prevented compliance exposure during audits. Research grounding is why initial external testing produced zero critical defects.
Four Product Streams (40+ People)
11
Clearing Operations
Redesigned trade processing from batch to real-time. Built the settlement engine and member portal with single sign-on, eliminating three-system login friction.
10
Risk Management
Rebuilt margin models for real-time processing. Designed collateral management with proactive monitoring and stress testing for extreme volatility.
10
Data Platform
Created unified data lake from multiple legacy sources. Built self-service reporting infrastructure and API layer for exchange and member integrations.
6
Integration
Mapped all 16 exchange connection requirements. Built testing frameworks enabling the parallel external testing model that compressed a 24-month serial schedule.

Six years of phased delivery toward a single production cutover.

Each completed phase de-risked the next. The June 2025 testing pause is consistent with this discipline: OCC does not launch until every dependency, internal and external, is fully resolved.

2019 to 2022 Complete
Foundation, Architecture and SEC Approval
50+ member interviews before design. Decomposed ENCORE into five independent microservices: clearing, settlement, risk, member, and data. Coordinated the SEC review process culminating in the October 2022 Notice of No Objection: the first cloud approval ever granted to a SIFMU.
2023 to mid-2024 Complete
Platform Build and Internal Validation
Core Ovation platform built to the microservices architecture. Internal testing across all five service domains completed. API layer for exchange and member integrations finalised ahead of external engagement.
July 2024 to June 2025 Round 1 Complete
External Testing: Round 1 with 16 Exchanges
Parallel testing across all 16 exchanges simultaneously. Centralised documentation and issue tracking compressed a 24-month serial schedule. Zero critical defects found across all initial external testing rounds.
June 2025 Current
External Testing Paused for Internal Readiness
OCC paused external testing to focus on internal readiness initiatives. A deliberate sequencing decision, not a setback. The platform is not in question. Resuming external validation before internal preparation is complete creates avoidable risk at a SIFMU-level launch.
Q4 2025 to Q1 2026 Upcoming
External Testing Resumes
Final validation rounds with all 16 exchanges. Confirms all connections, integrations, and cutover logistics meet production readiness criteria. Production cutover does not proceed until all 16 exchanges confirm operational readiness.
H1 2026 Target Launch
Ovation Production Launch
Zero-downtime cutover during a single processing cycle. Portfolio revaluation changes scheduled June 30, 2026. Every U.S. listed options contract will clear on a cloud-native platform for the first time in the market's history.

Programme milestones achieved ahead of the H1 2026 production launch.

Production results will be documented post-launch. The following have been achieved through phases 1 to 3. Anticipated post-launch outcomes are noted where relevant.

First
SIFMU to receive SEC cloud infrastructure approval. October 2022. Now the industry reference for systemically important utility modernisation.
Zero
Critical defects found across initial external testing with 16 independent exchange organisations. Traceable to pre-development member research.
75-85%
Projected reduction in feature deployment time: 6 to 12 months compressed to 2 to 4 weeks, enabled by microservices architecture.
5
Independent microservices replacing ENCORE's monolith. Each deploys without touching the others, the architectural change driving deployment speed gains.
40+
Cross-functional team members across four product streams, coordinated across design, development, data science, and integration domains.
$24T
Daily notional value the platform is designed to process when it goes live in H1 2026 across all 16 participating exchanges.
Upcoming Milestones
Q4 2025
External Testing Resumes
Final validation rounds with all 16 exchanges following the June 2025 internal readiness pause.
H1 2026
Ovation Production Launch
Zero-downtime production cutover. Every U.S. listed options contract transitions to the cloud-native Ovation platform.
June 30, 2026
Portfolio Revaluation Changes
First post-launch capability release on Ovation. Enabled by independent microservices deployment without full regression cycles.

What leading a SIFMU transformation teaches about programme management at scale.

A Planned Pause Is Discipline
The June 2025 decision to pause external testing was the correct call. Resuming with 16 exchanges before internal readiness is confirmed wastes partner capacity and risks exposing internal gaps during final validation. The discipline to pause a multi-year programme when sequencing demands it is what separates a controlled launch from a compromised one.
Regulatory Approval Is a Product Workstream
Securing the first-ever SIFMU cloud approval required understanding SEC risk concerns deeply enough to design an architecture that addressed them before the formal notice was filed. The October 2022 approval was the product of sustained relationship building and translating regulatory risk language into specific engineering requirements.
Research Is the Cheapest Risk Mitigation
Zero critical defects in initial external testing with 16 independent exchange organisations was not coincidence. It was the direct result of 50+ member interviews before development began. Designs addressed actual workflows. The cost of pre-development research is trivially small compared to discovering design errors during external validation of a $24T clearing platform.
External Coordination Is a Different Discipline
Managing 40+ internal team members across four streams is demanding. Coordinating external testing across 16 independent exchange organisations, each with their own schedules and compliance requirements, is a fundamentally different programme management challenge. Parallel testing with standardised documentation was the only viable way to compress a 24-month serial schedule.

If you are building something that cannot afford to fail, let's talk.

Complex programmes. Regulated environments. High-stakes stakeholder landscapes. That is where I do my best work.

Start a Conversation View Full Portfolio
More Case Studies
Compliance Platform ↗ Compliance Governance ↗ Compliance Intelligence Platform ↗ VoteGuard ↗ Family Wealth Simulator ↗ EmPact ↗
Disclaimer: The views, analysis, and observations expressed in this case study are solely my own and do not represent the positions, strategies, or opinions of the Options Clearing Corporation (OCC) or any affiliated entity. This case study is published for professional visibility and portfolio purposes only. All figures referenced are based on my personal recollection and have been generalised where appropriate to protect confidential information.