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 Mad Sad Glad
Agile
Mad Sad Glad
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
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.After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures.When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.
Complexitydifferent
LowMediumLowMedium
Timedifferent
30-60 min30-90 min45-90 min1-2 h
Participantsdifferent
3-103-123-124-12
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Emotion Board, Themes, Action ItemsPostmortem Doc, Action Items, TimelineExpectation Map, Alignment Notes, AgreementsAlignment Map, Open Issues, Decision Questions
Tagsno overlap
RetrospectiveTeamReflection
Site Reliability EngineeringIncidentLearningReliability
AlignmentStakeholdersTeam
AlignmentStakeholdersStrategyFacilitation
Add more methods