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
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Purposedifferent
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.With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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
HighMediumLowMedium
Timedifferent
Halber Tag1-2 h Setup, laufend1-2 Tage60-120 min
Participantsdifferent
5-2011-42-8
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Simulation Notes, Gaps List, Updated RunbooksAction Lists, Project List, Review RoutineArchitecture Document, Context View, Runtime View, Deployment ViewCommunication Canvas, Stakeholder Messages, Architecture Communication Plan
Tagsno overlap
ResilienceOperationsIncident
ProductivityPlanningTasksExecution
ArchitectureDocumentationCommunication
ArchitectureCommunicationStakeholdersCanvas
Add more methods