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 of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Paper illustration of MORT Analysis with its method-specific working model.
Operations
MORT Analysis
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.For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions.For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps.
Complexitydifferent
MediumMediumMediumHigh
Timedifferent
30-90 min2–4 h review as a planning range; preparation and evaluation additional2-4 hMehrere Tage bis Wochen
Participantsdifferent
3-12Designers, developers as users, and facilitation2-62-6
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Postmortem Doc, Action Items, TimelinePrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsBarrier Inventory, Failure Analysis per Barrier, Action BacklogMORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
ArchitectureEngineeringFeedbackValidationTasks
Root causeSafetyIncident
Root causeSafetySystemicIncident
Add more methods