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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Purposedifferent
When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.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.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.
Complexitydifferent
MediumLowLow
Timedifferent
1-3 h45-90 min30-60 min
Participantsdifferent
2-83-123-12
Formatdifferent
Workshop + asyncWorkshopWorkshop
Outputdifferent
Context Map, Integration Patterns, Boundary NotesForce Field Map, Change Levers, Risk NotesStart Stop Continue Board, Improvement Actions
Tagsno overlap
Domain-Driven DesignBoundariesStrategy
ChangeDecisionStrategy
RetrospectiveImprovementTeamReflection
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