CS / 01 · Operating System

Multi-site governance & execution.

Established a single plan-of-record across 5 global sites — 4,700+ issues driven to closure, ~$0.9M/yr in costs avoided, $15M+ in programs shipped.

Role: Sr. Program Manager
Scope: 5 sites · 100+ contributors
Timeline: 2023 — 2026

$15M+

Programs shipped

4,700+

Issues closed

~$0.9M/yr

Costs avoided

13%

TTM cut

01 / Context

What was broken.

The starting state

Problem

The starting state.

5 distributed sites (US, India, Singapore, Ukraine, Pakistan) each running their own cadence, tools, and definition of done.
No single plan-of-record — exec reporting reconstructed from email threads and Slack screenshots.
Cross-site dependencies surfaced too late, blocking critical path on hardware/firmware/software handoffs.

Approach

What I built.

Stood up a weekly risk & dependency review with named owners across all 5 sites — single GitLab board became the source of truth.
Standardized stage-gates (req → design → EVT → DVT → PVT) and program RAID across every workstream.
Built exec-ready reporting cadence (weekly status, monthly steering) so leadership saw the same numbers everyone else did.
Aligned 8 XFN teams (HW/FW/SW/Mfg/QA, 50+ engineers) on a shared milestone calendar with explicit handoff criteria.

02 / Mechanism

How it actually worked.

5 sites · 1 program

Operating System $15M+ Shipped

5 sites · 1 program CS / 01

03 / Outcome

The numbers that mattered.

Outcome

Headline result

$15M+

Total program value shipped on time across 5 global sites — $0.9M/yr avoided through one disciplined operating system.

04 / Takeaway

The work is the discipline the meeting forces.

In one line

A weekly risk-and-dependency review with named owners turned five disconnected sites into one program. The cadence is mundane; the alignment it produces is what shipped $15M in product.