Manuals / Project Management for Tech / Chapter 5

B · People & risk · intermediate · ~40 min · Chapter 5 of 9

RAID: risks, assumptions, issues, decisions

A living RAID log beats a risk slide that died in week one. Risks have owners, triggers, and mitigations.

Path progress
50%

Step 1 of 2

Start the RAID

Risks = maybe. Issues = now. Assumptions = believed true. Decisions = locked choices with date/owner.

Start the RAIDDrag stickies · tap for tips
Study mapDrag stickies · tap for tipsKeep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Assert the UIdrag · tap →Retry wiselydrag · tap →Seed datadrag · tap →Close the loopdrag · tap →Keep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Pathwise hackdrag · tap →Start the RAIDdrag · tap →Try thisdrag · tap →Follow the dashed drag · tap →

Example

Risk | Prob | Impact | Owner | Trigger | Mitigation | Status
Issue | Owner | Impact | Next action | Due
Assumption | Owner | Validate by | Status
Decision | Date | Decider | Alternatives considered

Do this now

Create a RAID table with at least 3 risks, 2 assumptions, 1 open issue, 2 decisions.

Was this step clear?
Chapter learning outcomes
  • Risk vs issue
  • Probability × impact
  • Decision log

Clear these before you leave

Side quest

Weekly RAID hygiene

Update RAID once this week in a real standup or async note.