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
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration for DACI
Decision Making
DACI
Purposedifferent
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.In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated.
Complexitydifferent
MediumLowLow
Timedifferent
30-90 min45-90 min30-60 min
Participantsdifferent
3-123-122-10
Formatdifferent
Workshop + asyncWorkshopWorkshop + async
Outputdifferent
Postmortem Doc, Action Items, TimelineExpectation Map, Alignment Notes, AgreementsDACI Matrix, Decision Owner, Decision Log
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
AlignmentStakeholdersTeam
DecisionRolesGovernanceAlignment
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping
Paper illustration for RAPID
Decision Making
RAPID
Paper illustration of Stakeholder Salience Model with its method-specific working model.
Facilitation
Stakeholder Salience Model
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