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 for Fault Isolation.
Engineering
Fault Isolation
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Purposedifferent
In technical failures, the visible symptom often gets mixed up with the actual cause. Fault Isolation narrows the fault space and progressively reduces which part of the system is truly affected.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.When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer.ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
30-180 min1-3 Wochen vom Draft bis zur Entscheidung60-90 min2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
1-63-20 Reviewer4-10Designers, developers as users, and facilitation
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault AreaRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsProblem Cluster, Prioritized Challenge, ExperimentPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
TroubleshootingDiagnosisEngineering
ArchitectureDecisionAsyncGovernance
FacilitationDecisionProblem solvingWorkshop
ArchitectureEngineeringFeedbackValidationTasks
Add more methods