View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:CATWOE AnalysisARID (Active Reviews for Intermediate Designs)Assumption MappingATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Systems Thinking CATWOE Analysis |  Architecture ARID (Active Reviews for Intermediate Designs) |  Product Discovery Assumption Mapping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way. | 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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | 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 | Medium | Medium | Medium | High |
Timedifferent | 45-90 min | 2–4 h review as a planning range; preparation and evaluation additional | 45-60 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-8 | Designers, developers as users, and facilitation | 2-8 | Evaluation team, architects, and relevant stakeholders |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Assumption map, Test backlog, Risk ranking | 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 | Systems thinkingFramingStakeholders | ArchitectureEngineeringFeedbackValidationTasks | AssumptionsRiskExperimentsValidation | ArchitectureQualityRiskTradeoffsStakeholders |