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
EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication 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.When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views.ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.
Complexitysame
MediumMediumMediumMedium
Timedifferent
1-2 h2-8 h2–4 h review as a planning range; preparation and evaluation additional60-120 min
Participantsdifferent
2-85-12Designers, developers as users, and facilitation2-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Product Canvas, Product Assumptions, Scope NotesEvent Timeline, Ubiquitous Language, Boundaries, Open QuestionsPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsCommunication Canvas, Stakeholder Messages, Architecture Communication Plan
Tagsno overlap
CanvasDiscoveryScope
Domain-Driven DesignEventsDiscoveryWorkshop
ArchitectureEngineeringFeedbackValidationTasks
ArchitectureCommunicationStakeholdersCanvas
Add more methods