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 Delegation Poker.
Facilitation
Delegation Poker
Paper illustration for RAPID
Decision Making
RAPID
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Purposedifferent
When decisions get stuck between leadership and team, Delegation Poker clarifies the desired scope of autonomy. It shows how much decision-making latitude a role should actually get in practice.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.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.
Complexitydifferent
LowMediumMedium
Timedifferent
45-90 min45-90 min30-90 min
Participantsdifferent
3-103-123-12
Formatdifferent
WorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Delegation Board, Decision Boundaries, Role AgreementsRAPID Role Map, Recommendation, Decision LogPostmortem Doc, Action Items, Timeline
Tagsno overlap
AutonomyRolesTeam
DecisionRolesGovernance
Site Reliability EngineeringIncidentLearningReliability
Add more methods

Often compared together

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

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 of Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command