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 for Round Robin Brainstorming
Innovation
Round Robin Brainstorming
Paper illustration for 1-2-4-All.
Facilitation
1-2-4-All
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.With unevenly distributed speaking time, the method brings every person into the contribution one after another. It prevents early voices from setting the direction while still producing a shared idea space. This makes participation plannable and the team's diversity visible.When many people in a group too rarely get to speak, 1-2-4-All distributes thinking time more fairly. The format builds participation step by step and makes quiet or still-unformed thoughts usable faster.
Complexitydifferent
MediumHighLowLow
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additionalSeveral meetings plus preparation and analysis; total effort depends on scope20-45 min10-20 min
Participantsdifferent
1 or a small team; particularly suitable for 3–4 peopleEvaluation team, architects, and relevant stakeholders4-104-100+
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
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 investigationsIdea List, Cluster, ShortlistIdea List, Shared Insights, Emergent Themes
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
ArchitectureQualityRiskTradeoffsStakeholders
BrainstormingIdeationFacilitationInclusionCreativity
FacilitationInclusionIdeation
Add more methods