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
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis
Paper illustration of GIST Planning with its method-specific working model.
Product Strategy
GIST Planning
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Purposedifferent
GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing.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.LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail.
Complexitysame
MediumMediumMedium
Timedifferent
1-3 hWochen bis Monate je Goal3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
2-83-101 or a small team; particularly suitable for 3–4 people
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Gap Matrix, Action Plan, Risk NotesGoals, Idea bank, Step-project list, Tasks, Learning reportsLean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks
Tagsno overlap
StrategyAnalysisPlanning
RoadmapOutcomesPlanningExperiments
ArchitectureQualityRiskAssessmentLean
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of a branching impact map with a Why goal at the root, actor circles, How behavior changes and What options.
Product Strategy
Impact Mapping
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping