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
A paper-based illustration representing WSJF with its core stages and visible working result.
Agile
WSJF
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
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 many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together.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
MediumHighLowLow
Timedifferent
1-3 h45-90 min1-2 Tage15-45 min
Participantsdifferent
3-123-101-41-3
Formatdifferent
WorkshopWorkshopWorkshop + asyncAsync
Outputdifferent
Knowledge Map, Critical Knowledge Areas, Transfer PlanRanked Backlog, Cost-of-Delay AssumptionsArchitecture Document, Context View, Runtime View, Deployment ViewADR File, Decision Log, Rationale
Tagsno overlap
KnowledgeMappingRisk
LeanEconomicsSequencePrioritization
ArchitectureDocumentationCommunication
ArchitectureRationaleDocumentationGovernance
Add more methods