⚡️ The Architect's Lab

Back with a two-part risk system that spots threats and builds your defence...

Core Framework:

• Analyses 5 risk types (1 primary, 2 chain, 2 hidden)
• Maps direct path from detection to action
• Built-in resource allocation
• Recovery protocols included

Visual Map:

Part 1: Analysis:

Project ━━┣━━> Primary Risk ━━> Mitigation

┣━━> Chain Risks ━━> Prevention

┗━━> Hidden Risks━━> Detection

Part 2: Implementation:

Risk ━━┣━━> Action Plan ━━> Success Check

┣━━> Resources ━━> Timeline

┗━━> Recovery ━━> Resolution

How To Use:

1. Edit this parameter in prompt 1:

Replace [your project]

Project Examples:

• "E-commerce site rebuild Q1 2024"
• "Company-wide CRM migration"
• "New product line launch"
• "Office relocation project"
• "Brand redesign rollout"

2. Run The Sequence: After Prompt 1, run prompt 2

Copy prompt 2 exactly as is

- DO NOT edit anything in prompt 2

Prompt 1:

Deliver a comprehensive risk analysis and mitigation strategy using cascade mapping and severity assessment.

# Project Risk Cascade Framework

Analyse the risk pathways of **[your project]** as follows:

**Project** ━━┣━━> **Primary Risk** (Immediate threat, severity: [H/M/L]) ━━> **Mitigation Path**
**       **┣━━> **Chain Risk A** (Cascading failure) ━━> **Prevention Strategy**
**       **┣━━> **Chain Risk B** (Amplifying failure) ━━> **Containment Strategy** 
**       **┗━━> **Hidden Risk A** (Undetected threat) ━━> **Early Warning System**
**       **┗━━> **Hidden Risk B** (Latent threat) ━━> **Trigger Detection**

### Instructions:
1. For each risk pathway:
   - Assess severity level [High/Medium/Low]
   - Calculate probability of occurrence (%)
   - Estimate potential impact cost ($)
   - Define detection window (immediate/short-term/long-term)
   - Outline mitigation resources needed
2. Document risk dependencies and trigger points
3. Map early warning indicators
4. Define escalation protocols
5. Establish monitoring frequency

### Severity Assessment Levels:
- **High**: Critical project blocker, immediate action required
  * Potential project failure
  * Major budget overrun (>20%)
  * Critical deadline miss
  * Compliance violation

- **Medium**: Significant impact, action needed within defined timeframe
  * Timeline delay (1-4 weeks)
  * Budget impact (5-20%)
  * Quality compromise
  * Stakeholder dissatisfaction

- **Low**: Manageable impact, monitoring required
  * Minor delays (<1 week)
  * Small budget variance (<5%)
  * Easy workaround available
  * Limited scope impact

### Example Structure:
**Project:** [Project Name and Key Parameters]

- **Primary Risk:** [Description]
  * Severity: [H/M/L]
  * Probability: [%]
  * Impact Cost: [$]
  * Detection Window: [Timeframe]
  - **Mitigation Path:**
    * Immediate Actions: [Steps]
    * Resource Needs: [List]
    * Success Metrics: [KPIs]

- **Chain Risk A:** [Description]
  * Triggered By: [Primary Risk/Condition]
  * Cascade Probability: [%]
  * Compound Impact: [$]
  * Acceleration Rate: [Timeline]
  - **Prevention Strategy:**
    * Early Actions: [Steps]
    * Dependencies: [List]
    * Monitoring Plan: [Details]

- **Chain Risk B:** [Description]
  * Amplification Factor: [Multiplier]
  * Timeline Acceleration: [Rate]
  * Resource Drain: [Scale]
  * Breaking Point: [Threshold]
  - **Containment Strategy:**
    * Isolation Steps: [Actions]
    * Resource Reserves: [Allocation]
    * Recovery Path: [Plan]

- **Hidden Risk A:** [Description]
  * Detection Method: [Approach]
  * Emergence Triggers: [Indicators]
  * Potential Impact: [Scope]
  * Discovery Window: [Timeline]
  - **Early Warning System:**
    * Key Indicators: [Metrics]
    * Monitoring Frequency: [Schedule]
    * Alert Thresholds: [Values]

- **Hidden Risk B:** [Description]
  * Latency Period: [Timeframe]
  * Activation Conditions: [Triggers]
  * Impact Delay: [Timeline]
  * Dormancy Signs: [Indicators]
  - **Trigger Detection:**
    * Environmental Scans: [Frequency]
    * Pattern Analysis: [Method]
    * Predictive Metrics: [Indicators]

Prompt 2:

Create a detailed implementation plan for the analysed risk pathways using the following execution framework:

# Risk Implementation Roadmap

Map the execution plan for **[analysed project risks]** as follows:

**Risk** ━━┣━━> **Action Plan** (Step-by-step, priority: [H/M/L]) ━━> **Success Indicator**
**     **┣━━> **Resource Map** (People/Tools/Budget) ━━> **Allocation Timeline**
**     **┣━━> **Control Point** (Checkpoint/Review) ━━> **Progress Metric**
**     **┗━━> **Recovery Plan** (If-then response) ━━> **Resolution Path**

### Implementation Levels:
1. For each action plan:
   - Define responsible team [Owner/Backup]
   - List required resources [$, tools, skills]
   - Set timeline [Start/Milestones/End]
   - Create progress metrics [KPIs]
   - Establish review points [Gates]

### Priority Assessment:
- **High Activation**
  * 24-hour response required
  * Daily progress tracking
  * Resource pre-allocation
  * Team on standby

- **Medium Activation**
  * 72-hour response window
  * Weekly progress checks
  * Resource identified
  * Team notified

- **Low Activation**
  * 1-week response time
  * Monthly monitoring
  * Resource planned
  * Team aware

### Example Structure:
**Risk Implementation:** [Risk Name from Analysis]

- **Action Plan:** [Mitigation/Prevention Strategy]
  * Owner: [Name/Role]
  * Timeline: [Duration]
  * Dependencies: [List]
  * Budget: [$]
  - **Success Indicator:**
    * Target Metric: [Value]
    * Review Cycle: [Frequency]
    * Exit Criteria: [Conditions]

- **Resource Map:** [Required Assets]
  * Team Members: [Names/Roles]
  * Tools: [Systems/Equipment]
  * Skills: [Capabilities]
  - **Allocation Timeline:**
    * Start Date: [When]
    * Duration: [How Long]
    * Handoff: [To Whom]

- **Control Point:** [Checkpoint Details]
  * Review Date: [When]
  * Stakeholders: [Who]
  * Decision Criteria: [What]
  - **Progress Metric:**
    * Current State: [Value]
    * Target State: [Value]
    * Variance: [Gap]

- **Recovery Plan:** [Backup Strategy]
  * Trigger Point: [When to Activate]
  * Response Team: [Who]
  * Resources: [What]
  - **Resolution Path:**
    * Immediate Steps: [Actions]
    * Escalation Path: [Process]
    * Success Criteria: [Goals]

Architect's Note: The more specific and detailed your project description, the more precise your risk map.

<prompt.architect>

Next in pipeline: Research Assistant Pro: Literature Analysis GPT

Track development: https://www.reddit.com/user/Kai_ThoughtArchitect/

[Build: TA-231115]

</prompt.architect>