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
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.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
MediumLowMediumLow
Timedifferent
1-3 h30 min Setup, dann laufend1-3 Tage15-45 min
Participantsdifferent
3-121-3 maintaining, briefing for everyone1-41-3
Formatdifferent
WorkshopAsyncWorkshop + asyncAsync
Outputdifferent
Knowledge Map, Critical Knowledge Areas, Transfer PlanRAID Log, Status Report SourceArchitecture Views, Cross-view Notes, RationaleADR File, Decision Log, Rationale
Tagsno overlap
KnowledgeMappingRisk
RiskTrackingStakeholdersGovernance
DocumentationStakeholdersArchitecture
ArchitectureRationaleDocumentationGovernance
Add more methods