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
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture 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.When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.
Complexitydifferent
LowHighLowLow
Timedifferent
1-2 Tage1-4 Wochen1-2 h1-2 h
Participantsdifferent
1-41-63-83-10
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewExperiment results, Decision log, Learning summaryInception Canvas, Risks, Goal List, Open QuestionsArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
ArchitectureDocumentationCommunication
ExperimentsGrowthAnalyticsValidation
AlignmentArchitectureCanvas
CanvasArchitectureAlignmentWorkshop
Add more methods