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 VUCA Scan with its method-specific working model.
Systems Thinking
VUCA Scan
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)
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Purposedifferent
The VUCA Scan helps read difficult situations more precisely. Instead of treating unclarity as generally complicated, the method separates fast change, missing knowledge, systemic entanglement, and ambiguous interpretation.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.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
LowMediumHigh
Timedifferent
30-90 min3–4 h for initial assessment; preparation and deeper analysis additionalPreparation, scenario analysis, and findings review; effort depends on scope
Participantsdifferent
1-101 or a small team; particularly suitable for 3–4 peopleArchitecture experts and stakeholders for scenarios and weighting
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
VUCA Map, Response Options, Signal and Learning PlanLean 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 checksDomain 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
SensemakingUncertaintyComplexityStrategyForesight
ArchitectureQualityRiskAssessmentLean
ArchitectureChangeAnalysisComparisonQuality
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 Business Model Stress Test with its method-specific working model.
Business Strategy
Business Model Stress Test
Paper illustration for Change Analysis.
Operations
Change Analysis
Paper illustration for Cynefin Workshop.
Decision Making
Cynefin Workshop