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
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: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of Rapid Ideation with its method-specific working model.
Innovation
Rapid Ideation
Paper illustration of an eight-panel idea sheet with varied sketches beside a timer set to eight minutes.
Innovation
Crazy 8s
Purposedifferent
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.ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.When a decision needs to be prepared quickly, the method generates many solution-close variants in a short time. It deliberately relies on pace to undercut self-censorship and perfectionism. This quickly produces a usable field for prioritization and further work.With only a few minutes available and a still-fuzzy solution search, the method forces a wide range of variants. It produces fast sketches before the first idea can settle in, making different directions directly comparable and open to further development.
Complexitydifferent
MediumHighLowLow
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additionalSeveral meetings plus preparation and analysis; total effort depends on scope5-20 min8-15 min
Participantsdifferent
1 or a small team; particularly suitable for 3–4 peopleEvaluation team, architects, and relevant stakeholders1-201-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Lean 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 checksPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsIdeenpool, Roh-Shortlist, ClusterSketch Set, Idea Shortlist, Direction Options
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
ArchitectureQualityRiskTradeoffsStakeholders
BrainstormingIdeationDivergenceSpeed
BrainstormingSketchingSpeedDivergenceDesign sprint
Add more methods