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) | ![]() Product Strategy KPI Tree | ![]() Business Strategy McKinsey 7S | ![]() Facilitation Alignment Mapping |
|---|---|---|---|---|
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 metrics across the organization drift apart, it arranges drivers and effects under one shared logic. It connects customer value, product logic, and decision priorities. The result is captured as a KPI tree and owner list. | 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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 90-180 min initial, dann laufend | 2-4 h | 1-2 h |
Participantsdifferent | Designers, developers as users, and facilitation | 3-8 | 3-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | KPI Tree, Owner List | 7S Assessment, Alignment Gaps, Change Actions | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | MetricsStrategyAlignmentMeasurement | OrganizationStrategyAlignmentChange | AlignmentStakeholdersStrategyFacilitation |



