View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Architecture ARID (Active Reviews for Intermediate Designs) | ![]() Architecture Request for Comments | ![]() Decision Making Cynefin Workshop |
|---|---|---|---|
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. | 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. | When problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 1-3 Wochen vom Draft bis zur Entscheidung | 60-180 min |
Participantsdifferent | Designers, developers as users, and facilitation | 3-20 Reviewer | 4-20 |
Formatdifferent | Workshop + async | Async | Workshop |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Cynefin Map, Domain-specific Actions, Sensemaking Notes |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | ArchitectureDecisionAsyncGovernance | ComplexitySensemakingDecision |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






