View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Architecture Architecture Decision Record | ![]() Architecture C4 Model | ![]() Facilitation Open Space Technology | ![]() Facilitation Barcamp |
|---|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | When a complex topic does not yet have a fitting agenda, Open Space Technology hands topic ownership back to the participants. The format suits questions that only move forward when real interest determines the order. | 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. |
Complexitydifferent | Low | Low | High | Medium |
Timedifferent | 15-45 min | 1-4 h | 0.5-2 Tage | Halber Tag bis 2 Tage |
Participantsdifferent | 1-3 | 1-5 | 20-500+ | 15-200 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Context Diagram, Container Diagram, Component Diagram | Session Marketplace, Proceedings, Action Topics | Session Board, Session Notes, Community Learnings |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationVisualization | FacilitationLarge groupAutonomy | FacilitationLarge groupLearning |



