---
# === IDENTITY ===
id: consulting/recipes/oia-client-presentation/2026
canonical_question: "How do you present OIA findings with health score visualization and risk heat maps?"
aliases:
  - "creating organizational health dashboards for client presentations"
  - "building OIA risk heat maps and remediation roadmaps"
  - "visualizing organizational diagnostics results for executives"
entity_type: execution_recipe
domain: consulting > recipes > OIA Client Presentation
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 — OIA methodology v1.0"
  next_review: 2026-09-25
  change_sensitivity: high

# === CONSTRAINTS ===
constraints:
  - "Health score methodology must be calibrated before presentation — raw scores without baseline comparison are meaningless"
  - "Network topology visualizations require anonymized data — never present individual employee names in heat maps to non-HR audiences"
  - "Before/after comparisons require minimum 30-day baseline measurement period — presenting without baseline is speculation, not diagnosis"
  - "Retainer proposals must use outcome-based pricing (metabolic recovery) — never propose time-and-materials for OIA engagements"
  - "Risk heat maps must use consistent severity scales across all client presentations — inconsistent scales destroy cross-engagement comparability"

# === SKIP CONDITIONS ===
skip_this_unit_if:
  - condition: "User needs the diagnostic methodology, not presentation format"
    use_instead: "consulting/oia/organizational-health-scoring/2026"
  - condition: "User needs pricing model design, not presentation recipe"
    use_instead: "consulting/oia/metabolic-recovery-pricing/2026"
  - condition: "User is building a live monitoring dashboard, not a client presentation"
    use_instead: "consulting/recipes/oia-wbc-deployment/2026"

# === AGENT HINTS ===
inputs_needed:
  - key: audience
    question: "Who is the primary audience for the presentation?"
    type: choice
    options: ["C-suite (CEO/COO/CFO)", "IT leadership (CTO/CIO/CISO)", "HR leadership (CHRO)", "mixed executive committee"]
  - key: diagnostic_data
    question: "What diagnostic data is available?"
    type: choice
    options: ["ONA network analysis complete", "WBC monitoring data available", "both ONA + WBC data", "survey data only (no network analysis)"]
  - key: engagement_stage
    question: "What stage of the engagement is this presentation for?"
    type: choice
    options: ["initial findings (discovery phase)", "progress report (mid-engagement)", "final deliverable (engagement close)", "retainer proposal (ongoing relationship)"]

# === EXECUTION METADATA ===
execution:
  required_inputs:
    - name: "Organizational health scores"
      source: "consulting/oia/organizational-health-scoring/2026"
      format: "structured JSON with dimension scores and benchmarks"
    - name: "Network topology data"
      source: "ONA analysis (Microsoft Viva Insights, Slack analytics, or custom ONA tool)"
      format: "graph data (nodes + edges) with anonymized identifiers"
    - name: "Risk assessment results"
      source: "OIA diagnostic phase output"
      format: "structured risk register with severity, likelihood, and impact scores"
  outputs:
    - name: "Client presentation deck"
      format: "interactive HTML dashboard or PDF report"
      description: "Health score visualizations, risk heat maps, before/after topology comparisons, and remediation roadmap"
    - name: "Retainer proposal document"
      format: "PDF or structured document"
      description: "Outcome-based pricing proposal with metabolic recovery milestones tied to health score improvement targets"
    - name: "Executive summary"
      format: "1-page PDF"
      description: "Single-page organizational health snapshot for board-level distribution"
  tools_required:
    - name: "D3.js or Observable"
      purpose: "Interactive network topology visualization and health score gauges"
      tier: free
      cost: "$0"
      alternatives: ["Plotly", "Chart.js", "Tableau (paid)"]
    - name: "Figma or Canva"
      purpose: "Executive summary layout and visual polish"
      tier: free
      cost: "$0 (free tier) to $15/mo (pro)"
      alternatives: ["Google Slides", "PowerPoint"]
    - name: "Mermaid.js"
      purpose: "Remediation roadmap timeline diagrams"
      tier: free
      cost: "$0"
      alternatives: ["Lucidchart", "draw.io"]
  credentials_needed:
    - service: "Client data source (Viva Insights / Slack Analytics)"
      type: "Read-only API access or exported dataset"
      where_to_get: "Client IT admin provides export"
      free_tier_limits: "N/A — client-provided data"
  estimated_duration: "8-16 hours for full presentation build"
  estimated_cost: "$0-50 (tools) + consultant time"

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

# === RELATED UNITS ===
related_kos:
  depends_on:
    - id: "consulting/oia/organizational-health-scoring/2026"
      label: "Organizational Health Scoring — provides the scores this recipe visualizes"
    - id: "consulting/oia/metabolic-recovery-pricing/2026"
      label: "Metabolic Recovery Pricing — the pricing model used in retainer proposals"
  feeds_into: []
  related_to:
    - id: "consulting/recipes/oia-wbc-deployment/2026"
      label: "WBC Deployment — provides monitoring data visualized in presentations"
    - id: "consulting/oia/swiss-cheese-model-for-orgs/2026"
      label: "Swiss Cheese Model — structural defect framing used in risk heat maps"
  alternative_to: []

# === SOURCES ===
sources:
  - id: src1
    title: "The Knowing-Doing Gap: How Smart Companies Turn Knowledge into Action"
    author: Jeffrey Pfeffer & Robert Sutton
    url: https://www.hbs.edu/faculty/Pages/item.aspx?num=6395
    type: academic_paper
    published: 2000-01-01
    reliability: high
  - id: src2
    title: "The New Science of Building Great Teams"
    author: Alex Pentland
    url: https://hbr.org/2012/04/the-new-science-of-building-great-teams
    type: primary_research
    published: 2012-04-01
    reliability: high
  - id: src3
    title: "Performance-Based Contracting in Business Markets"
    author: Hypko, Tilebein & Gleich
    url: https://doi.org/10.1016/j.indmarman.2010.06.014
    type: academic_paper
    published: 2010-11-01
    reliability: high
  - id: src4
    title: "Information Dashboard Design: Displaying Data for At-a-Glance Monitoring"
    author: Stephen Few
    url: https://www.perceptualedge.com/library.php
    type: academic_paper
    published: 2013-01-01
    reliability: high
  - id: src5
    title: "Storytelling with Data: A Data Visualization Guide for Business Professionals"
    author: Cole Nussbaumer Knaflic
    url: https://www.storytellingwithdata.com/books
    type: industry_report
    published: 2015-10-01
    reliability: high
---

# OIA Client Presentation

## Purpose

This recipe produces a complete client-facing presentation of Organizational Immune Analysis findings, including interactive health score dashboards, risk heat maps by organizational dimension, before/after network topology comparisons, a phased remediation roadmap, and an outcome-based retainer proposal. The presentation replaces the traditional 50-page slide deck with a living diagnostic that shows the organization as a biological system — visualizing dysfunction as structural disease rather than individual blame. [src1]

## Prerequisites

- [ ] **Organizational health scores** available from `consulting/oia/organizational-health-scoring/2026` — [Health Scoring Framework](/consulting/oia/organizational-health-scoring/2026)
- [ ] **Network topology data** — anonymized ONA graph export from Microsoft Viva Insights or Slack analytics
- [ ] **Risk assessment results** — structured risk register from OIA diagnostic phase
- [ ] **30-day baseline measurement** — minimum data collection period before presenting before/after comparisons
- [ ] **Audience profile** — confirmed primary audience (C-suite, IT leadership, HR, or mixed) to calibrate language and depth

## Constraints

- Anonymization: Never present individual employee names in network visualizations to non-HR audiences. Use role-based identifiers ("Engineering Lead #3") or team-level aggregation. [src2]
- Baseline requirement: Before/after topology comparisons require minimum 30 calendar days of baseline data. Presenting without a baseline is speculation, not diagnosis — it undermines the entire scientific credibility of the OIA methodology.
- Pricing model: Retainer proposals must use outcome-based (metabolic recovery) pricing, never time-and-materials. The entire value proposition of OIA is "pay for the cure, not the clock." [src3]
- Visual clarity: Follow Stephen Few's dashboard design principles — no 3D charts, no pie charts for more than 3 categories, no dual-axis charts. Cognitive load kills executive attention. [src4]
- Narrative structure: Every data visualization must answer a specific question. Uncontextualized charts create the "so what?" problem that kills consulting engagements. [src5]

## Tool Selection Decision

```
Which presentation format?
├── Audience is technical (CTO/CISO) AND engagement stage is mid/final
│   └── PATH A: Interactive HTML dashboard — D3.js + Observable
├── Audience is C-suite AND engagement stage is initial/final
│   └── PATH B: Narrative PDF report — Figma/Canva + static charts
├── Audience is mixed AND engagement includes retainer proposal
│   └── PATH C: Hybrid — interactive dashboard + executive summary PDF
└── Budget is minimal AND timeline is compressed
    └── PATH D: Google Slides/PowerPoint with embedded chart images
```

| Path | Tools | Cost | Speed | Output Quality |
|------|-------|------|-------|---------------|
| A: Interactive HTML | D3.js, Observable, Mermaid.js | $0 | 12-16 hours | Highest — drill-down capable |
| B: Narrative PDF | Figma, Chart.js, export to PDF | $0-15 | 8-12 hours | High — polished, executive-ready |
| C: Hybrid | D3.js + Figma + PDF export | $0-15 | 14-20 hours | Highest — covers all audiences |
| D: Slides | Google Slides, Chart.js screenshots | $0 | 4-8 hours | Medium — static, no interactivity |

## Execution Flow

### Step 1: Structure the Narrative Arc

**Duration**: 1-2 hours
**Tool**: Outline document

Build the presentation around a four-act diagnostic narrative:

1. **The Patient** — Current organizational state (health scores, vital signs)
2. **The Diagnosis** — Where the structural defects are (risk heat maps, network topology gaps)
3. **The Treatment Plan** — Remediation roadmap with phased interventions
4. **The Prognosis** — Expected outcomes with metabolic recovery milestones and retainer proposal

For each act, define the specific question being answered and the visualization type that answers it. Never present a chart without a preceding question. [src5]

**Verify**: Each section has a clear "question --> answer --> implication" structure. No orphan visualizations.
**If failed**: Review with a colleague — if they cannot state the takeaway of each section in one sentence, the narrative needs restructuring.

### Step 2: Build Health Score Dashboard

**Duration**: 3-5 hours
**Tool**: D3.js or Chart.js

Create the organizational health score visualization with these components:

- **Radar chart**: 6-8 dimensions (communication flow, decision velocity, knowledge distribution, structural resilience, compliance health, innovation capacity)
- **Benchmark overlay**: Industry benchmarks shown as a gray polygon behind the client's scores
- **Trend arrows**: Direction indicators showing improvement or degradation since baseline

```javascript
// Health score radar chart configuration
const dimensions = [
  { axis: "Communication Flow", value: 0.72, benchmark: 0.65 },
  { axis: "Decision Velocity", value: 0.45, benchmark: 0.60 },
  { axis: "Knowledge Distribution", value: 0.58, benchmark: 0.55 },
  { axis: "Structural Resilience", value: 0.38, benchmark: 0.50 },
  { axis: "Compliance Health", value: 0.81, benchmark: 0.70 },
  { axis: "Innovation Capacity", value: 0.52, benchmark: 0.55 }
];
// Red zone: < benchmark - 0.15 | Yellow: within 0.15 of benchmark | Green: > benchmark
```

**Verify**: All dimensions use 0-1 scale. Benchmark data is from validated industry source, not fabricated. Color coding follows red/yellow/green with accessible color choices.
**If failed**: If benchmark data unavailable, show absolute scores with percentile annotations from OIA historical database.

### Step 3: Generate Risk Heat Maps

**Duration**: 2-4 hours
**Tool**: D3.js heatmap or Plotly

Build a risk heat map matrix with organizational dimensions on one axis and risk categories on the other:

| | Communication | Decision-Making | Knowledge | Compliance | Innovation |
|---|---|---|---|---|---|
| **Single Point of Failure** | Low | Critical | High | Low | Medium |
| **Information Bottleneck** | High | Medium | Critical | Low | High |
| **Complexity Collapse** | Medium | High | Medium | Medium | Low |
| **Immune Response (change resistance)** | Low | Critical | Low | High | Critical |

Each cell shows severity (critical/high/medium/low) with supporting evidence from the ONA data. Critical cells link to specific structural findings.

**Verify**: Every "Critical" cell has supporting evidence from diagnostic data — no severity ratings based on intuition alone.
**If failed**: Downgrade any unsupported cells to "Insufficient Data" rather than guessing severity.

### Step 4: Create Before/After Network Topology Comparison

**Duration**: 2-3 hours
**Tool**: D3.js force-directed graph

Visualize the organizational communication network as a force-directed graph showing:

- **Before state**: Current topology with bottlenecks highlighted (oversized nodes = single points of failure, red edges = broken pathways, gray clusters = isolated silos)
- **After state (projected)**: Expected topology after remediation — distributed load, connected clusters, eliminated bottlenecks

Use the Swiss Cheese Model framing: show structural "holes" in the communication layers and how remediation closes them. [src2]

**Verify**: Node sizing correlates with actual communication centrality metrics (betweenness centrality). Not artistic interpretation.
**If failed**: If ONA data lacks sufficient granularity for individual node analysis, aggregate to team-level topology.

### Step 5: Build Remediation Roadmap

**Duration**: 1-2 hours
**Tool**: Mermaid.js or timeline library

Create a phased remediation timeline with:

- **Phase 1 (0-30 days)**: Quick wins — immediate structural fixes (communication channel redesign, bottleneck relief)
- **Phase 2 (30-90 days)**: Core remediation — process redesign, WBC deployment, escalation workflow activation
- **Phase 3 (90-180 days)**: Hardening — graduated autonomy expansion, measurement calibration, culture shift monitoring
- **Phase 4 (180+ days)**: Continuous immunity — ongoing monitoring, periodic re-diagnosis, retainer-based health maintenance

Each phase includes specific health score targets and measurable success criteria.

**Verify**: Each phase has quantified success criteria (e.g., "Decision velocity score improves from 0.45 to 0.55"). No vague milestones.
**If failed**: If health score targets cannot be quantified, use directional indicators ("improve by 15-20%") with confidence intervals.

### Step 6: Draft Retainer Proposal with Metabolic Recovery Pricing

**Duration**: 2-3 hours
**Tool**: Document template + pricing calculator

Build the retainer proposal using outcome-based pricing:

- **Recovery fee**: Percentage of quantified operational savings (typically 15-25% of documented waste reduction)
- **Monitoring retainer**: Fixed monthly fee for ongoing WBC operation and quarterly re-diagnosis
- **Success milestones**: Health score improvement targets that trigger retainer renewal
- **Risk sharing**: If health scores do not improve by agreed thresholds within 180 days, monitoring retainer is waived until improvement is demonstrated

This pricing model directly counters the "billable hour" incentive misalignment that kills traditional consulting engagements. [src3]

**Verify**: Pricing proposal includes explicit risk-sharing clause. Client should never feel they are paying for time — only for measurable health improvement.
**If failed**: If client procurement requires time-based billing, structure as "time with performance bonus" — base rate covers costs, bonus tied to outcomes.

## Output Schema

```json
{
  "output_type": "oia_presentation",
  "format": "HTML_dashboard_or_PDF",
  "components": [
    {"name": "health_score_dashboard", "type": "interactive_visualization", "description": "Radar chart with benchmark overlay and trend indicators", "required": true},
    {"name": "risk_heat_map", "type": "matrix_visualization", "description": "Dimension x risk-category severity matrix", "required": true},
    {"name": "network_topology_comparison", "type": "graph_visualization", "description": "Before/after force-directed graph of communication network", "required": true},
    {"name": "remediation_roadmap", "type": "timeline_diagram", "description": "4-phase remediation plan with milestones", "required": true},
    {"name": "retainer_proposal", "type": "document", "description": "Outcome-based pricing with metabolic recovery milestones", "required": true},
    {"name": "executive_summary", "type": "1_page_PDF", "description": "Single-page health snapshot for board distribution", "required": false}
  ]
}
```

## Quality Benchmarks

| Quality Metric | Minimum Acceptable | Good | Excellent |
|---------------|-------------------|------|-----------|
| Narrative clarity (can audience state takeaway per section?) | 60% of sections clear | 80% | 100% |
| Data backing (% of claims with quantified evidence) | > 70% | > 85% | > 95% |
| Visual accessibility (WCAG 2.1 AA compliance) | Color contrast passes | + alt text | + screen reader tested |
| Remediation specificity (% of phases with quantified targets) | > 50% | > 75% | 100% |
| Client engagement (questions asked during presentation) | > 3 questions | > 6 | > 10 (deep engagement) |

**If below minimum**: If narrative clarity is below 60%, restructure around the four-act framework before presenting. Never present with unclear narrative — it is worse than delaying.

## Error Handling

| Error | Likely Cause | Recovery Action |
|-------|-------------|----------------|
| Health scores seem implausible (all dimensions above 0.8) | Sampling bias or insufficient data collection period | Extend baseline measurement to 60 days. Cross-validate with qualitative interviews. |
| Network topology shows no clear bottlenecks | Organization may be genuinely healthy, or ONA data lacks granularity | Verify data source captures all communication channels (not just email). If confirmed healthy, present as strength. |
| Client rejects outcome-based pricing | Procurement requires time-based contracts | Offer "time + performance bonus" hybrid. Base rate at 60% of normal T&M, 40% tied to health score improvement. |
| Executive audience disengages during technical network visualizations | Too much technical detail for audience level | Switch to team-level aggregated view. Replace force-directed graph with simplified department connectivity matrix. |
| Before/after comparison shows regression | Intervention may have caused unintended disruption | Present honestly. Diagnose which intervention caused regression and propose correction. Transparency builds trust. |

## Cost Breakdown

| Component | Free Tier | Paid Tier | At Scale |
|-----------|-----------|-----------|----------|
| D3.js / Chart.js | $0 | $0 | $0 |
| Figma / Canva | $0 (free tier) | $15/mo | $15/mo |
| Observable | $0 (public notebooks) | $25/mo (private) | $25/mo |
| PDF generation | $0 (browser print) | $0 | $0 |
| **Total** | **$0** | **$15-40/mo** | **$15-40/mo** |

## Anti-Patterns

### Wrong: Presenting raw data without narrative structure
Dumping health scores, heat maps, and network graphs on executives without a connecting story is the digital equivalent of the 50-page slide deck — technically thorough but functionally useless. Pfeffer and Sutton's research shows this creates a "knowing-doing gap" where the client nods but never acts. [src1]

### Correct: Build every presentation around the four-act diagnostic narrative (Patient, Diagnosis, Treatment, Prognosis)
Each visualization answers a specific question. The audience should never wonder "so what?" — every chart flows into an actionable implication. [src5]

### Wrong: Using individual employee names in network topology visualizations
Presenting "Bob is a bottleneck" to a room of executives triggers defensive political reactions and kills trust. It turns a structural diagnosis into a personal attack. [src2]

### Correct: Use anonymized role-based identifiers or team-level aggregation
Show "Engineering Team Lead (Node #7) has 4.2x average centrality" rather than naming individuals. The structural insight is identical; the political risk is eliminated.

### Wrong: Proposing time-and-materials retainers after presenting OIA findings
If the diagnosis shows the organization is "bleeding" from structural defects and the remedy is continuous monitoring, billing by the hour creates the exact perverse incentive the OIA methodology was designed to eliminate. [src3]

### Correct: Always propose outcome-based (metabolic recovery) pricing tied to health score improvement
The consultant's revenue should depend on solving the problem, not studying it. This aligns incentives and differentiates OIA from traditional consulting.

## When This Matters

Use when the agent needs to produce a client-facing presentation of OIA diagnostic findings with health score visualizations, risk heat maps, and remediation roadmaps. Requires completed organizational health scoring and ONA data as inputs. This recipe produces presentation artifacts, not the diagnostic analysis itself.

## Related Units

- [Organizational Health Scoring](/consulting/oia/organizational-health-scoring/2026) — provides the scores this recipe visualizes
- [Metabolic Recovery Pricing](/consulting/oia/metabolic-recovery-pricing/2026) — the pricing model used in retainer proposals
- [WBC Deployment](/consulting/recipes/oia-wbc-deployment/2026) — provides monitoring data visualized in presentations
- [Swiss Cheese Model for Organizations](/consulting/oia/swiss-cheese-model-for-orgs/2026) — structural defect framing used in risk heat maps