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 Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
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 problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie.
Complexitysame
MediumMedium
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung1-3 h
Participantsdifferent
3-20 Reviewer2-8
Formatdifferent
AsyncWorkshop
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsCause Tree, Evidence Notes, Countermeasures
Tagsno overlap
ArchitectureDecisionAsyncGovernance
Root causeTreeIncidentQuality
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record