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 arc42 | ![]() Architecture Architecture Decision Record | ![]() Product Discovery Smoke Test | ![]() Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 1-2 Tage | 15-45 min | 1-5 Tage | 60-120 min |
Participantsdifferent | 1-4 | 1-3 | Nutzertraffic | 2-8 |
Formatdifferent | Workshop + async | Async | Async | Workshop + async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | ADR File, Decision Log, Rationale | Interest Metrics, Conversion Signal, Learning Note | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | ArchitectureDocumentationCommunication | ArchitectureRationaleDocumentationGovernance | ValidationExperimentsDemandGrowth | ArchitectureCommunicationStakeholdersCanvas |



