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)Force Field AnalysisRequest 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 the Force Field Analysis working structure.
Decision Making
Force Field Analysis
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.In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving.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 additional45-90 min1-3 Wochen vom Draft bis zur Entscheidung15-45 min
Participantsdifferent
Designers, developers as users, and facilitation3-123-20 Reviewer1-3
Formatdifferent
Workshop + asyncWorkshopAsyncAsync
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsForce Field Map, Change Levers, Risk NotesRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsADR File, Decision Log, Rationale
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
ChangeDecisionStrategy
ArchitectureDecisionAsyncGovernance
ArchitectureRationaleDocumentationGovernance
Add more methods