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 a branching category tree with a highlighted search path and possible dead ends.
UX Research
Tree Testing
Paper illustration of an IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
When a navigation exists but search paths still fail, tree testing checks findability without visual distraction. The method shows whether labels, levels, and paths really lead to the intended destination.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.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.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-2 Tage1-3 h1-2 Tage15-45 min
Participantsdifferent
Based on research question2-81-41-3
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Findability Metrics, Path Analysis, Revised IAIssue Map, Positions, Argument NotesArchitecture Document, Context View, Runtime View, Deployment ViewADR File, Decision Log, Rationale
Tagsno overlap
Information architectureNavigationFindability
RationaleKnowledgeDecision
ArchitectureDocumentationCommunication
ArchitectureRationaleDocumentationGovernance
Add more methods