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
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
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.Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic.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.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
MediumMediumLowLow
Timedifferent
1-2 h2-6 h15-45 min1-2 h
Participantsdifferent
2-82-81-33-8
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop
Outputdifferent
Product Canvas, Product Assumptions, Scope NotesEvent Model, UI Flow, Commands, Read ModelsADR File, Decision Log, RationaleInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
CanvasDiscoveryScope
EventsBlueprintDomain-Driven DesignBehavior
ArchitectureRationaleDocumentationGovernance
AlignmentArchitectureCanvas
Add more methods