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 Request for Comments |  Architecture C4 Model |  Architecture arc42 |
|---|---|---|---|---|
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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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. | 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 | Medium | Medium | Low | Low |
Timedifferent | Wochen bis Monate | 1-3 Wochen vom Draft bis zur Entscheidung | 1-4 h | 1-2 Tage |
Participantsdifferent | 3-12 | 3-20 Reviewer | 1-5 | 1-4 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Problem Statement, Solution Options, Prototypes, Deliverables per Phase | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Context Diagram, Container Diagram, Component Diagram | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ProcessDivergenceInnovation | ArchitectureDecisionAsyncGovernance | ArchitectureCommunicationVisualization | ArchitectureDocumentationCommunication |