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 for Alignment Mapping.
Facilitation
Alignment Mapping
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.When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.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
LowMediumLowMedium
Timedifferent
1-2 Tage1-2 h1-5 Tage1-5 Tage
Participantsdifferent
1-44-12NutzertrafficNutzertraffic
Formatdifferent
Workshop + asyncWorkshopAsyncAsync
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewAlignment Map, Open Issues, Decision QuestionsInterest Metrics, Conversion Signal, Learning NoteClick Data, Interest Signal, Learning Decision
Tagsno overlap
ArchitectureDocumentationCommunication
AlignmentStakeholdersStrategyFacilitation
ValidationExperimentsDemandGrowth
ValidationExperimentsDemandDiscovery
Add more methods