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 RAPID
Decision Making
RAPID
Paper illustration of Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping
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 complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels.In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
30-90 min45-90 min45-90 min90-180 min
Participantsdifferent
3-123-123-124-12
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Postmortem Doc, Action Items, TimelineExpectation Map, Alignment Notes, AgreementsRAPID Role Map, Recommendation, Decision LogDecision Rights Matrix, Agreement
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
AlignmentStakeholdersTeam
DecisionRolesGovernance
DecisionGovernanceAlignmentResponsibility
Add more methods