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
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
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.In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic.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
LowHighLowMedium
Timedifferent
30 min Setup, dann laufendHalber Tag15-45 min1-3 Tage
Participantsdifferent
1-3 maintaining, briefing for everyone5-201-31-4
Formatdifferent
AsyncWorkshopAsyncWorkshop + async
Outputdifferent
RAID Log, Status Report SourceSimulation Notes, Gaps List, Updated RunbooksADR File, Decision Log, RationaleArchitecture Views, Cross-view Notes, Rationale
Tagsno overlap
RiskTrackingStakeholdersGovernance
ResilienceOperationsIncident
ArchitectureRationaleDocumentationGovernance
DocumentationStakeholdersArchitecture
Add more methods