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 of a Concept Map with concepts and labelled links
Knowledge Modeling
Concept Mapping
Paper illustration of an IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
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.Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly.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.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.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
1-2 Tage1-2 h1-3 h1-3 h
Participantsdifferent
1-41-82-81-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewConcept Map, Relationship Labels, Knowledge GapsIssue Map, Positions, Argument NotesArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
ArchitectureDocumentationCommunication
KnowledgeConceptsMappingSensemaking
RationaleKnowledgeDecision
SensemakingDecisionRationale
Add more methods