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
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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.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.With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory.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.
Complexitydifferent
LowLowMediumLow
Timedifferent
60-90 min15-45 min1-2 h Setup, laufend1-2 Tage
Participantsdifferent
4-121-311-4
Formatdifferent
WorkshopAsyncAsyncWorkshop + async
Outputdifferent
Annotated Diagram, Prioritized Risk List, Action BacklogADR File, Decision Log, RationaleAction Lists, Project List, Review RoutineArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
RiskArchitectureWorkshopValidation
ArchitectureRationaleDocumentationGovernance
ProductivityPlanningTasksExecution
ArchitectureDocumentationCommunication
Add more methods