Lead Principal Technical Program Manager

Opening Statement (~60 sec)

The way I've consistently raised the bar on planning and execution discipline hasn't been through a formal mentoring title — it's been by codifying what worked into a reusable mechanism deliberately built to outlive the program that created it, and specific enough that another team could adopt it without me in the room%%. The AZ readiness-gate model I built for Dublin became the standard for Beijing and San Francisco; the Architecture Decision Record practice I introduced during an ad-deduplication rebuild was adopted by two other programs; and the charter-plus-guardrail structure from a 260M-member launch became the standing playbook for two subsequent programs. In each case, the artifact — not my presence — is what carried the discipline forward.

Situation

1. Across several large programs, I kept encountering the same gap: strong execution on the program in front of me, but nothing that made the *next* team's execution any faster or more disciplined, because the practices lived in my head rather than in a reusable form. 2. A one-off win doesn't raise the bar for anyone else — it just proves the approach worked once.

Task

My task, self-imposed on every large program since, was to design the operating mechanism — not just deliver the outcome — so the next team facing a similar problem started from a working standard instead of a blank page.

Action

1. 1.On the AZ program, codified the integrated-schedule and Day-1 readiness-gate model as an explicit, documented playbook after Dublin, rather than just carrying the knowledge into Beijing and San Francisco myself.
2. 2.During the ad-deduplication rebuild, introduced a formal Architecture Decision Record (ADR) process specifically to give a team an artifact to register trade-offs during a pivot — a process later adopted by two other programs as standard practice, not something I had to re-pitch each time.
3. 3.On the Prime Video launch, built the charter, risk-sequenced rollout, and guardrail structure as one documented operating model rather than a set of decisions made along the way, so it could be handed to the next program's owner intact.
4. 4.In each case, deliberately wrote the mechanism down in a form specific enough to be adopted without my direct involvement — a named threshold, a named review cadence, a named artifact — rather than leaving it as a lesson only I could apply.

Result

1. The AZ readiness-gate model transferred directly to Beijing and San Francisco, cutting the time to stand up a credible cross-team schedule on each subsequent launch. 2. The ADR process was adopted by two other programs as a standing practice for mid-program architecture pivots. 3. The charter-and-guardrail operating model became the standard playbook for two subsequent pricing and tier programs.

Closing Statement (~60 sec)

I'd be honest that this has been mechanism-driven rather than formal, one-on-one mentoring of other program managers by title — and if OCI's expectation for this role includes direct coaching of other TPMs, I'd want to build on the same instinct deliberately: writing down the standard, not just modeling it. The bar I hold myself to is that a practice I introduce should still be running after I've moved on to the next program — that's the actual test of whether it raised the bar or just solved one problem once.