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 for Time Blocking
Operations
Time Blocking
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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.With a calendar that grows on request, the method makes available time explicit again. It combines appointments, focus work, and buffer into a more realistic day structure.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.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.
Complexitysame
LowLowLowLow
Timedifferent
60-90 min15-30 min Planung, laufend1-2 Tage15-45 min
Participantsdifferent
4-1211-41-3
Formatdifferent
WorkshopAsyncWorkshop + asyncAsync
Outputdifferent
Annotated Diagram, Prioritized Risk List, Action BacklogBlocked Calendar, Capacity View, Focus PlanArchitecture Document, Context View, Runtime View, Deployment ViewADR File, Decision Log, Rationale
Tagsno overlap
RiskArchitectureWorkshopValidation
PlanningTime managementFocus
ArchitectureDocumentationCommunication
ArchitectureRationaleDocumentationGovernance
Add more methods