View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation Double Diamond |  Architecture arc42 |  Facilitation Stakeholder Salience Model |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | For complex problems with a fuzzy situation, the method cleanly separates search space and decision. It first creates breadth in understanding and then focus in elaboration. This brings open questions, problem definition, and solution path into a traceable movement. | 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. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | Wochen bis Monate | 1-2 Tage | 60-90 min | 15-45 min |
Participantsdifferent | 3-12 | 1-4 | 3-6 | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | Problem Statement, Solution Options, Prototypes, Deliverables per Phase | Architecture Document, Context View, Runtime View, Deployment View | Salience Diagram, Strategy per Class | ADR File, Decision Log, Rationale |
Tagsno overlap | ProcessDivergenceInnovation | ArchitectureDocumentationCommunication | StakeholdersFacilitationAlignmentGovernance | ArchitectureRationaleDocumentationGovernance |