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:Red TeamingARID (Active Reviews for Intermediate Designs)Request for CommentsAssumption Mapping
Criterion
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
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 a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Purposedifferent
For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments.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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.
Complexitydifferent
HighMediumMediumMedium
Timedifferent
1-4 h2–4 h review as a planning range; preparation and evaluation additional1-3 Wochen vom Draft bis zur Entscheidung45-60 min
Participantsdifferent
3-8Designers, developers as users, and facilitation3-20 Reviewer2-8
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Challenge Findings, Risk Register, Mitigation PlanPrioritized 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 ticketsAssumption map, Test backlog, Risk ranking
Tagsno overlap
RiskDecisionSensemaking
ArchitectureEngineeringFeedbackValidationTasks
ArchitectureDecisionAsyncGovernance
AssumptionsRiskExperimentsValidation
Add more methods