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 Architecture Communication Canvas | ![]() Decision Making Assumption Surfacing | ![]() Architecture arc42 |
|---|---|---|---|---|
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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. | 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 | Laufend, Wochen bis Monate | 60-120 min | 45-90 min | 1-2 Tage |
Participantsdifferent | 4-10 | 2-8 | 2-8 | 1-4 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Discovery Backlog, Delivery Backlog, Experiment-Ergebnisse, Validierte Stories | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Assumption List, Critical Assumptions, Learning Plan | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | AgileDiscoveryDelivery | ArchitectureCommunicationStakeholdersCanvas | AssumptionsRiskDecisionDiscovery | ArchitectureDocumentationCommunication |



