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
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
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 single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning.For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly.
Complexitydifferent
MediumLowHighHigh
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung15-30 minPreparation, scenario analysis, and findings review; effort depends on scope1-6 Wochen
Participantsdifferent
3-20 Reviewer2-6Architecture experts and stakeholders for scenarios and weighting4-10
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsRoot cause notes, CountermeasuresDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan
Tagsno overlap
ArchitectureDecisionAsyncGovernance
Root causeIncidentLeanProblem solving
ArchitectureChangeAnalysisComparisonQuality
QualityProblem solvingRoot cause
Add more methods