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 Problem Framing Workshop |  Architecture Architecture Decision Record |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
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 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. | 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. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 1-4 h | 60-120 min | 15-45 min | 60-90 min |
Participantsdifferent | 1-5 | 4-10 | 1-3 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions | ADR File, Decision Log, Rationale | Salience Diagram, Strategy per Class |
Tagsno overlap | ArchitectureCommunicationVisualization | FacilitationAlignmentDiscovery | ArchitectureRationaleDocumentationGovernance | StakeholdersFacilitationAlignmentGovernance |