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 for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
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
Purposedifferent
Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.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.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.
Complexitydifferent
MediumLowLowLow
Timedifferent
1-3 h1-2 h1-2 Tage1-2 h
Participantsdifferent
3-123-101-43-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Knowledge Map, Critical Knowledge Areas, Transfer PlanArchitecture Canvas, Goals, Constraints, Quality AttributesArchitecture Document, Context View, Runtime View, Deployment ViewInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
KnowledgeMappingRisk
CanvasArchitectureAlignmentWorkshop
ArchitectureDocumentationCommunication
AlignmentArchitectureCanvas
Add more methods