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
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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.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.LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail.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.
Complexitydifferent
MediumLowMediumLow
Timedifferent
30-90 min1-2 Tage3–4 h for initial assessment; preparation and deeper analysis additional15-45 min
Participantsdifferent
3-121-41 or a small team; particularly suitable for 3–4 people1-3
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Postmortem Doc, Action Items, TimelineArchitecture Document, Context View, Runtime View, Deployment ViewLean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checksADR File, Decision Log, Rationale
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
ArchitectureDocumentationCommunication
ArchitectureQualityRiskAssessmentLean
ArchitectureRationaleDocumentationGovernance
Add more methods