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 Teach-back.
Knowledge Modeling
Teach-back
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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
Teach-back checks whether an explanation actually got through to the other person. The method makes misunderstandings visible early and strengthens shared understanding in advisory and learning situations.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.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.
Complexitysame
LowLowLowLow
Timedifferent
5-20 min30 min Setup, dann laufend1-2 Tage15-45 min
Participantsdifferent
2-81-3 maintaining, briefing for everyone1-41-3
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncAsync
Outputdifferent
Understanding Check, Clarification Notes, Learning GapsRAID Log, Status Report SourceArchitecture Document, Context View, Runtime View, Deployment ViewADR File, Decision Log, Rationale
Tagsno overlap
LearningUnderstandingCommunication
RiskTrackingStakeholdersGovernance
ArchitectureDocumentationCommunication
ArchitectureRationaleDocumentationGovernance
Add more methods