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
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Surveys method illustration showing its working structure
UX Research
Surveys
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.When a topic needs to be validated broadly and many people can answer the same question, surveys gather structured feedback in a scalable form. Answers become comparable and segmentable instead of remaining merely anecdotal.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
LowMediumMediumLow
Timedifferent
15-45 min45-60 min3-14 Tage1-2 Tage
Participantsdifferent
1-32-850+1-4
Formatdifferent
AsyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
ADR File, Decision Log, RationaleAssumption map, Test backlog, Risk rankingSurvey Results, Charts, Segment InsightsArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
AssumptionsRiskExperimentsValidation
QuantitativeResearchValidation
ArchitectureDocumentationCommunication
Add more methods