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 Argument Mapping
Decision Making
Argument Mapping
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
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.When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.
Complexitydifferent
MediumLowMediumLow
Timedifferent
Ongoing20–45 min1-3 h30-90 min
Participantsdifferent
2-20Small cross-functional group1-82-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Chat Transcript, Action Log, AutomationsRisk list, Mitigation plan, Assumption logArgument Map, Evidence Gaps, Decision RationaleConstraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries
Tagsno overlap
CollaborationEngineeringIncident
RiskDecisionFailurePlanning
SensemakingDecisionRationale
ConstraintsDecisionPlanningOptions
Add more methods