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 Accountability Ladder
Operations
Accountability Ladder
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
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 for Mad Sad Glad
Agile
Mad Sad Glad
Purposedifferent
With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on.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.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.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
LowMediumLowLow
Timedifferent
20-45 min1-3 h30-60 min30-60 min
Participantsdifferent
1-82-83-123-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Ownership Reflection, Action Commitment, Coaching NotesContext Map, Integration Patterns, Boundary NotesStart Stop Continue Board, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
ResponsibilityLeadershipTeam
Domain-Driven DesignBoundariesStrategy
RetrospectiveImprovementTeamReflection
RetrospectiveTeamReflection
Add more methods