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 two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
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.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.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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.
Complexitydifferent
MediumLowLowMedium
Timedifferent
1-3 h15-45 min30 min Setup, dann laufend60-120 min
Participantsdifferent
3-121-31-3 maintaining, briefing for everyone2-8
Formatdifferent
WorkshopAsyncAsyncWorkshop + async
Outputdifferent
Knowledge Map, Critical Knowledge Areas, Transfer PlanADR File, Decision Log, RationaleRAID Log, Status Report SourceCommunication Canvas, Stakeholder Messages, Architecture Communication Plan
Tagsno overlap
KnowledgeMappingRisk
ArchitectureRationaleDocumentationGovernance
RiskTrackingStakeholdersGovernance
ArchitectureCommunicationStakeholdersCanvas
Add more methods