I lead operations for services that cannot go down

Technology operations and service delivery leader. Monitoring, major incidents, vendors and operating budgets at TMX Group, BMO and BlackBerry. Based in the Toronto area, seeking a senior leadership role in Canada.

Illustrated portrait of Mike Holownych

Operational proof. Scope and figures documented on this site.

Incident leadership

P1/P2 Incident Lead

TMX: a unified L1 monitoring and major incident team through three team leads, with ServiceNow MIM bridges.

People and vendors

9 FTE and 10 contract

BMO: Linux and Windows administrators plus TCS and HCL staff augmentation, in cloud and on-premises environments.

Operating budget

CAD ~$1.6M

BMO annual budget: overtime against service needs, vendor renewals, SLA reviews and performance escalations.

Service ownership

99.999% SLA target

BlackBerry BIS email owner with final production-change authority. The role’s stated service target.

Operating change

17 → 14 people

TMX: CDS Post Trade Modernization merged two support groups into one monitoring and major incident model.

NOC leadership

9 direct reports

Earlier BlackBerry NOC team lead; joined no-notice failovers of live traffic from Waterloo to the UK, at least quarterly.

Where this maps to your mandate.

I look for senior mandates where ownership is clear, authority matches accountability, and the scope is sustainable.

  • Operations or production-support leadership

    TMX monitoring and major-incident leadership through team leads; BMO leadership of 9 FTE and 10 contract resources; BlackBerry NOC team of 9.

  • Ownership and escalation clarity

    Cross-business TMX incident process; BMO production change authority within scope; BlackBerry portfolio change authority for BIS email.

  • Major incident coordination

    TMX P1/P2 Incident Lead (excluding Trayport); ServiceNow MIM integration; earlier major-incident facilitation at BMO.

  • Vendors, budget, and service delivery

    BMO CAD $1.6M operating budget with TCS and HCL contract management; BlackBerry vendor coordination for global email.

  • Practical automation

    BMO Ansible Automation Platform adoption for online banking; independent Nexus Code, Homelab AI, Citable, and Nebula Components.

References from colleagues, from LinkedIn.

Read them all on LinkedIn
One of the qualities that truly sets Mike apart is his ability to remain calm and composed, even in the face of challenges or tight deadlines.
Karthikheyan Somasundaram
Worked with Mike at BMO, March 2024
…he demonstrated strong collaboration and coordination skills with clear understanding of roles and responsibilities of multiple functional groups across the organization.
Salman Salmi
Worked with Mike, December 2013
Mike is an extremely capable individual and possesses the excellent ability to focus in on the technical and business goals, while keeping the big picture in mind.
Arpit Desai
Worked with Mike, September 2012

Experience at TMX Group, BMO and BlackBerry.

Full background and chronology
BIS email service owner scope at BlackBerry: accountabilities in scope and what sits outside the record.
  • TMX GroupManager, IT Operations and Incident ResponseFebruary 2025 to October 2026

    Led a unified L1 Monitoring and Major Incident Management team through three team leads. Accountable for escalations, executive communications, and developing team leads. Scope was monitoring and major incident operations, not infrastructure ownership.

  • BMO Financial GroupSenior Manager, Technology Support (and prior leadership roles)January 2015 to January 2025

    As Senior Manager, led 9 FTE systems administrators and 10 contract resources supporting corporate, finance, and financial-crimes technology across cloud and on-premises environments. Managed an approximately CAD 6 million annual operating budget.

  • BlackBerryGlobal IT Service Manager, BlackBerry Internet Service (Email), and prior NOC leadershipDecember 2008 to August 2012

    Service owner for a global email service with a 999% availability SLA. Accountable for continuity, incident and problem management, vendor coordination, and production change governance within that portfolio. Earlier, led a NOC team of 9 direct reports.

One incident team at TMX Group.

Major incident coordination: monitoring detects and declares, a Chat and Meet bridge opens, the incident lead coordinates recovery, and escalations carry executive updates.
Context
At TMX Group, IT Operations was split into two silos, ComOps for CDS and Site2 Ops for the rest of TMX. After CDS Post Trade Modernization, monitoring and major incident work had to operate as one team.
Responsibility
As Manager, IT Operations and Incident Response, I led the unified team through three team leads, with accountability for escalations and executive communications.
What I did
I amalgamated the two groups onto one operating model, documented an incident process across TMX businesses and subsidiaries (including Trayport) for all severity levels, and led ServiceNow Major Incident Management integration with Google Workspace automation that creates a Chat space and Meet bridge for each troubleshooting team.
Result
A single monitoring and major-incident team, a documented cross-business incident process, and ServiceNow MIM collaboration bridges in place.

Operating budget, people and vendors at BMO.

BMO operating responsibility: people, budget and vendors as three linked areas.
Context
At BMO, corporate, finance, and financial-crimes technology needed sustained support across AWS, Azure, and on-premises environments with employees and contracted capacity.
Responsibility
As Senior Manager, Technology Support, I led 9 FTE Linux and Windows administrators and 10 TCS and HCL contract resources, and managed an approximately CAD $1.6 million annual operating budget.
What I did
I negotiated and managed TCS and HCL after-hours staff augmentation, covering five resources per supplier under fixed-price and time-and-materials arrangements, including renewals, resource counts, SLA and KPI reviews, and performance escalations. I also held production change approval authority and related control attestations within assigned scope.
Result
People leadership across employees and contractors, active vendor operations, and budget accountability at the stated scale.

Operational risk and resilience. Handled inside operations.

Homelab AI rollback and evidence discipline: desired state in Git, Ansible roles and playbooks, a commissioned host profile, an authenticated gateway and rollback tracks.
  • Escalation

    Major incident leadership with executive communications and a documented severity process, at TMX and earlier at BMO.

  • Change

    Change governance and control attestations in assigned scope, with production change authority for a named service portfolio.

  • Vendors

    Renewals, SLA and KPI reviews and performance escalations inside operating budgets, for TCS and HCL at BMO.

  • Recovery

    Stated availability ownership for BIS email, no-notice failovers in the BlackBerry NOC, and desired-state, validation and rollback paths in Homelab AI.

  • Hygiene

    Vulnerability and patch automation for Internal Audit at BMO, and approval controls in Nexus Code. This is operational hygiene; CISO, penetration testing and certification work sit outside it.

Where AI fits

AI is an operational capability: useful use cases, workflows that can be operated, and governance held to the standard of monitoring and change. Homelab AI, Nexus Code, Citable and Nebula Components show recovery discipline in public.

Employer roles were technology operations mandates. The AI work shown here is personal project work, kept separate from enterprise client outcomes.

Independent projects. Four public repositories and products.

Where independent work sits: the enterprise operations foundation first, Nexus Code and Homelab AI second, with the claim boundary explicit.
  • Nexus CodeOpen source (FOSS) · solo · not a commercial productProject notes

    Operational question: how can an agentic coding tool make its actions reviewable instead of hiding them behind a single permission switch?

  • Homelab AIOpen source (FOSS) · solo · not a commercial productProject notes

    Operational question: how do you treat self-hosted inference like an operable system (desired state, validation evidence, and rollback) when you are the only operator?

  • Nebula ComponentsCommercial product · solo · live siteProject notes

    Operational question: how do you diagnose observable landing-page conversion friction with evidence-backed findings, without promising lift?

  • CitableOpen source (FOSS) · Apache-2.0 · soloProject notes

    Operational question: how do you make SEO, AEO, and GEO audit findings defensible by binding them to evidence, change control, and explicit unknowns?