Maintain the existing structure
Avoids disruption but sustains distortion and reactive reprioritization.
The operating problem
What leadership was facing.
T-Mobile's Revenue Technology organization managed ~500 initiatives across revenue systems and business process programs, tracked through 75+ inconsistent fields with no standardized lifecycle. A material portion of work labeled “active” was unfunded, under-defined, or stalled. The artificial congestion obscured real capacity, increased context switching, and stretched average delivery cycles to ~340 days. Execution capability was not the issue — distorted WIP and weak readiness discipline were.
Options on the table
The decision, framed honestly.
Re-platform portfolio tooling
Structural consistency at the cost of delay and adoption resistance.
Reset signal within the existing system
Reclassify work, normalize lifecycle definitions, and separate qualification from execution — without replacing the platform.
What I put in place
The structure behind the outcome.
- Reviewed ~500 initiatives and reclassified stalled or under-defined work out of the active pipeline
- Normalized 75+ tracking fields into one consistent lifecycle structure with staged readiness gates from concept through launch
- Implemented a dual-rail model separating qualification from execution so work entered delivery only when build-ready
- Shifted executive reporting to change-based discussions focused on risk and sequencing rather than status reconciliation
- Introduced governed generative AI as a clarity layer — documentation quality, meeting summaries, onboarding — with human review and approval authority intact
What changed
The operating difference.
Average delivery cycle time fell 65%, from ~340 to ~120 days. Throughput rose without added headcount. Context switching declined as sequencing ran against real, build-ready capacity, and executive confidence in portfolio reporting strengthened.
Why it mattered
The executive read.
Revenue Technology supports core monetization systems. Restoring accurate WIP visibility and enforcing readiness discipline aligned capacity to priority and made delivery predictable in a revenue-critical environment. This was a correction of portfolio decision structure — not a process expansion.
Related operating proof:
Messy demand to executive review route
Intake and signal modules