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 for OODA Loop.
Decision Making
OODA Loop
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
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
In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia.For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments.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.
Complexitydifferent
MediumHighMedium
Timedifferent
15-60 min je Zyklus1-4 h3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
1-83-81 or a small team; particularly suitable for 3–4 people
Formatdifferent
Workshop + asyncWorkshopWorkshop + async
Outputdifferent
Situation Assessment, Decision Loop, Action UpdatesChallenge Findings, Risk Register, Mitigation 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 checks
Tagsno overlap
DecisionChangeLearningStrategy
RiskDecisionSensemaking
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 the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration of a calibrated five-by-five risk matrix with response cards.
Decision Making
Risk Matrix
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)