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
ChatOps workspace showing the question, observations, and next decision.
DevOps
ChatOps
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration for Learning Review.
Operations
Learning Review
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Purposedifferent
For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together.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.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.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
MediumLowMediumMedium
Timedifferent
Ongoing45-90 min1-3 h15-60 min je Zyklus
Participantsdifferent
2-203-123-101-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Chat Transcript, Action Log, AutomationsForce Field Map, Change Levers, Risk NotesLearning Review Notes, System Factors, Improvement ActionsSituation Assessment, Decision Loop, Action Updates
Tagsno overlap
CollaborationEngineeringIncident
ChangeDecisionStrategy
LearningRetrospectiveIncidentOperations
DecisionChangeLearningStrategy
Add more methods