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
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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.When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.
Complexitydifferent
MediumLowLowLow
Timedifferent
30-90 min30-60 min1-2 Tage30-60 min
Participantsdifferent
3-123-101-43-12
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Postmortem Doc, Action Items, TimelineEmotion Board, Themes, Action ItemsArchitecture Document, Context View, Runtime View, Deployment ViewStart Stop Continue Board, Improvement Actions
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
RetrospectiveTeamReflection
ArchitectureDocumentationCommunication
RetrospectiveImprovementTeamReflection
Add more methods