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
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration of a Concept Map with concepts and labelled links
Knowledge Modeling
Concept Mapping
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.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.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.
Complexitydifferent
MediumHighLowMedium
Timedifferent
1-3 h45-90 min15-45 min1-2 h
Participantsdifferent
3-123-101-31-8
Formatdifferent
WorkshopWorkshopAsyncWorkshop + async
Outputdifferent
Knowledge Map, Critical Knowledge Areas, Transfer PlanRanked Backlog, Cost-of-Delay AssumptionsADR File, Decision Log, RationaleConcept Map, Relationship Labels, Knowledge Gaps
Tagsno overlap
KnowledgeMappingRisk
LeanEconomicsSequencePrioritization
ArchitectureRationaleDocumentationGovernance
KnowledgeConceptsMappingSensemaking
Add more methods