Maya Patel·
Our ERP migration risk register, scored and heat-mapped, with the year-end-close trap caught up front
Conduct structured risk assessments with probability-impact scoring, heat maps, and prioritized mitigation strategies.
Enterprise Risk Assessment & Mitigation Planner
You are a chief risk officer at a global enterprise. Conduct a comprehensive risk assessment for the following initiative.\n\nINITIATIVE/PROJECT: {{project_or_initiative_name}}\nCONTEXT: {{business_context_and_environment}}\nSTAKEHOLDERS: {{key_stakeholders_affected}}\nTIMELINE: {{project_timeline}}\nBUDGET/RISK TOLERANCE: {{budget_or_risk_tolerance_level}}\n\nOUTPUT — Complete Risk Assessment Document:\n\n## 1. RISK IDENTIFICATION\nIdentify risks across these 6 categories (minimum 3 per category = 18+ total):\n\n**Strategic Risks** — Market, competition, reputation, M&A\n**Operational Risks** — Process, people, systems, supply chain\n**Financial Risks** — Liquidity, currency, credit, pricing\n**Compliance/Legal Risks** — Regulations, contracts, litigation, IP\n**Technology Risks** — Security, obsolescence, integration, scalability\n**External Risks** — Macroeconomic, geopolitical, natural disasters, pandemic\n\nFor each risk provide:\n- Risk ID (e.g., R-001)\n- Risk statement (If [event], then [impact])\n- Risk category\n- Risk owner (role)\n- Root cause analysis (use 5 Whys)\n- Early warning indicators (3 per risk — what to monitor)\n\n## 2. RISK SCORING MATRIX\nScore each risk on a 1-5 scale for:\n- Probability (1=Rare, 5=Almost Certain)\n- Impact on Cost (1=Negligible, 5=Catastrophic)\n- Impact on Schedule (1=Negligible, 5=Catastrophic)\n- Impact on Quality/Reputation (1=Negligible, 5=Catastrophic)\n\nCalculate: Risk Score = Probability × Average Impact\n\nClassification:\n- 1-5: Low (monitor)\n- 6-10: Medium (manage actively)\n- 11-15: High (mitigation plan required)\n- 16-25: Critical (escalate immediately, contingency required)\n\n## 3. RISK HEAT MAP\nText-based visualization: 5x5 matrix with risks plotted by Probability (Y) vs. Impact (X). Show concentration zones.\n\n## 4. TOP 10 RISK REGISTER\n| Rank | Risk ID | Risk Statement | Score | Treatment Strategy | Owner | Target Date | Status |\n|------|---------|---------------|-------|-------------------|-------|-------------|--------|\n\n## 5. MITIGATION STRATEGIES\nFor each Critical and High risk:\n- Treatment option: [Avoid / Reduce / Transfer / Accept]\n- Specific mitigation actions (3-5 per risk)\n- Contingency plan (if mitigation fails)\n- Resource requirements (budget, people, time)\n- Residual risk score after mitigation\n\n## 6. RISK MONITORING DASHBOARD\n- KPIs to track (5-7 metrics)\n- Review cadence (daily/weekly/monthly triggers)\n- Escalation thresholds and pathways\n\n## 7. RISK CULTURE RECOMMENDATIONS\n- Communication plan for risk awareness\n- Training needs\n- Incentive alignment for risk reporting
Ergebnisse
## Enterprise Risk Assessment — ERP Migration to Cloud (SAP S/4HANA)
**Context:** replacing 14-year-old on-prem ERP across 6 plants. **Timeline:** 18 months. **Risk tolerance:** low (finance-critical).
### 1. Risk Identification (sample, 18 total across 6 categories)
| ID | Statement (If→Then) | Category | Owner | Early Warning |
|----|---------------------|----------|-------|---------------|
| R-003 | If data migration corrupts GL balances, then close cannot complete | Operational | Controller | Reconciliation breaks in UAT |
| R-007 | If key SAP architect leaves, then timeline slips 3+ months | Operational | CIO | Recruiter calls, PTO spike |
| R-011 | If go-live coincides with year-end close, then finance overloads | Strategic | CFO | Calendar overlap in plan |
### 2. Scoring (Probability × Avg Impact)
R-003: 3 × 5.0 = **15 (High)** · R-007: 2 × 4.3 = 8.6 (Medium) · R-011: 4 × 4.0 = **16 (Critical)**.
### 3. Heat Map (Probability Y ↑ / Impact X →)
```
P5 | R-011
P4 |
P3 | R-003
P2 | R-007
P1 |__________________________
I1 I2 I3 I4 I5
```
### 4. Mitigations
- **R-011 (Critical):** mandate go-live no later than Q3, hard-block December cutover. Contingency: parallel-run legacy for one close.
- **R-007:** retention agreement + documented runbooks + a shadow architect from day one.
### 5. Monitoring
KPIs: UAT reconciliation pass rate, architect retention, cutover-date drift, defect burn-down. Weekly steering review; escalate any Critical to the board.
Modell: Claude Sonnet 4
22 Likes8 SavesScore: 14
1 Kommentar
Noah Steiner·
Pasting this into Notion right now.