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
Paper illustration for Soft Systems Methodology.
Systems Thinking
Soft Systems Methodology
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
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.Soft Systems Methodology helps explore unclear or politically charged problems systematically. Instead of forcing a quick answer, the method builds a shared understanding of perspectives and room for action.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.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
MediumHighLowLow
Timedifferent
Ongoing0.5-3 Tage20–45 min45-90 min
Participantsdifferent
2-205-15Small cross-functional group2-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Chat Transcript, Action Log, AutomationsRich Picture, Root Definitions, Conceptual Models, Change AgendaRisk list, Mitigation plan, Assumption logAssumption List, Critical Assumptions, Learning Plan
Tagsno overlap
CollaborationEngineeringIncident
Soft systemsComplexitySensemakingSystems thinking
RiskDecisionFailurePlanning
AssumptionsRiskDecisionDiscovery
Add more methods