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 C4 Model | ![]() Facilitation Consensus Workshop | ![]() Facilitation Problem Framing Workshop | ![]() Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | 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 group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time. | When a team works on symptoms but the real question stays fuzzy, a Problem Framing Workshop sharpens the view of the right problem. It separates observation, interpretation, and target picture from each other. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 1-4 h | 1-3 h | 60-120 min | 1-2 Tage |
Participantsdifferent | 1-5 | 5-30 | 4-10 | 1-4 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Consensus Clusters, Theme Titles, Priority Areas | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ArchitectureCommunicationVisualization | FacilitationConsensusWorkshopAlignment | FacilitationAlignmentDiscovery | ArchitectureDocumentationCommunication |



