Manage Program Risk Across Hardware and Software Teams

Aerospace programs follow structured risk management processes (typically based on MIL-STD-882, SAE ARP4761, or company-specific standards). Each risk has a probability rating (1–5), severity rating (1–5), and a risk priority number (RPN = probability × severity). Risks scoring above a threshold require documented mitigation plans and regular review. Most programs maintain risk registers in Excel with 100–300 rows. These spreadsheets are reviewed monthly in 2-hour risk review meetings where half the time is spent finding the right row.

Replace the spreadsheet with a risk canvas organized by risk category: • Technical Risk — design complexity, material properties, testing limitations, integration challenges • Schedule Risk — supplier delays, test facility availability, certification timeline • Programmatic Risk — funding, staffing, requirements changes, subcontractor performance • Safety Risk — failure modes, human factors, maintenance procedures Each risk card includes probability and severity in the card notes. Color-code by RPN: red (15–25), yellow (8–14), green (1–7).

For each risk card with RPN > 10, create a mitigation card describing the planned action. Draw a depends-on connector from the risk to its mitigation. Mitigation cards have their own status workflow: Planned → In Progress → Completed → Effectiveness Verified. The "Effectiveness Verified" step is critical in aerospace — a mitigation isn't closed until you've confirmed it actually reduced the risk. Add a re-assessment date to the risk card after mitigation. A satellite subsystem team tracking 45 risks found that 8 mitigations marked "Completed" had never been verified. Two of those risks had re-emerged in testing.

Before each monthly risk review, run AI Risk Analysis on the canvas. The AI produces: • Risks sorted by RPN (highest first) • Risks with overdue mitigations • New risks added since last review • Risks whose probability or severity changed Project this during the review meeting. The team works directly on the canvas — updating RPNs, assigning new mitigations, closing resolved risks. Meeting time drops from 2 hours to 45 minutes because no one is searching through spreadsheet rows.

Draw relates-to connectors from high-severity risks to the program milestone cards they threaten. This makes it visible during schedule reviews which milestones carry the most risk. For programs approaching CDR (Critical Design Review) or PDR (Preliminary Design Review), filter the canvas to show only risks with connectors to the upcoming milestone.