Core takeaway: service ownership on a global customer-facing email platform is not a title for "knows everything at the company." On BlackBerry Internet Service (Email) it meant final production-change authority and continuity accountability inside one portfolio, with a stated 99.999% availability SLA on the résumé.
I held that mandate as Global IT Service Manager, BlackBerry Internet Service (Email) from January 2011 to August 2012. Earlier at BlackBerry I moved through NOC roles from December 2008 through December 2010, including NOC Team Lead with 9 direct reports.
This note stays inside verified BIS email facts. It does not describe every BlackBerry product line.
What the service owner actually owned
The site résumé defines service ownership for this portfolio as final production-change authority within the assigned portfolio and accountability for continuity of that customer-facing global email service.
That definition maps to operating work, not abstract leadership language:
- incident and problem management inside the portfolio
- vendor coordination when the service needed external capacity or support
- production change governance so live email did not move on ambiguous sign-off
Business stake: email at carrier scale fails in the boring places. Change windows, vendor handoffs, and unclear approvers turn small defects into customer-visible outages. Service owner accountability exists so those decisions have a named end point before traffic moves.
The SLA is a contract boundary, not a personal scorecard
The résumé states a 99.999% availability SLA for the global email service in this portfolio.
I was accountable for that service level as the named owner. I am not claiming personal uptime heroics, invented MTTR, or incident counts beyond what the record supports.
Public incident detail beyond SLA ownership and failover participation is thin on the résumé. This article does not fill that gap with fiction.
High-agency read: treat the five-nines figure as the operating contract you inherit as service owner, then ask how change authority, vendor coordination, and problem management connect to it. Treating SLA as a résumé decoration is how hiring screens miss whether someone actually held production authority.
NOC work before the service manager title
Before the Global IT Service Manager role I was NOC Team Lead with 9 direct reports through December 2010.
That leadership was operational, not a parallel product mandate. It built context for how live email traffic behaved before I held portfolio-level change authority.
The résumé also records participation in no-notice, leadership-initiated failovers of live production traffic from Waterloo to the UK at least quarterly.
Scar tissue from that pattern: scheduled drills are rehearsed. No-notice failovers are where routing, monitoring, and handoff assumptions get tested without a convenient narrative.
I participated in that operating reality. I am not inventing a single outage story or recovery time to make the résumé sound more dramatic.
What this record does not prove
BlackBerry employment on this chronology runs December 2008 to August 2012 across NOC and BIS service management roles. If you need someone who has held named production authority on a global email service, coordinated vendors under an SLA, and led NOC staff before taking a service owner title, use this record.
Do not use it as proof that I owned every technology decision BlackBerry shipped in that era. The portfolio boundary is the point.
I am seeking a senior technology operations or service delivery leadership role in Canada. The experience page on this site carries the same dates and role titles.