RAID Log Project Matrix

Template Overview

Complex software projects rarely fail due to technical incompetence; they fail because unmanaged dependencies break, unchecked assumptions prove false, or known risks materialize without mitigations. The RAID Log Project Matrix consolidates Risks, Assumptions, Issues, and Dependencies into a single, high-visibility Markdown ledger. It provides engineering managers and project leads with a living control document to ensure accountability across sprint lifecycles.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "RAID Log: [Project Name / Initiative]"
date_updated: [YYYY-MM-DD]
project_manager: "[[Project Manager Name]]"
technical_lead: "[[Tech Lead Name]]"
overall_project_rag_status: "[Red / Amber / Green]"
tags: [project-management, raid-log, risk-management, governance, dependencies]
---

# RAID Log Project Matrix — [Project Name]

## 1. Project Governance & Status Summary
- **Project Goal:** `[Brief 1-sentence delivery objective]`
- **Target Launch Date:** [YYYY-MM-DD]
- **Current RAG Status:** **Amber** (Due to external security audit dependency).

## 2. Risks Register (Potential Future Hazards)
| Risk ID | Risk Description | Likelihood (1-5) | Impact (1-5) | Severity (LxI) | Planned Mitigation Strategy | Owner |
|---|---|---|---|---|---|---|
| R-01 | Apple Silicon neural compiler updates break Core ML model weights | 3 | 4 | **12 (High)** | Pin Xcode SDK toolchain versions in Docker CI runners | [[Tech Lead]] |
| R-02 | Key machine learning engineer departs before model optimization freeze | 2 | 5 | **10 (High)** | Pair-program all quantization modules; document math proofs | [[VP Eng]] |
| R-03 | Local disk write permissions fail on restricted macOS MDM profiles | 3 | 3 | 9 (Medium) | Provide explicit pre-flight permission diagnostics in app | [[SRE Lead]] |

## 3. Assumptions Register (Unverified Premises)
| Assump ID | Statement of Assumption | Impact if False | Validation Action & Deadline | Validation Status |
|---|---|---|---|---|
| A-01 | Target enterprise customers permit local desktop binaries without admin IT sign-off | High | Conduct 10 IT admin discovery interviews by [Date] | Validated |
| A-02 | Users possess minimum 16GB RAM for running large-v3 quantized models | High | Query telemetry from open beta by [Date] | In Progress |

## 4. Issues Register (Active Current Problems)
| Issue ID | Problem Description | Severity | Triggered Date | Immediate Containment / Resolution | Owner |
|---|---|---|---|---|---|
| I-01 | Memory leak observed during 3+ hour continuous audio recordings | Critical | [Date] | Implemented sliding-window audio buffer cache | [[David Chen]] |
| I-02 | Third-party notarization pipeline failing on macOS 15 release builds | High | [Date] | Re-keyed Apple developer certificates in GitHub Secrets | [[DevOps Lead]] |

## 5. Dependencies Register (Cross-Team Deliverables)
| Dep ID | Required Deliverable | Providing Team / Vendor | Target Need Date | Impact of Delay | Critical Path? |
|---|---|---|---|---|---|
| D-01 | External SOC 2 Type II audit report | Compliance Firm | [Date] | Delays enterprise contract executions | **Yes** |
| D-02 | Localized German / Japanese UI strings | Localization Vendor | [Date] | Delays international press announcements | No |

## 6. Weekly RAID Action Items
- [ ] Review High-Severity Risk R-01 mitigations during Tuesday architecture sync.
- [ ] Close validated Assumption A-01 in project charter.
- [ ] Ping compliance firm regarding final draft of Dependency D-01.

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "RAID Log: Oyma Desktop v2.4 Rollout"
date_updated: 2026-10-09
project_manager: "[[Julian Thorne]]"
technical_lead: "[[Marcus Vance]]"
overall_project_rag_status: "Green"
tags: [project-management, raid-log, risk-management, governance, dependencies]
---

# RAID Log Project Matrix — Oyma Desktop v2.4 Rollout

## 1. Project Governance
- Goal: Ship 360 Markdown templates and on-device Whisper transcription to production.
- Status: **Green** (All 24 SEO gates passing, 134 automated unit tests green).

## 2. Key Risks & Mitigations
- **R-01:** Cloudflare Workers edge deployment exceeds memory budget during bulk static serving.
  - *Mitigation:* Deployed asset streaming chunks and verified edge cache headers. Status: Resolved.

## 3. Active Issues
- None currently open. Issue I-01 (Wrangler OAuth token expiration) was resolved via automated refresh script.

## 4. Next Actions
- Verify production edge CDN status across international regions post-deploy.

When to Use and When to Avoid

When to Use

• Use during kickoffs and throughout execution of complex multi-month software initiatives.
• Use to establish transparency and prevent surprises during executive steering committee reviews.
• Use when multiple cross-functional teams share interdependent technical deliverables.

When to Avoid

• Avoid using for quick 2-day personal hackathon projects.
• Avoid using as a substitute for an active software bug tracker (use Jira/Linear for bugs).

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Analyze the RAID log project matrix:
1. Identify all critical-path dependencies that have past-due or high-risk delivery dates.
2. Calculate total risk exposure score and rank top three existential project hazards.
3. Formulate an executive briefing summarizing active issues and requested leadership escalations.
Output in structured Markdown.

Your data remains securely on your Mac with zero cloud exposure.