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 Soft Systems Methodology.
Systems Thinking
Soft Systems Methodology
Paper illustration of an IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Purposedifferent
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.IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus.During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.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.
Complexitydifferent
HighMediumMediumMedium
Timedifferent
0.5-3 Tage1-3 hAs needed1-3 h
Participantsdifferent
5-152-84-151-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Rich Picture, Root Definitions, Conceptual Models, Change AgendaIssue Map, Positions, Argument NotesIncident Log, Action Tracker, Stakeholder UpdatesArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
Soft systemsComplexitySensemakingSystems thinking
RationaleKnowledgeDecision
IncidentOperationsReliability
SensemakingDecisionRationale
Add more methods