Mandate context
I was Manager, IT Operations and Incident Response at TMX Group from February 2025 to October 2026. The mandate was L1 Monitoring and Major Incident Management. Infrastructure ownership sat outside that scope.
At TMX, businesses and subsidiaries could carry different escalation habits until one documented incident path applied group-wide.
What cross-business process work covered
I designed, documented, and implemented an incident management process across TMX businesses and subsidiaries, including Trayport, covering all severity levels.
That work was process and operating discipline: shared severity language, escalation expectations, and one documented path across entities. It applied to every business unit in scope, not only the incidents where I held live lead.
Why this was not the same job as live incident lead
I served as Incident Lead for P1 and P2 incidents across TMX, excluding Trayport. In that role I coordinated recovery, escalations, and executive updates while the incident was active.
Process ownership could include Trayport. Live P1 and P2 lead did not.
Live lead answered who coordinated recovery during an active P1 or P2. Process design answered what path every business and subsidiary used across severities, including Trayport.
What design through implementation meant in practice
Design meant one severity model and escalation expectations that could apply when different businesses page different on-call paths.
Documentation meant a written process every entity could reference before severity escalates, not tribal knowledge locked in one support group.
Implementation meant the process was usable in operations, aligned with how monitoring and major incident work ran after CDS Post Trade Modernization consolidated ComOps and Site2 Ops into one team.
I amalgamated those two support groups onto one monitoring and major incident operating model. Documenting incident management across businesses, including Trayport, for all severity levels sat on the same timeline as that consolidation because post-modernization operations need one escalation picture.
Tools inside the mandate, ownership outside it
Monitoring and observability used Splunk Observability Cloud, Dynatrace, and Grafana to support detection and handling. Those tools sat inside the monitoring mandate, not platform build ownership.
I also led ServiceNow Major Incident Management integration, including Google Workspace automation that creates a dedicated Chat space and Meet bridge for each troubleshooting team. That integration supported collaboration during incidents. It did not change who held live lead on a Trayport P1 or P2.
How process work connected to executive communication
When I held live P1 and P2 lead, executive updates stayed concise and focused on business impact. They covered what was affected, scope of impact, what we knew, what we did not know, actions underway, and when the next update could be expected.
The cross-business process gave shared language for severity and escalation before those updates started. The live lead role handled recovery coordination and the update cadence while the incident was active.
Post-incident review sat in the same operating picture: reconstructing timelines, examining detection and escalation effectiveness, and turning findings into accountable corrective actions through problem management. That rhythm was part of how the documented process was meant to behave after service restoration.
Mandate boundaries
My TMX position was impacted in a restructuring in October 2026. I am seeking senior technology operations or service delivery leadership in Canada.