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 Hypothesis-Driven Troubleshooting.
Engineering
Hypothesis-Driven Troubleshooting
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
Purposedifferent
When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable.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.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.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.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
30-240 min1-3 Wochen vom Draft bis zur Entscheidung2–4 h review as a planning range; preparation and evaluation additional60-90 min
Participantsdifferent
1-63-20 ReviewerDesigners, developers as users, and facilitation4-10
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop
Outputdifferent
Hypothesis Log, Test Plan, Evidence Notes, Diagnosis SummaryRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsProblem Cluster, Prioritized Challenge, Experiment
Tagsno overlap
TroubleshootingProblem solvingDiagnosis
ArchitectureDecisionAsyncGovernance
ArchitectureEngineeringFeedbackValidationTasks
FacilitationDecisionProblem solvingWorkshop
Add more methods