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 for Accountability Ladder
Operations
Accountability Ladder
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Purposedifferent
With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on.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.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 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.
Complexitysame
LowLowLowLow
Timedifferent
20-45 min1-2 h1-2 Tage1-2 h
Participantsdifferent
1-83-101-43-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Ownership Reflection, Action Commitment, Coaching NotesArchitecture Canvas, Goals, Constraints, Quality AttributesArchitecture Document, Context View, Runtime View, Deployment ViewInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
ResponsibilityLeadershipTeam
CanvasArchitectureAlignmentWorkshop
ArchitectureDocumentationCommunication
AlignmentArchitectureCanvas
Add more methods