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 two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
A paper-based illustration representing Design Sprint with its core stages and visible working result.
Innovation
Design Sprint
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
An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.When the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess.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
LowHighMediumMedium
Timedifferent
15-45 min4-5 Tage1-3 Wochen vom Draft bis zur Entscheidung2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
1-35-83-20 ReviewerDesigners, developers as users, and facilitation
Formatdifferent
AsyncWorkshopAsyncWorkshop + async
Outputdifferent
ADR File, Decision Log, RationalePrototype, Test Findings, Decision RationaleRFC 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
ArchitectureRationaleDocumentationGovernance
Design sprintPrototypeValidationInnovation
ArchitectureDecisionAsyncGovernance
ArchitectureEngineeringFeedbackValidationTasks
Add more methods