View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Lotus BlossomLASR (Lightweight Approach for Software Reviews)Reverse BrainstormingATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Innovation Lotus Blossom |  Architecture LASR (Lightweight Approach for Software Reviews) |  Innovation Reverse Brainstorming |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | When a central question feels too large, the method breaks it into neighboring topic fields with their own depth of ideation. It holds structure and openness at the same time, so adjacent perspectives don't get lost. This grows an idea space out of a core problem. | 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. | 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. |
Complexitydifferent | Low | Medium | Low | High |
Timedifferent | 45-90 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 30-60 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-10 | 1 or a small team; particularly suitable for 3–4 people | 3-12 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Lotus Diagram, Idea Themes, Shortlist | 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 | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | BrainstormingIdeationCreativityDivergenceWorkshop | ArchitectureQualityRiskAssessmentLean | BrainstormingIdeationCreativityRisk | ArchitectureQualityRiskTradeoffsStakeholders |