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.

Selected:Decision JamA/B TestingRequest for CommentsARID (Active Reviews for Intermediate Designs)
Criterion
Paper illustration of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
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)
Purposedifferent
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.When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.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.
Complexitydifferent
LowHighMediumMedium
Timedifferent
60-90 min1-4 Wochen1-3 Wochen vom Draft bis zur Entscheidung2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
4-101-63-20 ReviewerDesigners, developers as users, and facilitation
Formatdifferent
WorkshopAsyncAsyncWorkshop + async
Outputdifferent
Problem Cluster, Prioritized Challenge, ExperimentExperiment results, Decision log, Learning 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 revisions
Tagsno overlap
FacilitationDecisionProblem solvingWorkshop
ExperimentsGrowthAnalyticsValidation
ArchitectureDecisionAsyncGovernance
ArchitectureEngineeringFeedbackValidationTasks
Add more methods