Automation for Operations -- T-Mobile Journey#

Issa Abu Eid, Udaya Tadikonda — T-Mobile USA

• Why: A Tier-1 operator's account of moving from manual workflows to automation-first operations, with the guardrail design spelled out — the "how do we make automated actions safe" question is where most automation programs actually fail, and this addresses it head-on.
• What: Reactive and proactive automation categories: alert correlation/deduplication and auto-created tickets with SLA clocks starting at detection, multi-signal service-aware outage detection with impact identification before customers notice, guarded break/fix (explicitly not automating ambiguous failures or one-off fixes; every automated action gated by redundancy-aware checks, capacity validation, audit trail, and rollback), pre/post-change validation with policy-driven rollback evaluation, continuous compliance/drift/EOL-EOS monitoring, and capacity early-warning with trend analysis. A maturity model — Visibility → Intelligence → Enablement — with the honest sequencing rule that automation cannot succeed without reliable state and that early efforts must focus on visibility, not action. AI is framed as an assistive layer on top of strong automation foundations, not a replacement for operator judgment.
• How: Automation treated as production software; one deliverable described is a centralized internal platform used by 1,300+ engineers with incident correlation across multi-vendor networks.
• Where applicable: T-Mobile US Tier-1 scale (org-specific tooling and metrics), but the guardrail taxonomy, the "explicitly not automated" list, and the visibility-first phasing are directly transferable patterns for any operations organization, including much smaller ones.