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 for Mad Sad Glad
Agile
Mad Sad Glad
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
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.When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible.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.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
Ongoing30-60 min45-90 min15-60 min je Zyklus
Participantsdifferent
2-203-103-121-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Chat Transcript, Action Log, AutomationsEmotion Board, Themes, Action ItemsForce Field Map, Change Levers, Risk NotesSituation Assessment, Decision Loop, Action Updates
Tagsno overlap
CollaborationEngineeringIncident
RetrospectiveTeamReflection
ChangeDecisionStrategy
DecisionChangeLearningStrategy
Add more methods