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
A paper-based illustration representing Product Canvas with its core stages and visible working result.
Product Strategy
Product Canvas
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Purposedifferent
When product goal and feature scope don't yet fit cleanly together, it creates a shared working picture. It connects need, core features, and assumptions into a solid starting point.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.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.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
1-2 h60-120 min15-45 min1-3 Tage
Participantsdifferent
2-82-81-31-4
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Product Canvas, Product Assumptions, Scope NotesCommunication Canvas, Stakeholder Messages, Architecture Communication PlanADR File, Decision Log, RationaleArchitecture Views, Cross-view Notes, Rationale
Tagsno overlap
CanvasDiscoveryScope
ArchitectureCommunicationStakeholdersCanvas
ArchitectureRationaleDocumentationGovernance
DocumentationStakeholdersArchitecture
Add more methods