methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration for Learning Review.
Operations
Learning Review
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Purposedifferent
After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.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.After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement.
Complexitydifferent
MediumLowLow
Timedifferent
1-3 h30 min Setup, dann laufend20-45 min
Participantsdifferent
3-101-3 maintaining, briefing for everyone3-12
Formatdifferent
WorkshopAsyncWorkshop + async
Outputdifferent
Learning Review Notes, System Factors, Improvement ActionsRAID Log, Status Report SourceLessons learned, Action items, Event summary
Tagsno overlap
LearningRetrospectiveIncidentOperations
RiskTrackingStakeholdersGovernance
LearningOperationsImprovement
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem