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 RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement.When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.
Complexitydifferent
HighLowMediumLow
Timedifferent
0.5-3 Tage30 min Setup, dann laufend90-180 min20-40 min initial, dann laufend
Participantsdifferent
5-151-3 maintaining, briefing for everyone4-123-15
Formatdifferent
WorkshopAsyncWorkshopWorkshop + async
Outputdifferent
Rich Picture, Root Definitions, Conceptual Models, Change AgendaRAID Log, Status Report SourceDecision Rights Matrix, AgreementROAM Board, Owner List
Tagsno overlap
Soft systemsComplexitySensemakingSystems thinking
RiskTrackingStakeholdersGovernance
DecisionGovernanceAlignmentResponsibility
RiskAgileTrackingAlignment
Add more methods