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
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration for Sailboat Retrospective
Agile
Sailboat 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
Purposedifferent
After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures.ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture.When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.
Complexitydifferent
MediumMediumLowLow
Timedifferent
30-90 min2–4 h review as a planning range; preparation and evaluation additional45-90 min45–75 min
Participantsdifferent
3-12Designers, developers as users, and facilitation4-12Team members involved
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Postmortem Doc, Action Items, TimelinePrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsSailboat Board, Risks, Improvement Actions4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
ArchitectureEngineeringFeedbackValidationTasks
RetrospectiveTeamImprovement
RetrospectiveLearningReflectionTeam
Add more methods