View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Product Discovery Dual-Track Agile | ![]() Architecture arc42 | ![]() Decision Making Assumption Surfacing | ![]() Architecture C4 Model |
|---|---|---|---|---|
Purposedifferent | When uncertainty and delivery run in parallel, it separates learning work from implementation while keeping both connected. It prevents unvalidated ideas from falling directly into the delivery stream. | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | Laufend, Wochen bis Monate | 1-2 Tage | 45-90 min | 1-4 h |
Participantsdifferent | 4-10 | 1-4 | 2-8 | 1-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Discovery Backlog, Delivery Backlog, Experiment-Ergebnisse, Validierte Stories | Architecture Document, Context View, Runtime View, Deployment View | Assumption List, Critical Assumptions, Learning Plan | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | AgileDiscoveryDelivery | ArchitectureDocumentationCommunication | AssumptionsRiskDecisionDiscovery | ArchitectureCommunicationVisualization |



