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
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Purposedifferent
The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.
Complexitydifferent
LowMediumMedium
Timedifferent
1-2 h45-90 minAs needed
Participantsdifferent
3-102-54-15
Formatdifferent
WorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Architecture Canvas, Goals, Constraints, Quality AttributesA3 Report, Action Plan, Root Cause AnalysisIncident Log, Action Tracker, Stakeholder Updates
Tagsno overlap
CanvasArchitectureAlignmentWorkshop
LeanProblem solvingCoachingOperations
IncidentOperationsReliability
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem