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 Risk Storming.
Architecture
Risk Storming
Surveys method illustration showing its working structure
UX Research
Surveys
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Purposedifferent
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.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.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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.
Complexitydifferent
LowMediumLowMedium
Timedifferent
60-90 min3-14 Tage1-2 h60-120 min
Participantsdifferent
4-1250+3-102-8
Formatdifferent
WorkshopAsyncWorkshopWorkshop + async
Outputdifferent
Annotated Diagram, Prioritized Risk List, Action BacklogSurvey Results, Charts, Segment InsightsArchitecture Canvas, Goals, Constraints, Quality AttributesCommunication Canvas, Stakeholder Messages, Architecture Communication Plan
Tagsno overlap
RiskArchitectureWorkshopValidation
QuantitativeResearchValidation
CanvasArchitectureAlignmentWorkshop
ArchitectureCommunicationStakeholdersCanvas
Add more methods