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 of an IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus.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.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.
Complexitydifferent
MediumMediumLowLow
Timedifferent
1-3 h1-3 h1-2 h15-45 min
Participantsdifferent
2-83-123-101-3
Formatdifferent
Workshop + asyncWorkshopWorkshopAsync
Outputdifferent
Issue Map, Positions, Argument NotesKnowledge Map, Critical Knowledge Areas, Transfer PlanArchitecture Canvas, Goals, Constraints, Quality AttributesADR File, Decision Log, Rationale
Tagsno overlap
RationaleKnowledgeDecision
KnowledgeMappingRisk
CanvasArchitectureAlignmentWorkshop
ArchitectureRationaleDocumentationGovernance
Add more methods