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
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration for Causal Factor Analysis.
Operations
Causal Factor Analysis
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
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.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.For an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events.For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions.
Complexitydifferent
LowMediumHighMedium
Timedifferent
45-90 min30-90 min2-6 h2-4 h
Participantsdifferent
3-103-123-102-6
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Delegation Board, Decision Boundaries, Role AgreementsPostmortem Doc, Action Items, TimelineEvent Timeline, Causal Factor Chart, Cause List, Corrective ActionsBarrier Inventory, Failure Analysis per Barrier, Action Backlog
Tagsno overlap
AutonomyRolesTeam
Site Reliability EngineeringIncidentLearningReliability
CausalityIncidentRoot causeTimeline
Root causeSafetyIncident
Add more methods