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 fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
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 a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.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
LowLowMediumLow
Timedifferent
30 min Setup, dann laufend30-60 min1-3 Tage15-45 min
Participantsdifferent
1-3 maintaining, briefing for everyone2-81-41-3
Formatdifferent
AsyncWorkshopWorkshop + asyncAsync
Outputdifferent
RAID Log, Status Report SourceFishbone Diagram, Cause Categories, Investigation BacklogArchitecture Views, Cross-view Notes, RationaleADR File, Decision Log, Rationale
Tagsno overlap
RiskTrackingStakeholdersGovernance
Root causeQualityOperations
DocumentationStakeholdersArchitecture
ArchitectureRationaleDocumentationGovernance
Add more methods