View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:BrainstormingATAM (Architecture Tradeoff Analysis Method)LASR (Lightweight Approach for Software Reviews)Reverse Brainstorming
| Criterion |  Innovation Brainstorming |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture LASR (Lightweight Approach for Software Reviews) |  Innovation Reverse Brainstorming |
|---|---|---|---|---|
Purposedifferent | When a team faces an open question with many obvious directions, the method first creates breadth instead of premature commitment. It separates idea flow from evaluation and makes lines of thought visible, creating a pool for selection and further development. | 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. | 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. | For persistent errors or blockages, the method shifts the view to the opposite of the desired effect. It exposes the mechanics of failure and makes hidden causes easier to grasp. This makes improvement more concrete and the problem clearer. |
Complexitydifferent | Low | High | Medium | Low |
Timedifferent | 30-60 min | Several meetings plus preparation and analysis; total effort depends on scope | 3–4 h for initial assessment; preparation and deeper analysis additional | 30-60 min |
Participantsdifferent | 4-12 | Evaluation team, architects, and relevant stakeholders | 1 or a small team; particularly suitable for 3–4 people | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Idea pool, Theme clusters, Shortlist | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | 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 checks | Reverse Ideas, Risk Themes, Solution Ideas |
Tagsno overlap | BrainstormingIdeationCreativityWorkshopDivergence | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureQualityRiskAssessmentLean | BrainstormingIdeationCreativityRisk |