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
Paper illustration for Learning Review.
Operations
Learning Review
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
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 Mad Sad Glad
Agile
Mad Sad Glad
Purposedifferent
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 domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole.When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.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
MediumMediumLowLow
Timedifferent
1-3 h1-3 h45–75 min30-60 min
Participantsdifferent
3-103-10Team members involved3-10
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Learning Review Notes, System Factors, Improvement ActionsDomain Context Map, Boundary Notes, Ownership Map4Ls Board, Learning Themes, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
LearningRetrospectiveIncidentOperations
Domain-Driven DesignContextBoundaries
RetrospectiveLearningReflectionTeam
RetrospectiveTeamReflection
Add more methods