View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture arc42 |  DevOps Blameless Postmortem |  Agile Mad Sad Glad |  Agile Start Stop Continue |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | Low | Medium | Low | Low |
Timedifferent | 1-2 Tage | 30-90 min | 30-60 min | 30-60 min |
Participantsdifferent | 1-4 | 3-12 | 3-10 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Postmortem Doc, Action Items, Timeline | Emotion Board, Themes, Action Items | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | ArchitectureDocumentationCommunication | Site Reliability EngineeringIncidentLearningReliability | RetrospectiveTeamReflection | RetrospectiveImprovementTeamReflection |