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 the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Causal Loop Diagram workspace showing the question, observations, and next decision.
Systems Thinking
Causal Loop Diagram
Paper illustration of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
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.In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving.A Causal Loop Diagram makes feedback, reinforcement, and balance in a system legible. It uncovers side effects and self-reinforcement that stay hidden in linear explanations.Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy.
Complexitydifferent
MediumLowMediumHigh
Timedifferent
30-90 min45-90 min1-3 hHalf day
Participantsdifferent
3-123-122-83-12
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Postmortem Doc, Action Items, TimelineForce Field Map, Change Levers, Risk NotesCausal Loop Diagram, Feedback Notes, Leverage PointsLeverage Map, Action Strategy
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
ChangeDecisionStrategy
FeedbackSystems thinkingCausalityDynamics
Systems thinkingChangeStrategy
Add more methods