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 of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Purposedifferent
Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy.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.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.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.
Complexitydifferent
HighLowHighHigh
Timedifferent
Half day30-60 minPreparation, scenario analysis, and findings review; effort depends on scope2-6 h
Participantsdifferent
3-122-8Architecture experts and stakeholders for scenarios and weighting3-10
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Leverage Map, Action StrategyFishbone Diagram, Cause Categories, Investigation BacklogDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
Systems thinkingChangeStrategy
Root causeQualityOperations
ArchitectureChangeAnalysisComparisonQuality
RiskQualityOperationsRoot cause
Add more methods