Keeping the James Webb Space Telescope funded.

In 2011 and 2012 the James Webb Space Telescope, NASA's flagship astrophysics mission, was over budget, behind schedule and facing cancellation by Congress. As Budget Request Team Lead with Booz Allen Hamilton, I led the team that turned complex contractor data into one defensible funding case, and the program was replanned at approximately $8B with a path to launch.

250+

Organizations across 14 countries brought under one risk framework

$8B

Approximate replan baseline defended during congressional funding reviews

Network diagram linking every prime and subcontractor critical path

2021

Program preserved and launched on December 25, 2021

The challenge.

Disconnected risk across hundreds of contracts.

The program ran on hundreds of independent contracts that each looked manageable on its own. Together they hid how far cost and schedule had drifted. When the program came under congressional review, leadership faced five systemic bottlenecks.

Siloed contractor reporting. Each prime contractor reported against its own schedule, so leadership had no single view of the total program.
Delayed subcontractor visibility. Subcontractor slips were reported late, after downstream critical paths had already been affected.
Separate cost and schedule tracking. Cost and schedule risks were evaluated apart, which hid how schedule delays pushed up the budget baseline.
Unaddressed off-track vendors. Several subcontractors drifted on cost, schedule and scope at the same time, with no formal reconciliation plans.
Fragmented data. Congressional oversight needed one defensible budget figure, but the supporting data was spread across hundreds of vendor reports.

The key measure.

Total cost and launch date confidence.

Program baseline = total program cost + target launch date, tied to an explicit confidence level

One baseline for every congressional review

Every dollar and milestone in the budget package traced back to specific contractor work packages and quantified risk bands. That provenance let leadership defend the budget under intense oversight review.

The three stage method.

The ALIGN™ framework applied to program funding. Assess and Lead in Stage 1, Integrate and Grow in Stage 2, Normalize in Stage 3.

Stage 1, establish the program view

Contractor scope audits. My team reviewed every prime contractor to audit scope, spend and schedule health.

A single network diagram. Hundreds of prime and subcontractor schedules were combined into one visual network diagram, with the critical path and parallel dependencies on a single page.

Stage 2, connect schedule slips to cost exposure

Delivery tolerance bands. Every major delivery got a risk range based on that vendor's technical and schedule risks.

A unified risk framework. Risk scoring was standardized across all work packages, so a schedule delay showed up immediately as a projected cost variance.

Stage 3, reconcile off-track vendors and secure funding

Vendor reconciliation plans. Each subcontractor that was over cost, slipping schedule or drifting in scope got a tailored remediation plan.

The congressional budget package. I led the analysis, writing, risk modeling and review of the formal budget request presented in congressional funding sessions.

Findings and remediation.

The pattern in each program area and the solution put in place.

Program area	Legacy operational pattern	Framework solution implemented
Program visibility	Primes reporting in silos with no unified view	A single network diagram linking every prime and subcontractor schedule on one page
Subcontractor risk	Slips reported after downstream work was affected	Delivery tolerance bands capturing lead time and schedule slack
Risk modeling	Cost and schedule tracked in separate systems	Unified risk scoring that maps schedule slips directly to cost exposure
Vendor drift	Off-track subcontractors working without recovery plans	Reconciliation plans with corrective actions for behind-schedule subcontractors
Governance	Unverifiable budget requests drawn from scattered reports	An audit-ready budget package with full provenance to source data

Executive deliverables and outcomes.

Five deliverables behind the funding case.

A program network diagram

One view of every prime and subcontractor schedule, mapping parallel paths and critical dependencies.

Quantified delivery tolerance bands

Risk ranges for every milestone, showing how much schedule float existed before launch dates moved.

An integrated cost and schedule risk model

One risk framework where schedule delays showed up automatically as projected budget impact.

A subcontractor reconciliation blueprint

Remediation plans for every vendor off track on cost, schedule or technical scope.

A defensible congressional funding case

An audited budget package that kept federal funding in place for the program through launch.

Why this matters for technology spend.

The same failure mode shows up in an $8B telescope and in an enterprise technology portfolio.

In both cases, dozens of siloed vendor contracts run without a single view of the whole. The method that fixes it stays the same.

Bring every commitment into one visual system.
Apply a standard risk framework that links operating performance to financial exposure.
Give leadership a defensible baseline number to protect margin and win executive backing.

Related case studies

$1B+ defense and space programs governed for DoD and NASA. Read the case study
$100M in avoided technology costs for a Series C company. Read the case study