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 the Force Field Analysis working structure.
Decision Making
Force Field 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)
Paper illustration for Change Analysis.
Operations
Change Analysis
Purposedifferent
In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving.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 deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise.
Complexitydifferent
LowLowHighMedium
Timedifferent
45-90 min30-60 minPreparation, scenario analysis, and findings review; effort depends on scope45-120 min
Participantsdifferent
3-122-8Architecture experts and stakeholders for scenarios and weighting2-6
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Force Field Map, Change Levers, Risk NotesFishbone 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 alternativesChange Matrix, Cause Hypotheses, Validation Questions, Action List
Tagsno overlap
ChangeDecisionStrategy
Root causeQualityOperations
ArchitectureChangeAnalysisComparisonQuality
ChangeRoot causeTroubleshootingComparison
Add more methods