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
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
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
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 two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.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
LowHighMediumLow
Timedifferent
30 min Setup, dann laufend1-4 Wochen1-3 Tage15-45 min
Participantsdifferent
1-3 maintaining, briefing for everyone1-61-41-3
Formatdifferent
AsyncAsyncWorkshop + asyncAsync
Outputdifferent
RAID Log, Status Report SourceExperiment results, Decision log, Learning summaryArchitecture Views, Cross-view Notes, RationaleADR File, Decision Log, Rationale
Tagsno overlap
RiskTrackingStakeholdersGovernance
ExperimentsGrowthAnalyticsValidation
DocumentationStakeholdersArchitecture
ArchitectureRationaleDocumentationGovernance
Add more methods