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
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
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.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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.
Complexitydifferent
LowHighMediumMedium
Timedifferent
30 min Setup, dann laufendHalber Tag1-3 Tage60-120 min
Participantsdifferent
1-3 maintaining, briefing for everyone5-201-42-8
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
RAID Log, Status Report SourceSimulation Notes, Gaps List, Updated RunbooksArchitecture Views, Cross-view Notes, RationaleCommunication Canvas, Stakeholder Messages, Architecture Communication Plan
Tagsno overlap
RiskTrackingStakeholdersGovernance
ResilienceOperationsIncident
DocumentationStakeholdersArchitecture
ArchitectureCommunicationStakeholdersCanvas
Add more methods