View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Business Strategy Balanced Scorecard | ![]() Architecture ARID (Active Reviews for Intermediate Designs) | ![]() Facilitation Stakeholder Mapping |
|---|---|---|---|
Purposedifferent | Balanced Scorecard translates strategy into a few interconnected perspectives and metrics. It holds impact, steering, and learning together in daily work instead of narrowing strategy down to financial figures. | 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 | High | Medium | Low |
Timedifferent | Halber Tag bis mehrere Wochen | 2–4 h review as a planning range; preparation and evaluation additional | 60–90 min |
Participantsdifferent | 4-12 | Designers, developers as users, and facilitation | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Balanced Scorecard, Strategic Measures, Initiative Map | 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 | StrategyMetricsExecution | ArchitectureEngineeringFeedbackValidationTasks | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






