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
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Paper illustration of an IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
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.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.When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.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.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
1-2 Tage1-3 h1-3 h1-3 h
Participantsdifferent
1-43-121-82-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewKnowledge Map, Critical Knowledge Areas, Transfer PlanArgument Map, Evidence Gaps, Decision RationaleIssue Map, Positions, Argument Notes
Tagsno overlap
ArchitectureDocumentationCommunication
KnowledgeMappingRisk
SensemakingDecisionRationale
RationaleKnowledgeDecision
Add more methods