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 of Product Vision Board with its method-specific working model.
Product Strategy
Product Vision Board
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
When a product needs a shared direction, it connects target audience, benefit, and business picture in a clear vision. It makes the envisioned future legible for the team.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.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.When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.
Complexitydifferent
LowLowLowMedium
Timedifferent
1-2 h1-2 h15-45 min1-2 h
Participantsdifferent
2-83-101-34-12
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop
Outputdifferent
Product Vision Board, Vision Statement, Assumptions and Validation QuestionsArchitecture Canvas, Goals, Constraints, Quality AttributesADR File, Decision Log, RationaleAlignment Map, Open Issues, Decision Questions
Tagsno overlap
VisionCanvasStrategyAlignment
CanvasArchitectureAlignmentWorkshop
ArchitectureRationaleDocumentationGovernance
AlignmentStakeholdersStrategyFacilitation
Add more methods