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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration of an IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
Paper illustration for DACI
Decision Making
DACI
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
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.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.In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated.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.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional1-3 h30-60 min1-3 Wochen vom Draft bis zur Entscheidung
Participantsdifferent
Designers, developers as users, and facilitation2-82-103-20 Reviewer
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsIssue Map, Positions, Argument NotesDACI Matrix, Decision Owner, Decision LogRFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
RationaleKnowledgeDecision
DecisionRolesGovernanceAlignment
ArchitectureDecisionAsyncGovernance
Add more methods