View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Morphological AnalysisATAM (Architecture Tradeoff Analysis Method)Reverse BrainstormingLASR (Lightweight Approach for Software Reviews)
| Criterion |  Innovation Morphological Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Innovation Reverse Brainstorming |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
Purposedifferent | For a search for solutions with many degrees of freedom, a grid emerges for systematic combinations. The method separates features, variants, and exclusion criteria, so the space gets explored deliberately. | 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. | 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. | 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 | Medium | High | Low | Medium |
Timedifferent | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope | 30-60 min | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 2-8 | Evaluation team, architects, and relevant stakeholders | 3-12 | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Morphological Box, Concept Combinations, Idea Shortlist | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Reverse Ideas, Risk Themes, Solution Ideas | 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 |
Tagsno overlap | IdeationInnovationCreativity | ArchitectureQualityRiskTradeoffsStakeholders | BrainstormingIdeationCreativityRisk | ArchitectureQualityRiskAssessmentLean |