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 |  Product Discovery Outcome-Driven Innovation |  Decision Making Decision Rights Mapping |  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. | Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. | 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 | High | Medium | Low |
Timedifferent | 1-4 h | Mehrere Wochen | 90-180 min | 1-2 Tage |
Participantsdifferent | 1-5 | 2-6 researchers plus sample | 4-12 | 1-4 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Decision Rights Matrix, Agreement | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ArchitectureCommunicationVisualization | OutcomesInnovationResearchQuantitative | DecisionGovernanceAlignmentResponsibility | ArchitectureDocumentationCommunication |