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 two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Purposedifferent
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.In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.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.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.
Complexitydifferent
LowLowMediumLow
Timedifferent
15-45 min20–45 min1-3 Tage30 min Setup, dann laufend
Participantsdifferent
1-3Small cross-functional group1-41-3 maintaining, briefing for everyone
Formatdifferent
AsyncWorkshopWorkshop + asyncAsync
Outputdifferent
ADR File, Decision Log, RationaleRisk list, Mitigation plan, Assumption logArchitecture Views, Cross-view Notes, RationaleRAID Log, Status Report Source
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
RiskDecisionFailurePlanning
DocumentationStakeholdersArchitecture
RiskTrackingStakeholdersGovernance
Add more methods