View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:LASR (Lightweight Approach for Software Reviews)Design CharretteATAM (Architecture Tradeoff Analysis Method)Lotus Blossom
| Criterion |  Architecture LASR (Lightweight Approach for Software Reviews) |  Innovation Design Charrette |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Innovation Lotus Blossom |
|---|---|---|---|---|
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. | In a tightly timed design process with many participants, the method pools several lines of thinking in a short time. It brings parallel design energy without letting the discussion tip into endless coordination. This quickly produces solid directions for architecture or space. | 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 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. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 3–4 h for initial assessment; preparation and deeper analysis additional | Halber Tag bis mehrere Tage | Several meetings plus preparation and analysis; total effort depends on scope | 45-90 min |
Participantsdifferent | 1 or a small team; particularly suitable for 3–4 people | 10-50 | Evaluation team, architects, and relevant stakeholders | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
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 checks | Sketches and Concepts, Consolidated Solution Sketch, Prioritized Direction | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | ArchitectureQualityRiskAssessmentLean | BrainstormingWorkshopCollaborationIdeation | ArchitectureQualityRiskTradeoffsStakeholders | BrainstormingIdeationCreativityDivergenceWorkshop |