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 a Test Card with four fields for hypothesis, test, metric, and success threshold.
Product Discovery
Test Card
Paper illustration of DIBB with its method-specific working model.
Product Strategy
DIBB
Paper illustration of Experiment Canvas with a method-specific labelled workspace.
Product Discovery
Experiment 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.The Test Card turns a critical assumption into a testable claim and specifies in advance which result counts as success.DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report.When experiments become unreadable after the fact, it arranges hypothesis, signal, and learning goal on a single canvas. It separates problem, assumption, solution, and evidence. The result is captured as a Completed Experiment Canvas and a Success Metric.
Complexitysame
LowLowLowLow
Timedifferent
1-2 Tage20-35 min1-2 h30-60 min
Participantsdifferent
1-41-52-81-5
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewTest Card with a pre-set thresholdDIBB document, Belief list, Bet list, Learning reportCompleted Experiment Canvas, Success Metric
Tagsno overlap
ArchitectureDocumentationCommunication
ExperimentsValidationDiscoveryHypothesis
StrategyDecisionAssumptionsHypothesis
ExperimentsValidationDiscoveryHypothesis
Add more methods