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
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration for RAPID
Decision Making
RAPID
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Purposedifferent
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.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.In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels.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.
Complexitydifferent
HighMediumMediumMedium
Timedifferent
1-4 Wochen2–4 h review as a planning range; preparation and evaluation additional45-90 min1-3 Wochen vom Draft bis zur Entscheidung
Participantsdifferent
1-6Designers, developers as users, and facilitation3-123-20 Reviewer
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Experiment results, Decision log, Learning summaryPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsRAPID Role Map, Recommendation, Decision LogRFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets
Tagsno overlap
ExperimentsGrowthAnalyticsValidation
ArchitectureEngineeringFeedbackValidationTasks
DecisionRolesGovernance
ArchitectureDecisionAsyncGovernance
Add more methods