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 of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Purposedifferent
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.When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.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.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.
Complexitydifferent
LowMediumLowMedium
Timedifferent
30 min Setup, dann laufend1-3 h15-45 min1-3 Tage
Participantsdifferent
1-3 maintaining, briefing for everyone1-81-31-4
Formatdifferent
AsyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
RAID Log, Status Report SourceArgument Map, Evidence Gaps, Decision RationaleADR File, Decision Log, RationaleArchitecture Views, Cross-view Notes, Rationale
Tagsno overlap
RiskTrackingStakeholdersGovernance
SensemakingDecisionRationale
ArchitectureRationaleDocumentationGovernance
DocumentationStakeholdersArchitecture
Add more methods