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)5-Minuten VC-CheckRequest for CommentsArchitecture Decision Record
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 Five-Minute VC Check with its method-specific working model.
Business Strategy
5-Minuten VC-Check
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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.The 5-Minute VC Check clarifies opportunities and strategic options at the earliest idea stage. It compares problem quality, customer willingness to pay, alternatives, differentiation, and market potential, and captures the result as a VC-check note, go/sharpen/park decision, and risk list.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.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.
Complexitydifferent
MediumLowMediumLow
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional5-15 min1-3 Wochen vom Draft bis zur Entscheidung15-45 min
Participantsdifferent
Designers, developers as users, and facilitation1-53-20 Reviewer1-3
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncAsync
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsVC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation stepRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsADR File, Decision Log, Rationale
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
StartupValidationCompetition
ArchitectureDecisionAsyncGovernance
ArchitectureRationaleDocumentationGovernance
Add more methods