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
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
A paper-based illustration representing Customer Journey Canvas with its core stages and visible working result.
UX Design
Customer Journey 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.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.When a journey needs to be understood across several phases, it arranges experience, touchpoints, and opportunities into one picture. It makes gaps and friction along the user path clear.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
LowLowMediumLow
Timedifferent
1-2 Tage1-2 h1-3 h1-2 h
Participantsdifferent
1-43-83-103-10
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewInception Canvas, Risks, Goal List, Open QuestionsCustomer Journey Canvas, Pain Points, Experience OpportunitiesArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
ArchitectureDocumentationCommunication
AlignmentArchitectureCanvas
JourneyCustomerService designCanvas
CanvasArchitectureAlignmentWorkshop
Add more methods