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 GIST Planning with its method-specific working model.
Product Strategy
GIST Planning
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
GIST Planning helps clarify target groups, value, goals, and priorities. It links customer value, product logic, and decision priorities, and captures the result as goals, an idea bank, and a step-project list.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.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 single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.
Complexitydifferent
MediumMediumHighLow
Timedifferent
Wochen bis Monate je Goal1-4 hPreparation, scenario analysis, and findings review; effort depends on scope15-30 min
Participantsdifferent
3-103-8Architecture experts and stakeholders for scenarios and weighting2-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Goals, Idea bank, Step-project list, Tasks, Learning reportsProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesRoot cause notes, Countermeasures
Tagsno overlap
RoadmapOutcomesPlanningExperiments
Root causeProblem solvingQualityIncident
ArchitectureChangeAnalysisComparisonQuality
Root causeIncidentLeanProblem solving
Add more methods