Program Atlas case study

See how a partner’s delay affects a launch date. Compare ways to recover time, understand each cost or remaining risk, and record who needs to make the next decision.

The product choice: Explain the effect of a delay before choosing which cost or change in scope to accept. Try the sample · Follow the walkthrough.

Experience and decision

My program work at Raytheon included integrated plans, critical paths, dependencies and phased delivery. This example isolates how a changed dependency becomes an explicit scope, cost or timing decision. This is a separate fictional portfolio exercise; its records, rules and results do not reproduce an employer system.

Decision to challenge: Which recovery is worth its cost, and who must accept the remaining risk? A date that improves on screen does not establish partner capacity or authorize a changed commitment.

Product and program ownership

Mo directed this prototype toward program management: cross-functional dependencies, commitment consequences and accountable escalation. The Northstar sample is original fictional data. AI assisted implementation, review and software verification. The work is not presented as manual-only development, employer research, a defense program tool or a customer outcome.

Problem and product choice

A shared partner pack affects two downstream routes. Independent readiness flags could show healthy roots while the overall pilot slips. The product therefore uses a dependency map/list and immutable baseline, lets a lead inspect the cause, and requires review of a recovery’s patch, cost and residual risk before confirmation.

The smallest observable outcome is a causal executive exception brief and complete escalation record. A status-only dashboard was rejected as the principal alternative because it leaves the commitment-changing decision implicit. A resource allocator and earned-value system were excluded because they would require a different validated contract.

Implemented decision story

A four-day partner delay consumes one day of float and slips the baseline by three working days. Scope reduction recovers two, resequencing one and contingency two in the declared original scenario. Their consequences differ: evidence breadth, real-contract reconciliation or fictional incremental spend. None removes the need to acknowledge a remaining exception. The escalation records accountable owner, decision needed, evidence and due point; it never applies a recovery through saving a record.

The review separates exploration from commitment. Changed state invalidates an earlier preview, confirmed work can restore in this browser, and Undo is limited to the last confirmed snapshot. Invalid saved work requires deliberate recovery. The exported brief represents one reviewed point in time, so a later scenario must not be mistaken for the commitment already recorded.

Evidence and limits

Software verification is recorded in Validation.md, with independent hand-calculated dates and invalid graph/state cases separated from browser journeys. These checks establish behavior in the bounded prototype. They do not establish user comprehension, acceptance of the recovery, actual partner capacity, forecast accuracy, commercial impact or Mo’s personal review. Initial public source/deployment and live-file parity passed independent release verification; the exact evidence is recorded in Validation.

Proposed evaluation: present the original and delayed scenarios without prompting the cause. Ask a program lead to identify the upstream impact, explain criticality versus slack, select a recovery and name the unresolved risk. Score cause identification and escalation completeness separately from completion time. No such research has been performed.

Next investment decision

Before adding more workstreams or schedule sophistication, compare the exception brief with the lead's existing status review using the same delayed scenario. Can the lead explain why a recovery still leaves an exception and identify the owner who must accept the changed commitment? If the map improves scanning but not that decision, strengthen the handoff and escalation explanation. Any operational investment also requires validated calendar and resource assumptions plus agreed decision authority; the sample's unlimited parallel capacity cannot substantiate partner feasibility or the value of contingency spend.