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 |  Facilitation Problem Framing Workshop |  Architecture arc42 |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
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. | 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. | 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 | 15-45 min | 60-120 min | 1-2 Tage | 60-90 min |
Participantsdifferent | 1-3 | 4-10 | 1-4 | 3-6 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions | Architecture Document, Context View, Runtime View, Deployment View | Salience Diagram, Strategy per Class |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | FacilitationAlignmentDiscovery | ArchitectureDocumentationCommunication | StakeholdersFacilitationAlignmentGovernance |