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
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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
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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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.
Complexitydifferent
LowLowMediumLow
Timedifferent
60-90 min1-2 Tage3-14 Tage15-45 min
Participantsdifferent
4-121-450+1-3
Formatdifferent
WorkshopWorkshop + asyncAsyncAsync
Outputdifferent
Annotated Diagram, Prioritized Risk List, Action BacklogArchitecture Document, Context View, Runtime View, Deployment ViewSurvey Results, Charts, Segment InsightsADR File, Decision Log, Rationale
Tagsno overlap
RiskArchitectureWorkshopValidation
ArchitectureDocumentationCommunication
QuantitativeResearchValidation
ArchitectureRationaleDocumentationGovernance
Add more methods