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 Lightning Decision Jam working structure.
Facilitation
Decision Jam
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Paper illustration for OODA Loop.
Decision Making
OODA Loop
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.When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer.When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first.In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia.
Complexitydifferent
MediumLowLowMedium
Timedifferent
30-90 min60-90 min60–90 min15-60 min je Zyklus
Participantsdifferent
3-124-102-81-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Postmortem Doc, Action Items, TimelineProblem Cluster, Prioritized Challenge, ExperimentStakeholder Map, Engagement Plan, Risk NotesSituation Assessment, Decision Loop, Action Updates
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
FacilitationDecisionProblem solvingWorkshop
StakeholdersAlignmentFacilitationChange
DecisionChangeLearningStrategy
Add more methods