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 illustration of Value Chain Analysis with its method-specific working model.
Business Strategy
Value Chain Analysis
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)
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.Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list.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.
Complexitydifferent
HighHighLowHigh
Timedifferent
Half dayHalf day30-60 minPreparation, scenario analysis, and findings review; effort depends on scope
Participantsdifferent
3-123-82-8Architecture experts and stakeholders for scenarios and weighting
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Leverage Map, Action StrategyValue Chain Map, Lever ListFishbone 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 alternatives
Tagsno overlap
Systems thinkingChangeStrategy
StrategyBusiness modelDiagnosisAnalysis
Root causeQualityOperations
ArchitectureChangeAnalysisComparisonQuality
Add more methods