Six Sigma Project RAID Log
This is a practical guide to building a raid log for a six sigma project project — a consolidated log of Risks, Assumptions, Issues and Dependencies, adapted to the realities of reducing defects and variation in a process.
What a RAID Log is
A raid log is a consolidated log of Risks, Assumptions, Issues and Dependencies. For the full concept and how it works in general, see RAID Log. On a six sigma project project it plays the same role, tuned to this kind of work.
Why it matters for a Six Sigma Project project
Six Sigma Project projects live or die on reducing defects and variation in a process. A well-built raid log gives the team a shared, explicit reference for exactly that — reducing ambiguity, aligning stakeholders, and making problems visible early enough to act. Skipping it, or doing it generically, is how six sigma project projects drift into avoidable delay and cost.
What to include
- Risks
- Assumptions
- Issues
- Dependencies
- Owners and status
Six Sigma Project-specific considerations
Tailor the raid log to the risks that most often derail six sigma project projects:
- Data availability
- Root-cause complexity
- Sustaining control
Example
On a real six sigma project project, the raid log would be shaped by reducing defects and variation in a process. In particular, it should explicitly account for the project’s biggest risks — data availability, root-cause complexity, sustaining control — rather than treating them as afterthoughts.