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 RAPID
Decision Making
RAPID
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.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.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
MediumLowLowLow
Timedifferent
45-90 min30 min Setup, dann laufend15-45 min1-2 Tage
Participantsdifferent
3-121-3 maintaining, briefing for everyone1-31-4
Formatdifferent
Workshop + asyncAsyncAsyncWorkshop + async
Outputdifferent
RAPID Role Map, Recommendation, Decision LogRAID Log, Status Report SourceADR File, Decision Log, RationaleArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
DecisionRolesGovernance
RiskTrackingStakeholdersGovernance
ArchitectureRationaleDocumentationGovernance
ArchitectureDocumentationCommunication
Add more methods