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 Problem Interview
Product Discovery
Problem Interview
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
When the picture of the problem still needs to become solid, it asks about real situations and consequences. It separates genuine suffering from mere interest in a solution.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.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.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
MediumMediumLowMedium
Timedifferent
30-60 min je Interview1-3 Tage1-2 h1-2 h
Participantsdifferent
5-12 Interviews1-43-104-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Problem Evidence, Risk Notes, Customer SegmentsArchitecture Views, Cross-view Notes, RationaleArchitecture Canvas, Goals, Constraints, Quality AttributesAlignment Map, Open Issues, Decision Questions
Tagsno overlap
DiscoveryInterviewsValidation
DocumentationStakeholdersArchitecture
CanvasArchitectureAlignmentWorkshop
AlignmentStakeholdersStrategyFacilitation
Add more methods