View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordARID (Active Reviews for Intermediate Designs)Stakeholder Mapping
| Criterion |  Architecture Architecture Decision Record |  Architecture ARID (Active Reviews for Intermediate Designs) |  Facilitation Stakeholder Mapping |
|---|---|---|---|
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. | 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. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 15-45 min | 2–4 h review as a planning range; preparation and evaluation additional | 60–90 min |
Participantsdifferent | 1-3 | Designers, developers as users, and facilitation | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ArchitectureEngineeringFeedbackValidationTasks | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
