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 of Strategy Map with its method-specific working model.
Business Strategy
Strategy Map
Paper illustration for RAPID
Decision Making
RAPID
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
A Strategy Map translates strategy into a few connected objectives across perspectives such as finance, customers, processes, and learning. This makes visible which capabilities and activities are meant to drive which results.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.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
MediumMediumLowLow
Timedifferent
2-4 h workshop plus review45-90 min15-45 min1-2 Tage
Participantsdifferent
4-103-121-31-4
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Strategy Map, Objective Set, Cause-Effect HypothesesRAPID Role Map, Recommendation, Decision LogADR File, Decision Log, RationaleArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
AlignmentExecutionGoalsCausality
DecisionRolesGovernance
ArchitectureRationaleDocumentationGovernance
ArchitectureDocumentationCommunication
Add more methods