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 Intervention Mapping.
Systems Thinking
Intervention Mapping
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Purposedifferent
Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.
Complexitydifferent
HighHighHighLow
Timedifferent
1-5 Tage2-6 hPreparation, scenario analysis, and findings review; effort depends on scope30-60 min
Participantsdifferent
4-123-10Architecture experts and stakeholders for scenarios and weighting2-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Logic Model, Change Objectives, Intervention Components, Evaluation PlanFMEA Table, Risk Priority, Mitigation ActionsDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesFishbone Diagram, Cause Categories, Investigation Backlog
Tagsno overlap
ChangeSystems thinkingCapability
RiskQualityOperationsRoot cause
ArchitectureChangeAnalysisComparisonQuality
Root causeQualityOperations
Add more methods