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 for Learning Review.
Operations
Learning Review
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
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.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.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.
Complexitydifferent
MediumMediumLow
Timedifferent
1-3 h1-3 h30-60 min
Participantsdifferent
2-83-103-10
Formatdifferent
Workshop + asyncWorkshopWorkshop
Outputdifferent
Context Map, Integration Patterns, Boundary NotesLearning Review Notes, System Factors, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
Domain-Driven DesignBoundariesStrategy
LearningRetrospectiveIncidentOperations
RetrospectiveTeamReflection
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 of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem