Purpose
Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.
Delivery
RAID Log
Moves scope, sequence, and delivery flow toward a concrete result through "create a table for Risks, Assumptions, Issues, and Dependencies", "carry over initial entries from discovery and kickoff", and "archive resolved items instead of deleting them".
Which risks, assumptions, issues and dependencies are currently open, who takes care of them, and which ones need movement or escalation now?
LowAsync30 min Setup, dann laufend
How it works
The team follows the steps "create a table for Risks, Assumptions, Issues, and Dependencies", "carry over initial entries from discovery and kickoff", "set an owner and next action for each entry", "let program management maintain it weekly", and "archive resolved items instead of deleting them". Each step is made visible. At the end, RAID Log and status-report source are available so decisions, tests, or actions can continue directly.
Visual orientation
Method sketch for a quick mental model.
Flow
- 1Create a table for Risks, Assumptions, Issues, and Dependencies
- 2Carry over initial entries from discovery and kickoff
- 3Set an owner and next action for each entry
- 4Maintain it weekly in program management
- 5Archive resolved items instead of deleting them
The runsheet guides execution with 4 phases, timeboxes, 5 pitfalls, and clear stop criteria.
Open runsheetIdeal for
- Program or multi-team initiatives
- Compliance projects
- Handovers to clients
Not good for
- Fast discovery sprints
- Pure engineering backlogs
Deep dive
In detail
The RAID Log is a project management classic that combines risks, assumptions, open issues, and dependencies in one living list. Each entry gets an owner, status, date, and next step. It works well as an asynchronous backbone artifact and briefing source for stakeholders.
Facilitation
Set aside a fixed 15-minute slot once a week to keep it current. Close stale items decisively or move them to a different category.
Output artifacts
RAID LogStatusbericht-Quelle
Artifact templates
RAID Log Working TemplateCompact working template for RAID Log with context, input, output artifacts, and next step.markdown
RAID Log Working TemplateCompact working template for RAID Log with context, input, output artifacts, and next step.
markdownraid-log-working-template.md
Compact working template for RAID Log with context, input, output artifacts, and next step.
RAID Log Working Template
Goal
Keeps risks, assumptions, issues, and dependencies captured in one place.
Context
When and for what do we use this method?
Input
Which data, observations, decisions, or materials are available?
Execution
Short notes along the runsheet.
Output artifacts
- RAID Log:
- Status report source:
Assumptions and open questions
- ...
Decision / next step
Owner, date, and success signal.
When to choose differently
Short decision aid for existing alternatives.
ROAM Board
Statt RAID Log, wenn ihr Risiken gemeinsam besprechen wollt und nur einen lebendigen Maßnahmenstatus braucht.
Similar methods
All methodsAgile
ROAM Board
Moves backlog, sprint work, and team flow toward a concrete result through "create a board with the four columns Resolved, Owned, Accepted, Mitigated", "carry over risks from earlier stages such as Risk Storming", and "update the board at every review".
Statt RAID Log, wenn ihr Risiken gemeinsam besprechen wollt und nur einen lebendigen Maßnahmenstatus braucht.
Decision Making
Risk Matrix
Moves options, criteria, and risks toward a concrete result through "set the scales for likelihood and impact", "collect risks or carry them over from earlier identification", and "define actions for each high-risk item".
Delivery
Communication Plan
Turns scope, sequencing, and delivery flow into a tangible result by listing stakeholders and audiences, clarifying information needs, and planning review and adaptation.
Facilitation
Stakeholder Salience Model
Moves group input, selection, and decision toward a concrete result through "prepare the stakeholder list", "define power, legitimacy, and urgency", and "derive strategy by class".
Delivery
MoSCoW
Turns scope, ordering, and flow into a tangible result by collecting items, assigning must/should/could/won't categories, and finalizing the release set.
Facilitation
Power Interest Grid
Moves group input, selection, and decision toward a concrete result through "collect stakeholders individually and by group", "explain power and interest", and "derive a strategy for each quadrant".