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
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Purposedifferent
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.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.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 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
LowLowMediumMedium
Timedifferent
45-90 min45-90 min30-90 min15-60 min je Zyklus
Participantsdifferent
3-122-83-121-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Force Field Map, Change Levers, Risk NotesAssumption List, Critical Assumptions, Learning PlanPostmortem Doc, Action Items, TimelineSituation Assessment, Decision Loop, Action Updates
Tagsno overlap
ChangeDecisionStrategy
AssumptionsRiskDecisionDiscovery
Site Reliability EngineeringIncidentLearningReliability
DecisionChangeLearningStrategy
Add more methods