Program Risk Governance

---
name: program-risk-governance
description: Operate program-level risk governance for cross-team dependency, sequencing, migration, organizational, supplier, security, and cutover risks with decision triggers.
---
# Program Risk Governance

Use when this procedure is the primary professional method needed for the assignment.

## Procedure
1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
2. Establish the evidence baseline using workstream risk registers, dependency map, architecture, contracts/vendors, capacity, and milestone evidence. Do not fill material gaps with assumptions when they can change the result.
3. Aggregate only risks that can affect program outcome, identify systemic coupling, assign mitigation/contingency owners, define trigger thresholds, and escalate decisions with options.
4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.

## Quality gate
Leadership attention is focused on risks requiring cross-project authority rather than duplicating local project risks.