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 of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for Learning Review.
Operations
Learning Review
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
Purposedifferent
An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.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.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
15-45 min1-3 h30-60 min1-2 Tage
Participantsdifferent
1-33-103-101-4
Formatdifferent
AsyncWorkshopWorkshopWorkshop + async
Outputdifferent
ADR File, Decision Log, RationaleLearning Review Notes, System Factors, Improvement ActionsEmotion Board, Themes, Action ItemsArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
LearningRetrospectiveIncidentOperations
RetrospectiveTeamReflection
ArchitectureDocumentationCommunication
Add more methods