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 of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Paper illustration for Learning Review.
Operations
Learning Review
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Purposedifferent
When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.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.
Complexitysame
MediumMediumMedium
Timedifferent
45-60 min1-3 h30-90 min
Participantsdifferent
2-83-103-12
Formatdifferent
Workshop + asyncWorkshopWorkshop + async
Outputdifferent
Assumption map, Test backlog, Risk rankingLearning Review Notes, System Factors, Improvement ActionsPostmortem Doc, Action Items, Timeline
Tagsno overlap
AssumptionsRiskExperimentsValidation
LearningRetrospectiveIncidentOperations
Site Reliability EngineeringIncidentLearningReliability
Add more methods

Often compared together

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

Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration of a Learning Card with four fields for hypothesis, observation, insight, and action.
Product Discovery
Learning Card
Paper illustration of Riskiest Assumption Test with a method-specific labelled workspace.
Product Discovery
Riskiest Assumption Test
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