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 Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration for Change Analysis.
Operations
Change Analysis
Paper illustration for Current Reality Tree
Systems Thinking
Current Reality Tree
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise.A Current Reality Tree condenses many symptoms into a few causal chains. The method makes visible which core problems drive several negative effects at once.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.
Complexitydifferent
MediumMediumHighLow
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung45-120 min2-6 h15-45 min
Participantsdifferent
3-20 Reviewer2-63-81-3
Formatdifferent
AsyncWorkshop + asyncWorkshopAsync
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsChange Matrix, Cause Hypotheses, Validation Questions, Action ListCurrent Reality Tree, Core Problems, Intervention IdeasADR File, Decision Log, Rationale
Tagsno overlap
ArchitectureDecisionAsyncGovernance
ChangeRoot causeTroubleshootingComparison
Systems thinkingRoot causeConstraintsCausality
ArchitectureRationaleDocumentationGovernance
Add more methods