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
ChatOps workspace showing the question, observations, and next decision.
DevOps
ChatOps
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Purposedifferent
For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together.In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.
Complexitydifferent
MediumLowMediumLow
Timedifferent
Ongoing20–45 min1-3 h45-90 min
Participantsdifferent
2-20Small cross-functional group3-122-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Chat Transcript, Action Log, AutomationsRisk list, Mitigation plan, Assumption logKnowledge Map, Critical Knowledge Areas, Transfer PlanAssumption List, Critical Assumptions, Learning Plan
Tagsno overlap
CollaborationEngineeringIncident
RiskDecisionFailurePlanning
KnowledgeMappingRisk
AssumptionsRiskDecisionDiscovery
Add more methods