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
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture 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 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 C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes.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
MediumLowLowLow
Timedifferent
1-3 h1-2 h1-4 h1-2 h
Participantsdifferent
3-123-81-53-10
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Knowledge Map, Critical Knowledge Areas, Transfer PlanInception Canvas, Risks, Goal List, Open QuestionsContext Diagram, Container Diagram, Component DiagramArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
KnowledgeMappingRisk
AlignmentArchitectureCanvas
ArchitectureCommunicationVisualization
CanvasArchitectureAlignmentWorkshop
Add more methods