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 a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
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 wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.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.
Complexitydifferent
MediumLowLow
Timedifferent
Ongoing30-60 min45-90 min
Participantsdifferent
2-203-123-12
Formatdifferent
Workshop + asyncWorkshopWorkshop
Outputdifferent
Chat Transcript, Action Log, AutomationsStart Stop Continue Board, Improvement ActionsForce Field Map, Change Levers, Risk Notes
Tagsno overlap
CollaborationEngineeringIncident
RetrospectiveImprovementTeamReflection
ChangeDecisionStrategy
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective