Maintain the existing structure
Avoids disruption but sustains distortion and reactive reprioritization.
65%delivery cycle-time reduction
340 → 120days average delivery cycle
~500initiatives reviewed and reclassified
75+tracking fields normalized into one lifecycle
The operating problem
What leadership was facing.
T-Mobile's Revenue Technology organization managed ~500 initiatives across monetization systems and business process programs, tracked through 75+ inconsistent fields with no standardized lifecycle. Too much work appeared active before it was funded, defined, or ready for build. That portfolio congestion obscured real capacity, increased context switching, and stretched average delivery cycles to ~340 days. Execution capability was not the issue — demand management and readiness discipline needed a cleaner operating model.
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.
- Led 7 product managers as dotted-line reports — logging their progress against readiness gates — and chaired the cross-team governance forums for the 100+ contributors they represented
- 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
- Translated an enterprise project-to-product funding shift into portfolio tracking, governance cadence, and executive reporting for the Revenue Technology workstream
- 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 more 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
Intake and signal modules
Supporting references
Revenue Technology colleagues reinforced the portfolio-reset story.
Excerpts from LinkedIn recommendations tied to the T-Mobile Revenue Technology engagement.
T‑Mobile
He navigated a complex portfolio of initiatives with ease and became a central resource for my whole team to go to with questions.
He excels at PMO leadership, balancing innovation with analytical precision … a solutions-oriented critical thinker who can quickly analyze complex situations and determine the best path forward.
He successfully managed a complex portfolio of initiatives, provided invaluable insights to leadership, drove process improvements, and encouraged technology adoption.
Continue