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 an IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
Paper illustration for Risk Storming.
Architecture
Risk Storming
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)
Purposedifferent
IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.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.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
1-3 h60-90 min1-3 Wochen vom Draft bis zur Entscheidung2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
2-84-123-20 ReviewerDesigners, developers as users, and facilitation
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop + async
Outputdifferent
Issue Map, Positions, Argument NotesAnnotated Diagram, Prioritized Risk List, Action BacklogRFC 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 revisions
Tagsno overlap
RationaleKnowledgeDecision
RiskArchitectureWorkshopValidation
ArchitectureDecisionAsyncGovernance
ArchitectureEngineeringFeedbackValidationTasks
Add more methods