At TMX Group I was Manager, IT Operations and Incident Response from February 2025 through October 2026. The mandate was L1 Monitoring and Major Incident Management. Infrastructure ownership sat elsewhere on the org chart.

In a live P1 or P2, people look for one name on the bridge and one name on executive updates. They also ask who owns the company-wide incident playbook. Those are related jobs, but they were separate assignments for me.

What live P1 and P2 lead meant for me

I served as Incident Lead for P1 and P2 incidents across TMX, excluding Trayport.

In that role I coordinated technical recovery, escalations, and executive updates while the incident was active. I did not hold live P1 or P2 incident lead for Trayport.

What process design covered

Separately, 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. Trayport was in scope for the process. It did not become a live P1 or P2 lead assignment for me.

Why the split matters

Two statements are both true and need to stay separate:

  • live P1/P2 incident lead across TMX excluding Trayport
  • cross-business incident process, including Trayport, for all severity levels

Anyone routing a major incident needs the first one before the first bridge invite goes out. Anyone assessing my work needs the second one to see the scope of the process I built. Merging them into one line overstates one assignment or understates the other.

What stayed outside the mandate

I did not own infrastructure at TMX. Monitoring and observability used Splunk Observability Cloud, Dynatrace, and Grafana to support detection and handling. Those tools sat inside the monitoring and major incident mandate, not platform build ownership.

I led ServiceNow Major Incident Management integration, including Google Workspace automation that creates a dedicated Chat space and Meet bridge per troubleshooting team. That integration did not change who held live lead on a Trayport P1 or P2.

My TMX position was impacted in a restructuring in October 2026. I am seeking senior technology operations or service delivery leadership in Canada. The experience page on this site carries the same dates and the same Trayport boundary.