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 Product Canvas with its core stages and visible working result.
Product Strategy
Product Canvas
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
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Purposedifferent
When product goal and feature scope don't yet fit cleanly together, it creates a shared working picture. It connects need, core features, and assumptions into a solid starting point.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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.
Complexitydifferent
MediumLowLowMedium
Timedifferent
1-2 h1-2 Tage20-35 min60-120 min
Participantsdifferent
2-81-41-52-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Product Canvas, Product Assumptions, Scope NotesArchitecture Document, Context View, Runtime View, Deployment ViewTest Card with a pre-set thresholdCommunication Canvas, Stakeholder Messages, Architecture Communication Plan
Tagsno overlap
CanvasDiscoveryScope
ArchitectureDocumentationCommunication
ExperimentsValidationDiscoveryHypothesis
ArchitectureCommunicationStakeholdersCanvas
Add more methods