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) |  Business Strategy McKinsey 7S |  Facilitation Stakeholder Salience Model |
|---|---|---|---|
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. | McKinsey 7S checks whether Strategy, Structure, Systems, Shared Values, Skills, Style, and Staff fit together. Organizational misalignments become visible across multiple levers as a result. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 2-4 h | 60-90 min |
Participantsdifferent | Designers, developers as users, and facilitation | 3-12 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | 7S Assessment, Alignment Gaps, Change Actions | Salience Diagram, Strategy per Class |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | OrganizationStrategyAlignmentChange | StakeholdersFacilitationAlignmentGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
