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:Request for CommentsAnsoff MatrixARID (Active Reviews for Intermediate Designs)A/B Testing
Criterion
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration of a two-by-two Ansoff Matrix with four growth directions
Business Strategy
Ansoff Matrix
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
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.The Ansoff Matrix organizes growth options by market and product relation. It helps weigh expansion, diversification, and adaptation cleanly against each other.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 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.
Complexitydifferent
MediumLowMediumHigh
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung45-90 min2–4 h review as a planning range; preparation and evaluation additional1-4 Wochen
Participantsdifferent
3-20 Reviewer2-8Designers, developers as users, and facilitation1-6
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsAnsoff Matrix, Growth Options, Risk NotesPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsExperiment results, Decision log, Learning summary
Tagsno overlap
ArchitectureDecisionAsyncGovernance
GrowthStrategyMarketPortfolio
ArchitectureEngineeringFeedbackValidationTasks
ExperimentsGrowthAnalyticsValidation
Add more methods