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 for Kaizen Event.
Operations
Kaizen Event
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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 tightly scoped process segment with noticeable waste, the method bundles shared energy for change. It suits situations that call for fast learning loops and visible adjustments.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.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
1-2 h0.5-5 Tage15-45 min1-2 Tage
Participantsdifferent
3-104-101-31-4
Formatdifferent
WorkshopWorkshopAsyncWorkshop + async
Outputdifferent
Architecture Canvas, Goals, Constraints, Quality AttributesKaizen Charter, Waste List, Improvement Experiments, Standard Work UpdateADR File, Decision Log, RationaleArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
CanvasArchitectureAlignmentWorkshop
LeanContinuous improvementOperations
ArchitectureRationaleDocumentationGovernance
ArchitectureDocumentationCommunication
Add more methods