methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
Paper illustration for Fake Door Test
Product Discovery
Fake Door Test
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.When demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small.
Complexitydifferent
LowLowLowMedium
Timedifferent
1-2 Tage15-45 min1-5 Tage1-5 Tage
Participantsdifferent
1-41-3NutzertrafficNutzertraffic
Formatdifferent
Workshop + asyncAsyncAsyncAsync
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewADR File, Decision Log, RationaleInterest Metrics, Conversion Signal, Learning NoteClick Data, Interest Signal, Learning Decision
Tagsno overlap
ArchitectureDocumentationCommunication
ArchitectureRationaleDocumentationGovernance
ValidationExperimentsDemandGrowth
ValidationExperimentsDemandDiscovery
Add more methods