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 of Five-Minute VC Check with its method-specific working model.
Business Strategy
5-Minuten VC-Check
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Paper illustration of Family Tree Analysis with its method-specific working model.
Operations
Family Tree 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.The 5-Minute VC Check clarifies opportunities and strategic options at the earliest idea stage. It compares problem quality, customer willingness to pay, alternatives, differentiation, and market potential, and captures the result as a VC-check note, go/sharpen/park decision, and risk list.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 series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
30-90 min5-15 min2-4 h2-4 h
Participantsdifferent
3-121-52-62-6
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Postmortem Doc, Action Items, TimelineVC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation stepBarrier Inventory, Failure Analysis per Barrier, Action BacklogFamily Tree Diagram, Pattern Notes, Systemic Measures
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
StartupValidationCompetition
Root causeSafetyIncident
Root causePatternsIncidentSystemic
Add more methods