View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Barcamp |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations 5 Whys |
|---|---|---|---|
Purposedifferent | When many people can contribute knowledge and the flow should stay open, Barcamp provides a framework for self-organized sessions. The format channels energy without defining the content too narrowly in advance. | 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. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Medium | High | Low |
Timedifferent | Halber Tag bis 2 Tage | Several meetings plus preparation and analysis; total effort depends on scope | 15-30 min |
Participantsdifferent | 15-200 | Evaluation team, architects, and relevant stakeholders | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Session Board, Session Notes, Community Learnings | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Root cause notes, Countermeasures |
Tagsno overlap | FacilitationLarge groupLearning | ArchitectureQualityRiskTradeoffsStakeholders | Root causeIncidentLeanProblem solving |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
