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 Failure Mode and Effects Analysis
Operations
Failure Mode and Effects 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 process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.
Complexitydifferent
MediumHigh
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung2-6 h
Participantsdifferent
3-20 Reviewer3-10
Formatdifferent
AsyncWorkshop
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
ArchitectureDecisionAsyncGovernance
RiskQualityOperationsRoot cause
Add more methods

Often compared together

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

Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration for Kepner-Tregoe
Operations
Kepner-Tregoe
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