View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:BrainwritingATAM (Architecture Tradeoff Analysis Method)Mind MappingLASR (Lightweight Approach for Software Reviews)
| Criterion |  Innovation Brainwriting |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Facilitation Mind Mapping |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
Purposedifferent | When loud voices or hierarchy distort the idea search, the method creates a quiet entry into joint development. It gives everyone thinking space and gathers contributions without social brakes, making diversity more visible and easier to build on. | 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 topic is still unclear and too many thoughts surface at once, Mind Mapping creates an open surface for ordering them. It makes connections, subtopics, and starting points visible without fixing them too early. | 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 | Low | High | Low | Medium |
Timedifferent | 15-30 min | Several meetings plus preparation and analysis; total effort depends on scope | 15-45 min | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 3-12 | Evaluation team, architects, and relevant stakeholders | 1-10 | 1 or a small team; particularly suitable for 3–4 people |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Idea sheets, Expanded concepts, Prioritized list | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Mind Map, Topic Clusters, Open Questions | 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 | BrainstormingCollaborationInclusionIdeas | ArchitectureQualityRiskTradeoffsStakeholders | BrainstormingIdeasMappingStructureFacilitation | ArchitectureQualityRiskAssessmentLean |