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
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
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.After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement.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.The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.
Complexitydifferent
LowLowMediumLow
Timedifferent
1-2 h20-45 minAs needed1-2 h
Participantsdifferent
3-103-124-153-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Architecture Canvas, Goals, Constraints, Quality AttributesLessons learned, Action items, Event summaryIncident Log, Action Tracker, Stakeholder UpdatesInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
CanvasArchitectureAlignmentWorkshop
LearningOperationsImprovement
IncidentOperationsReliability
AlignmentArchitectureCanvas
Add more methods