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 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 for Smoke Test.
Product Discovery
Smoke Test
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
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.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 demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung2–4 h review as a planning range; preparation and evaluation additional1-5 Tage45-60 min
Participantsdifferent
3-20 ReviewerDesigners, developers as users, and facilitationNutzertraffic2-8
Formatdifferent
AsyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
RFC 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 revisionsInterest Metrics, Conversion Signal, Learning NoteAssumption map, Test backlog, Risk ranking
Tagsno overlap
ArchitectureDecisionAsyncGovernance
ArchitectureEngineeringFeedbackValidationTasks
ValidationExperimentsDemandGrowth
AssumptionsRiskExperimentsValidation
Add more methods