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 Futures Wheel with its method-specific working model.
Systems Thinking
Futures Wheel
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
The Futures Wheel helps explore the consequences of a decision, a trend, or a strategic move in a structured way. It makes visible which first, second, and third-order effects could arise from an event.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.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.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
60-120 min15-45 min30 min Setup, dann laufend1-2 Tage
Participantsdifferent
3-101-31-3 maintaining, briefing for everyone1-4
Formatdifferent
Workshop + asyncAsyncAsyncWorkshop + async
Outputdifferent
Futures Wheel, Consequence Chains, Strategic SignalsADR File, Decision Log, RationaleRAID Log, Status Report SourceArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
ForesightSystems thinkingSignals
ArchitectureRationaleDocumentationGovernance
RiskTrackingStakeholdersGovernance
ArchitectureDocumentationCommunication
Add more methods