Plan my session
Plan a concrete work block with agenda, roles, preparation, and a copyable result artifact.
Session: RAID Log
The plan distributes preparation, review, and outcome work across an asynchronous work run. Your inputs flow directly into the session brief and work artifact.
Async work run with 1-3 Pflege, Briefing für alle. The plan uses the existing method logic and the runsheet.
RunsheetUse the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.
The session works directly toward RAID Log. After the session, the artifact should be shareable, reviewable, or reusable.
- 1
Prepare brief
15-30 minPrepare the working question, input, target artifact, and review deadline for RAID Log. Link relevant data, sources, and existing artifacts.
OwnerSession brief - 2
Work asynchronously
24 to 72 hParticipants work through the method along the template. Focus: add contributions directly to the artifact, mark assumptions, and link evidence.
ParticipantsRAID Log - 3
Consolidate review
20-30 minCluster comments, contradictions, and open questions. Sort unclear points into decisions, risks, or follow-ups.
FacilitatorReview notes - 4
Finalize artifact
15-30 minCreate the integrated version, set status, and schedule the next review or decision point.
OwnerStatusbericht-Quelle - 5
Publish artifact
10 minCheck the artifact for completeness, define location, set version or status, and name review recipients.
OwnerRAID Log
Session Brief
For invitations, boards, tickets, PR descriptions, or workshop notes.
session-brief.md
Session Brief: RAID Log
Goal
Artifact: RAID Log
Working Question
Which risks, assumptions, issues and dependencies are currently open, who takes care of them, and which ones need movement or escalation now?
Context
Initiative charter; stakeholder list; current discovery or kickoff notes; known risks, assumptions, dependencies from Pre-Mortem or kickoff.
Setup
- Format: Async work run
- Duration: 24 to 72 h
- Mode: asynchronous
- Participants: One maintenance owner (PM, RTE or program lead); owner per entry from relevant teams; sponsor as escalation recipient; all contributors with write access.
- Owner: One maintenance owner (PM, RTE or program lead)
- Participation mode: Team round, shared work and alignment
- Outcome logic: Finish artifact
Participation Logic
Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.
Outcome Logic
The session works directly toward RAID Log. After the session, the artifact should be shareable, reviewable, or reusable.
Input
Table or database with columns ID, category (R/A/I/D), description, owner, status, date created, date last updated, next action; wiki or sheet link; briefing template for status reports.
Preparation
Create table, configure columns. Definition per category as header: Risk = occurrence uncertain, negative impact; Assumption = assumed true, testable; Issue = already occurred, needs action; Dependency = external input needed. Define status values (Open, In Progress, Resolved, Closed).
Agenda
-
Prepare brief (15-30 min) Owner: Owner Action: Prepare the working question, input, target artifact, and review deadline for RAID Log. Link relevant data, sources, and existing artifacts. Output: Session brief
-
Work asynchronously (24 to 72 h) Owner: Participants Action: Participants work through the method along the template. Focus: add contributions directly to the artifact, mark assumptions, and link evidence. Output: RAID Log
-
Consolidate review (20-30 min) Owner: Facilitator Action: Cluster comments, contradictions, and open questions. Sort unclear points into decisions, risks, or follow-ups. Output: Review notes
-
Finalize artifact (15-30 min) Owner: Owner Action: Create the integrated version, set status, and schedule the next review or decision point. Output: Statusbericht-Quelle
-
Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: RAID Log
Closeout
- Update result artifact: RAID Log
- Define location, version, and review recipients.
- Define owner, next step, and review date.
Work artifact
Pre-filled starting point based on the matching template.
work-artifact.md
RAID Log: RAID Log
Working Question
Which risks, assumptions, issues and dependencies are currently open, who takes care of them, and which ones need movement or escalation now?
Context
Initiative charter; stakeholder list; current discovery or kickoff notes; known risks, assumptions, dependencies from Pre-Mortem or kickoff.
Participants
- Owner: One maintenance owner (PM, RTE or program lead)
- Participants: One maintenance owner (PM, RTE or program lead); owner per entry from relevant teams; sponsor as escalation recipient; all contributors with write access.
Input
Table or database with columns ID, category (R/A/I/D), description, owner, status, date created, date last updated, next action; wiki or sheet link; briefing template for status reports.
Template
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.
Completion Check
- RAID Log is complete enough for review:
- Location:
- Version / status:
- Review by:
- Next step:
Next Step
- Review result
- Mark open questions
- Schedule review or decision
RAID Log Working Template
View templateCompact working template for RAID Log with context, input, output artifacts, and next step.markdown
raid-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.
- Working question, owner, and target artifact are visible.
- The result fits RAID Log.
- Entries with ID and creation date. Changes with date in edit log. Resolved entries by quarter into archive tab. Weekly briefings as wiki page with date, not overwritten.
- Open questions are noted as follow-ups.
- The next review or decision point is scheduled.