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
Surveys method illustration showing its working structure
UX Research
Surveys
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration for Risk Storming.
Architecture
Risk Storming
Purposedifferent
When a topic needs to be validated broadly and many people can answer the same question, surveys gather structured feedback in a scalable form. Answers become comparable and segmentable instead of remaining merely anecdotal.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 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.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.
Complexitydifferent
MediumLowLowLow
Timedifferent
3-14 Tage15-45 min1-2 h60-90 min
Participantsdifferent
50+1-33-104-12
Formatdifferent
AsyncAsyncWorkshopWorkshop
Outputdifferent
Survey Results, Charts, Segment InsightsADR File, Decision Log, RationaleArchitecture Canvas, Goals, Constraints, Quality AttributesAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
QuantitativeResearchValidation
ArchitectureRationaleDocumentationGovernance
CanvasArchitectureAlignmentWorkshop
RiskArchitectureWorkshopValidation
Add more methods