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 a decision table with criteria rows, weighted ratings, and a narrowly leading alternative.
Decision Making
Decision Matrix
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
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)
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Purposedifferent
When several options collide with several criteria, comparison quickly becomes subjective. A Decision Matrix makes the trade-off visible and brings weighting, criteria, and options into a shared logic.When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.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.In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.
Complexitydifferent
MediumLowMediumLow
Timedifferent
45-90 min30-90 min3–4 h for initial assessment; preparation and deeper analysis additional20–45 min
Participantsdifferent
2-82-81 or a small team; particularly suitable for 3–4 peopleSmall cross-functional group
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Decision Matrix, Scoring Rationale, Selected OptionConstraint List, Hard/Soft Classification, Option Impact Notes, Decision BoundariesLean 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 checksRisk list, Mitigation plan, Assumption log
Tagsno overlap
DecisionCriteriaScoringTradeoffs
ConstraintsDecisionPlanningOptions
ArchitectureQualityRiskAssessmentLean
RiskDecisionFailurePlanning
Add more methods