---
# === IDENTITY ===
id: consulting/recipes/oia-stress-test-execution/2026
canonical_question: "How do you execute organizational stress tests with scenario design and recovery scoring?"
aliases:
  - "Organizational stress test execution guide"
  - "How to run tabletop exercises for organizational resilience"
  - "Resilience scoring with scenario-based stress testing"
entity_type: execution_recipe
domain: consulting > recipes > OIA Stress Test Execution
region: global
jurisdiction: global
temporal_scope: 2026-2027

# === VERIFICATION ===
last_verified: 2026-03-29
confidence: 0.85
version: 1.0
first_published: 2026-03-29

# === TEMPORAL VALIDITY ===
temporal_validity:
  status: evolving
  last_breaking_change: "Initial release — stress test protocols v1.0"
  next_review: 2026-09-25
  change_sensitivity: high

# === CONSTRAINTS ===
constraints:
  - "Silent stress tests require explicit executive approval — never run without it"
  - "Tabletop exercises require leadership team availability for 2-hour block"
  - "Controlled disruptions must be low-risk and reversible — no production impact"
  - "Recovery scoring must use standardized rubric — no subjective assessments"
  - "Stress test findings must be shared with leadership before broader distribution"

# === SKIP CONDITIONS ===
skip_this_unit_if:
  - condition: "User needs network analysis, not resilience testing"
    use_instead: "consulting/recipes/oia-network-analysis-execution/2026"
  - condition: "User needs autoimmune scan, not stress testing"
    use_instead: "consulting/recipes/oia-autoimmune-scan-execution/2026"
  - condition: "User needs full OIA engagement plan"
    use_instead: "consulting/recipes/oia-engagement-playbook/2026"

# === AGENT HINTS ===
inputs_needed:
  - key: leadership_availability
    question: "Can the leadership team commit to a 2-hour tabletop exercise?"
    type: choice
    options: ["yes — full team", "partial — some leaders available", "no — async only", "unknown"]
  - key: silent_test_approval
    question: "Is executive approval available for a controlled disruption test?"
    type: choice
    options: ["yes — approved", "maybe — needs discussion", "no — too sensitive", "not applicable"]
  - key: spof_inventory
    question: "Has a single-point-of-failure inventory been completed?"
    type: choice
    options: ["yes — from network analysis", "partial", "no — needs to be built", "unknown"]
  - key: industry
    question: "What industry is the organization in?"
    type: choice
    options: ["technology", "financial services", "healthcare", "professional services", "manufacturing", "other"]

# === EXECUTION METADATA ===
execution:
  required_inputs:
    - name: "Network analysis findings (SPOF inventory)"
      source: "consulting/recipes/oia-network-analysis-execution/2026"
      format: "PDF + CSV"
    - name: "Autoimmune scan findings"
      source: "consulting/recipes/oia-autoimmune-scan-execution/2026"
      format: "XLSX + PDF"
    - name: "Executive approval for stress test scope"
      source: "client/executive-sponsor"
      format: "document"

  outputs:
    - name: "Resilience score report"
      format: "PDF + JSON"
      description: "Composite resilience score per department and overall, with gap analysis against HRO benchmarks"
    - name: "Stress test results"
      format: "spreadsheet + PDF"
      description: "Scenario-by-scenario response analysis with detection speed, response quality, coordination, and recovery time"
    - name: "Remediation recommendations"
      format: "PDF"
      description: "Top 3 resilience gaps with specific remediation actions"

  tools_required:
    - name: "Facilitated workshop"
      purpose: "Tabletop stress test exercise with leadership team"
      tier: "free"
      cost: "$0 (consultant facilitation)"
      alternatives: ["async scenario questionnaire"]
    - name: "IT admin tools"
      purpose: "Execute controlled disruption (silent test)"
      tier: "free"
      cost: "$0 (client's existing tools)"
      alternatives: ["skip silent test — tabletop only"]
    - name: "Scoring rubric template"
      purpose: "Standardized resilience measurement"
      tier: "free"
      cost: "$0"
      alternatives: []

  credentials_needed:
    - service: "IT admin"
      type: "Configuration access for controlled disruption"
      where_to_get: "Client IT team"
      free_tier_limits: "N/A — client provides access"

  estimated_duration: "1-2 weeks"
  estimated_cost: "$0-$2K (facilitation costs)"

# === DISTRIBUTION ===
canonical_source: "https://knowledgelib.io/consulting/recipes/oia-stress-test-execution/2026"
suggested_citation: "Source: knowledgelib.io — AI Knowledge Library (verified 2026-03-29)"

# === RELATED UNITS ===
related_kos:
  depends_on:
    - id: "consulting/recipes/oia-autoimmune-scan-execution/2026"
      label: "Autoimmune findings inform stress test scenario design"
    - id: "consulting/recipes/oia-network-analysis-execution/2026"
      label: "SPOF inventory drives scenario selection"
  feeds_into:
    - id: "consulting/recipes/oia-engagement-playbook/2026"
      label: "Results feed into final OIA health score report"
  related_to:
    - id: "consulting/oia/organizational-stress-testing/2026"
      label: "Stress testing theory and methodology"

# === SOURCES ===
sources:
  - id: src1
    title: "Chaos Engineering"
    author: Basiri, A. et al.
    url: https://ieeexplore.ieee.org/document/7436642
    type: academic_paper
    published: 2016-01-01
    reliability: authoritative
  - id: src2
    title: "The Art of the Long View"
    author: Schwartz, P.
    url: https://www.penguinrandomhouse.com/books/172854/the-art-of-the-long-view-by-peter-schwartz/
    type: academic_paper
    published: 1991-01-01
    reliability: authoritative
  - id: src3
    title: "Managing the Unexpected"
    author: Weick, K. & Sutcliffe, K.
    url: https://www.wiley.com/en-us/Managing+the+Unexpected-p-9780787996499
    type: academic_paper
    published: 2007-01-01
    reliability: authoritative
  - id: src4
    title: "A Leader's Framework for Decision Making"
    author: Snowden, D. & Boone, M.
    url: https://hbr.org/2007/11/a-leaders-framework-for-decision-making
    type: academic_paper
    published: 2007-11-01
    reliability: authoritative
---

# OIA Stress Test Execution

## Purpose

This recipe executes organizational stress tests that measure how quickly and effectively the organization detects, responds to, coordinates around, and recovers from disruption scenarios. It produces a composite resilience score benchmarked against High-Reliability Organization standards, identifying the top 3 resilience gaps with specific remediation recommendations. Adapts chaos engineering principles from software systems to organizational design. [src1, src3]

## Prerequisites
<!-- Agents: verify ALL prerequisites before executing. Missing prerequisites = failed execution. -->

- [ ] **Network analysis findings** with SPOF inventory from [OIA Network Analysis](/consulting/recipes/oia-network-analysis-execution/2026)
- [ ] **Autoimmune scan findings** from [OIA Autoimmune Scan](/consulting/recipes/oia-autoimmune-scan-execution/2026)
- [ ] **Executive approval** for stress test scope — signed confirmation of scenarios and controlled disruption parameters
- [ ] **Leadership team availability** — 2-hour block for tabletop exercise (or async alternative)
- [ ] **IT admin cooperation** — for silent stress test execution (if approved)

## Constraints
<!-- Hard rules. Agents: enforce throughout execution. -->

- Silent stress tests require explicit written executive approval. Never run a controlled disruption without it. [src1]
- Controlled disruptions must be low-risk and fully reversible. No production system outages, no customer-facing impact.
- Tabletop exercises require a 2-hour uninterrupted block with the leadership team. Shorter sessions produce superficial results.
- All scoring uses the standardized 5-dimension rubric (Detection, Response, Coordination, Recovery, Learning). No subjective assessments. [src3]
- Stress test findings shared with leadership before any broader distribution.

## Tool Selection Decision

```
Which approach?
├── Full leadership availability + executive approval for silent test
│   └── PATH A: Tabletop + Silent Test — comprehensive resilience assessment
├── Full leadership availability, no silent test approval
│   └── PATH B: Tabletop Only — strong assessment without live disruption
├── Partial leadership availability
│   └── PATH C: Async Scenarios + Mini Tabletop — adapted for scheduling constraints
└── No leadership availability
    └── PATH D: Async-Only — written scenario responses, limited but viable
```

| Path | Tools | Cost | Speed | Output Quality |
|------|-------|------|-------|---------------|
| A: Full | Tabletop + silent test + scoring | $0-$2K | 1-2 weeks | Excellent — observed + tested |
| B: Tabletop | Facilitated workshop + scoring | $0-$1K | 1 week | Good — discussed but not tested |
| C: Async + Mini | Written scenarios + 1-hour session | $0-$500 | 1 week | Adequate — limited interaction |
| D: Async-Only | Written questionnaire | $0-$200 | 3-5 days | Basic — self-reported only |

## Execution Flow

### Step 1: Scenario Design

**Duration**: 4-8 hours
**Tool**: Scenario template based on SPOF inventory

Design 3-5 stress test scenarios based on the SPOF inventory from network analysis and vulnerability patterns from the autoimmune scan. Each scenario must have a clear trigger, affected departments, expected impact timeline, and success criteria. [src2]

```
# Scenario Design Template

## Scenario A: Key Person Departure
- Trigger: Top-1 bottleneck (from network analysis) resigns with 2 weeks notice
- Affected: [departments that depend on this person]
- Expected impact: [knowledge loss, relationship disruption, process stall]
- Success criteria: Operations continue within 48 hours, no client impact

## Scenario B: Critical System Outage
- Trigger: Primary communication platform (Slack/Teams) down for 48 hours
- Affected: All departments
- Expected impact: [coordination breakdown, decision delays]
- Success criteria: Alternative communication established within 2 hours

## Scenario C: Regulatory Audit
- Trigger: Regulator announces audit with 2-week preparation deadline
- Affected: Compliance, legal, finance, operations
- Expected impact: [documentation scramble, resource diversion]
- Success criteria: Audit-ready documentation assembled within 5 business days

## Scenario D: Budget Cut
- Trigger: 20% budget reduction required within 30 days
- Affected: All departments
- Expected impact: [project cancellations, headcount decisions, vendor renegotiation]
- Success criteria: Prioritized cut plan within 48 hours, no critical capability loss

## Scenario E: Major Client Risk
- Trigger: Largest client (>15% revenue) threatens to leave
- Affected: Sales, account management, product, executive team
- Expected impact: [revenue risk, relationship scramble, retention offers]
- Success criteria: Retention plan activated within 24 hours
```

**Verify**: Each scenario has clear trigger, affected departments, expected impact, and measurable success criteria. Scenarios cover personnel, technology, regulatory, financial, and customer dimensions.
**If failed**: If SPOF inventory incomplete, design generic scenarios based on industry-standard risks and refine after tabletop reveals specific vulnerabilities.

### Step 2: Tabletop Exercise

**Duration**: 2 hours
**Tool**: Facilitated workshop with leadership team

Run the war-gaming session. Present each scenario in sequence, observe and record leadership team responses. [src2, src4]

Facilitation protocol:
1. Present scenario trigger (2 minutes)
2. Ask: "What happens first? Who is responsible?" — observe time to identify owner (target: < 60 seconds)
3. Ask: "Walk me through your response plan" — assess quality and specificity
4. Ask: "Which other teams need to be involved? How do you coordinate?" — assess cross-departmental cooperation
5. Ask: "How long until you are back to normal operations?" — assess recovery time estimate
6. Document observations, do not correct or guide responses

```
# Tabletop Observation Template
| Scenario | Detection Time | Response Quality | Coordination | Recovery Estimate | Notable Observations |
|----------|---------------|-----------------|--------------|-------------------|---------------------|
| A: Key person | [time to identify owner] | [1-5 score] | [1-5 score] | [hours/days] | [quotes, body language, disagreements] |
| B: System down | | | | | |
| C: Audit | | | | | |
| D: Budget cut | | | | | |
| E: Client risk | | | | | |
```

**Verify**: All scenarios exercised. Observations documented for each of the 5 measurement dimensions.
**If failed**: If leadership team runs out of time, prioritize Scenarios A and B (personnel and technology) — these reveal the most about organizational resilience.

### Step 3: Silent Stress Test

**Duration**: 1 week (observation period)
**Tool**: IT admin configuration + observation

With executive approval, introduce one low-risk controlled disruption. Observe the organization's natural response without announcing the test. [src1]

Recommended silent tests (choose one):
- **Approval rerouting**: Temporarily route one approval chain through an alternate person for 1 week. Observe: how fast is the change detected, how do people adapt.
- **Tool restriction**: Restrict access to one non-critical but popular tool for 3 days. Observe: workaround speed, shadow IT emergence.
- **Information delay**: Delay distribution of one regular report by 48 hours. Observe: who notices, who escalates, who works around it.

```
# Silent Test Design
- Test type: [approval rerouting / tool restriction / information delay]
- Duration: [3-7 days]
- Scope: [which department/process]
- Risk assessment: [what could go wrong, rollback plan]
- Observation points: [what to measure]
- Executive approval: [confirmed by name, date]
- Rollback trigger: [conditions for immediate reversal]
```

**Verify**: Disruption contained within planned scope. Observations captured (detection speed, adaptation quality, escalation patterns).
**If failed**: If disruption causes unexpected impact, execute rollback immediately. Document the failure as a finding — it reveals a resilience gap.

### Step 4: Response Measurement

**Duration**: 4-8 hours
**Tool**: Standardized scoring rubric

Score each scenario response across 5 dimensions using a 1-5 scale. Combine tabletop observations and silent test results. [src3]

Scoring dimensions:
1. **Detection Speed** (1-5): How fast was the problem identified?
   - 1 = Not detected within exercise timeframe
   - 3 = Detected within reasonable time with prompting
   - 5 = Detected immediately, clear ownership
2. **Response Quality** (1-5): How appropriate were initial actions?
   - 1 = No coherent response plan
   - 3 = Reasonable plan with gaps
   - 5 = Comprehensive, practiced response
3. **Coordination** (1-5): How well did teams work together?
   - 1 = Siloed response, no cross-team communication
   - 3 = Some coordination, ad hoc
   - 5 = Seamless cross-team cooperation, clear communication
4. **Recovery Time** (1-5): How fast would normal operations resume?
   - 1 = Weeks to recover
   - 3 = Days to recover
   - 5 = Hours to recover
5. **Learning** (1-5): Did the team identify improvement actions?
   - 1 = No post-incident reflection
   - 3 = Some lessons identified
   - 5 = Structured improvement plan with owners and deadlines

```
# Response Scoring Matrix
| Scenario | Detection (1-5) | Response (1-5) | Coordination (1-5) | Recovery (1-5) | Learning (1-5) | Composite |
|----------|-----------------|----------------|---------------------|----------------|----------------|-----------|
| A: Key person | | | | | | /25 |
| B: System down | | | | | | /25 |
| C: Audit | | | | | | /25 |
| D: Budget cut | | | | | | /25 |
| E: Client risk | | | | | | /25 |
| **Average** | | | | | | **/25** |
```

**Verify**: All 5 dimensions scored per scenario. Scores documented with evidence from observations.
**If failed**: If scoring is ambiguous, re-review observation notes with second analyst for calibration.

### Step 5: Resilience Score Calculation

**Duration**: 4-8 hours
**Tool**: Scoring framework + benchmark comparison

Produce composite resilience score per department and overall. Compare against High-Reliability Organization (HRO) benchmarks. Identify top 3 gaps. [src3]

```
# Resilience Score Calculation

# Overall score: average across all scenarios, normalized to 0-100
overall_score = (sum_of_all_composite_scores / max_possible) * 100

# Department scores: weight by scenario relevance
# (e.g., Engineering weighted more on Scenario B, Finance on Scenario C)

# HRO Benchmarks (Weick & Sutcliffe):
# - Preoccupation with failure: Detection Speed >= 4
# - Reluctance to simplify: Response Quality >= 4
# - Sensitivity to operations: Coordination >= 4
# - Commitment to resilience: Recovery Time >= 4
# - Deference to expertise: Learning >= 4

# Gap Analysis
# Identify dimensions scoring < 3 across multiple scenarios
# These are systemic resilience gaps requiring structural remediation
```

**Output files**:
- `resilience_score_report.pdf` — Composite scores with department breakdown and HRO benchmark comparison
- `stress_test_results.xlsx` — Scenario-by-scenario scoring with evidence
- `remediation_recommendations.pdf` — Top 3 gaps with specific remediation actions, owners, and timelines

**Verify**: Remediation recommendations produced for top 3 gaps. Each recommendation has a specific action, responsible owner, and timeline.
**If failed**: If scoring reveals no gaps (all dimensions > 4), the scenarios may have been too easy. Design more challenging scenarios based on actual SPOF data.

## Output Schema

```json
{
  "output_type": "resilience_assessment_report",
  "format": "PDF + XLSX + JSON",
  "files": [
    {"name": "resilience_score_report.pdf", "description": "Composite resilience scores with HRO benchmark comparison"},
    {"name": "stress_test_results.xlsx", "description": "Scenario-by-scenario scoring matrix"},
    {"name": "remediation_recommendations.pdf", "description": "Top 3 resilience gaps with actions"}
  ],
  "key_metrics": [
    {"name": "overall_resilience_score", "type": "number", "description": "0-100 composite resilience score"},
    {"name": "detection_avg", "type": "number", "description": "Average detection speed across scenarios (1-5)"},
    {"name": "coordination_avg", "type": "number", "description": "Average cross-team coordination score (1-5)"},
    {"name": "recovery_avg", "type": "number", "description": "Average recovery time score (1-5)"},
    {"name": "gap_count", "type": "number", "description": "Number of dimensions scoring below 3"}
  ]
}
```

## Quality Benchmarks

| Quality Metric | Minimum Acceptable | Good | Excellent |
|---------------|-------------------|------|-----------|
| Scenarios tested | 3 | 4 | 5+ |
| Leadership participation | > 60% of team | > 80% | > 95% |
| Scoring consistency (inter-rater) | > 70% agreement | > 85% | > 95% |
| Remediation specificity | General recommendations | Specific actions with owners | Actions + timelines + success criteria |
| Silent test executed | No (tabletop only) | Yes (1 test) | Yes (2+ tests) |

**If below minimum**: If fewer than 3 scenarios tested, extend exercise. If leadership participation low, run async scenarios for absent members.

## Error Handling

| Error | Likely Cause | Recovery Action |
|-------|-------------|----------------|
| Leadership team disengaged during tabletop | Scenarios not relevant to their concerns | Pause, ask what keeps them up at night, redesign scenarios around real fears |
| Silent test causes unexpected impact | Risk assessment underestimated dependencies | Execute rollback immediately, document as a resilience finding |
| Scoring disagreement between analysts | Ambiguous observations or different standards | Re-review observation notes together, use evidence-based calibration |
| All scores above 4 (too optimistic) | Scenarios too easy or leadership overconfident | Design harder scenarios based on actual SPOF data, consider silent test to validate |
| No time for tabletop exercise | Leadership scheduling conflict | Fall back to async scenario responses, schedule 30-min follow-up for discussion |

## Cost Breakdown

| Component | Tabletop Only | Tabletop + Silent | Full Assessment |
|-----------|---------------|-------------------|-----------------|
| Scenario design | $0 (consultant time) | $0 | $0 |
| Facilitation | $0-$500 | $0-$500 | $0-$1K |
| Silent test execution | N/A | $0-$500 (IT time) | $0-$1K |
| Analysis and scoring | $0 (consultant time) | $0 | $0 |
| **Total** | **$0-$500** | **$0-$1K** | **$0-$2K** |

## Anti-Patterns

### Wrong: Running tabletop as a presentation
Reading scenarios aloud and telling the leadership team what would happen instead of letting them respond. Result: no actual resilience data collected — the exercise becomes a lecture, not a test. [src3]

### Correct: Facilitate, don't lecture
Present the trigger and observe. Ask open questions. Document what they say and do, not what you think they should do. Silence after a trigger is data — it means detection is slow.

### Wrong: Designing scenarios that are too abstract
Using generic scenarios like "a major disruption occurs" without specificity. Result: leadership gives generic answers, scores are meaningless. [src2]

### Correct: Ground scenarios in SPOF data
Use actual bottleneck names (anonymized), real system names, real client names. Specificity forces specific responses, which produce measurable resilience data.

### Wrong: Skipping the silent stress test
Relying entirely on tabletop responses without any real-world validation. Result: overestimating resilience — people describe ideal responses, not actual behavior. [src1]

### Correct: Validate with at least one silent test
Even a small controlled disruption reveals the gap between described and actual organizational behavior. This is the chaos engineering principle applied to organizations. [src1]

## When This Matters

Use when an agent needs to measure organizational resilience through scenario-based stress testing. This is Step 5 of the OIA engagement lifecycle. Requires SPOF inventory from network analysis and autoimmune findings as inputs. Output feeds into the final OIA health score report and monitoring retainer design.

## Related Units

- [OIA Autoimmune Scan Execution](/consulting/recipes/oia-autoimmune-scan-execution/2026)
- [OIA Network Analysis Execution](/consulting/recipes/oia-network-analysis-execution/2026)
- [OIA Engagement Playbook](/consulting/recipes/oia-engagement-playbook/2026)
- [Organizational Stress Testing Theory](/consulting/oia/organizational-stress-testing/2026)