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)Solution InterviewStakeholder MappingStakeholder Salience Model
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Product Discovery Solution Interview |  Facilitation Stakeholder Mapping |  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. | When a solution idea is already on the table, it checks how it is understood and evaluated. It looks for resonance, objections, and missing fit early in the conversation. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 30-60 min je Interview | 60–90 min | 60-90 min |
Participantsdifferent | Designers, developers as users, and facilitation | 5-10 Interviews | 2-8 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Solution Feedback, Objection List, Validation Notes | Stakeholder Map, Engagement Plan, Risk Notes | Salience Diagram, Strategy per Class |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | ValidationInterviewsPrototype | StakeholdersAlignmentFacilitationChange | StakeholdersFacilitationAlignmentGovernance |