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:ARID (Active Reviews for Intermediate Designs)Request for CommentsRiskiest Assumption TestAssumption Mapping
Criterion
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration of Riskiest Assumption Test with a method-specific labelled workspace.
Product Discovery
Riskiest Assumption 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
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.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.When an idea hinges on one critical unknown, it prioritizes testing that exact piece of uncertainty first. It separates problem, assumption, solution, and evidence. The result is captured as a prioritized list of assumptions, a test plan, and a result report.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.
Complexitysame
MediumMediumMediumMedium
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional1-3 Wochen vom Draft bis zur Entscheidung1-2 Wochen pro Iteration45-60 min
Participantsdifferent
Designers, developers as users, and facilitation3-20 Reviewer2-62-8
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsPrioritized Assumption List, Test Plan, Results ReportAssumption map, Test backlog, Risk ranking
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
ArchitectureDecisionAsyncGovernance
ExperimentsValidationDiscoveryAssumptions
AssumptionsRiskExperimentsValidation
Add more methods