View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ARID (Active Reviews for Intermediate Designs)ATAM (Architecture Tradeoff Analysis Method)Design CharretteLotus Blossom
| Criterion | ![]() Architecture ARID (Active Reviews for Intermediate Designs) | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) | ![]() Innovation Design Charrette | ![]() Innovation Lotus Blossom |
|---|---|---|---|---|
Purposedifferent | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | 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. | 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. | 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 | High | Medium | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | Several meetings plus preparation and analysis; total effort depends on scope | Halber Tag bis mehrere Tage | 45-90 min |
Participantsdifferent | Designers, developers as users, and facilitation | Evaluation team, architects, and relevant stakeholders | 10-50 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Sketches and Concepts, Consolidated Solution Sketch, Prioritized Direction | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | ArchitectureQualityRiskTradeoffsStakeholders | BrainstormingWorkshopCollaborationIdeation | BrainstormingIdeationCreativityDivergenceWorkshop |



