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 AnalysisArchitecture Decision Record
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Decision Making Force Field Analysis |  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 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 | Medium | Low | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 45-90 min | 15-45 min |
Participantsdifferent | Designers, developers as users, and facilitation | 3-12 | 1-3 |
Formatdifferent | Workshop + async | Workshop | Async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Force Field Map, Change Levers, Risk Notes | ADR File, Decision Log, Rationale |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | ChangeDecisionStrategy | ArchitectureRationaleDocumentationGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
