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)Design SprintStakeholder MappingStakeholder Salience Model
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Innovation Design Sprint |  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 the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess. | 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 | High | Low | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 4-5 Tage | 60–90 min | 60-90 min |
Participantsdifferent | Designers, developers as users, and facilitation | 5-8 | 2-8 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Prototype, Test Findings, Decision Rationale | Stakeholder Map, Engagement Plan, Risk Notes | Salience Diagram, Strategy per Class |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | Design sprintPrototypeValidationInnovation | StakeholdersAlignmentFacilitationChange | StakeholdersFacilitationAlignmentGovernance |